Although not totally NEW – It’s been out for about a month; VMware View 3.1.1 Build version 175957 is out. The release notes can be found here. The sort of normal point release that you would expect. New Manager, new Agent, new Client.
The preferred upgrade path for me would look something like this :
- Upgrade Manager – Seems pretty straight forward ; Be sure to upgrade all brokers including replicas and security servers.
- Upgrade Agent – If you are using composer, upgrade the agent in the master images, recompose and redeploy and if you have private images, script your deployment.
- Upgrade Clients – Script deployment for FAT clients. Manually upgrade the Thin Clients and if you ThinApp’d the client, just replace the EXE. :)
While working with John Simon, we used his Active Directory policies to push down a STARTUP to the Private images that would silently upgrade the agent upon boot up. You can hack together a script for yourself from the example below. The Script checks the registry for the Build Number and if it does not find the latest (175957), then it will run the EXE upgrade package. Since the script runs on startup, we don’t bother suppressing the reboot.
@echo offset key="HKEY_LOCAL_MACHINE\SOFTWARE\VMware, Inc.\VMware VDM"set DspName=Not Foundfor /f "Tokens=2*" %%a in ('reg query %key% /V BuildNumber^|Find "REG_SZ"') do (set DspName=%%b)if /i "%DspName%" NEQ "175957" goto :vdmup@echo Version FoundGoTo :End:vdmup@echo Old Version@echo Upgrading VMD
reg query "HKEY_LOCAL_MACHINE\SOFTWARE\VMware, Inc.\VMware VDM" /v BuildNumber >> c:\vma.txtGoTo :End:End