How does Workspace Environment Management Improve Windows Logon Time

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.

I understand the why.

I want to now understand the how.

Let’s first examine the Windows logon process.

When a user enters their credentials into Windows, a series of steps occurs to fully setup and configure the user environment.  Windows initializes the session and then starts applying the user’s profile, group policy preferences, running logon scripts, mapping drives and mapping printers. During this entire process, the user sees the “Welcome” screen.

Size and complexity equals longer logon times.  If your profile is extremely large, it will take longer to log on. If the logon script is long and complete, it will take longer to process.  If there are numerous group policy preferences, it will take longer to log on.

And once all of these processes complete, the shell initializes.  Once complete, the user is now able to see and interact with their desktop interface.

The easiest solution is to simply remove these time-intensive operations from our logon.

With Workspace Environment Management, we do exactly that.

We remove all of the profile, policy, script and mapping operations from our traditional logon. This lets Windows immediately initialize the Windows shell, displaying the desktop interface to the user where they can begin working.

In the background, Workspace Environment Management applies our profile, policies, scripts and drive/printer mappings.

This simple change gives us fast logon times while still providing the same user personalization as before.

Daniel (Follow on Twitter @djfeller)
Citrix XenApp and XenDesktop 7.6 VDI Handbook
XenApp Best Practices
XenApp Videos

5 thoughts on “How does Workspace Environment Management Improve Windows Logon Time”

    1. The phase of logon when those configurations are applied change from before the desktop loads until after to desktop loads. Once the desktop loads, the user can start interacting. So the user perception is a much faster logon


      1. So there is a period of time where the user is able to start interacting with the desktop but their profile and settings are not yet available to them? For example, the desktop loads, they immediately launch Outlook. Is the Outlook profile from their UPM profile on the machine yet? If not does WEM have a streaming mechanism or some ability to allow it to prioritize access to what the user is requesting? If some user in particular has a very large profile for some reason, will they have problems every time they log on if they launch applications without giving the machine an extra minute or two to complete background processing? And if a user makes a change to something WEM touches before processing has completed does WEM merge the changes somehow or overwrite them?


Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

This site uses Akismet to reduce spam. Learn how your comment data is processed.