This year is going to be a big one for System Center, with a whole raft of major product updates scheduled to be released later during 2012. Microsoft TechEds the world over are going to be chock-a-block with some excellent, and hopefully very exciting announcements and hands-on labs.
To get things rolling in my own little lab environment, I’m getting started with SCVMM 2012. The current release is Beta 2, so it will be interesting to see how the upgrade process through RC and RTM goes. If it’s anything like the experience with SCVMM 2008 and 2008 R2, it should be pretty good.
Read on for a step-by-step installation.
For the SCVMM 2012 server, I’ve got a Hyper-V VM running Server 2008 R2 Enterprise SP1 with 4GB RAM allocated – of course, in the wonderful world that is Dynamic Memory, it’s not actually using 4GB. That is just the allocated amount so that the SCVMM installer passes the prerequisite check.
The SCVMM 2012 installer looks pretty similar to previous product versions:
Read that EULA exceptionally thoroughly, like you ALWAYS do
Select which product components to install:
This is just the beta so far, so no need for much in the way of identification or product keys:
We all love Windows Update – plus I’m curious to see how it will integrate over the lifecycle of the pre-release products:
And sure – let’s keep the default installation location
And d’oh! Installation prerequisite check failed, as SCVMM 2012 needs the Windows Automated Installation Kit to install. This was automatically installed with SCVMM 2008 R2, but not as it seems with 2012 (or at least, not in the pre-release versions).
So, I quickly installed the WAIK (available for download from here) and re-ran the checker. Again, some failures which I’ll summarise rather than screenshot everything:
- Windows Automated Installation Kit (WAIK)
- Windows Remote Management (WinRM) service must be running – it has a delayed start, so it’s possible to encounter this issue if you kick off the installer too soon after a reboot
- SQL Server 2008 R2 Command Line Utilities (available from the SQL Server 2008 R2 Feature Pack page here, and the direct download for the 64-bit version is here). The SQL Server Native Client is also required (to be honest, it’s easier to perform the install from the SQL Server 2008 R2 media)
Once the prerequisites are passed, choose a SQL server to use – because there’s a pre-existing VMM database, I changed the default name slightly:
I prefer to use an AD account for the VMM service account rather than the local SYSTEM account – it gives greater portability down the line, especially if you want to move the VMM database, and it’s also needed for shared ISOs. This domain account needs to be a member of the local Administrators group on the VMM server:
Leave the network ports as default:
And set up a new SCVMM library share:
And away goes the installer – STOP! Coffee time….
Once complete, I launched the SCVMM Console and added a new Hyper-V host. It’s actually the same host which is currently managed by the SCVMM 2008 R2 SP1 system, so I’ll be breaking that particular management relationship:
The host is a Windows machine on an AD domain:
Select the credentials to be used (I’ll go through setting up a RunAs account in another blog post). The account specified cannot be the same account used for the SCVMM server and it has to be a member of the local Administrators account on the host:
There’s no upgrade path from SCVMM 2008 R2 to SCVMM 2012, so if a Hyper-V host has a 2008 R2 version of the SCVMM agent, the SCVMM 2012 Add Host wizard will error. The agent needs to be manually uninstalled first. Once complete, the host and all the VMs are available for management – nice!