Monthly archives: February, 2014

Unable to install Microsoft Windows Server 2012 on VMware ESXi host – IBM System x

This will be a “note to self” kind of post. But I guest if you work with IBM or vendor based Windows Server media like IBM’s ROC/OEM you will run in to this. When you get the Windows Server 2012 R2 Datacenter ROC media from IBM, and try to install it in a VM on a IBM VMware vSphere host, you will get to a point where the installer stops and says :
“Please check with your computer manufacturer to resoleve ant issues your are having with this computer. These tools are built to only run on IBM Computers. Since this is not an IBM computer click OK to shutdown”
IBM Windows server 2012 R2 ROC Error
IBM has been so kind to include a system check, to see if the media is used on a non IBM server. This is okay, but in my case the host is a IBM System x! The checker is not designed to run on a VM so you have to do one of two things. 1) you could go out and find a retail Windows Server 2012 R2 DC OEM media that has no hardware vendor checker. 2) you can edit the .vmx file of the VM to add the SMBIOS.reflectHost and set it to true like this : SMBIOS.reflectHost = “true”. This updates the virtual machine BIOS with the IBM Original Equipment Manufacture (OEM) information required to use IBM-provided Operating System (OS) installation media. IBM addressed this with there Windows 2008/R2 ROC media, but it is still true with Windows Server 2012 R2.
Please leave a comment below if you have similar experiences with other vendors or any comment to this post. Thank!

The vExpert 2014 applications are now open!

Applications for the 2014 vExpert program are now open. You can submit your application at : This year there is a fast trackĀ application for 2013 vExpert. Also new for 2014 there will be a nomination for 2014 for those that did not make the first cut, to get in later on in the year. You have until March 6th to get your application.

Unable to initialize the Microsoft Exchange Information Store service

Okay, so I got this error in the event log (ID 5003) on a Exchange Server 2010, after a update and a reboot of the server. The Information store service could not start up
Event ID 5003: Unable to initialize the Microsoft Exchange Information Store service because the clocks on the client and on the server machine are skewed. This may be caused by a time change either in the client or the server machine, and may require a reboot of that machine. Other than that, verify that your domain is properly configured and is currently online.
The time was okay on the server and the DC (PDC) was okay. Then I checked the VMware tools to see if the “Time Sync” Feature of the vmware tools was disabled, and it was. I noticed after a second reboot that the time was off by 10 minutes, and then jumped back to the correct time!?. Then I looked at the VMware vSphere host in the “Time Configuration” the time was of by… you guest it.. 10 minutes! The host was set to sync with an external time server ( But the time was off anyway. So I decided to reboot the host, to see if the time was off by 10 minutes after a reboot and it was! Then I did another reboot and jumped in the UEFI (BIOS) of the server and there it was… time in the BIOS was 10 minutes behind. I corrected it and booted the host and now the time on the host and the VM was okay even after a reboot.
I hope that you can use this information, I know where I will look next time there is a time sync issue in a VM. Please leave a comment below if found the useful. Thanks!