Remote PC

Last Modified: Aug 16, 2017 @ 5:31 pm

Navigation

ūüí° = Recently Updated

Remote PC Catalog

  1. In Citrix Studio, create a Machine Catalog.
  2. In the Introduction page, click Next.
  3. In the Operating System page, select Remote PC Access, and click Next.
  4. In the Machine Accounts page, click Add OUs.
  5. Browse to an OU containing office PCs. Check the box next to Include subfolders, and click OK.
  6. Then click Next.
  7. Name the catalog Remote PC or similar, and then click Finish.
  8. After the Catalog is created, you can Edit Machine Catalog to add more OUs.

  9. Or explicitly add individual machines to the Catalog.

Remote PC Delivery Group

  1. Create a Delivery Group.
  2. In the Introduction page, click Next.
  3. In the Machines page, highlight the Remote PC catalog, and click Next.
  4. Add users that can access the Remote PCs, and then click Next.
  5. In the¬†Desktop Assignment Rules page, adding an entry here will let users connect to unassigned machines. If you don’t add anything here, then users can only connect to machines to which they’ve been explicitly assigned. Click Next.
  6. In the Summary page, enter a name for the Delivery Group, and then click Finish.
  7. Click Yes when prompted that there are no desktops to deliver.

Multiple Users per PC

Citrix CTX137805 How to Switch Off Remote PC Access Multiple User Assignment in XenDesktop 7.x: By default, when using Remote PC Access in XenDesktop, anybody that logs into the console session of the physical PC is automatically assigned to the Catalog machine in Citrix Studio. This can result in multiple users assigned to the same machine. For IT desktop support staff that routinely log into multiple PCs to support them, the IT staff could see many more machines in StoreFront than they intend.

To stop this, on every Delivery Controller, configure the following registry value so only the first user to log on to the machine after it has registered with the Citrix Broker service gets assigned to the machine. You can still manually assign users to machines using Studio or Director.

  • HKLM\Software\Citrix\DesktopServer\
    • AllowMultipleRemotePCAssignments (DWORD) = 0

Wake On LAN

If you have SCCM configured for Wake On LAN, you can connect XenDesktop to SCCM to power manage the Remote PC machines.

  1. In Citrix Studio, go to Configuration, right-click Hosting, and click Add Connection and Resources.
  2. In the Connection page, change the selection to Create a new connection.
  3. Change the Connection type to Microsoft Configuration Manager Wake on LAN.
  4. Enter the SCCM server’s FQDN.
  5. Enter SCCM credentials. The SCCM credentials you specify must include collections in the scope, and the Remote Tools Operator role.
  6. Give the Connection a name, and click Next.
  7. In the Summary page, click Finish.
  8. Edit the Remote PC Machine Catalog.
  9. In the Power Management page, change the selection to Yes, and click OK

Install VDA on PC

  1. On the PC, install .NET Framework 3.5.1 (Windows 7) or 4.5.2 (or newer).
  2. Disable power saving options (e.g. Hibernate, Sleep, etc.)
  3. If Wake on LAN is desired, configure the PC’s BIOS and NIC to enable Wake on LAN.
    1. Make sure SCCM Agent is installed, and Hardware Inventory has run at least once.
  4. Download Standalone Virtual Delivery Agent 7.15. It’s in the¬†Components that are on the product ISO but also packaged separately section.¬† ūüí°
  5. 7.12 and newer has two standalone installers for Desktop OS. The Desktop OS Core Services VDA is designed specifically for Remote PC, and is the smallest installer available.
  6. Remote PC is typically installed on many distributed PCs. Use a software deployment tool to install the VDA package using CLI parameters. See Use the standalone VDA installer at Citrix Docs for more information.
  7. For the Core Services VDA 7.12 and newer, use a command line similar to the following:
    VDAWorkstationCorpSetup_7.15.exe /quiet /controllers "xdc01.corp.local xdc04.corp.local" /enable_hdx_ports /noreboot
  8. For the larger standalone Virtual Desktop Agent (or VDA’s older than 7.12), use the /remotepc switch. The /components switch lets you exclude¬†Receiver.
    VDAWorkstationSetup_7.15.exe /quiet /remotepc /components VDA /controllers "xdc01.corp.local xdc04.corp.local" /enable_framehawk_port /enable_remote_assistance /enable_hdx_ports /enable_real_time_transport /noreboot
  9. After the machine is rebooted, if the machine is in one of the OUs assigned to the Remote PC Catalog, then the machine will be automatically added to the Catalog and the Delivery Group.
  10. When somebody logs into the console of the machine, that user will be automatically assigned to the machine. You can use the Change User link on the right to change or add users. Multiple users can be assigned to one machine.

  11. When the user logs into StoreFront, the user will see the actual machine name.
  12. The name displayed in StoreFront can be changed by running Set-BrokerPrivateDesktop MyMachine -PublishedName MyDisplayName.

