vCenter Operations Manager for View is a new VMware product that correlates al kinds of performance figures in a VMware View environment. More info on vCenter Operations Manager for View can be found here
vCenter Operations Manager for View basicaly is a set of front end tools for vCenter Operations Manager 5 that gets info from all View components.
Whenever you connect to the vCenter Operations Manager 5 UI VM, you automatically end up at the default login page for vCenter Operations Manager 5, which made me enter my credentials at the wrong place all the time, since this instance is only used for vCenter Operations Manager for View.
The correct way to access vCenter Operations Manager for View is go to the
https://<UI VM>/vcops-custom url, which off course can be bookmarked, but since I access this system from multiple desktops, I was looking for an easier way to do this, and succeeded.
It’s pretty simple, Continue reading
In the release notes for the View client for iPad version 1.5 I read one of the new features for the client is:
Save password option if administrator enables new VMware View 5.1 policy
Since I already upgraded my Lab/Demo environment to View 5.1, and this would be a very welcome feature for demo purposes (I would not use this in a production environment due to the security issues this might cause) I decided to enable it.
Because the release notes talked about a policy, I kind of expected this option to be either in an ADM template, or in the policy section of the Connection Server.
It was not …. Continue reading
Today I was working on upgrading some hosts in a vSphere 5 environment that is using Cisco Nexus 1000V virtual switches. I imported the extension bundle in Update Manager, created a baseline, and scanned the hosts. After a couple of seconds , I got a message in vCenter telling me the scan failed:
Scan entity <hostname> Host cannot download files from VMware vSphere Update Manager patch store. Check the network connectivity and firewall setup, and check esxupdate logs for details. Continue reading
The last few weeks I have been working on some serious issues in an environment where we used vSphere 5 with an EMC VNX storage array. All seemed to run fine, but whenever we started a Storage vMotion, we noticed all kinds of strange errors we where not expecting at all.
We saw messages regarding write-quiesced VMFS volumes, we lost paths. and in some cases, the Storage vMotions did not complete at all.
During these Storage vMotions we noticed datastore latency peaked at more then 5 seconds on the source and destination LUN’s.
Last week while working at a customer, we migrated their VM’s from a Standard Switch to a Distributed Switch using the “Migrate Virtual Machine Networking” wizard.
After the migration, some VM’s appeared to be connected to two Port Groups, even though they only had one Network adapter configured: