June, 2013 Remote PC v2 Excalibur - XenDesktop 7 Mick Glover Worldwide Support Readiness

© 2013 Citrix | Confidential – Do Not Distribute Remote PC v1.0 Background - Pre XenDesktop 7 Although not promoted as a remote PC solution, several customers successfully used XenDesktop for remote access to office PCs This worked very well with Windows XP but caused issues with Win 7 due to a WDDM driver conflict (Citrix & local)  Local WDDM driver is disabled when installing VDA on physical machine Result: Local experience is degraded (SVGA driver installed)

© 2013 Citrix | Confidential – Do Not Distribute Remote PC v1.0 Goals Main Goal  Performance: To Provide XenDesktop customers with the ability to give their users secure remote access to physical PCs in the office without degrading or impacting their experience locally i.e. provide the same user experience when using a physical machine locally and remotely  Automation: Automatically add physical PCs to a XenDesktop site, and create the association between local physical PCs and users  Flexibility: Provide built-in alternative to GoToMyPC & other 3 rd party products Secondary Goal  Help drive VDI adoption

© 2013 Citrix | Confidential – Do Not Distribute Remote PC v1.0 Overview Project Nighthawk First introduced and still available as separate component with XenDesktop 5.6 FP1  Note: XD Plt & Ent feature ONLY  Custom download  Remote PC Services feature-pack-1-platinum.htmlhttps:// feature-pack-1-platinum.html

© 2013 Citrix | Confidential – Do Not Distribute Remote PC v2.0 New Features Citrix Studio Integration Multiple Catalogs to Machines or Users Support for Windows 8 Enhancements for MS Lync XenClient Enterprise Integration GPU Remoting of DirectX Apps GPU Transcoding of Windows Media redirection 3 rd party Credential provider support Support for legacy VDA 5.6

© 2013 Citrix | Confidential – Do Not Distribute Remote PC v1 vs. v2 Key Differences ConfigurationControlling ServiceExecution v1 v2

© 2013 Citrix | Confidential – Do Not Distribute Remote PC v1 vs. v2 Key Differences ConfigurationControlling ServiceExecution v1RemotePCAccessConfig.xml v2Citrix Studio\PoSH (PowerShell)

© 2013 Citrix | Confidential – Do Not Distribute Remote PC v1 vs. v2 Key Differences ConfigurationControlling ServiceExecution v1RemotePCAccessConfig.xmlRemote PC Access Service v2Citrix Studio\PoSH (PowerShell) Broker Service

© 2013 Citrix | Confidential – Do Not Distribute Remote PC v1 vs. v2 Key Differences ConfigurationControlling ServiceExecution v1RemotePCAccessConfig.xmlRemote PC Access ServiceRemotePCAccess.ps1 v2Citrix Studio\PoSH (PowerShell) Broker ServiceNew Remote PC Deployment Wizard\Broker Service

© 2013 Citrix | Confidential – Do Not Distribute Remote PC v2 Citrix Studio Integration Top level workflow wizard  Uses Pre-built PoSH scripts Automatically creates Catalog and Desktop Group  Remote PC Access Machines  Remote PC Access Desktops

© 2013 Citrix | Confidential – Do Not Distribute Remote PC v2 Configuration Through Citrix Studio and or PoSH (PowerShell)… Citrix Studio  Limited config PoSH  Advanced config

© 2013 Citrix | Confidential – Do Not Distribute Remote PC Access deployment User/Machine Filter Configuration

© 2013 Citrix | Confidential – Do Not Distribute Catalogs, Desktop Groups & Users… Remote PC v1  Single Catalog\Desktop Group combination Remote PC v2  Multiple Catalog\Desktop Group combinations can be configured  New DB table will map the associations and make this possible Note: In v2, the Broker service will not restrict the assignment of a single user to a desktop  A valid domain logon session from a second user will additionally assign that second user to the desktop  This behaviour can be changed by setting a new DC registry key: See next slide…

© 2013 Citrix | Confidential – Do Not Distribute Disabling Multi-User to single Desktop Remote PC v2 HKEY_LOCAL_MACHINE\Software\Citrix\DesktopServer\ [AllowMultipleRemotePCAssignments] Type: REG_DWORD Default: 1  Change value to 0 to disable Multi-User to single desktop feature

© 2013 Citrix | Confidential – Do Not Distribute User account assignments Remote PC v2.0 Add specific user a/c’s or security groups to be assigned to Desktops automatically… Required for auto-assignment to work

© 2013 Citrix | Confidential – Do Not Distribute Machine account Filtering Remote PC v2.0 Add specific machine a/c’s to be discovered or Select OUs containing machines to be discovered

© 2013 Citrix | Confidential – Do Not Distribute Manual Creation through Citrix Studio Create new Machine Catalog  Select Remote PC Access Advantage over workflow wizard?  Name the Machine Catalog  Create multiple Remote PC Catalogs

© 2013 Citrix | Confidential – Do Not Distribute Changes to the DB Remote PC v2.0 Changes to Broker service DB Schema to store additional data  Chb_Config.RemotePCAccounts  Chb_Config.RemotePCMappings

© 2013 Citrix | Confidential – Do Not Distribute RemotePCAccounts Table Database Schema Contains multiple relationships between OUs and Remote PC Catalogs

© 2013 Citrix | Confidential – Do Not Distribute RemotePCMappings Table Database Schema Contains multiple relationships between Remote PC Catalogs and Groups

© 2013 Citrix | Confidential – Do Not Distribute Broker Service Actions Remote PC v2.0 The Broker will perform the following each time a VDA registers…  (both CBP 1.0 and 1.5 to be supported)

