文件名称：虚拟桌面连接建立过程-Citrix桌面虚拟化技术交流内部资料
文件大小：2.94MB
文件格式：PPT
更新时间：2024-05-12 13:36:28
桌面虚拟
虚拟桌面连接建立过程 LAN Connected Users Desktop Appliances Desktop Delivery Controller XenApp Portable Profiles Provisioning Server Domain Controller AD OU Xen, Hyper-V, VM SAN Data Center 1. authenticate 2. find “best” virtual desktop 3. start VM 4. PXE-boot VM and stream OS 5. register 6. connect using ICA 7. acquire license and determine policies 8. login 9. apply profile 10. deliver apps Full range of authentication methods supported through web interface technology Full support for SmartAccess and ICA session policies So now you understand the basic components and their arrangement in your data enter, let’s look at what actually happens when end users connect. That way you will be in a better position to understand the recommendations I make for deployment later. First of all, the user authenticates, using the web service exposed by the DDC. By the way, XenDesktop supports a rich set of authentication methods, as you’re used to from XenApp. The DDC determines the best virtual desktop for the user, given the current environment. Typically, this will be a VM that’s already up and running, in particular if the administrator has configure idle pool policies appropriately that enable the DDC to spin up VMs before demand occurs. This will cause the VM to PXE-boot from PVS, starting up the standard operating environment configured in the golden image - or vDisk - prepared earlier. Once the VM is started, it will communicate with the DDC through a set of web service interfaces, and the DDC will relay the VM’s address to the desktop receiver on the endpoint device. This then results in an ICA connection to be made to the VM, which calls back into the DDC to acquire a license for the session. The DDC also determines policies that should apply to the session – XenDesktop supports the full set of ICA policies also available in XenApp, and also integrates with SmartAccess, in other words you can disable functionality based on information gathered on the end-user’s endpoint devices. After a license has been acquired, the user is automatically logged into their virtual desktop, which also causes their profile to be applied using standard roaming profiles. Now the user can launch applications, whether they be installed locally, or delivered from XenApp (using the app receiver deployed into the standard operating environment). *