SCVMM 2012: Quickstart deployment guide

The following document will cover a basic install of System Center Virtual Machine Manager 2012 at a generic customer.  This is to be used as a template only, for a customer to implement as their own pilot or POC deployment guide.  It is intended to be general in nature and will require the customer to modify it to suit their specific data and processes.

SVCMM can be scaled to match the customer requirements. This document will cover a single server model, where all server roles are installed on a single VM/Server.

This is not an architecture guide or intended to be a design guide in any way.

  • Windows Server 2008 R2 SP1 Enterprise edition will be installed as the base OS for all platforms. All servers will be a member of the AD domain.
  • SQL 2008 R2 ENT edition with CU6 will be the base standard for all database and SQL reporting services.

High Level Deployment Process:


1.  In AD, create the following accounts and groups, according to your naming convention:

  • DOMAIN\scvmmsvc SCVMM Service Account account
  • DOMAIN\scvmmadmin SCVMM RunAs account for managing hosts
  • DOMAIN\sqlsvc SQL 2008 service account
  • DOMAIN\SCVMMAdmins SCVMM Administrators security group

2.  Add the “scvmmsvc” and “scvmmadmin” account to the “SCVMMAdmins” global group.

3.  Add the domain user accounts for yourself and your team to the SCVMMAdmins group.

4.  Install Windows Server 2008 R2 SP1 to all server role servers.

5.  Install Prerequisites and SQL 2008 R2.

6.  Install the SCVMM Server, Console, and Self Service Portal.

7.  Deploy SCVMM Agent to Hyper-V hosts.



1.  Install Windows Server 2008R2 SP1 to the SCVMM server.

2.  Ensure server has a minimum of 2GB of RAM.

3.  Add .Net 3.5.1 and IIS role. IIS is being added to support the self service portal.

From open powershell (as an administrator) and run the following:

Import-Module ServerManager


Add-WindowsFeature NET-Framework-Core,Web-Static-Content,Web-Default-Doc,Web-Dir-Browsing,Web-Http-Errors,Web-Http-Logging,Web-Request-Monitor,Web-Filtering,Web-Stat-Compression,Web-Mgmt-Console,Web-Metabase,Web-Asp-Net,Web-Windows-Auth -Restart

4.  Install .NET 4.0 to all servers

5.  Install all available Windows Updates.

6.  Join all servers to domain.

7.  Add the “DOMAIN\SCVMMAdmins” domain global group and the “DOMAIN\scvmmsvc” domain account explicitly to the Local Administrators group on each SCVMM server.

8.  Install the Windows Automated Installation Kit (AIK) 2.0.

9.  Install SQL 2008 R2 DB engine.

  • Setup is fairly straightforward. This document will not go into details and best practices for SQL configuration. Consult your DBA team to ensure your SQL deployment is configured for best practices according to your corporate standards.
  • Run setup, choose Installation > New Installation…
  • When prompted for feature selection, install ALL of the following:
    • Database Engine Services
  • Optionally – consider adding the following to ease administration:
    • Management Tools – Basic and Complete (for running queries and configuring SQL services)
  • On the Instance configuration, choose a default instance, or a named instance. Default instances are fine for testing and labs. Production clustered instances of SQL will generally be a named instance. For the purposes of the POC, choose default instance to keep things simple.
  • On the Server configuration screen, set SQL Server Agent to Automatic. Click “Use the same account for all SQL Server Services, and input the SQL service account and password we created earlier.
  • On the Collation Tab – make sure SQL_Latin1_General_CP1_CI_AS is selected, as that is the ONLY collation supported.
  • On the Account provisioning tab – add your personal domain user account or a group you already have set up for SQL admins. Alternatively, you can use the SCVMMAdmins global group here. This will grant more rights than is required to all SCVMM Admin accounts, but is fine for testing purposes of the POC.
  • On the Data Directories tab – set your drive letters correctly for your SQL databases, logs, TempDB, and backup.
  • Setup will complete.
  • Apply SQL 2008 R2 CU6
  • The update is very straightforward. Accept the defaults and update all features. When complete, reboot the SQL server.

Step by step deployment guide:

