Remote PC Access
allows an end user to log on remotely from virtually anywhere to the physical
Windows PC in the office. The Virtual Delivery Agent (VDA) is installed on the
office PC; it registers with the Delivery Controller and manages the HDX
connection between the PC and the end user client devices. Remote PC Access
supports a self-service model; after you set up the whitelist of machines that
users are permitted to access, those users can join their office PCs to a Site
themselves, without administrator intervention. The Citrix Receiver running on
their client device enables access to the applications and data on the office
PC from the Remote PC Access desktop session.
A user can have
multiple desktops, including more than one physical PC or a combination of
physical PCs and virtual desktops.
Note: Remote PC
Access is valid only for XenDesktop licenses; sessions consume licenses in the
same way as other XenDesktop sessions.
- Before configuring the
remote PC deployment site, set up your Organizational Units (OUs) and security
groups and then create user accounts. Use these accounts to specify users for
the Delivery Groups you will use to provide Remote PC Access.
- If you modify Active
Directory after a machine has been added to a machine catalog, Remote PC Access
does not reevaluate that assignment. You can manually reassign a machine to a
different catalog, if needed.
- If you move or delete OUs,
those used for Remote PC Access can become out of date. VDAs might no longer be
associated with the most appropriate (or any) machine catalog or Delivery
and Delivery Group considerations:
- A machine can be assigned
to only one machine catalog and one Delivery Group at a time.
- You can put machines in one
or more Remote PC Access machine catalogs.
- When choosing Machine
Accounts for a machine catalog, select the lowest applicable OU to avoid
potential conflicts with machines in another catalog. For example, in the case
of Bank/officers/tellers, select tellers.
- You can allocate all
machines from one remote PC machine catalog through one or more Delivery
Groups. For example, if one group of users requires certain policy settings and
another group requires different settings, assigning the users to different
Delivery Groups enables you to filter the HDX policies according to each
- If your IT infrastructure
assigns responsibility for servicing users based on geographic location,
department, or some other category, you can group machines and users
accordingly to allow for delegated administration. Ensure that each
administrator has permissions for both the relevant machine catalogs and the
corresponding Delivery Groups.
- For users with office PCs
running Windows XP, create a separate machine catalog and Delivery Group for
those systems. When choosing machine accounts for that catalog in Studio,
select the checkbox indicating that some machines are running Windows XP.
XenDesktop features are not supported for Remote PC Access deployments:
- Creating master images
and virtual machines
- Delivering hosted
- Personal vDisks
- Client folder redirection
Wake on LAN
Remote PC Access supports Wake on LAN, which gives users the ability to turn on physical PCs remotely. This feature enables users to keep their office PCs turned off when not in use, saving energy costs. It also enables remote access when a machine has been turned off inadvertently, such as during weather events.
The Remote PC Access Wake on LAN feature is supported on both of the following:
- PCs that support Intel Active Management Technology (AMT)
- PCs that have the Wake on LAN option enabled in the BIOS
You must configure Microsoft System Center Configuration Manager (ConfigMgr) 2012 to use the Wake on LAN feature. ConfigMgr provides access to invoke AMT power commands for the PC, plus Wake-up proxy and magic-packet support. Then, when you use Studio to create a Remote PC Access deployment (or when you add another power management connection to be used for Remote PC Access), you enable power management and specify ConfigMgr access information.
- Using AMT power operations is preferred for security and reliability; however, support is also provided for two non-AMT methods: ConfigMgr Wake-up proxy and raw magic packets.
- On AMT-capable machines only, the Wake on LAN feature also supports the Force-Shutdown and Force-Restart actions in Studio and Director. Additionally, a Restart action is available in StoreFront and Receiver.
For more information, see Microsoft System Center Configuration Manager and Remote PC Access Wake on LAN and Provide users with Remote PC Access.