Remote PC Maintenance

Assign/Un-assign users ‚Äď There are four methods of assigning users to desktops:

  • Let Remote PC do it automatically. The first user that logs into the physical machine will be assigned to the desktop. If single user mode is not enabled then all other users that log into the machine will also be assigned to the desktop.
  • In Citrix Studio, find the machine, right-click it, and click¬†Change User.
  • In Director, go to machine details and click Manage Users.
  • Use PowerShell:
    asnp citrix.*
    Remove-BrokerUser -Machine 'CORP\WIN1002' -Name 'CORP\user01'
    Add-BrokerUser -Machine 'CORP\WIN1002' -Name 'CORP\user01'

Rename desktop icon ‚Äď For Remote PC, the icon displayed to the user is the actual machine name. This sometimes is not very intuitive. The name displayed to the user can be changed by running a PowerShell command.

asnp citrix.*
Set-BrokerPrivateDesktop CORP\WIN10002 -PublishedName "Users Desktop"

Display last login time for the machines ‚ÄstUse the following PowerShell to display desktops sorted by when they were last used. Adjust the date filter as desired. You can manually remove the older machines or pipe the results to Remove-BrokerMachine.

asnp citrix.*

Get-BrokerDesktop -CatalogName "Remote PC" -filter {LastConnectionTime -le "2015-02-28"} 
-property AssociatedUserNames,MachineName,LastConnectionTime | Sort-Object LastConnectionTime

The above PowerShell command uses the -filter and -property switches. These switches process the filtering on the server-side, which improves performance.

