I say all the below despite the fact that SCVMM is provided for trial as a virtual machine. My experience could have been machine or some other environment specific but nonetheless I give you the below…
In my experience the short and simple word when it comes to installing Systems Center Virtual Machine Manager 2008 R2 (SCVMM) is that you should not do this on a virtual disk. Here is my experience and long convoluted path to getting it installed.
I spent numerous hours last week trying to install SCVMM onto a virtual drive, a Hyper-V VHD specifically and continually would get either an outright crash during the final portion of the install or it would come back with a message stating that a file(s) it needed to access was locked.
Don’t confuse the statement that I was installing it onto a VHD with the idea that I was virtualizing the OS and software. In the first instance I was installing to an OS that was a native boot of Windows Server 2008 R2- but it was a VHD native boot. No luck. This is where I usually had the message that a file was locked. Eventually I did get a crash of the install process and SCVMM now sits on that machine unable to be installed or uninstalled. It shows in the list of installed programs despite and if an uninstall is attempted it simply crashes.
After finally getting stuck in no mans land between installed and uninstalled I decided I’d give it a try on a fresh virtual instance of Windows Server 2008 R2. Crash, Crash, Crash. No luck. One common denominator they both were using a VHD – one as a native boot disk the other as a disk for the virtual machine. The forums for SCVMM had some references to issues with SCVMM and installing/running on a VHD.
Let’s not use a VHD in the process.
Giving up that idea I knew I had to come up with a solution. The SCVMM install was a part of my Team Foundation Server 2010 Microsoft Test Lab Manager environment I was building out. Not to be deterred I decided I’d try it on a VMware instance. I have a not so powerful 64 bit server on which I run ESXi. The ESXi server (Cronenberg) runs my tiny home office AD right now and has room to run something like SCVMM. I started the VMware standalone converter to convert a sysprepped WIN 2K8 x64 VHD based image I use as a seed for all my servers. The converter reminded me after running the conversion process for a while that the target ESXi infrastructure server would not support x64 client. OH YEAH! That ESXi server is x64 but it’s an older Dell PowerEdge 830 server that does not have the proper hardware assisted virtualization technology in the chip to support x64 clients. Ughhh.. now what.
Then it hit me. I have a Toshiba Satellite R25-S3513 notebook on the shelf. It’s x64 and 4GB of RAM. Like the PowerEdge it has no hardware assisted virtualization but that is ok. I already had Windows Server 2008 hanging out on it. When I cranked it up it prompted for a Hard Drive Protection password. I knew the password but that function would have to go away as it’s not very suitable for a server that I’d want to restart unattended. Into the BIOS I go but the BIOS won’t allow the removal. Some research shows I need to use a Toshiba Utility to remove it.
More troubles.
I boot up the Toshiba, download the tool only to be told during installation that the OS is not supported for this application. So… I install a copy of Vista onto the machine just so that I can run this one tool. With the HDD password tool gone I push on a new Win 2K8 R2 onto the laptop. All is good. I install the SCVMM server and console first pass with no issues.
So far so good. I have not yet really used the server. I’ll let you know. That is on tap for sometime in the next 24 hours. I spent may many hours trying many things on a few different environments. Based on the threads I read do think there is a likelihood of SCVMM issues when installed to a VHD. I can’t be sure- there were many variables. I’d recommend you avoid it. As for vmdk… I have no idea. As I set up the rest of my MTLM environment I’ll keep you informed.
Just because I am curious I may try it under VMware with a VMDK and I may try to do a P2V on the machine that has it successfully installed and see if it runs fine virtualized and is mainly an issue as installation.
Then again I have a lot more stuff to do that ranks higher.