In today's society, want users to their data from anywhere and everywhere, with what whatever devices fit their lifestyle.
You might need to access a desktop or an application via a secure data links, use a mobile device to respond quickly to an important email or share files safely. If they work in a branch office, they would not like to suffer a WAN performance.
To IT to meet these needs, Citrix offers the Citrix Workspace Suite , a PowerSuite software to address performance, security and mobility requirements. The Citrix Workspace Suite consists of XenDesktop, XenApp, XenMobile and Share File and Cloudbridge and NetScaler.
As an existing Citrix customer, you already know the benefits of XenDesktop and XenApp and should use them have the strength and the ability of NetScaler. XenMobile provides an enterprise mobility management solution with MDM, MAM and mobility applications, enterprise-class, including Share File for secure file sync and share.
If you are an existing customer XenDesktop, Citrix offers a trade-up program that you retain your current licenses can but add additional technologies such XenMobile and Share File at a discounted price. But trading up means that you to add new technologies your environment! The Citrix Solutions Lab has released a document that looks at what is required to move from XenDesktop 7.5 on Citrix Workspace Suite. The document prepared by an already installed version of XenDesktop in our case XenDesktop 7.5 and NetScaler configured and used to enter the environment. It goes through the upgrade from XenDesktop 7.5 to XenDesktop 7.6 and adds XenMobile and Share File to support 2,000 users.
The document also uses Citrix "special sauce": a few tricks that we have come to reduce the memory requirements
, the first is the RAM cache capacity of PVS (provisioning server) to reduce the use of IOPS storage .. by using the RAM cache with disk overflow, the write cache file with PVS is in storage with a receive overflow plate to the hard disk. This improves performance and reduces storage needs.
The second is the way of XenApp VMs are configured.
XenApp VMs were deployed on blade servers; each server had two physical drives, to keep an operating system, and keep one with the write cache files, then PVS RAM cache has been implemented to reduce the IOPs for storage. A delivery group or farm, was created by XenApp VM server, so if one VM or physical server the remaining servers would have been in the delivery group, to take the load. This removes support the need for an external memory the VMs. configure For more information on the pros and cons of XenApp in this way, check out this blog.
to simplify your trade, up to Citrix Workspace Suite, read the new document Reference Architecture released here.
0 Komentar