Remote PC

Last Modified: Sep 30, 2020 @ 7:51 am


ūüí° = Recently Updated

Change Log

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 Citrix Virtual Apps and Desktops (CVAD), 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 Citrix Virtual Apps and Desktops (CVAD) 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. Windows 10 Compatibility – CTX224843 Windows 10 compatibility with Citrix Virtual Desktops (XenDesktop)

  2. On the PC, install 4.7.1 (or newer).
  3. Disable power saving options (e.g. Hibernate, Sleep, etc.)
  4. If Wake on LAN is desired, configure the PC’s BIOS and NIC to enable Wake on LAN.
    • Make sure SCCM Agent is installed, and Hardware Inventory has run at least once.
  5. Download Standalone Single-session OS (aka Desktop OS) installers for Virtual Delivery Agent 2009, Virtual Delivery Agent 1912 LTSR CU1, or Virtual Delivery Agent 7.15 LTSR Cumulative Update 5.
    1. The standalone VDA installers are in the Components that are on the product ISO but also packaged separately section.
    2. The Single-session OS Core Services VDA is designed specifically for Remote PC, and is the smallest installer available. However, Core Services VDAs older than version 2003 do not include Browser Content Redirection and Teams Redirection.
    3. In VDA 2003 and newer, the Core Services installer includes Browser Content Redirection (BCR) and Teams Redirection.
  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 Teams Redirection and Browser Content Redirection (BCR) in VDA 1912 and older, use the full VDA installer with the /remotepc switch:
    VDAWorkstationSetup_1912.exe /quiet /remotepc /controllers "xdc01.corp.local xdc02.corp.local" /enable_hdx_ports /noreboot
  8. For Teams Redirection and Browser Content Redirection (BCR) in the Core Services VDA 2003 and newer, use a command line similar to the following:
    VDAWorkstationCoreSetup_2009.exe /quiet /controllers "xdc01.corp.local xdc02.corp.local" /enable_hdx_ports /noresume /noreboot
  9. CTX256820 When a user connects to his physical VDA using Remote PC Access, the monitor layout order changes.
    1. On the Remote PC machine, in regedit, go to HKEY_LOCAL_MACHINE\SOFTWARE\Citrix\Graphics
    2. Create a DWORD named  UseSDCForLocalModes and set it to 1.
  10. Vrajesh Subrahari at Remote PC Solution Issue – The virtual machine ‘Unknown’ cannot accept additional sessions at Citrix Discussions recommends disabling Fast Boot.
    1. On the Remote PC machine, in regedit, go to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Power\.
    2. Set HiberbootEnabled to 0.
  11. 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.
  12. 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.

  13. When the user logs into StoreFront, the user will see the actual machine name.
  14. 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.

