My final article in the virtual desktop infrastructure (VDI) series at SearchVMware.com has been published!
From the article, “Networks, host OSes strained by VMware VDI deployments”:
Deploying Virtual Desktop Infrastructure (VDI) on VMware Infrastructure 3 (VI3) can have a considerable impact on your network design and hosted operating system (OS) instances.
The article goes on to discuss specific ways in which the network and the guest operating systems have to be architected in a VDI deployment. I hope you find the information useful!
Tags: Networking, VDI, Virtualization, VMware, Writing


2 comments
Comments feed for this article
Trackback link
http://blog.scottlowe.org/2008/02/21/final-article-in-vdi-series/trackback/
Thursday, February 21, 2008 at 10:18 pm
Tony
Scott,
Interesting article but in your discussion of 3 items needed for VDI, I think you left out the most important detail that is right up there with the broker….profile management.
If you’re doing 1 to 1 VDI, it’s not that difficult, but when your pooling VM’s you MUST allow user specific settings to move along with the user. In it’s simplist of forms, you could just use roaming profiles. Coming from the Terminal Server world…those don’t work well and very quickly become administrative head-aches. You can also try group policy which works with some of the setting some of the time.
When the discussion of brokers comes up, IMO there is only ONE solid connection broker that works the way a broker should right out of the box…Provision Virtual Access Suite (no I don’t work for Quest) Provison does include profile management which is….ok. My favorite solution - ScriptLogic Desktop Authority. (no I don’t work for Quest, seriously) Eventually I would think the 2 products merge somehow because of the Quest acquisions.
VDM2 is a step in the right direction from VMWare, but still lacks the functionality of VAS. Citrix XenDesktop is pretty good too, but doesn’t have the Virtual Center intergration…yet.
Thursday, February 21, 2008 at 10:39 pm
slowe
Tony,
You are absolutely correct! Profile management is definitely an item that needs to be considered in any VDI deployment. Thanks for bringing that up…I think you may have given me an idea for yet one more VDI article.