Comments on: Final Article in VDI Series http://blog.scottlowe.org/2008/02/21/final-article-in-vdi-series/ The weblog of an IT pro specializing in virtualization, storage, and servers Wed, 08 Feb 2012 17:13:47 +0000 hourly 1 http://wordpress.org/?v= By: slowe http://blog.scottlowe.org/2008/02/21/final-article-in-vdi-series/comment-page-1/#comment-35724 slowe Fri, 22 Feb 2008 03:39:45 +0000 http://blog.scottlowe.org/2008/02/21/final-article-in-vdi-series/#comment-35724 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. :) 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. :)

]]> By: Tony http://blog.scottlowe.org/2008/02/21/final-article-in-vdi-series/comment-page-1/#comment-35723 Tony Fri, 22 Feb 2008 03:18:03 +0000 http://blog.scottlowe.org/2008/02/21/final-article-in-vdi-series/#comment-35723 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. 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.

]]>