146 thoughts on “Remote PC”

  1. Should AppDisk VDA plugin be installed when running the VDA install via command line? I noticed it being included even with the /remotepc switch

  2. I have an odd issue and havent been able to find a solution. I have created a Remote PC Access Machine Catalogue and added some physical workstations paired with users, then created a Delivery Group and assigned the Machine Catalogue to the Delivery Group (without a Desktop Assignment Rule as we want them manually assigned). This works great. However when adding a new machine to the Machine Catalogue, I cant seem to get it assigned to the Delivery Group… When looking at the Catalogues tab on the Delivery Group, I can see the number of machines in the assigned catalogue has gone up, but when looking at the Desktops tab, it hasn’t…. Using the “Add Machine” button results in an error that its already assigned…

    How do i get the Delivery Group to update with the newly added machines ?

  3. If the remote local host accessing Remote PC is a Mac, can printers be made available? I can see local storage, but not locally connected (USB) printers. WiFi printing would be awesome, but even USB would do.

  4. Hello Carl!

    Firstly: Great job you do!
    My question: I face black monitors on W10 notebooks when installing Remote PC VDA on them. Happens after a reboot. Monitor on dockingstation is not detected any more than. Unplug the dock and replug helps if only 1 monitor attached. If 2 are attached, only 1 gets detected again. Anyone already has also facedc this issue and maybe already has a solution?


  5. Any Recommendations for fine-tuning of remote pc access on Citrix XenDesktop 7.15 ltsr cu5???
    Since the user is using his remote PC with Citrix and connected the Citrix storefront URL through a third-party VPN. ( Not using Netscaler )
    Citrix infrastructure in on-premise.
    Remote PC is having 3D graphical applications installed on it and user wants high definition experience. ( No lag in performance )

    FYI ‚Äď the endpoint is having 10 Mbps dedicated bandwidth ( Work from Home)

    1. The newest VDA has the newest Citrix codecs, which should perform better.

      VDA 1912 and newer supports EDT MTU Discovery.

      1. If VDA version (ex: 7.15 CU6/1912) is higher than the studio version (say 7.15 CU5), will it affect citrix policies ability to apply effectively ?

  6. Carl,
    Do you have any suggestions or best practices regarding the Citrix Policies assigned to Remote PC Access? I would assume they would be much the same as other VDA connections but I’d like to optimize the experience for my customers.
    Thank you.

  7. I’m sure every other org is in the same boat now, but RemotePC currently has a lot of shine on it. We’re trying to make it DR capable in the short term; we have a separate site built out in another datacenter and we were hoping to export the current Machines/AssignedUsers from the Active site to a CSV and then import those machines/assignedusers to the DR site in the case of an event. At the moment we can’t just join these delivery controllers to the existing site. However, we’re running into some issues with machines that have multiple users assigned (a few PCs do need multiple assignments and some are support staff/test machines).

    here’s what we are trying to use at the moment:
    get-brokermachine -adminaddress DeliveryControllerName -desktopgroupname “remotepc” | Select MachineName, @{l=”AssignedUserSIDs”;e={$_.AssignedUserSIDs -join “;”}} | export-csv C:\test.csv -append -notypeinformation

    The issue i guess is we need the AssignedUserSIDs converted to SamAccountNames and associated with the proper Machines still. Has anyone else ran into this issue and found a solution? Or a citrix provided script possibly? Thanks!

      1. I have not yet but I certainly will look into it. Doing a quick read that may not work for us though as it says it does it in batches of 500. We have several thousand RemotePCs in our environment so we’d have to run it multiple (30+) times. Thanks!

    1. I searched high and low to find a way to nightly export all of the users and computers that we had added to our RemotePC deployment.

      The following has worked for me:

      Get-BrokerMachine -AdminAddress “Controllername:80” -MaxRecordCount 10000 -Filter “((DesktopGroupName -eq `”DeliveryGroupName`”))” | Select {$_.AssociatedUserNames}, {$_.DNSName}, {$_.RegistrationState} | Export-csv -path c:\remotepc.csv

      Just replace Controllername with the FQDN of your controller and replace DeliveryGroupName with the name of your RemotePC Delivery Group name.

      You can remove the RegistrationState info, as I don’t think you would need that.

      You’d then just need to create a new csv file from the exported info in order to Import the computers & users and then upload to your DR site. You may have to use the Excel Concatenate formula to adjust the computernames into a Domain\computer name format for the import csv file. That’s the way I have been uploading into my Machine Catolog. But maybe the fully qualified machine name from the export will also work.

      The above will show the multiple user names associated with a computer, however, you may have to manually adjust those for the import csv. I have not yet tried importing multiple user names per computer.

      1. The reason we didn’t use AssociatedUserNames is because sometimes that doesn’t always match up to who is actually assigned to the device. We have multiple PCs that show 2+ AssociatedUserNames but when we look at who is actually assigned in studio (AssignedUserSIDs) there is only 1 person. When users log into the RemotePC they are not automatically assigned. I suppose it has to do with how RemotePC was setup but i assume you don’t encounter this in your environment?

  8. Hi Carl great document!
    Is it possible to start remote pc when another user is logged on? like remote desktop when you can disconnect user?

Leave a Reply