We recently upgraded our environment from vWorkspace 7.0 to vWorkspace 7.1.
Upgrading the server components (broker/web servers/ssl gateways) went very smooth, no problems at all.
However, upgrading the pntools on the virtual desktops seems to be a very difficult proces to automate.
If you do it manually it looks something like this:
uninstall pntools
reboot virtual machine
install new pntools
reboot viirtual machine
Ofcourse we want to automaticly do this on all clients.
The way it works now, we could script an uninstall of pntools followed by a reboot. But then when the system comes up, the client can't login (because pntools is missing).
We can only install new software during login.
Normally, when you upgrade software, there is a special upgrade package which doesn't need a reboot before being installed. This would be alot easier to distribute automaticly using distribution tools.
Have you looked at the possibility of using your uninstall script to populate the RunOnce and AutoAdminLogon registry keys?
This would allow your workstations to automatically log in and then execute a RunOnce script to install the new PNtools before removing those settings and rebooting ready for user logon.
You can bulk uninstall and install pntools and the virtual machines should reboot automatically. But if that doesn't work the way you want you can also set up scheduled tasks to do that for you. The only exception would be the template machine being used for linked clones (VMware) or VHD differencing disks (Hyper-V/SCVMM) where you would have to update the templates manually.
Due to the low level at which the drivers operate we do require a reboot on both install and uninstall of the PNtools.
P.S. The forum is not in Spanish for me or my colleagues, can you check your system settings or try a different browser, I believe this may be a local setting you have applied.
We tried it on some clients, but if we uninstall and then install the new version, followed by a reboot, clients can't connect to the virtual desktop anymore.
It only works if we force a reboot direct after the uninstall. This would mean 2 reboots.
Another problem is that a lot of users don't turn off their desktop, but just disconnect. I we do something with schedules, people may loose work.
ps: This forum is now default in spanish? "Agregar respuesta" "Cancelar" "Respuesta"
P.S. The forum is not in Spanish for me or my colleagues, can you check your system settings or try a different browser, I believe this may be a local setting you have applied.
Strange, I haven't changed anything. The forum is also in spanish when not logged in. Local settings are dutch.
I understand that pntools uses low level drivers, but how do other companies upgrade pntools then?
If you have thousands of client running, you want a solid upgrade procedure. You can't risk that something goes wrong during the remove-reboot-runonce install new version-reboot process.
Vmtools also use low level drivers, but can easily be upgraded. It would be nice if something simulair would be possible in the future for the pntools.
DELL-David Y
228 Posts
357
0
Posted October 26th, 2010 13:00
Hello René,
Have you looked at the possibility of using your uninstall script to populate the RunOnce and AutoAdminLogon registry keys?
This would allow your workstations to automatically log in and then execute a RunOnce script to install the new PNtools before removing those settings and rebooting ready for user logon.