SCVMM 2012 SP1 Install Notes and Steps
After I downloaded SP1 RTM bits, I decided to go through the installation once more and check out the VMM SP1 RTM requirements. I will be going through the install steps and provide some brief information on the requirements.
To start with, for Management server (without library server - for library space you need more space), the recommended system requirements (for up to managing 150 hosts) are 2-dual core 2.8GHz+, 4 GB memory, 40 GB for VMM, and 100 for SQL if it is local.
- VMM 2012 can be installed on Windows Server 2008 R2
- VMM 2012 SP1 can be installed on Windows Server 2012
Note: If virtualized and Dynamic memory used, the start-up memory should be at least 2048MB.
Additional Software Needed:
1. .NET Framework
- VMM 2012 on Windows 2008 R2 requires 3.5. Setup will install automatically.
- VMM 2012 SP1 requires 4.0 or 4.5 framework. 4.5 is included in Windows 2012. 4.5 is located here: Full version, Web installer
- VMM 2012: AIK for Windows 7
- VMM 2012 SP1: Windows Assessment and Deployment Kit (ADK) for Windows 8: Web installer (install Deployment Tools and the Windows Preinstallation Environment), for full installation files, select “Download the Assessment and Deployment Kit for installation on a separate computer” and save the installer.
- 2. Deployment and Installation Kit:
- 3. SQL for VMM Database
- If installed separately, the recommended specs is similar to the above for the DB:
Dual core, 2 GHz, 4 GB memory, 150 GB space for up to 150 hosts.
- VMM 2012 supports
SQL 2008 R2 (64 bit) SP1- (standard/Enterprise/Datacenter)
SQL 2008 SP2+ (standard/Enterprise)
- VMM 2012 SP1 supports:
SQL 2008 R2 (64 bit) SP1+ (standard/Enterprise/Datacenter)
SQL 2012 (all editions)
- VMM 2012 sp1: 2008 R2 SP1+ or Windows 2012
- VMM 2012: Windows 2008 R2 SP1-, 2008 SP2
(if installed on a separate server)
- NO SQL EXPRESS SUPPORT
- Needs case-insensitive collation
- Only Database Engine Services and the Management Tools are needed
- !!! VMM Self-Service Portal is no longer available with SP1 !!!!
- if you want to manage Windows 2012 Hyper-V hosts (and 2008 R2), you need VMM 2012 SP1. VMM 2012 can only manage 2008 R2, and 2008 SP2 hosts.
- !!! The server name cannot contains character string of –SCVMM-
- It is not supported to change VMM service account after the installation. You need to uninstall and reinstall if necessary.
- If domain account used, it must be added to local administrators group
- For ISO shared images, disjoint namespaces, or highly-available VMM server, domain account needs to be used.
Distributed Key Management:
VMM encrypts some data in its database such as run as accounts, passwords etc. For encryption, the local computer account and the service account VMM runs under is used. This is why if you reinstall VMM on another server, all run as accounts, passwords in profiles is getting removed. With Distributed Key Management, by storing encryption keys in AD DS, you can now move your VMM server. DKM also needed for high available installs since when the node failovers, VMM needs to be able to decrypt the data.
- Required for high-available deployments
- Need to pre-create a container in AD in the same domain as VMM and service account, eg, CN=VMMDKM, DC=contoso,DC=com
- VMM service account needs to have full control over this container (This object and all descendant objects)
Now, lets do basic installation; one VMM Management server (2012 SP1) over Windows 2012 with SQL 2012, and with DKM in AD DS.
- First, install the prereqs:
- 1. If already not installed, enable .NET Framework 4.5. It should be enabled by default.
2. Install ADK.
Now we only have the followings installed:
3. Install SQL
SQL Install enables .NET Framework 3.5
After SQL install completes, the features installed:
Note: If you install .NET 3.5 by yourself via Add roles and Features Wizard, you need windows 2012 source media:
Steps are self-explanatory.
For license, if you do not enter product key, it will be 180-days trial. You can later change trial version to full version by entering the key.
For the next screen below, do not forget to create a Container in AD DS for DKM, and service account for VMM. The service account will also need to be added to local administrator group.
Default Ports used by SCVMM:
8100 – Communication with the VMM console
5985 – Communication to agents on hosts and library servers
443 – File transfers to agents on hosts and library servers
8102 – Communication with Windows Deployment Services
8101 – Communication with Windows Preinstallation Environment (Windows PE) agents
8103 – Communication with Windows PE agent for time synchronization
VMM Setup logs are located at “C:\ProgramData\VMMLogs”. Log folder contains the following files:
For this install I intentionally did not create a container for DKM. Luckily, it has been created by VMM by using the account (domain admin) running the setup. However, the service account did not have any permissions on the container. It did have “read” via “authenticated users”. I gave full permission to the service account manually.
Post Install : (
My install ended up with some warnings:
The Service Principal Name (SPN) could not be registered in Active Directory Domain Services (AD DS) for the VMM management server.
1) Use setspn.exe to create SPN for vmmserver using following command "C:\Windows\system32\setspn.exe -S SCVMM/scvmm.bt.local BT\vmmservice".
2) Add SPN values to following registry key "Software\Microsoft\Microsoft System Center Virtual Machine Manager Server\Setup\VmmServicePrincipalNames".
3) Run "C:\Program Files\Microsoft System Center 2012\Virtual Machine Manager\setup\ConfigureSCPTool.exe -install" to configure SCP.
If SPN and SCP are not registered, VMM consoles on other computers will not be able to connect to this VMM management server and deploying a Hyper-V host to a bare-metal computer will not work.
The logs have the same warning but no explanations:
12:59:00:Start setspn.exe parameters -S SCVMM/scvmm.bt.local BT\vmmservice
12:59:01:Setspn.exe failed with errorcode: 1
While I was blaming UAC being on, I then figured it out, I had already used the same SPN with another installation under different service account. –S Switch checks for duplicates and if exists aborts. I deleted the SPN’s from that account and re-registered it on vmmservice. I then completed step 2, and step 3.
After setup, installed features are:
And VMM setup is now completed:
Good luck : )