SDK installation problem on VM
- Hello,
I am trying to install .NET Services SDK on VMs (virtual windows/virtual pc). My disks are dynamic, with giggs of free space. Just before "Install" command I encounter a message box with the message "Please wait while the installer finishes determining your space disk requirements". The box never closes. I notest that all goes well if installing on the physical machine.
Have you any clue on that ?
The issue is important as we neet to have the Azure environment on VMs.
Thank you in advance.
Marius
Answers
Appearently seems to be an issue of Windows installer in virtual environments, not specific to the Azure package.
Go to command line in elevated security mode, and type:msiexec.exe -package MyPackage.msi -qr
This will basically run the installation package in quiet mode with reduced UI.
Else everything of the Azure Dev tools are working fine in VMs- Marked As Answer byMarius Zaharia Thursday, October 22, 2009 8:13 AM
All Replies
- Hello, the installation should work fine on VM, although I haven't tried with a dynamic disk. I don't know much about dynamic disks. But can you try to install something else? Does the installation fail only for .NET Services SDK?
Also, for a virtual hard disk, actually you can configure it to use, say 1000GB. But it won't occupy 1000GB on your physical hard disk. It only occupies the amont that the actual data is stored on the virtual disk. So a lot of features come from dynamic disk may not be so valueable on virtual disk. You may as well try to use a basic disk.
Lante, shanaolanxing This posting is provided "AS IS" with no warranties, and confers no rights. Appearently seems to be an issue of Windows installer in virtual environments, not specific to the Azure package.
Go to command line in elevated security mode, and type:msiexec.exe -package MyPackage.msi -qr
This will basically run the installation package in quiet mode with reduced UI.
Else everything of the Azure Dev tools are working fine in VMs- Marked As Answer byMarius Zaharia Thursday, October 22, 2009 8:13 AM
- Thank you all for the answers.
I continued myself the tests and I found also the solution:
a. as above (msiexec elevated)
b. more simple: open command line as Administrator, and then execute the MSI from the command line.
All goes smoothly after that.
I posted the resolution here also.
Thank you all, again.
Marius


