VMware Communities: Message List - Pooled persistent desktop management issue

Re: Pooled persistent desktop management issue

SteveHudson — Wed, 13 Aug 2008 15:33:15 GMT

I see you mention a user profile solution as I have seen in other threads but I have to say that there is a much better option than the RTO solution you mention. Entrigue's Script Start ProfileUnity makes a HUGE difference in logon performance improvement. We tested ProfileUnity and even the largest of profiles only took seconds to logon to. At the same time, Entrigue's solution actually provisions initial network admin profile settings for users, things that are normally a pain in the butt that admins have to do on a daily basis such as map drives/printers, create desktop shortcuts, setup MAPI profiles. BTW, we found Entigue because their profile provisioning solution is availabe as an easy to install Open Source solution....so admins can even run the profile provisioning solution at ZERO cost.

Re: Pooled persistent desktop management issue

mittim12 — Mon, 21 Apr 2008 13:26:39 GMT

wponder wrote:This is possible but not exactly how you describe. Non-Persistent pools when using VDM are not non-persistent in the context of disks. You can however implement them that way by doing some scripting on the back end to set the disks to non-persistent disks after they are cloned. I would also recommend you combine this with a profile virtualization or management solution such as RTOsoft virtual profiles otherwise your users settings will be lost after each reset.

Depending on the size of the environment you might not even need to set the disk to non persistant. You could simply delete all the VM's if you have the need to make a change to the template or you could simply use the delete after first use option in VMware's VDM (assuming that is what he is using) to keep your pool up to date with the latest changes int he template.

Re: Pooled persistent desktop management issue

wponder — Mon, 21 Apr 2008 12:55:35 GMT

This is possible but not exactly how you describe. Non-Persistent pools when using VDM are not non-persistent in the context of disks. You can however implement them that way by doing some scripting on the back end to set the disks to non-persistent disks after they are cloned. I would also recommend you combine this with a profile virtualization or management solution such as RTOsoft virtual profiles otherwise your users settings will be lost after each reset.

WP

Pooled persistent desktop management issue

vitzares — Mon, 21 Apr 2008 11:06:06 GMT

Dear all,

I get a question in mind. If we use VDI to deploy pooled persistent desktop to user, Every user still get their own desktop. As an IT department, We still need to maintain patch, update anti-virus, update application in all virtual desktop. The only benefit is that we can reduce cost on traveling to user premises on repairing hardware failure.

On the other hand, if we can deploy pooled non-persisent desktop VDI to all users. The benefit will be much greater. Let say that we create a template to contain all necessary business applications, anti-virus etc and automatically roll out to all users.

User can save their work (My Documents) and email into network drive. When they log off, the VM will be automatically destructed. If any application revision is needed, We just modify the VM template and redeploy to all VDI users again.

When user login next time, their desktop is already new one with patched application and security update.

Is it possible to do so in VDI ? any success story ?

Regards,
Edward