Saturday, October 17, 2009 3:03 PMI'm attempting to install SCVMM 2008 R2 onto a Windows 2008 Standard SP2 x64 operating system. The setup proceeds to the point where the progress box says:
Please wait while the Setup prepares to install the VMM server...
It displays this for a few seconds and then the progress box disappears. After which there is nothing. There is no further troubleshooting information that I can find though I'm sure there should be a log file somewhere?
The VMM Configuration Analyser returns with no issues found. Setup is being run elevated. I preinstalled WAIK but thet didn't help. The server is running SCOM.
Using the command-line is even worse (setup /server /i /f <path>\VMServer.ini ) because you don't even get to see something disappear: Nothing appears, nothing happens. No log option it seems. Helpful isn't it.
How can I get something intelligent out of Setup.exe?
Monday, October 19, 2009 10:49 AMI thought that maybe I shouldn't install on a virtual machine (I tried two) as I don't think this is encouraged. So I tried it on a physical Windows 2008 R2 RTM machine (actually the Hyper-V host).
Exactly the same.
No explanations, no logs that I can find, no nothing: The progress box just disappears and that's the end of it!
I'm failing to install the MSDN download of SCVMM R2. Can I have a copy of what everyone else is using!
[Update] I've also just spent hours downloading the Evaluation edition: It does exactly the same. So it isn't the media or the edition. These are very uncomplicated servers, why is this installation failing on every server I try it on? What are the rest of you doing? Where can I find the installation log that presumably will tell me what went wrong and where?
[Update] I've found an installation log! If I ignore Setup.exe and just run the msi file then it creates a log that says: "Launch Setup.exe for installing Virtual Machine Manager Server"... Wowww!
Monday, October 19, 2009 6:16 PMYou should be able to find the setup logs in this location : Programdata\VMMLogs. Example: c:\ProgramData\VMMLogs. There are logs for each setup component - serversetuplog, clientSetupLog and AgentSetuplog. ServerInspectReport should have the pre-requisite inspection report.
Monday, October 19, 2009 6:38 PMThank you Psridhar,
If only it was that simple...
No logs, no C:\ProgramData\VMMLogs folder for that matter. The same on all servers tried.
[Update] It does copy a load of install files successfully to the %temp% folder including the vmmServer.msi file: It seems to then fail to hand over to these files.
Tuesday, October 20, 2009 3:33 PM____'s teeth: It does exactly the same thing for the SCVMM 2008 R1 installation too!!!
I cannot even attempt to install the administrative console on a physical Vista machine. I've now tried four different machines around the organisation and not one gets past the "please wait while..." dialog box. Is there is something in our infrastructure that SCVMM just cannot cope with?
Surely I do not run an utterly unique infrastructure? Someone out there must know what I'm talking about?
Is there anyway I can bypass the obviously defective "Setup.exe" and just cut straight to the MSI?
Tuesday, October 20, 2009 3:54 PMRight, here's getting somewhere. Well actually I'm getting no-where but it might point to the problem:
If I logon as the local Administrator I cannot install the server because it tells me a domain account is required. At least the defective Setup has told me something! However, if I attemp to install the Administrative console with this account it actually WORKS!!!
But if I use any domain account, including the built-in Administrator and admin accounts in Domain Admins, Enterprise Admins and Schema Admins, I cannot even install the Admin console, let alone the Server component. The setup fails without any logs, any events or any messages what so ever.
Now does anyone know what I'm talking about?
Wednesday, October 21, 2009 11:31 AMAs I can't get any help on this bone-headed defective installation I've tried the following:
The install copies the installation files to the hard-drive (%TEMP%) where they are left when the installation fails. You are not allowed to run the SetupVM.exe left behind because it tells you to run Setup.exe; however it does appear to take the same command-line options. So I edited the VMServer.ini file in the temporary setup folder to:
# CompanyName=Microsoft Corporation
ProgramFiles=C:\Program Files\Microsoft System Center Virtual Machine Manager 2008 R2
# DatabaseFiles=D:\ProgramData\Microsoft\System Center Virtual Machine Manager\Database
LibrarySharePath=D:\ProgramData\Microsoft\System Center Virtual Machine Manager\Library Files
LibraryShareDescription=Default Virtual Machine Manager library files location
And ran the following from the same folder (elevated of course):
SetupVM.exe /server /i /f VMServer.ini /L %TEMP%\SetupVM.log /VMMServiceDomain MYDOMAIN /VMMServiceUserName scvmmservice /VMMServiceUserPassword password
It ran! Task Manager confirmed MSIEXEC was running in the background (this is an unattended install) but after a few minutes ended with:
Configuration of Virtual Machine Manager failed. (ID:292)
But now I've got a log file! Seems the setup location is missing some files (!!!). Eventually I end up copying the VMMData, i386 and amd64 folders from the DVD to the temporary setup location. Put the service account back into local Administrators again because SetupVM.exe is too stupid to figure out that it is a member of a group nested in Administrators (Administrators is a Group Policy restricted group here). And the result:
I've now got to play the same games getting other components installed. I'll post the results here.
[NOTE] I am using the SetupVM.exe file copied by Setup.exe to the %TEMP% here. I cannot use the similar published command-line options with Setup.exe direct from the DVD because it will silently fail just like the GUI setup.
Wednesday, October 21, 2009 5:22 PMNot quite there!
While I can install the Administrator Console using the local Administrator account and avoid the above messing about, I cannot configure Operations Manager with this account.
However, there doesn't appear to be a command-line option to configure Operations Manager. I'm stuck again!
I'll open another thread for this.
Thursday, October 22, 2009 8:19 AMGetting the Operations Manager integration running was no trouble: I just had to read the documentation!
This manual installation means I can almost avoid the despicable Setup.exe: I only need it to install the Administrator Console, and that actually works if I use the machine's local Administrator account.
Only the Self-service Portal to deal with now, and I expect it to fall to the same work-a-round as the Server setup.
- Marked As Answer by Frogbit Thursday, October 22, 2009 8:19 AM
Thursday, October 22, 2009 8:25 AMThere is something troubling in all this:
A month or so ago I was installing the CLM components of ILM-2 RC0: It would not install and created no logs to say why. Eventually it installed using the command-line (MSIEXEC in that case). Sounds familiar!
What is Microsoft up to with its GUI installs?
Over the next few months am I going to find that cannot install any Microsoft products into my environment using the GUI setup?
- Proposed As Answer by Waleed Al Mahmeed Wednesday, November 04, 2009 5:41 AM
Wednesday, November 04, 2009 5:43 AMPlease, burn the downloaded MSDN image into DVD and then try the installation. This has solved my problem like charm.
Saturday, November 07, 2009 9:40 AMI was burning a DVD to install the console on physical workstations. They have exactly the same problem: I cannot install using "setup.exe". However in these cases where I'm only installing the console I can use "setup.exe" with a local administrator account (not domain account) rather than resort to tricks from the command-line.
There is something in our AD domain environment that is preventing setup from working. I don't think it is Group Policy because I have tried accounts with "Domain Admin" like permissions (including the built-in Administrator account) that have been isolated from most policies.
I'd really like to know what Microsoft is up to before I find I can no longer install any of their products!
Wednesday, April 11, 2012 12:08 PM
I faced the same problem.... And after lot of trial and error finally got a resolution for it.
Install all components manually before starting SCVMM setup:
1. Make sure server 2008 R2 is UPDATED.
2. Enable IIS on the server.
3. Install Microsoft .NET Framework 3.0 or 3.0 SP1 (http://www.microsoft.com/download/en/details.aspx?id=3005)
4. Install SQL server 2008 R2.
5. Install latest version of AIK (http://www.microsoft.com/download/en/details.aspx?id=5753)
6. Now proceed with installing SCVMM.
Worked for me ..Finally !!