An Architect’s Guide to Desktop Virtualization

What does it take to be a desktop virtualization architect?

Being able to say “It depends” in twelve different languages is a great start.

  • English (American): It depends
  • English (Australian): It depends
  • English (British): It depends
  • English (Canadian): It depends
  • German: je nachdem
  • Spanish: eso depende
  • French: elle dépend
  • Dutch: het hangt ervan
  • Italian: dipende
  • Swahilli: inategemea
  • Chinese: 视情况而定
  • Japanese: それは場合による

Translations courtesy of Google Translator. For all I know, I just said “My hovercraft is full of eels” in many different languages. 

Seriously, the reason why an architect says “It depends” so much is because we don’t have enough information to make the best decision, or even an educated guess. To put simply, it depends on the circumstances. Unfortunately, “It depends” isn’t the answer; it is the start of a longer discussion meant to uncover the underlying challenges and goals. And because a true desktop virtualization solution can take on so many different forms, the time to develop the skills as an architect can be quite long.

How do we shorten this timeframe? It starts with gaining an understanding of the information one needs to gather, how that information goes into defining user groups and virtualization models and identifying/selecting the appropriate design decisions.

This is a huge undertaking, and one we are excited to take on. As you might have seen, we recently released the Citrix Virtual Desktop Handbook, which grew out of the successful Citrix XenDesktop Handbook (we are creative with names ). We wanted to focus on more than XenDesktop because desktop virtualization is so much more than VDI. We want to create an all-encompassing guide for an architect.

Version 1 of the handbook focuses on the Assess phase, which identifies what you need to know and do to successfully start your project. This is only the start. We are getting close to releasing version 2, which will include portions of the design section (this is the part that excites most architects).

If you haven’t already, download the handbook, find a comfy chair, and let us know what you think of the initial release.

Stay tuned for more

Daniel – Lead Architect

1 thought on “An Architect’s Guide to Desktop Virtualization”

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.