Kevin Holman's System Center Blog

Posts in this blog are provided "AS IS" with no warranties, and confers no rights. Use of included script samples are subject to the terms specified in the Terms of UseAre you interested in having a dedicated engineer that will be your Mic

SCVMM 2012 SP1 - QuickStart deployment guide

SCVMM 2012 SP1 - QuickStart deployment guide

  • Comments 20
  • Likes

 

The following document will cover a basic install of System Center Virtual Machine Manager 2012 SP1 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 two server model, where all SCVMM roles are installed on a single VM/Server, and leverage a remote SQL database server.

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

  • Windows Server 2012 will be installed as the base OS for all platforms. All servers will be a member of the AD domain.
  • SQL 2012 will be the base standard for all SQL database services.

Server Names\Roles:

  • DB1          SQL 2012 Database Services
  • SCVMM    VMM Management Server and Console

 

 

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 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 2012 to all server role servers.

5.  Install Prerequisites and SQL 2012.

6.  Install the SCVMM Server and Console.

7.  Deploy SCVMM Agent to Hyper-V hosts.

Prerequisites:

1.  Install Windows Server 2012 to all servers.

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

3.  Join all servers to domain.

4.  Install all available Windows Updates.

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

8.  On the SCVMM server, install the Windows Assessment and Deployment Kit (ADK) for Windows 8http://www.microsoft.com/en-us/download/details.aspx?id=30652  When you install this – install only the “Deployment Tools” and “Windows Preinstallation Environment” options.  This can take a significant amount of time depending on download speed.

9.  On the SCVMM server – install the SQL 2012 Native Client and the SQL 2012 Command Line Utilities from http://go.microsoft.com/fwlink/?LinkId=253555

10.  On the SQL database server, install SQL 2012.

  • 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 SQL server stand-alone installation…..
  • When prompted for feature selection, install ALL of the following:
    • Database Engine Services
  • Additionally, the product documentation for SCVMM states to install the management tools – complete:
    • 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.  I prefer to use a service account for SQL, so I will set the Agent and DB Engine to run under my DOMAIN\sqlsvc account and provide the password.  This is optional.
  • On the Collation Tab – you can use the default of SQL_Latin1_General_CP1_CI_AS or choose another supported collation.
  • 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.
  •         

 

Step by step deployment guide:

1. Install SCVMM 2012 SP1:

  • 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 Management Server
    • VMM Console
  • On the Product Registration – input a product key for a licensed version, otherwise Eval will be installed with a timeout.  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 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. One the Instance Name – click the pull-down to select the instance you wish to install to.  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 simple deployment. Click Next.
  • On the Port configuration screen, accept 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 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.

 

3.  Create host groups and clouds

4.  Configure WSUS for updates to Hosts

5.  Configure Logical Networks

6.  Connect with OpsMgr 2012 SP1:

http://technet.microsoft.com/en-us/library/hh427287.aspx

 

 

    Comments
    • Hi, Kevin

      can we have a SQL 2012 cluster to host all System Center 2012 databases, separated by instances?

      thanks

      PEM

    • Technically - yes - that would work for database engines, for any applications that supported a clustered database, and some things can share instances where it makes sense.  

      However, you still need multiple standalone reporting (SSRS) servers in that case... one for SCOM, one for ConfigMgr, and one for SCSM.

      As to designing System Center databases, it really comes down to how big each infrastructure needs to scale out to.  For a lab environment - I deploy 3 SQL servers, each with its own SSRS.

      DB1 - OpsMgr, VMM, Orchestrator databases.  SSRS for SCOM.

      DB2 - SCSM databases.  SSRS for SCSM.

      DB3 - SCCM databases.  SSRS for SCCM.

    • Thanks Kevin.  This was a great quickstart guide!

    • Great post,

      Any more tips for the last section..

      3.  Create host groups and clouds

      4.  Configure WSUS for updates to Hosts

      5.  Configure Logical Networks

    • This is a good start but you're missing a ton of information like steps 3, 4, 5.

    • Dear Kevin,

      I have installed DC and SQL servers... While installing service manager 2012, exactly in the last step, i have faced the following error message:

      “An error occurred while executing a custom action:_CreateDatabase

      This upgrade attempt has failed before permanent modifications were made.

      Upgrade has successfully rolled back to original state of the system. Once

      the correction are made, you can retry upgrade for this role.”

      Any advice?

      Regards,

    • Failed to create the group. Maybe this portion was not explicit. Seemed fine until job failed. Could have more detail on setting up. Good start though. Now I have to see if I really needed to add a local admin entry of the domain account...

    • Hello Guys,

      I have a clustered CSV Hyper-V platform made of 2 physical servers running Windows Server 2012.

      I have installed SCVMM 2012 SP1 on a virtual machine hosted in the cluster and running windows server 2012.

      SCVMM installation has completed successfully and with no errors. then I came to add the hosts into the fabric, the 1st host has completed successfully but the 2nd server is continuing to fail giving the error:

      Error 2917: Virtual Machine Manager cannot process the request because an error occurred while authenticating <server_name>. Possible causes are:

      1- the specified user name or password are not valid (same username and password was used for the 1st server and it completed successfully)

      2- The service Principle name (SPN) for the remote computer name and port does not exist (I did not understand this error honestly)

      3- The client and remote computer are in different domain and there is not a two-way full trust between the two domains. the network path was not found (0x80070035)

      Anyone can help on this case? I know this error is very general but I need to get out of this.

      Thanks

    • Great article...

      My exisiting privite cloud is running on RC. I have setup SCVMM 2012 with app. controller in the new RTM.

      I need some help in understanding how to move my hyperv cluster to this new SCVMM 2012 setup?

    • I am looking at this as a replacement for Vmware lab manager. LM is basically used for student to log in and do their labs online in different OS's. What other recommendations do you have on completing this?

    • Hello All, as an FYI I have created some detailed guides on SCVMM installation if it will help anyone.

      I haven't created any guides yet on configuration, but plan to do so.

      I have posted the guides on my blog here: adinermie.wordpress.com/.../01-installation-guides and have also posted them on this site as well: www.windows-noob.com/.../index.php.

      Hope it helps.

    • Hi!

      I have problem installing SCVMM SP1 agent on a perimeter host. Host is Windows Server 2008 R2 Enterpise and is not domain member.

      I get error 1603 in event log. Below is error from detailed log:

      MSI (s) (9C:D0) [14:51:42:942]: Doing action: AddLocalComputerToAdministratorsGroup

      Action 14:51:42: AddLocalComputerToAdministratorsGroup.

      Action start 14:51:42: AddLocalComputerToAdministratorsGroup.

      MSI (s) (9C:5C) [14:51:42:942]: Invoking remote custom action. DLL: C:\Windows\Installer\MSI69FE.tmp, Entrypoint: AddLocalComputerToAdministratorsGroup

      CustomAction AddLocalComputerToAdministratorsGroup returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox)

      Action ended 14:51:45: AddLocalComputerToAdministratorsGroup. Return value 3.

      MSI (s) (9C:D0) [14:51:45:236]: Machine policy value 'DisableRollback' is 0

      MSI (s) (9C:D0) [14:51:45:236]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2

      MSI (s) (9C:D0) [14:51:45:236]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2

      MSI (s) (9C:D0) [14:51:45:236]: No System Restore sequence number for this installation.

      MSI (s) (9C:D0) [14:51:45:236]: Unlocking Server

      Action ended 14:51:45: INSTALL. Return value 3.

      Any advice?

    • Hi to all,

      Today I downloaded the SCVMM VM, installed SCVMM and SQL, all running well.

      Main issue, I need to show the self service web console.

      Tried to find it and to install it, its hidden in c:\program files\Microsoft system center 2012\vmm\setup\msi\msdeploy\1033 webdeploy

      But this is not working, it installs something, but I do not get an web environment.

      Can anyone help me how to solve this?

      Kind regards,

      Ben

    • @Ben -

      You need to deploy System Center App Controller - this is the self service portal for VMM private clouds, in addition to Windows Azure subscriptions.

    • Regarding my problem installing SCVMM SP1 agent on a perimeter host, where host is Windows Server 2008 R2 Enterpise and is not domain member, I found the solution (with a  little help from Sysinternals Process monitor).

      All I had to do was to add local account hostname$ (where hostname is name of the host) on perimeter host.

    Your comment has been posted.   Close
    Thank you, your comment requires moderation so it may take a while to appear.   Close
    Leave a Comment
    Search Blogs