© 2013 Citrix | Confidential – Do Not Distribute Discovery\Registration process Add Machine to Catalog If Machine is NOT in a Catalog Machine is NOT in maintenance mode Soft Registered Successfully

© 2013 Citrix | Confidential – Do Not Distribute Discovery\Registration process Add machine to Catalog If Machine is NOT in a Catalog Machine is NOT in maintenance mode Soft Registered Successfully Then Resolve the name of the OU in which the machine exists Find matching rows in the RemotePCAccounts table Add the machine to the Catalog from the most specific matching RemotePCAccounts row

© 2013 Citrix | Confidential – Do Not Distribute Discovery\Registration process in action… Step 1

© 2013 Citrix | Confidential – Do Not Distribute Discovery\Registration process in action… Step 2

© 2013 Citrix | Confidential – Do Not Distribute Discovery\Registration process in action… Step 3

© 2013 Citrix | Confidential – Do Not Distribute Discovery\Registration process in action… Step 4

© 2013 Citrix | Confidential – Do Not Distribute Discovery\Registration process Add unassigned machine to 'temporary' Desktop Group If Machine is in a RemotePC Catalog Machine is NOT in a Delivery Group Machine is NOT in maintenance mode Machine is NOT assigned to a user

© 2013 Citrix | Confidential – Do Not Distribute Discovery\Registration process Add unassigned machine to 'temporary' Desktop Group If Machine is in a RemotePC Catalog Machine is NOT in a Delivery Group Machine is NOT in maintenance mode Machine is NOT assigned to a user Then Select a RemotePC Delivery Group associated with the catalog in the RemotePCMappings table Pick the Delivery Group/Catalog association with the highest priority (by default, the first created) and add machine to this Delivery Group

© 2013 Citrix | Confidential – Do Not Distribute New Remote PC Site Service RemotePC Polls registered VDAs every 30 seconds to repair any side-effects of configuration changes that would normally only occur during machine re- registration

© 2013 Citrix | Confidential – Do Not Distribute Login process Assign user to Machine If Machine is in a Remote PC Catalog Machine is not in maintenance mode Machine is NOT assigned to this user (AllowMultipleRemotePCAssignments=1 (default)) Machine is NOT assigned to any user (AllowMultipleRemotePCAssignments=0) Session is NOT in a disconnected state Machine is in a 'temporary' Desktop Group

© 2013 Citrix | Confidential – Do Not Distribute Login process Assign user to Machine Then Find top matching Desktop Group Order the resulting Desktop Groups by priority (default: Creation Order) Select the top Desktop Group from the ordered results Assign the user to the machine Set the Machine Published Name to the Machine NETBIOS name The desktop is now available for remote brokered access by the user

© 2013 Citrix | Confidential – Do Not Distribute Login\Assignment process in Action Step 1

© 2013 Citrix | Confidential – Do Not Distribute Login\Assignment process in Action Step 2

© 2013 Citrix | Confidential – Do Not Distribute Login\Assignment process in Action Step3

© 2013 Citrix | Confidential – Do Not Distribute Login\Assignment process in Action Step 4

© 2013 Citrix | Confidential – Do Not Distribute Login\Assignment process in Action Step 5

© 2013 Citrix | Confidential – Do Not Distribute Login\Assignment process in Action Step 6

© 2013 Citrix | Confidential – Do Not Distribute Login\Assignment process in Action Step 7

© 2013 Citrix | Confidential – Do Not Distribute Advanced Configuration through PoSH Get-BrokerRemotePCAccount Returns RemotePC configuration for Site  Complete contents of RemotePCAccounts DB Table

© 2013 Citrix | Confidential – Do Not Distribute Advanced Configuration through PoSH Set-BrokerRemotePCAccount Can be used to change normal values i.e. OU and advanced filters such as MachinesExcluded & MachinesIncluded

© 2013 Citrix | Confidential – Do Not Distribute Limitations Remote PC v2 The service will not exclude machines based on OS type: Win XP, Vista and Win 7 will all be discovered and added, if meeting the configured machine- name/OU criteria for Remote PCs The service will not exclude machines that are VM-hosted, as the broker cannot conclusively determine if a registering VDA is installed on a physical PC or a VM  OU Filtering will have to be used (Studio\PoSH) The OU entries in RemotePCAccounts could become stale if the OU is moved or deleted _v2/Remote_PC_Access_v2_-_Functional_Spechttp://mindtouch.eng.citrite.net/Releases/Jasper/Features/Remote_PC_Access _v2/Remote_PC_Access_v2_-_Functional_Spec

© 2013 Citrix | Confidential – Do Not Distribute Upgrade Options In-place upgrade supported with additional tasks  Remote PC Access (v1) will need to be removed. This needs to occur during the in- place upgrade of the DC via the Meta-installer  Configuration data from the v1 service should be read from Global Site Metadata, and used to configure the v2 feature by adding settings directly to the specified Catalog and Desktop Group objects This will occur during the site DB schema upgrade performed by Desktop Studio Note: The Citrix Remote PC Access v2 service is an integral part of the broker service for Excalibur, and is not separately installable/removable

© 2013 Citrix | Confidential – Do Not Distribute Help And Diagnostics Configuration Logging Service  Configuration changes to Remote PC-related Broker objects by Citrix Studio and the PoSH SDK Windows event log messages using the FMA EventLog SDK  Application event log

© 2013 Citrix | Confidential – Do Not Distribute Resources RemotePC v2 mindtouch page  Remote PC Access v2 - Functional Spec  mote_PC_Access_v2_-_Functional_Spec mote_PC_Access_v2_-_Functional_Spec

Work better. Live better.