4.6.1 upgrade from 4.6

[chouse]

Considering an upgrade from 4.6 to 4.6.1.

Have reviewed the release notes at http://www.vmware.com/support/view46/doc/view-461-release-notes.html and the 4.6 upgrades pdf http://www.vmware.com/pdf/view-46-upgrades.pdf

Has anyone done the 4.6 to 4.6.1 upgrade? Any issues?

Reading the upgrade guide, it says "Stop the service called VMware View Connection Server service on all View Connection Server instances in the group. View LDAP database corruption can occur if you upgrade a View Connection Server instance while other instances in the same group are running" -- is this applicable for 4.6 to 4.6.1? Or really meant for folks upgrading from 4.x to 4.6?

Also, it says "On the host of the View Connection Server instance that is the standard, or first, server instance in the group, run the installer for the VMware View 4.6 Connection Server." -- is there a way to tell which connection server is the standard/first one that was installed, and which were installed as replicas?

[mydearcosmo]

Why not upgrading to version 5.0 instead? It has better features than the previous ones and you will surely get used to it.

[chouse]

The enterprise is not ready to move to 5.x.

[mittim12]

Chris wrote:

Considering an upgrade from 4.6 to 4.6.1.

Have reviewed the release notes at http://www.vmware.com/support/view46/doc/view-461-release-notes.html and the 4.6 upgrades pdf http://www.vmware.com/pdf/view-46-upgrades.pdf

Has anyone done the 4.6 to 4.6.1 upgrade? Any issues?

Reading the upgrade guide, it says "Stop the service called VMware View Connection Server service on all View Connection Server instances in the group. View LDAP database corruption can occur if you upgrade a View Connection Server instance while other instances in the same group are running" -- is this applicable for 4.6 to 4.6.1? Or really meant for folks upgrading from 4.x to 4.6?

Also, it says "On the host of the View Connection Server instance that is the standard, or first, server instance in the group, run the installer for the VMware View 4.6 Connection Server." -- is there a way to tell which connection server is the standard/first one that was installed, and which were installed as replicas?

1:  Stopping the connection server instances for the replication group should be done every upgrade.

2:   It honestly doesn't matter.  Once you add replica servers  they are all equal partners in the replication group.

[chouse]

So all connection servers must have their View Connection Server service stopped, which effectively locks everybody out of the VDI environment, correct?

Another question, in the Upgrade guide, after upgrading all connection servers in a group, it says to upgrade the Security Servers. We have two Security Servers. The guide says "Repeat Step 1 through Step 7 to upgrade each security server." However, Step 1 is to stop all the _Connection Servers_ in the group. Do they really need to be stopped in order to do the Security Server upgrade or is it the View Security Server service which must be stopped, and the connection servers can keep their connection server service running?

[chouse]

I opened a case with HP to confirm that all connection servers must be stopped, as well as security servers, and connection servers must all be stopped while each connection & security server is upgraded.

I also checked the dates on the View server folders to figure out which connection server was installed first, but agree that they're all replicas anyway so it shouldn't really matter.

[mittim12]

Yes, VDI would be down during the upgrade process due to all services being stopped.   As far as the security servers I do mine at the same time as the connection brokers so the service is already stopped.

[chouse]

4.6.1 upgrade went well. Only thing I noticed was that the connection server that is paired with a security server that is about to be upgraded should be upgraded first, and the connection server service must be running when upgrading the security server service because during the install, it tries to connect and validate with the connection server and validate the one-time password that must be set.