How to install vCenter Server and Update Manager 5.0 on Windows 7 64-bit

How to install vCenter Server and Update Manager 5.0 on Windows 7 64-bit

I published solution "How to install vCenter Server 4.1 on Windows 7 64-bit" some time ago,

you can find it here:

Now I come with guide "How to install vCenter Server and/ or Update Manager 5.0 on Windows 7 64-bit",

because this OS again is not supported for this applications. Unfortunately.

It isn't supported but it works. Fortunately.

Preamble warning: this hacking is not supported by VMware !

1/ extract iso image of vCenter Server (e.g. in 7zip) to any folder in destination machine

2/ download application for editing msi file e.g. Insted from and install it

3/ run Insted and open file ...\vCenter-Server\VMware vCenter Server.msi

4/ in Tables click on item "LaunchCondition"

5/ on the right find row with text:

Installed Or ((MsiNTProductType = 3) And (VersionNT > 502 Or (VersionNT = 502 And ServicePackLevel >= 2)))

and modify it to:

Installed Or ((MsiNTProductType = 1) And (VersionNT > 502 Or (VersionNT > 502 And ServicePackLevel >= 0)))

after that save and close

6/ in Insted open file ...\UpdateManager\VMware vSphere Update Manager.msi

7/ in Tables click on item "LaunchCondition"

8/ on the right find row with text:

(MsiNTProductType = 3) And (VersionNT > 502 Or (VersionNT = 502 And ServicePackLevel >= 2))

and modify it to:

(MsiNTProductType = 1) And (VersionNT > 502 Or (VersionNT > 502 And ServicePackLevel >= 0))

after that save and close

9/ download 64-bit version of Microsoft AD LDS (new name for ADAM) from:

and install it

10/ run ..\autorun.exe to install vCenter Server and Update Manager ...


- tested only on Windows 7 Professional SP1 English

- Power Settings in Windows 7 setup on High Performance

- if OS Windows 7 is member of domain, one thing is important: person doing all that installations must be signed as domain administrator not as local administrator

- I have UAC disabled

- I believe that it will work on Windows Vista 64-bit too

- this procedure was successfully tested for upgrade from vCenter Server 4.1 U1 too

Optimalizations (optional):

- disable IP6 if is not need (and service IP Helper)

- disable unnecessary services as Desktop Window Manager Session Manager, Security Center, Superfetch,

Themes, Windows Audio, Windows Audio Endpoint Builder, Windows Defender, Windows Search

If backup is realized at the VMware level, you should enable Auto Shrink for database VIM_VCDB in SQL Server 2008 Management Studio Express.

Good luck.

Tags (3)

at the moment it will not work if you choose german language. You will get absurdity messages. If you choose english the installer works.

Thanks!  Smiley Happy

Thanks vlho Smiley Happy

I would like to say thanks, but since this howto is not complete and doesn't work, I won't. Smiley Wink

When using the above howto, the install of vCenter Server stops with Wrong input – either a command line argument is wrong, a file cannot be found or the spec file doesn’t contain the required information, or the clocks on the two systems are not synchronized. Check vm_ssoreg.log in system temporary folder for details.

But the log is nowhere to be found.

After some trial and error, this worked here:

These two

\vCenter-Server\VMware vCenter Server.msi

\UpdateManager\VMware vSphere Update Manager.msi

are not the only ones that need modifying.

\Single Sign On\vCenter Single Sign On.msi

needs modifying as well.

After installing Microsoft AD LDS, first manually (without using autorun.exe) install Single Sign On, then Inventory Service, followed by vCenter Server which will now install without problems..

However, Update Manager will not install and stops with an error: vCenter Server credentials could not be validated.

Google says there are spaces in the environment variables, not the case here. Turned UAC off, didn't help. Run as admin didn't do anything either.

Who knows how to fix this?

Hi bartgrefte,

I know, look here:

During install wizard try define Username in format: DOMAIN\administrator

no administrator only...

Tried that, same problem.

However, I can logon using the web client without problems. But the same credentials do not work with the update manager, same error as before.

Version history
Revision #:
1 of 1
Last update:
‎08-26-2011 06:54 AM
Updated by: