Showing posts from December, 2015

Upgrading View 5.3.5 + to View 6.x

One thing to keep in mind when upgrading is that View 5.3.5 disables SSLv3 and TLS 1.0.
If you upgrade to View 6.x you will need to View 6.2.0 or 6.2, if you upgrade to 6.0 -6.1.1 you will be missing certain java components that have changed.

Looks like it is in the release notes:

Upgrading View 5.3.5 to View 6.0 is not supported due to JRE incompatibilities.
Workaround: Upgrade to View 6.1.0 or later

In-place Upgrading your 5.X ESXIi host to 6.X with Realtek drivers

Ok so after what should have been a simple 20 minute upgrade took 3 hours I'm writing the steps on how to upgrade your ESXi 5.X server to 6.0 in place and using the Realtek drivers
If you only have Realtek NIC's you are going to need to firm make sure you have a FAT16 USB stick that will work in your host. 

first get to a command line and run the following
/etc/init.d/usbarbitrator stop

Now insert your USB drive and run this command
esxcli storage core device list | grep -i usb

You should see something like "Local USB Direct-Access"
now run 
ls /vmfs/volumes
You should see a volume with 'NO NAME' as the title (if you do not, then your USB drive is probably not supported or not formatted with FAT 16. format the drive with FAT 16 or try a different USB drive till you get one that works)

Now that you have verified you have a Drive you can use on the host lets begin the upgrade.
First download the NIC VIB from here

View 6.2.1 Upgrade

So One thing to keep in mind is if you are doing a staged upgrade of View, you may run into some issues with older versions of the client, or older versions of the agent.
One thing that came up in my testing is if you are using PSG, and upgrade your servers first, you will not be able to connect. This has to do with the fact that TLS 1.0 is completely disabled by default. To fix this you must either enable it or upgrade your agents sooner.

It looks like they updated the documentation to show this.

VMware View and vsphere 5.5U3b cause composer issues

So one thing I wanted to make people aware of is that if you upgrade your host to 5.5U3b, you will break VMware View on version older than 6.2.

So why does this happen?
With the release of 5.5U3b VMware has disabled SSLv3

Older version of View utilize the SSLv3 to communicate with both vCenter and the ESXi hosts.

You may see errors such as:

| UFA main thread 16 | FATAL | CommonLib.UfaSubsystem.UfaWorkItem - UFA error: fail in open computer operation.
| UFA main thread 16 | INFO | CommonLib.UfaSubsystem.InitializeDiskUfaWorkItem - UFA error: fail to finish init disk operation for disk: datastore: [datastore_name] VMNAME1/VMNAME1-internal.vmdk, host: FQDN, port: 902.
| UFA main thread 16 | FATAL | CommonLib.UfaSubsystem.InitializeDiskSetUfaWorkItem - Error: CompletionCallbackProxy failed to init disk with result

If you have upgraded your host , you have 2 options.

1. Upgrade to View 6.2 or 6.2.1, thi…

VMware Access Point fails to start

Ran across an issue with access point the other day where it refused to start. After searching four hours found this post on editing the vmware_ap_supervisord file to fix the stale pid file issue.

View 6.2.1 Released

VMware View Security Server Dynamic IP update script.

To go along with my previous post
Im adding a new script for dynamically updating a security server.

Simply replace the cn=SEC with the name of your security
run the scrip on a schedule on your connection server as some one who has access to the ADAM database.