1. Install SCVMM 2012:

  • Log on using your domain user account that is a member of the SCVMMAdmins group.
  • Run Setup.exe
  • Click Install
  • Accept the license agreement and click Next.
  • Select:
    • VMM Server
    • VMM Administrator Console
    • VMM Self Service Portal
  • On the Product Registration – click Next.
  • Accept or change the default install path and click Next.
  • If you get any Prerequisite errors – resolve them. If you get any warnings, understand them and click Next to proceed.
  • On the Database Configuration screen, enter in the name of your SQL database server (SVCMM if using the locally installed SQL instance) and leave port blank. You can leave “use the following credentials” blank if you are installing to the local SQL server. You can enter credentials here to connect to a remote SQL server if your user account you are running setup as does not have enough rights over the instance to create a database. Ensure “New Database” is checked and use the default name or change it to suit your naming standards. Click Next when this screen is complete.
  • On the Account Configuration screen, enter the domain account for the SCVMM service account that we created earlier (DOMAIN\scvmmsvc). Leave the default to store encryption keys locally for this deployment. Click Next.
  • On the Port configuration screen, accept defaults and click Next.
  • On the Self-Service Portal configuration screen – type in the name of the local SCVMM server we are installing to, accept all other defaults, and click Next.
  • On the Library configuration screen, change the library path or accept the default location, and click Next.
  • Click Install.
  • Setup will install all three roles and complete.

2. Deploy an agent to an existing Hyper-V Host.

  • Open the System Center Virtual Machine Manager 2012 console.
  • Connect to the SCVMM server.
  • In the lower left hand pane of the console – select “Fabric”.
  • In the folder list – Right click “All Hosts” and choose “Create Host Group”.
  • Name your custom host group something like “Demo”
  • Right click the Demo host group and choose “Add Hyper-V hosts and Clusters”
  • On the Resource Location screen – choose the first bullet for a trusted AD domain computer.
  • On the Credentials screen, click Browse.
  • Select “Create Run As Account”
  • On the General screen, enter a Name of “Hyper-V Host Administration Account”
  • Input a DOMAIN\username of an AD account that has admin access to your Hyper-V servers. This account will be used to administer the Host and VM guests. For the purposes of the POC, we will use the DOMAIN\scvmmadmin account.
  • After inputting the password, and accepting the new account, we will return to the Credentials screen with our existing RunAs account shown. Click Next.
  • Type in the computer names of your Hyper-V servers that you wish to Manage. Ensure that the DOMAIN\SCVMMAdmins global group is a member of the local admins group on all Hyper-V servers so that we can manage them. Click Next.
  • Select all the discovered Hyper-V servers, and click Next.
  • Assign the discovered hosts to the “Demo” host group.
  • Click Next, Finish.
  • A job will be created to deploy the SCVMM agent to the Hyper-V hosts.

Comments (9)

  1. Please add windows firewall exceptions that need to be opened

  2. Kevin Holman says:

    Jon –

    The SQL agent isnt a requirement – I just used my standard SQL install instructions, and SQL agent enabling is a best practice for maintenance jobs, backups, etc… so I enable it on 100% of my SQL deployments.  Some System Center roles do leverage it, like SCOM reporting.

  3. Great article, thank you!  I'm deploying it in my lab now.  Quick note, seems to be that with SP1 it requires the Windows Assessment and Deployment toolkit.  Handy to have if you're installing a System center lab regardless.

  4. If you are using Volume Licensing corrctly then you will be buying Windows Server Datacentre licenses for your virtualisation hosts. This allows you to run an unlimited number of virtual machines on that host with any OS version (STD/ENT).

    It makes sense to use ENT as it supports more featurres than standard and wont cost you anymore if you are buying datacentee licenses.

    There is a process for converting Standard to Enterprise so you could just use standard and convert the boxes than need ENT features.

  5. Kevin Holman says:

    @Chris – no reason, really, I just use EE as my base OS image so I can deploy advanced features if needed.

    @Gary – agreed.

  6. Chris says:

    Why do you standardize on using Windows 2008 R2 Enterprise as opposed to Standard?

  7. Jon says:

    Hi Kevin,

    Why do you set the SQL Agent to automatic? Is there something missing in the SQL documentation for VMM?

    I cannot find anything on this in the Technet documentation/requirements for VMM:…/gg610574.aspx


    Additional information

    You must use a case-insensitive instance of SQL Server.

    If the VMM management server and the computer on which SQL Server is running are not both members of the same Active Directory domain, there must be a two-way trust between the two domains.

    The name of the computer on which SQL Server is installed cannot exceed 15 characters.


    I'm currently troubleshooting several VMM2012 problems so I'm clutching at straws.. 😛

    Kind regards,


  8. WinRM says:

    You should add a section pointing out that WinRM should be installed and configured before installing.

    winrm quickconfig from an administrator command prompt should do it.

  9. John says:

    plz I am having trouble in connecting remote instanace of sql server 2012 to scvmm 2012. plz if anyone find mail me at  

Skip to main content