I’ve been able to experience the results of implementing Workspace Environment Management into a Citrix XenApp and XenDesktop environment. I was easily able to obtain at least a 50% reduction in logon duration.
In 2012, I started my pursuit of astrophotography. Let’s just say the results of M42 – The Orion Nebula were not very impressive.
Over the course of 5 years, I continued to try out new techniques and learned a lot about signal-to-noise ratios, imaging histograms, Bahtinov masks and more. I continued striving for better results and am glad to say, the my work is finally showing positive results.
All of the effort is starting to show some very good results.
I find that astrophotography gives people a “Wow” feeling; so, let’s change topics to something that creates the opposite feeling: Logon Time.
The title is correct. We can improve user logon time by implementing PVS accelerator in XenServer 7.1.
This actually makes perfect sense.
We already showed that PVS Accelerator drastically improves VM boot times because portions of the master vDisk image are cached locally. Booting a VM equates to roughly 80% reads and 20% writes. VMs using the same image are reading the same blocks of data. Due to this similarity, we are able to see huge network utilization reductions by using the PVS Accelerator cache. These reductions in the network utilization translates into faster boot times.
An interesting new feature was included with the XenServer 7.1 release: Provisioning Services Accelerator.
In a single sentence,
PVS Accelerator overcomes PVS server and network latency by utilizing local XenServer RAM/Disk resources to cache blocks of a PVS vDisk to fulfill local target VM requests.
Instead of comparing XenApp 6.5 with XenApp 7.x, let’s put some of these new technologies into practice by solving the following design requirement.
Define a set of XenApp hosts as failover servers for a group of XenApp hosts delivering the primary app? In addition, the failover servers have the following conditions:
The failover servers are a subset of servers hosting their own set of apps
The failover servers only host the primary app in the event the primary hosts are unavailable
As described in the blog How do I migrate a XenApp worker group structure, we saw how the use of Delivery groups, application groups and tags allow us to replicate XenApp 6.5 worker group capabilities to XenApp 7.x. There are some operational differences between Worker Groups and Delivery Groups, namely, how do increase the capacity of the delivery/worker group.
One of the more interesting capabilities of XenApp 6.5 worker groups was in the ways an admin could increase worker group capacity. By adding a server into a worker group, the capacity of the worker group increased.
Many organizations took this approach a step further by basing worker group membership on Active Directory group membership or Active Directory OU membership. In the XenApp console, each worker group was assigned to a single Active Directory group or OU. Any server in the Active Directory group or OU would be a member of that worker group.