Microsof recently announced the final release of System Center Virtual Machine Manager (SCVMM) 2008 R2 SP1. This service pack release provides support for Dynamic Memory and RemoteFX – features which were added to Hyper-V with Server 2008 R2 SP1.
Because my home Hyper-V system makes heavy use of Dynamic Memory, I’ve been running the RC build of SCVMM 2008 R2 SP1, and it’s been doing the job without a hitch. However, one of the claims of the RC is that there’s a smooth upgrade path from the RC to the final release, so after downloading the RTM from TechNet, I got upgrading.
My SCVMM system is slightly different from the default configuration in that it uses a remote SQL server for the SCVMM database, and it uses a Managed Service Account in AD to run the SCVMM service and to communicate with the agent on the host Hyper-V server.
After mounting the product ISO and launching Autorun, I selected “VMM Server” on the splash screen:
And of COURSE I read the EULA most carefully:
The installer detected an existing installation of SCVMM 2008 R2 SP1 and prompted for an upgrade:
I was then prompted to enter domain credentials to connect to the SQL server. The ones I’d logged in with were sufficient.
And then – error message and the whole process came crashing to a halt.
This was a wierd one – the credentials were definitely good, but why was the installer looking for an RTM database when it knew full well that this was an RC-to-RTM upgrade?
After a bit of digging around, I just back onto the Microsoft Connect page for the RC version and found a utility called “VMM 2008 R2 SP1 RC to RTM Upgrade Tool”, the description being “When upgrading from the SCVMM 2008 R2 SP1 Release Candidate to SCVMM 2008 R2 SP1 RTM this tool is required to complete the upgrade.”
Fair enough – would have been good to know earlier, I guess. Still – downloaded the tool, which is a command-line utility used to upgrade the SCVMM database on the SQL server:
Once complete, I re-ran the installer but BOOM – same error.
So – some more digging ensued, and it turns out that (according to the TechNet document which I guess I should have read first) you do have to uninstall the VMM server. So, I ran the uninstaller from Programs and Features using the “Retain Data” option:
Once done, I re-ran the UpgradeVMMR2SP1RC utility from the SCVMM server and made sure everything was good in the logs, then re-ran the installer. This time, the installer just picked up the presence of the SCVMM Admin Console, which it proposed to upgrade. Once done, it ran a fresh install of SCVMM. The only difference between this install and the initial was that the installer picked up the settings for the existing VirtualManagerDB on the remote SQL server, as well as the existing Library share:
The one thing it didn’t pick up was that I’d been running SCVMM with an AD account – the installer defaulted back to the Local System account, so that had to be changed. After than it was pretty smooth sailing:
Once I logged back into the console, I was expecting to have to update the SCVMM agent on the host Hyper-V server, but that wasn’t necessary. Looks like the agent builds between the RC and the RTM are the same. The host looked good and all the VMs were ticking away, along with all the Dynamic Memory integration:
So – all is good (and the trial period which was in place on the RC is gone too!). It’s also a lesson to read the damn TechNet article first 🙂