课件教案cc-p培训remotepc v2

1、June, 2013Remote PC v2Excalibur - XenDesktop 7Mick Glover - Worldwide Support ReadinessRemote PC v1.0Background - Pre XenDesktop 7Although not promoted as a remote PC solution, several customers successfully used XenDesktop for remote access to office PCsThis worked very well with Windows XP but cau

2、sed issues with Win 7 due to a WDDM driver conflict (Citrix & local)Local WDDM driver is disabled when installing VDA on physical machineResult: Local experience is degraded (SVGA driver installed)Remote PC v1.0GoalsMain GoalPerformance: To Provide XenDesktop customers with the ability to give their

3、 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 remotelyAutomation: Automatically add physical PCs to a XenDesktop site, and create the association betwee

4、n local physical PCs and users Flexibility: Provide built-in alternative to GoToMyPC & other 3rd party productsSecondary GoalHelp drive VDI adoptionRemote PC v1.0OverviewProject NighthawkFirst introduced and still available as separate component with XenDesktop 5.6 FP1 Note: XD Plt & Ent feature ONL

5、YCustom downloadRemote PC Services Remote PC v2.0New FeaturesCitrix Studio IntegrationMultiple Catalogs to Machines or UsersSupport for Windows 8Enhancements for MS LyncXenClient Enterprise Integration3rd party Credential provider supportSupport for legacy VDA 5.6Remote PC v1 vs. v2Key DifferencesCo

6、nfigurationControlling ServiceExecutionv1v2Remote PC v1 vs. v2Key DifferencesConfigurationControlling ServiceExecutionv1RemotePCAccessConfig.xmlv2Citrix StudioPoSH (PowerShell)Remote PC v1 vs. v2Key DifferencesConfigurationControlling ServiceExecutionv1RemotePCAccessConfig.xmlRemote PC Access Servic

7、ev2Citrix StudioPoSH (PowerShell)Broker ServiceRemote PC v1 vs. v2Key DifferencesConfigurationControlling ServiceExecutionv1RemotePCAccessConfig.xmlRemote PC Access ServiceRemotePCAccess.ps1v2Citrix StudioPoSH (PowerShell)Broker ServiceNew Remote PC Deployment WizardBroker ServiceRemote PC v2Citrix

8、Studio IntegrationTop level workflow wizardUses Pre-built PoSH scriptsAutomatically creates Catalog and Delivery GroupRemote PC Access MachinesRemote PC Access DesktopsRemote PC v2ConfigurationThrough Citrix Studio and or PoSH (PowerShell)Citrix StudioLimited configPoSHAdvanced configRemote PC Acces

9、s deployment User/Machine Filter ConfigurationCatalogs, Delivery Groups & UsersRemote PC v1Single CatalogDesktop Group combinationRemote PC v2Multiple CatalogDelivery Group combinations can be configuredNew DB table will map the associations and make this possibleNote: In v2, the Broker service will

10、 not restrict the assignment of a single user to a desktopA valid domain logon session from a second user will additionally assign that second user to the desktopThis behaviour can be changed by setting a new DC registry key: See next slideDisabling Multi-User to single DesktopRemote PC v2HKEY_LOCAL

11、_MACHINESoftwareCitrixDesktopServerAllowMultipleRemotePCAssignmentsType: REG_DWORDDefault: 1Change value to 0 to disable Multi-User to single desktop featureMulti-User to single DesktopIn ActionUser account assignmentsRemote PC v2.0Add specific user a/cs or security groups to be assigned to Desktops

12、 automaticallyRequired for auto-assignment to workMachine account FilteringRemote PC v2.0Add specific machine a/cs to be discovered orSelect OUs containing machines to be discoveredManual Creation through Citrix StudioCreate new Machine CatalogSelect Remote PC AccessAdvantage over workflow wizard?Na

13、me the Machine CatalogCreate multiple Remote PC CatalogsChanges to the DBRemote PC v2.0Changes to Broker service DB Schema to store additional dataChb_Config.RemotePCAccountsChb_Config.RemotePCMappingsRemotePCAccounts TableDatabase Schema Contains multiple relationships between OUs and Remote PC Cat

14、alogsRemotePCMappings TableDatabase Schema Contains multiple relationships between Remote PC Catalogs and GroupsBroker Service ActionsRemote PC v2.0TheBroker will perform the following each time a VDA registers(both CBP 1.0 and 1.5 to be supported)DiscoveryRegistration processAdd Machine to CatalogI

15、fMachine is NOT in a CatalogMachine is NOT in maintenance modeSoft Registered SuccessfullyDiscoveryRegistration processAdd machine to CatalogIfMachine is NOT in a CatalogMachine is NOT in maintenance modeSoft Registered SuccessfullyThenResolve the name of the OU in which the machine existsFind match

16、ing rows in the RemotePCAccounts tableAdd the machine to the Catalog from the most specific matching RemotePCAccounts rowDiscoveryRegistration process in actionStep 1DiscoveryRegistration process in actionStep 2DiscoveryRegistration process in actionStep 3DiscoveryRegistration process in actionStep

17、4DiscoveryRegistration processAdd unassigned machine to temporary Delivery GroupIfMachine is in a RemotePC CatalogMachine is NOT in a Delivery GroupMachine is NOT in maintenance modeMachine is NOT assigned to a userDiscoveryRegistration processAdd unassigned machine to temporary Delivery GroupIfMach

18、ine is in a RemotePC CatalogMachine is NOT in a Delivery GroupMachine is NOT in maintenance modeMachine is NOT assigned to a userThenSelect a RemotePC Delivery Group associated with the catalog in the RemotePCMappings tablePick the Delivery Group/Catalog association with the highest priority (by def

19、ault, the first created) and add machine to this Delivery GroupNew Remote PC Site ServiceRemotePCPolls registered VDAs every 30 seconds to repair any side-effects of configuration changes that would normally only occur during machine re-registrationLogin processAssign user to MachineIfMachine is in

20、a Remote PC CatalogMachine is not in maintenance modeMachine isNOT assigned to this user (AllowMultipleRemotePCAssignments=1 (default)Machine isNOT assigned to any user (AllowMultipleRemotePCAssignments=0)Session isNOT in a disconnected stateMachine is in a temporary Delivery GroupLogin processAssig

21、n user to MachineThenFind top matching Delivery GroupOrder the resulting Delivery Groups by priority (default: Creation Order)Select the top Delivery Group from the ordered resultsAssign the user to the machineSet the Machine Published Name to the Machine NETBIOS nameThe desktop is now available for

22、 remote brokered access by the userLoginAssignment process in ActionStep 1LoginAssignment process in ActionStep 2LoginAssignment process in ActionStep3LoginAssignment process in ActionStep 4LoginAssignment process in ActionStep 5LoginAssignment process in ActionStep 6LoginAssignment process in Actio

23、nStep 7Advanced Configuration through PoSHGet-BrokerRemotePCAccount Returns RemotePC configuration for SiteComplete contents of RemotePCAccounts DB TableAdvanced Configuration through PoSHSet-BrokerRemotePCAccountCan be used to change normal values i.e. OU and advanced filters such as MachinesExclud

24、ed & MachinesIncludedLimitations Remote PC v2The 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 PCsThe service will not exclude machines that are VM-hosted, as the broker cann

25、ot conclusively determine if a registering VDA is installed on a physical PC or a VMOU Filtering will have to be used (StudioPoSH)The OU entries in RemotePCAccounts could e stale if the OU is moved or deleted Upgrade OptionsIn-place upgrade supported with additional tasksRemote PC Access (v1) will need to be