18 Mar 3 Considerations for Designing a Desktop Virtualization Model
Once you have a clear understanding of the project goals from an organization-wide perspective, it is time start designing the architecture of your desktop virtualization. Designing an achievable virtualization model that is scalable for the future is critical, but in order to do that there are some key points to address. So with that, here are 3 considerations for designing a desktop virtualization model.
It’s essential to inventory and rationalize your organization’s applications before jumping in to a virtualization project. How many of your apps are actually being used and what is the appropriate model for each in the virtual environment? Will homegrown applications work in a shared environment?
“You need to analyze your applications up front. Understand where each app writes to. Does it write to locations outside of the user profile? Is it terminal services or RDS compliant?” said Nick Rintalan, Senior Architect Citrix Consulting Services, in the Citrix eBook, Desktop Virtualization Deployment Insights.
Designing a desktop virtualization model and getting it off the ground is the easy part. Delivering a product to your users that they will benefit from and appreciate is an entirely different story. Segment the user base in as few segments as possible. Over segmentation can complicate and sink the project. Look at the physical desktops. Which segments are most using which apps and how are they accessing them? Look at the drive mappings, how are the desktops configured? The only way to execute this use discovery process properly is to sit down with your people and see how, when, and how much they actually use the apps on their machines.
“It’s key to understand the various use cases and provide the right technologies to service each one. However, behind the scenes it is also important to identify commonalities. Often user cases that seem very different may only vary by a few apps, or by their preferred access method,” said Steve Greenberg, Founder and Chief Architect, Thin Client Computing in the eBook.
Organizational change is an entire subject unto itself, so covering it here won’t be possible, but it is important to stress that without the enthusiasm of upper management and other users, any project is dead in the water. Aim for the easy targets first. A few big wins early on will help drive and maintain buy-in. Keep the project team and the users informed and involved throughout the project, and remind them that they have a role in the project. And the change is happening with the goal of improving their work experience.
“My standard questions to users are: 1) What do you do today? 2) What challenges do you have and what could be better? 3) If we could wave a magic wand and make it do whatever you want, what would that be? Most of the time the answers to 3) are exactly what we can do with application and desktop virtualization, users just don’t know these things are already possible,” Greenberg said.