Installing VMWare View Patch 4.6.2 in 4.6.0 environment:

Here is the security advisory with links to downloads and release notes:

http://www.vmware.com/security/advisories/VMSA-2012-0017.html

The documentation I found was a bit confusing it kept referencing full scale upgrades rather than patch deployment. While those docs did reference a lot of verify this and that and backup this and that I will assume you know your environment and have backups for your backups, snapshots,… as I did before I started.

Out of curiosity I used my golden image that had the 4.6.0 agent to create a new pool upgrading it to the 4.6.2 agent, without making any other changes to my environment such as the connection server. I found that it worked fine in my configuration. So I changed that to the default pool and moved my users over to the 4.6.2 agent on their VDI’s. Worse case if anything went south I would reconnect to the old 4.6.0 agent pool.

I have no security server in this environment so I was able to skip that step.

On View connection Server I ran an additional backup by going to the View Administrator Console
Expanding “View Configuration”> Select “Servers”:

clip_image001

To the right on the View Connection Servers I highlighted my server and selected Backup now as shown below:

clip_image003

After hours I then made snapshots of my VCenter and View Connection servers.

Once the snapshot completed I closed the View Administrator and ran the installation on my View Connection Server.

Note: Other documentation I found referenced stopping services… but in my single Connection Server environment that was not necessary the installation stopped and started the services as required.

“VMware-viewconnectionserver-4.6.2-916912” for my 64 bit environment

I then logged back onto the View Administrator Console confirmed all was ok and the version was listed as 4.6.2-916912 and thoroughly tested my View Agent connectivity. Then I cleaned up my snapshots. No upgrade task was required on VCenter.

Comments

Post a Comment

Popular posts from this blog

Office 365 Deployment Tool Office Download fails “Could not Install”

Image
Problem: you run the setup.exe /download download.xml and fails immediately with “Couldn’t install” You make sure all the settings are correct (see other blogs) and find nothing wrong Solution: Change drives and run it as an administrator again. For example above i am in the F:\OfficeDeploy directory which is the same directory I have the download.xml directing the download to. If i Change to the c: and run the same command again it works The Office Data folder was created and updated as shown below:
Read more

FRS to DFSR Post Cleanup “File Replication NtFrs Stopped”

Image
After successfully migrating from FRS to DFSR you get the File Replication NtFrs service is Stopped error on the local servers AD DS Services list. In the Event logs you may see Event id 13575 13577. You can confirm your migration completed by opening a cmd prompt as administrator and typing in: dfsrmig /getmigrationstate After your migration to DFSR is completed and you have given your servers ample time to propagate this service is no longer required. Since it is set to “Automatic”, as shown below” it shows in logs as a false positive error. Edit the File Replication Service and change it to “Disabled”, as shown below: Once it is listed as “Disabled” it will no longer show in the Console as an “error” Note : it may take some time to clear from the active view
Read more

Domain Migration SubinACL /Migratetodomain How To:

Caution : DO NOT run this on Domain Controller C:\ and only run on roaming profiles folders, or my docs shares day of migration to avoid ownership change issues. Confirm Domain trust is in place and users and groups have been migrated Test ping of olddomain.org from new domain Test ping of newdomain.org from olddomain Add newdomain.org domain controller host records to olddomain.org including reverse DNS records Confirm the user running the app is a domain admin in BOTH domains Download SubinACL here: http://www.microsoft.com/en-us/download/details.aspx?id=23510 /Migratetodomain- command will add the permissions of the new user to the old files and folders for example if jimbob@olddomain.org was migrated to the new domain jimbob@newdomain.org and you run the command below any file or folder in that path that has jimbob@olddomain.org will add Jimbob@newdomain.org with the exact same permissions. This is a safer way to migrate by keeping the old and new permissions intact while a
Read more