Attempting an installation of vRealize Operations Manager 6.0 on Windows Server 2008 R2 fails with the following message:-
Error Running PostInstall Script – Unfortunately, an error was encountered running the Post-Install and First Boot scripts.
After completely uninstalling the previous vROps installation via the Control Panel, and completing a reboot of the system, I tried the installation again. My initial attempt was directed at the default directory (c:\vmware\vcenter-operations), this failed. A subsquent attempt followed, directing the install at a different directory name (c:\vmware-vrops\vcenter-operations). Both installs failed with the above error. Right then, time to make a coffee to widen my eyes and troll through the numerous logs as stated in the above error 🙂
I found the most informative logs were vcops-firstboot.py_log and postinstall.log
In order to resolve this and complete a successful installation, I performed the following steps. I’m not stating all of these steps are actually required, and I’m not sure this is entirely supported, however these are the steps that worked for me. I wanted to make sure I cleaned up the operating system as best as possible.
- Snapshot or backup the virtual machine
Delete the contents in the following folders
Note: I previously performed the installation using the local administrator account which is why I cleaned up this folder.
Delete the following folders
Perform pegistry searches and remove the following entries relating to:-
Note: Just to repeat, I’m not stating all of these are required, however I cleaned them all up.
Note: Also, your Data folder may be located elsewhere
- Reboot the Guest OS
- Run installer as Administrator (standard stuff)
- Default folder for C:\
- Data folder changed to D:\ (your location may be different)
I’ve performed these tasks on two different virtual machines. Just a word of caution as always before attempting the above – Use your own judgement to decide if the above steps are suitable for your environment.
Hopefully this helps anyone who comes across this error and saves a little time 🙂