Implementing a virtual desktop infrastructure is no small undertaking. Thousands of decisions go into building such a system, each more critical than the next. In architecting a virtual desktop (VDI environment), a smart system architect will ask “What is the best solution for the environment?” An even smarter architect will ask, “Does the solution meet the end user’s needs?"
And the brilliant Citrix architects will look at all eleven systems your virtual desktop infrastructure will interact with (storage, group policy, network infrastructure, etc.) and make sure every system is optimized for virtual desktop delivery before the first desktop rolls out.
If Citrix logins are longer than 30 seconds, we call that broken. The good news is we can help you fix it.
Your workers — your computer users — of course, are the backbone of your business. Building an environment that meets business goals is useless if it does not also meet the needs of the folks who will be using it. And consider that you probably have different categories of workers. Task workers, for example, will likely have different needs than “power” or “knowledge” workers.
As you’re architecting your network, research your company’s user types. Go talk to them. What’s important to each? Is a fast login time important? Is it eliminating multiple sign-ons? Are you providing the right tools for each user? Can they use their favorite web browser? Do graphics load quickly? How are they going to print? Where do they need to print to? Will they want to work from outside of the office?
If you fail to consider users’ needs, you’ll suffer the consequences:
As you can see, failing to completely consider users’ needs can lead to some fairly dire consequences and a whole lot of expense and time spent where there should have been significant savings.
Understand your use cases first-hand if possible, and get a good architecture built on a hardware platform that is highly available. Citrix XenDesktop and XenApp are only as good as the software/hardware/network infrastructure they are built on.
At Whitehat, we apply more than 400 modifications to the networks we build and manage to make sure every interrelated system, from mass storage to Active Directory/Group Policy are optimized for the best user experience possible.
Done right, login times can be less than 10 seconds. Some environments have a lot of overhead that makes sub-10-second-login times impossible, but, regardless of environment, login times should never be longer than 30 seconds.
If your login experience is longer than 30 seconds, we would call that broken. The good news is we can help you fix it. The better news is that if you take us up on our Citrix 30 Second Challenge, our work might be free.