84 thoughts on “Remote PC”

  1. CArl, we have Win7 desktops published to users and XenApp published apps as well. When user tries to access published app from different machine B, Win7 desktop disconnect from machine A and reconnect at machine B. This happens to both Remote PC desktops and Win7 VDI. what is the command to disable sessionreconnection for Desktop OS delivery group? For XenApp server OS delivery group we have used set-brokerentitlementpolicyrule.

  2. Hi Carl,

    I cannot see ‘Enable AppV component’ option while choosing ‘Remote PC Access’ for VDA 7.12 server setup.

    Can’t we use AppV packages for Remote PC Access?

    1. Remote PC VDA is nothing more than excluding components. You could always do a normal CLI install and exclude/include the components that you want. I can’t think of any reason why AppV component wouldn’t work on a physical PC.

      1. Hi Carl,

        I don’t use MCS/PVS to provision citrix VDA’s. We have remote PC option selected for other Citrix VDA’s and need Appv component on these.
        Any way we can get these?

  3. Carl: If I want to run a Windows 7 virtual desktop (“golden image”) on LOCAL PC (So that it uses LOCAL PC hardware resources), instead of the resources of my Hypervisor, is “Remote PC” (through XenApp 7.x) my answer? If not, does such a technology exist? I’ve looked at “Jentu” but they don’t seem to have a product I can download and try… Thanks!

      1. Thanks for your Reply. Just to be clear, I’m not looking for a way for a User to access a Remote PC; I’m looking for a “localized VDI” solution, where a read-only Image that I create and maintain somehow “streams to” (or is pushed to) the Local PC and runs on THAT machine’s Compute resources (as opposed to a Hypervisor’s)… That’s what XenApp 7.x gives me? Again, I hope you don’t mind my asking more about it. Thank you!

        1. Citrix Provisioning Services can do streaming to physical. However, the vDisk contains the entire C: drive, including drivers, so the endpoint hardware must be identical.

          Or, you can use DesktopPlayer for Windows and Citrix Synchronizer to run Type 2 VMs on endpoint machines.

  4. In the 7.14 security best practices Citrix recommends that you do not assign VDA administrator privileges to general session users. How do you verify that is not happening. Is there a VDA Admin group to check?

  5. Hello Carl!
    I am wondering if only i got that Problem:
    I work locally on a Remote PC (this is my main Machine), when i log on to another Machine every time i start a Published App from our XenApp Farm, the RemotePC is also starting (my main Machine) – i have set the Storefront Setting in the Webconfig File (autoLaunchDesktop=”false”), but that does not work…

    I know the RegKey WSCReconnect – is that the only Method to prevent this behaviour or is there another setting i have not seen?
    Thx in Advance!

  6. Carl,

    I have been searching around but not found much yet. Just wondering if you know.

    I have setup Remote access pc for one machine testing. Everything is working apart from one issue. When I access the machine and try to spread the desktop over multiple monitors It does not work. it just greys out the edges rather than spanning all my monitors. Is this by design? Is there anything I can do to change this functionality?

    Thanks

    1. Hey you can delete this I worked it out.

      I have a nvidia card in the machine and needed to install the VDA as HDX 3d pro. When connecting without it it would have seen the shared video as 0MB so would not have been able to drive more than one screen at all.

      thanks

  7. Hi Carl – Are there any licensing considerations for Remote PC usage – Do we have to purchase a license per a device ? We are currently at the limit of our existing XenDeskop licenses. Thanks

    1. XenDesktop Enterprise licenses are required for each connection to a Remote PC. No licenses are needed to install, just to connect.

  8. hi Carl,

    just wanted to say thank You :), very useful and detailed guide for publishing end user PCs to a farm.

  9. Hi Carl, How would i apply the Set-BrokerPrivateDesktop parameter against 200 machines within a specific delivery group ? thanks

        1. Hi carl, If this needed to be reverted back so that all machines received the name as per identified in the delivery group , would you know how this could be done ? Thanks

  10. I assume that you can run multiple desktop sessions to different endpoints at the same time?

    e.g. Single user logs into PC at home, launches Receiver, user wants to run 1 Hosted Shared Desktop and 1 RemotePC access desktop simultaneously.

    1. From the same endpoint, yes. From different endpoints, you’d need to run a PowerShell command to enable it (prevents Workspace Control from connecting to existing sessions).

      1. CArl, we have Win7 desktops published to users and XenApp published apps as well. When user tries to access published app from different machine B, Win7 desktop disconnect from machine A and reconnect at machine B. This happens to both Remote PC desktops and Win7 VDI. what is the command to disable sessionreconnection for Desktop OS delivery group? For XenApp server OS delivery group we have used set-brokerentitlementpolicyrule.

      1. We are using sslvpn through the netscaler gateway. upon establishing a tunnel we than go to an internal storefront server login and attempt to launch the remote pc published desktop. Should we be able to successfully connect through ica to the remote pc machine? We are testing using XA7.11 and StoreFront 3.8. Thanks Carl

        1. If configured correctly. Are you doing Single FQDN? What is the Internal Beacon? Is the Internal Beacon reachable through the VPN? Are you doing Split Tunnel or Authorization Policies?

  11. I am only able to get the VDAWorkstationCoreSetup command line installation to work properly if specifying the /controllers parameter without quotation marks and a comma separating the controllers.
    Like this: /controllers xdc01.corp.local,xdc04.corp.local

    Perhaps an error in the Citrix documentation?
    Anyone else that see the same behavior?

    1. I have no problem with VDA 7.13 and /controllers “xdc01.corp.local xdc04.corp.local” in my home lab. I check the ListOfDDCs registry key after installation. Are you installing the English version?

      1. Hi Carl,

        Yeah, I am using the 7.13.0.13 English (United States) version.
        If i run it with the documentet parameters you mention above I do not get the ListOfDDCs registry entry at all.
        I have tried this on 3 separate computers (Win7 and Win10) now, and the same behavior or all three.

        Something else I didnt expect is that it does force restart the PC for me the first time I run the command (even though /noreboot is used) and then I will have to run the command once more after logging in because the VDA has been installed yet.
        I actually had the same weird behavior when using the GUI installer.. Set the options and controllers, but then it just restarted with no warning and I had to to it all over again before it got properly installed.

        Have you seen anything like this previously?

      2. Hi again,

        I managed to figure out why the installer was behaving in this way.

        The PC was missing one of the prereqs, and in this case a prereq that will force a restart before it has started installing the vda components (visual c++ 2015).
        After the reboot when I start the installer again i noticed in the log that it “ERROR” on certain steps (a corrupt/not available xml and some other things).
        And because of this it makes the controller parameter to fail as well (could be that the other parameters also fail).
        (Weird that changing the controller parameter to no quotation marks and a comma separator would make it work.)

        So the prereq forced reboot seem to break a few things.

        If I install the prereq first, do a manual reboot and then run the vda-installer again everything works just fine.

  12. Great blog! Is it possible to *only* statically assign a device in Studio to a specific user without adding the AD user name/group to the delivery group?

    This goal being to allow the specific user to log on but prevent the device being available in the portal and dynamically assignable to other users

    Thanks!

    1. Are you asking about Desktop Assignment Rules? Edit the Delivery Group. Change to the Desktop Assignment Rules page and remove all rules.

  13. I was able to solve this by using KEYWORDS in User settings for the Remote PC Delivery Goup and not the Desktop assignment setting (used for random DGs)

  14. Carl,

    Do you know if Remote PC or static/dedicated VDI Delivery groups can have Keywords applied to them. I asked because I have a separate store if SF that I would like to have a user log into and see their Remote PC or assigned VDI plus the 2 training desktops already there. I can add non-static assigned VDI delivery groups and Apps with keywords (store and delivery group) and they show up. Cannot get Remote PC or Static desktop to show up. Both Remote PC and static VDIs show up in the main store.

  15. Dear Carl

    I have POC for persistent provisioning on Moonshot,
    1) Do i need VDA agent on each cartilage desktop/WS ?
    2) can I have remote PC group in catalog and add all these PC for remote access

  16. Carl, your site is amazing! I had to take the time to leave you a feedback! You’re always up to date, your site is the “bible” for Citrix products. Keep up the good work and thanks for all you do for us, Citrix customers!

  17. Is there a way to allow users to restart their desktops via Storefront when using unmanaged remote PC VDAs on physical desktops? Or is this only available for managed virtual desktops, or RemotePC with ConfigMgr integration?

  18. Hello Carl!

    First thank you for this site, this was more than one my lifesaver…

    A Question to remotepc: is it possibe to play Audio on the remote Machine? We have a small Windows PC as a Jukebox in use (with no Display) and for now we do this with RDP, but it would be better with ica, well – i didnt found an option?

    1. Are you asking if audio played on remote machine should be played on the client machine? Certainly. You can run HDX Monitor to verify that the Audio channel is enabled. Audio is controlled by Citrix Policies.

      1. No, Audio should play on the remote pc, not on the client machine – we have a hifi receiver connected with the remotepc and we would like to control this machine with ica… On RDP there is an option where the Audio should play… This would be the Client audio redirection Policy i think? I am very new to RemotePC – the “normal” Policies for XenDesktop are also here valid?

        1. You want a remote user to connect to a office PC and run audio on that office PC even though nobody is near that office PC to hear it?

  19. Hi Carl, great site. Have been able to get a lot of useful information on in depth Citrix information here. Have an issue when using Remote PC. Users can log in and ica into their physical desktops. With ungraceful disconnects (either power save on their laptop or loss of network connectivity) the physical machine never releases the session. The physical machine will have the monitors in power save mode. The pc is not hung as we can use a remote control software and remote into the pc. We can work via the remote tool but cannot log into using the physical keyboard and monitors. Ctrl Alt Del does not work and cannot use ICA to reconnect. Only solution is reboot and then connection can be reestablished.

  20. Hello Carl,
    I’m not able to find the path below on a workstation where I installed the VDA.
    VDA version 7.9 and the machine is windows 10.

    HKLM\SOFTWARE\Citrix\PortICA\RemotePC\SasNotification=dword:00000001

  21. Remote PC is working great for us, but I have a couple of challenges for which I am unable to find solutions. First, Citrix policies assigned via GPO don’t seem to be taking effect on the targeted Remote PCs. I need to make sure we block HDX file access from the connecting machines. We don’t want file access in/our of the Citrix environment.

    Secondly, we typically get audit reports (via Manage Engine Audit Manager) regarding user logins to the shared desktop environment and I’d like the same thing when users access Remote PC. But I’m not necessarily interested in EVERY login event to their workstation – just the Remote PC connections. Do you know of any way to accomplish this? Any suggestion, 3rd party tool, etc. would be appriciated.

    1. 1494/2598 needs to be opened to every VDA.

      Controllers need port 80 opened to every VDA. I’ve seen antivirus interfere with this.

  22. Hi Carl,

    Excellent article! However, we’re trying to set up Remote PC and have managed to get the Machine to appear in SF, however, when a user clicks the Desktop to connect to it, it doesn’t move past the “Connection in Progress…” screen. The user has the right to log into the machine.

    What are we doing wrong?

  23. Carl,

    We just want users to access their own desktop PC this way. Is there a way to do this without creating a Machine Catalog for each machine/user connection?

    1. Of course. You create a Remote PC Catalog and a Remote PC Delivery Group. Any machine added to the Catalog is automatically added to the Delivery Group. All Remote PC users must be assigned to the Delivery Group > Users tab. Then you assign individual users to each machine in the Catalog. Remote PC can do this for you automatically based on who logs into the physical machine. Or you can use Director or Studio to change the users assigned to each individual machine.

      1. Hi Carl thanks for reply, I do the same procedure but still not visible the publish desktop in storefront

  24. I have create the machine catalog and Delivery Group for physical PC and its showing registered VDA but not visible in storefront.

    Please advise.

    1. If the machine is asleep or powered off then users can’t connect. Unless you maybe integrate with SCCM Power Management.

  25. Hello Carl

    Can you do Remote PC Access with a Windows Server OS (Windows Server 2012 R2) using the Server VDA?

    How come you didn’t use the 7.6.300 version of the VDA?

    Is it possible to have multiple simultaneous connections using Remote PC Access?

    Thanks

    Andrew

    1. Not sure about server OS. I’ve never tried it. You run Server OS on your physical PCs?

      Good catch on the VDA version. I’ll update the topic. I missed it when doing updates.

      For desktop OS, only one user at a time. That’s a Microsoft limitation. Otherwise you’d be using XenApp (RDSH).

  26. Hi Carl, I have my MC & Delivery group set up but my user is not getting the desktop icon from the reciever or storefront page. If I manually assign a user to the machine the desktop then becomes available. I do not want to manually assign users so I’m wondering what I am missing. I have logged in via RDP several times to the machines which I understand to be a supported option to auto-assign users. Is this the case or do I need to physically sign into the machine?

    1. The Catalog and Delivery Group are of type “Remote PC”? The machines are automatically added to both? The user is assigned to the Delivery Group (not the machine)? I’ve seen it work with RDP logon but there’s no harm in trying physical logon.

  27. When a Remote PC is used by an user, the next user gets a “useless” error message in saying something like “cannot connect to app. contact helpdesk” is n’t there a way to indicate to the requester who is already using the machine?

    1. I’m not aware of any way to do this. You might have to call Citrix Support and submit an enhancement request.

  28. How can I restrict certain users from ever having a pc assigned to them. Example – those users are not allowed to access their pc remotely but share a pc with someone who is?

    1. Don’t assign the user to the Delivery Group. Edit the Delivery Group properties and on the Users page remove Domain Users and instead add a group containing authorized users.

      1. Hello… We just went to Xen 7.14… On Xen 7.6 all remote machines show up in StoreFront as the machine name… With 7.14 it shows up as Remote PC and the second one we added in said Remote PC (2)…. I am looking hard and don’t see much of a difference… Is this something obvious I am missing or is this a new feature in 7.14?

        1. I’m seeing the exact same behavior with 7.14.1.
          If I run Get-BrokerPrivateDesktop I see that “PublishedName” is missing on the 7.14 machine.

          1. Yep. 7.14 broke our RemotePC naming too. A way to set the default behavior back to using the hostname as the PublishedName when adding new machines would be most excellent!

Leave a Reply