Explained The Remote PC Service

Explained The Remote PC Service -

A Synergy San Francisco May (and re-announced at Synergy Barcelona in October), Citrix introduced remote PC as part of XenDesktop 5.6 Feature Pack 1 to 1 of FlexCast new model designed to dramatically increase workplace productivity and eliminate the administration, support and deployment costs associated with secure connectivity to assets and existing notebook PC.

The irresistible piece remote PC is that we take HDX and Citrix Receiver (coupled with SmartAccess Access Gateway) to provide a superior experience, controlled and secure access to Windows Active Cubicle

to see it in action a demonstration can be found here :. PC Remote Demo

The use case in the demo is that I Unshackled the confines of the cell during the day, not only the assumptions of a day off at night or Regional interrupting event (weather, events, etc.) situations that typically define "remote access" from outside the DMZ.

I can watch a training video / GoToMeeting presentation to lunch or meetings in the corridor that normally I have to "break" to work or carry my laptop with me. Instead of gaining the corridor "hey can you come here for a second?" I just bring my BYO with me to their place and show them.

Another value for remote PC is that you may be considering VDI or hosted shared deployment models FlexCast, so I have a question for you: Why do your users expect earnings delayed even HDX and experience of the receiver Bring them now with the PC remotely and build the infrastructure? in internships. Your users are already happy using HDX and receiver at the time of PC / laptop is replaced permanently.

Maybe you want to keep using local images (PC / notebook cooling) and deploy remote PC on its own merit. The vast majority of customers deploying remote PC using this way today; to replace telecommuting style "remote" connection access for mid-00 models. These customers now have even more added value in that they also have access to our other fantastic FlexCast solutions at hand to deploy and migrate images, applications and VDI profiles, shared Hosted, XenClient Enterprise XenApp ... and when they are ready. We have a large network of partners and services to help that, using AppDNA as a key technology to enable it.

However, it is not only about the user experience and value to FlexCast Remote PC that brings, it is also the. administration and support experience

one of the most important features released alongside XD 5.6 FP1, is remote PC service; . The point of this blog

From configuring and deploying perspective, to create the link to the active remote PC in Citrix Receiver as seen in the demo, you need to do three things in the XenDesktop Studio:

1. Create the catalog and add it to the machine
2. Create assignment and add the new machine from the catalog to her
3. Assign the user to the machine itself (this is the part when it appears in the receiver for this user)

this would certainly mean a lot of clicks and manual administration by the user to deploy 10,000 of remote PC assets. The remote PC service focuses on eliminating the administrative overhead

There is a Windows service that is installed on the XenDesktop 5.6 dealer who operates three components :.

1. RemotePCAccess.ps1 file
2. RemotePCAccessConfig.xml
3. RemotePCService.exe

... then ultimately be controlled (on / off) via the sERVICES.MSC the broker.

To begin, download the installer from the remote PC service from here:

• http://www.citrix.com/downloads/xendesktop/ product-software / XenDesktop-56-feature-pack-1 enterprise.html
  • MyCitrix connection required
• http://deliver.citrix.com/xdexpressdl
  • New customers get this download

Run the MSI on a single broker in the 5.6 site XenDesktop (one second for redundancy but disabled), all components are then installed. It takes about 30 seconds. Once it is installed, it is ready to perform the functionality, but not really anything until you change the XML file. This is necessary to make it work

Just "Stop" remote PC service and edit the XML file in c :. Program Files (x86) Citrix Remote Desktop Services with a "wide open" configuration listed here: http://support.citrix.com/proddocs/topic/xendesktop-56fp1/cds-remotepc-configure.html. .. late in "Important: To activate ..." section . Also listed are various ways in which you can handle based groups and OR

Note :. Today, there is a current limitation of a single XML + service broker who will only add machines to a catalog and specific assignment based on the settings XML file. You can work around this by having multiple XML files, then share or manually edit the XML file for the "time" of your deployment by department and use the organization put together unit, or have a separate broker in the same site with a different configuration XML using the oR setting, or a different broker for every catalog. We seek to improve this limitation in the future

Once you've made the basic setting changes, the Remote PC Service will do the following :.

1. Per XenDesktop site, creates the catalog and transfer based on XML parameters - if they already exist, skip
2. In the XD site, look for "soft recorded" machinery ( they are machines that are registered but are not "home" again), and add them to the preconfigured catalog from the XML file
3. adds this machine to the preconfigured assignment from the XML file, and assigns as a resource available to a user
   1. service can not detect if the machine is physical or virtual, so if the combination of service with VDI, your best bet is to set also using the UO method.
4. is the last step the user station. This is done by having the user login at the local level where the Virtual Desktop Agent (VDA) XD 5.6 FP1 is installed. Once they have done only once, the PC or the laptop will be displayed everywhere receiver for this user! It is important that you use the Feature Pack 1 VDA, as previous ADV are not encoded with remote PC. The XenDeskop56.ISO has an older VDA, so make sure you use the "Update" VDA.

Now you have a functional self-discovery, self-registration and self-attribution of the solution in about 2 minutes for each user without having to manage -. you simply provide the VDA 5.6 FP1 by ESD, GPO, self-service, or by manual deployment

from the perspective of helpdesk support, they will now just be aligning their support questions very similar and familiar XenApp as: outside the general network connectivity and behavior of the receptor interaction - not specialized VPN tunnels, the DMZ device configurations, other protocols on the network and network authentication control . This will save on support costs from an administration point of view, deployment and support (more if you feel like you have a plan to disable other protocols that may be predisposed to common vectors attack (viruses, malware, hackers), this can contribute to achieving that).

Finally, a request that came from time to time, is to be able to affect only one user per PC remote resource. Today, the service automatically assigns each user that physically connects successfully to the PC / laptop where the local VDA is installed (and remote PC service is running) this resource. To work around this problem, you can change the file RemotePCAccess.ps1 to "auto-assign first use, single user" - by making the following changes:

Warning - problems with the remote PC service can occur if you change the file incorrectly RemotePCAccess.ps1. These problems might require that you reinstall the Remote PC Service. Edit at your own risk.

1. Stop the Remote PC Service
2. Make a backup of the file RemotePCAccess.ps1
3. Make the following changes in the file:

A line No. 238 -

 # this user is already assigned to this machine? $ AssignedUsers = @ | if ($ assignedUsers  -contains $ dk.SessionUserSid ) {return} 

(Get-BrokerUser -MachineUid $ dk.MachineUid% {$ _ SID.}). .. to change ...

 # is already assigned a user to this machine? $ AssignedUsers = @ (Get-BrokerUser -MachineUid $ dk.MachineUid |% {$ _ SID.}) If ($ assignedUsers  -ne $ null ) {return} 

Save the file and start the remote PC Service Note: you must manually delete users assigned to resources before enabling this edition. He does not "clean up" the users of resources already allocated.

Now after you implement this change, you may notice that when you check to make sure it works, performances Studio "In Use" and lists two different users. You need to "right-click" on the machine in the Studio and select "Switch User" this will actually show you the assignment (authorization for the HDX session via remote PC). The Studio view shows a combination of local and remote session if the local session is used by a person other than the remote session user account assigned.

Thanks for reading!

Tweet