I found the installer was trying to run a non-existing file "ocsetup.exe" at this step, weird thing is vCenter installer doesn't complain about that, it only waits, the log file is under %temp%\vminst.log.
- VMware VirtualCenter-build-1235232: 11/27/13 09:48:55 Begin Logging
- VMware VirtualCenter-build-1235232: 11/27/13 09:48:55 --- CA exec: VMAdamInstall
- VMware VirtualCenter-build-1235232: 11/27/13 09:48:55 Getting Property CustomActionData = 603;603;C:\Users\ADMINI~1.VML\AppData\Local\Temp\{A4400513-2688-45A9-8439-CA991F4E4106};C:\Windows\SysWOW64\;C:\Windows\system32\;C:\Windows\ADAM\
- VMware VirtualCenter-build-1235232: 11/27/13 09:48:55 setupApp = [C:\Windows\system32\ocsetup.exe]
- VMware VirtualCenter-build-1235232: 11/27/13 09:48:55 --- function: SetupComponentOnWindows
- VMware VirtualCenter-build-1235232: 11/27/13 09:48:55 [C:\Windows\system32\cmd.exe /c start /w C:\Windows\system32\ocsetup.exe DirectoryServices-ADAM /passive /norestart]
- VMware VirtualCenter-build-1235232: 11/27/13 09:48:55 Util_Launch::Wait: 1 Hide: 1
- VMware VirtualCenter-build-1235232: 11/27/13 09:48:55 Found "C:\Windows\system32\cmd.exe"
- VMware VirtualCenter-build-1235232: 11/27/13 09:48:55 Attempting to launch ["C:\Windows\system32\cmd.exe" /c start /w C:\Windows\system32\ocsetup.exe DirectoryServices-ADAM /passive /norestart]
I copied ocsetup.exe file from a Windows Server 2008 R2 server's system32 to C:\Windows\system32 folder on Windows Server 2012 R2.
- VMware VirtualCenter-build-1235232: 11/27/13 10:40:44 Attempting to launch ["C:\Windows\system32\cmd.exe" /c start /w C:\Windows\system32\ocsetup.exe DirectoryServices-ADAM /passive /norestart]
- VMware VirtualCenter-build-1235232: 11/27/13 10:41:11 Process returned 0
Hope it helps.
No comments:
Post a Comment