New VMware Product: VMware Vcenter Log Insight

There is a new log analytics product from VMware.  It is in beta now and I hope to get it installed and take a look at it.  It will be a purchased product in Q3 it appears.


Powercli: Which VM’s were affected by HA Event 5.x

We had an HA event and needed to find out which VM’s were affected, but it has proven to be extremely difficult to identify these from the VI Client.  It appears you can do it from the Web Client as shown in this video, but I prefer the Powercli method.

Jonathon Medd has a post here:

I am interested in the update 2 which works with 5.x +

Here is the commands to get the VM’s that restarted with an HA event for last 5 days:

Get-VIEvent -maxsamples 100000 -Start ($Date).AddDays(-$HAVMrestartold) -type warning | Where {$_.FullFormattedMessage -match "restarted"} |select CreatedTime,FullFormattedMessage |sort CreatedTime -Descending

The output will list the VM’s and which host they were on. I cut off the output for security purposes.

Running Dell DSET Remotely on ESXi 5.1 / 5.5

UPDATE: These instructions do work for ESXi 5.5 U1

These instructions will allow you to get a DSET for ESXi from the command line of a windows server.  In order to do this, you will need to have your Dell OMSA VIB package installed.  For 5.1 the current version is 7.2 at the time of this writing.  The package can be found here:

Next, you will need to download the Dell Windows DSET utility which can be found here: .  Once downloaded, run the installer and install the DSET Collector.
Open the CLI from your program files per screenshot below.


At the command prompt enter this line and it will prompt for password: C:\Program Files (x86)\Dell\AdvDiags\DSET\bin>DellSystemInfo.exe -s HOSTNAME -u root -d hw -n root/dcim/sysman -r   .  I have seen issues if your password has special characters at the beginning.  So, if it keeps failing try changing root to something different and then change back after collection.

dset-3Dset will collect information and put it into a filename that was specified in the command to your Desktop or you can point it to where you want it exported to.


Upload your DSET and troubleshoot your issues!

VCenter 5.0 to 5.1 U1 Upgrade while Separating or Splitting out Services (Part 4): Vcenter Service

We are now to the final piece to get the base 5.1 U1 upgrade completed.  In this first part, we need to uninstall the original inventory service and in order to do this we must uninstall the Vcenter service.  So, be sure to put in a change control or notify anyone that your Vcenter will be down during this time.   Important!  Your local accounts will not be imported into the permissions on your upgrade.  In order to use local non domain users they must be on your SSO server, but this is not the recommended method.

1. Log on to your Vcenter server.  Go to Control Panel and select Uninstall a program.


2.  Find the Vmware Vcenter Service and choose uninstall.


3.  Hit yes and uninstall the service, but don’t remove database if the option is given.


4.  Start Vcenter Installer and choose Vcenter installation or open Vcenter installer directly from its subfolder.

vc-15.  Enter your license key or choose to skip and enter it

6.  Choose use existing database and select your DSN.

vc-37.  Enter the database username and existing password


8.  The warning below will appear if you are using Vmware Update Manager which is most likely the case in most enterprises.  This just means you will not be able to use VUM until you upgrade that component. Which I recommend doing right after this upgrade.


9.  Choose to Upgrade your existing Vcenter Server Database.  Be sure to have a backup prior to continuing if you didn’t have one already!


10. Choose automatic to update the hosts with the new agent.  This should not cause any downtime, but be sure to have a Change Control in place if your enterprise requires it to cover your bases.


11.  Choose SYSTEM account or run the service under your standard.  Make sure the FQDN of your Vcenter server is correct.


12.  Take default ports or change to your needs.


13.  Set the JVM size based on your environment, but I always go larger if you feel you will grow into it over time.  This can be modified later if

13.  Enter your SSO FQDN and Username/Password that was created in part 1.


13.  You will see this warning if you have users that were local.  It will store them in the system temp folder which should be %temp%


14.  Enter your Inventory Service Server FQDN that was created in Part 3.


15.  Select the location to install Vcenter to.


16.  Wait for Vcenter install to

17.  Once complete, you are done and ready to test your login.  Load up the web client http://Vcentername:9443 and attempt to login.  If you have it correct, you should see your Vcenter listed.  If something with your SSO or login isn’t correct, you may not see your Vcenter.  Double check you have the right Domains added under the web client configuration.  You can still use the fat client if you need to get into Vcenter while you troubleshoot your Web Client/SSO.


Vcenter Installation is done!  Now you will want to go upgrade Vmware Update Manager.  It is basically the same process that we did here.  You run Vum installer and choose to upgrade your database.  The only caveat with VUM is that it only has scanning and compliance in the web client.  You must still use the VI client with 5.1 in order to create baselines and upgrade your hosts.  In future postings, I will show how to create a baseline in VUM, create your own iso, and update hosts.

VCenter 5.0 to 5.1 U1 Upgrade while Separating or Splitting out Services (Part 3): Inventory Service

As part of this series, we have already install SSO and the web client.  We will now be installing inventory on it’s own server.  The inventory service contains it’s own local database that is created during installation.  It does not need a SQL database, but I am not quite sure what it is using.  The inventory service install does not really contain anything until we get to Part 4 when we upgrade Vcenter and connect it to the inventory service.

1.  Log onto the server that you will be installing the inventory service.

2. Double click the auto install of your Vcenter Download and select inventory service or browse directly to the install for this component and double click.  Hit Next.


3.  Select the install directory and hit next.


4.  Enter the FQDN of this server if not already populated and hit next.


5.  Take default ports or change them to your organization’s standard and hit next.


6.  Select the Java heap size for your environment.  In my opinion it doesn’t hurt to go one size larger if you ever think your environment will grow.


7.  Enter the FQDN or your SSO server that was built in Part 1 and enter the admin@System-Domain password.


8.  Install the default self signed certificates for the inventory service.  You can replace them with CA certificates at a later time if need be.


9.  Begin the install and wait for it to finish.


10.  Click finish on the install and on to the last part!


Next part will be getting the Vcenter service upgraded and pointed to the new SSO/Inventory servers.