You are getting a Host IPMI System Event Log Status Alarm on an ESXi/ESX Host.


To clear the log and reset the sensors:

Step # 1

In the vCenter Inventory, select the ESXi/ESX host that has this Alert

Step # 2

Click the Alarms tab, to verify that this ESXi/ESX host does in fact have the Alert.

Step # 3

Click the Hardware Status tab.

Step # 4

Click on the drop down button with Sensors and switch it to System event log.


Step # 5

Click on Reset event log.


You will now see that you are Resetting System event log


Step # 6

Click Reset Sensors to reset the host sensors.

Step # 7

You should now see this message.


Or if you Update your view you might see this message.


You should now have a cleared System Event Log File.

Step # 9

You will now need to Acknowledge Alarm and Clear.

You are finally done!


Issue:You need to either increase or decrease these settings, after installation with the wizard.Since there is not a utility to re-run to adjust either of these settings, you have to do it manually.1) Size of log file before rotation: = <maxSize>10</maxSize>2) Log rotations to keep: = <rotate>50</rotate>
Fix:You will need to edit an XML file, I recommend using Notepad++ for this task.Here is the file location for each OS.1) Windows Server 2003C:\Users\All Users\VMware\VMware Syslog Collector\vmconfig-syslog.xml

2) Windows Server 2008/2012

C:\ProgramData\VMware\VMware Syslog Collector\vmconfig-syslog.xml

Once you have located the above referenced file, make a backup copy of it.You will need to edit this file as an Administrator, if using Notepad++, just run it as an Administrator.Then find the XML Element <defaultvalues>, this is where you will be making your changes.<defaultValues><port>514</port><protocol>TCP,UDP</protocol><maxSize>10</maxSize>




Now you can change either the maxSize in Megabytes, or the Rotate count.

Next, re-start the VMware vSphere Syslog Collector Service.

Here is a screen shot of the original wizard where you made the selections, or went with the defaults, now you find yourself needing to make a change.


Step # 1
Now we will make changes to your Power Options.Click on the Start button.

Next, click on Control Panel, then Hardware and Sound, and Power Options.


Now, click the down arrow, to the right of Show additional plans and then select High performance.

Step # 2
Now we will make a few changes to this Power Plan, within the Preferred Plans Section.Make sure that you Click on the Change plan settings, next to High performance.

Next, set both the Display and Sleep settings to Never.


Click the Save changes button.

These changes are done.

Step # 3
Now click on Change plan settings, next to High performance, and then click Change advanced power settings.We have a few changes to make within the Advanced Settings area.

First, click on Hard disk, then Turn off hard disk after, next change the setting to Never.


Second, click on Display, then Turn off display after, next change the setting to Never.


Then Click on Apply and then the Ok button.

These two changes are done.

Step # 4
Now we will make changes to our Ethernet Adapter.Click on the Start button.

Next, click on Control Panel, then Network and Internet.

Click on Network and Sharing Center, then Change adapter settings.

Next, we will select Local Area Connection, then Right-Click and choose Properties.

Check that within the Connect using: dialog box you’re Virtual Network Card (vNIC) is shown.

Next, click the Configure… button.

Now, click the Power Management Tab.

Then uncheck “Allow the computer to turn off this device to save power”.


Then click the Ok button.

This change is done.

If you are running vCheck Daily Report to perform Health Checks on your VMware Environment.
You might have virtual machines that are listed under “Guest with wrong OS”.


1) Guests with wrong OS

2) Virtual machines with incorrect OS configuration:

Guests with wrong OS

The following virtual machines contain operating systems other than the ones selected in the VM configuration.
Name InstalledOS SelectedOS
Server01 Microsoft Windows Server 2008 R2 (64-bit) Microsoft Windows Server 2008 (64-bit)


Virtual machines with incorrect OS configuration : 1

The following virtual machines have an installed OS that is different from the configured OS. This can impact the performance of the virtual machine.
Name GuestId Guest OS Configured GuestId Configured Guest OS
Server01 windows7Server64Guest Microsoft Windows Server 2008 R2 (64-bit) winLonghorn64Guest Microsoft Windows Server 2008 (64-bit)


Change the Configured Guest Operating System in the vSphere Client and/or Web Client

When you change the guest operating system type in the virtual machine settings, you change the setting for the guest operating system inside the virtual machine’s configuration file.

This will not change the guest operating system itself. If you need to change the guest operating system you will need to reinstall the operating system, this just changes the virtual machine’s configuration file settings.

When you set the guest operating system type for a new virtual machine, vCenter Server chooses configuration defaults based on the guest type. Changing the guest operating system type after the virtual machine is created does not retroactively change those settings.


1) Power off the virtual machine.

Procedure for vSphere Client

1) In the vSphere Client inventory, right-click the virtual machine and select Edit Settings.

2) Click the Options tab and select General Options.

3) Select a guest operating system type and version.

4) Click OK to save your changes and close the dialog box.

The virtual machine configuration parameters for the guest operating system are changed.

Procedure for vSphere Web Client

1) In the vSphere Web Client, select vCenter then under inventory trees, select VMs and Templates, then virtual machines.

2) Next, select your virtual machine and then right-click and select Edit Settings.

3) Select the VM Options tab, next expand General Options, now you can change the Guest OS and Guest OS Version.

The virtual machine configuration parameters for the guest operating system are changed.

More information on vCheck Daily Reports can be found over at Alan’s Web Site:

Failed to connect to VMware Lookup Service
https://vCVA_IP_address:7444/lookupservice/sdk – SSL
certificate verification failed.
You will need to toggle the certificate settings on the VMware vCenter Server Appliance (vCSA).

To toggle the certificate settings:

  1. Log in to the vCenter Server Appliance Web interface at https://hostname:5480/.
  2. Click the Admin tab.
  3. Regenerate certificates:
    • vCenter Server 5.1: Select Toggle certificate setting so that the Certificate regeneration enabled displays Yes.
    • vCenter Server 5.5: Select Yes under Certificate regeneration enabled.
  4. Reboot the vCenter Server Appliance.
  5. After the vCenter Server Appliance reboots, confirm that the Certificate regeneration enabled option is set to disabled.

vCenter Server generates new default certificates using this option. For systems that use custom certificates, regenerate the certificates manually.

Further Information on this issue can be found over at VMware Knowledge Base article number (2033338)
Troubleshooting the vCenter Server Appliance with Single Sign-On login (2033338)