App Controller 2012 R2 – QuickStart Deployment Guide

Once you deploy SCVMM, you will want to immediately deploy App Controller, as this is the Self-Service portal for Virtual Machine Manager in a private cloud scenario.

App Controller is a lightweight web based interface to SCVMM based Private Clouds, and Windows Azure.  It is very simple to deploy.  It consists of a front end website, and a back end database component.

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

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

Server Names\Roles:

  • DB01             SQL 2012 with SP1 Database Services
  • SCAC01         App Controller web server

High Level Deployment Process:

1.  Install Windows Server 2012 R2 to all server role servers.

2.  Install Prerequisites and SQL 2012 with SP1.

3.  Install SC App Controller.


1.  Install Windows Server 2012 R2 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 explicitly to the Local Administrators group on each SCAC role server.

6.  Install the SCVMM Console on the SCAC server. 

  • From the SCVMM media, run Setup.exe.
  • Click Install
  • Choose VMM Console.
  • Agree to the terms.
  • On the CEIP screen, click Next.
  • Accept the default path, Next.
  • Accept the default port number, Next.
  • Click Install.

7.  Install a certificate for IIS for the SCAC server

  • Open IIS Manager
  • Select the server name in the left pane
  • Find the “Server Certificates” icon in the middle pane and open it.
  • Choose “Create Domain Certificate”
  • Input the required information for the certificate.  for the common name I typically use the FQDN of the server the cert is being requested for.
  • Hit the Select button to choose your enterprise domain CA.  Input a friendly name for your cert that you will see in the IIS admin console.  I will use “SCAC Web Cert”
  • Click Finish.

8.  On the SQL database server, install SQL 2012 with SP1.

  • 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
  • If you are going to be deploying a shared SQL server for other System Center components, you might consider adding:

    • Full-Text and Semantic Extractions for Search
    • Reporting Services – Native
  • 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.  You can accept the defaults for the service accounts, but I recommend using a Domain account for the service account.  Input the DOMAIN\sqlsvc account and password for Agent, Engine, and Reporting.
  • On the Collation Tab – you can use the default which is 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 SCVMMAdmins 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.
  • On the Reporting Services Configuration – choose to Install and Configure. This will install and configure SRS to be active on this server, and use the default DBengine present to house the reporting server databases. This is the simplest configuration. If you install Reporting Services on a stand-alone (no DBEngine) server, you will need to configure this manually.
  • Setup will complete.
  • You will need to disable Windows Firewall on the SQL server, or make the necessary modifications to the firewall to allow all SQL traffic.  See    

Step by step deployment guide:

1. Install SC App Controller 2012 R2:

  • Log on using your domain user account that is a member of the SCVMMAdmins group.   (This is a group you created when you installed SCVMM and will ensure you have rights to SCVMM)
  • Run Setup.exe
  • Click Install
  • On the Product Registration – input a product key for a licensed version, otherwise Eval will be installed with a timeout.  Click Next.
  • Accept the license agreement and click Next.
  • On the prerequisites screen, resolve any blocking issues.  Setup will install the IIS role and WCF Data Services.
  • Accept the default path and click Next.
  • Accept the default Network Service account and port, and click Next.
  • On Configure the website – choose the existing certificate we configured in the prerequisites, and click Next.   
  • On the Database Configuration screen, enter in the name of your SQL database server and leave port blank.  On the Instance Name – click the pull-down to select the instance you wish to install to.  Use the default database name or change it to suit your naming standards. Click Next when this screen is complete.
  • Choose to participate in CEIP and to use MU or not.  Next.
  • Click Install.
  • Setup will complete quickly.  Click Finish.

2.  Connect App Controller to Virtual Machine Manager

  • Open the App Controller web portal.
  • Settings > Connections
  • Click Connect > SCVMM
  • Supply a name for the connection and the server name in FQDN format.  Click OK.

3.  Connect App Controller to Windows Azure:

Comments (3)

  1. Kevin Holman says:

    @Mayank Dhama –

    Yes – same instance of SQL is fine, almost everyone does that.
    Yes – you can install app controller on the SCVMM server. Works fine.
    When you deploy – app controller communicates with the SCVMM API, so you will have the necessary information in both machines. SCVMM polls the hypervisors and discovers new VM’s as well.

  2. MJ Almassud says:

    Dear Kevin,

    How is it that you have the time to learn all of those products, and then actually have the time to create very nice blogs to help other IT Pros?


    Thank you very much.


  3. Mayank Dhama says:

    Hi Kevin,

    Thanks for sharing this!

    I have few below queries:

    -> Can we use SCVMM DB instance for app controller?

    -> If I install app controller on the same SCVMM Server then what challenges we may have?

    -> If I deploy app controller and it’s DB on separate machine then how will it sync with SCVMM server and if I deploy any VM throup app controller console then which DB it will use – SCVMM or APP Controller DB?

    Will be waiting for Your response and Thanks in advance!

    Best Regards,
    Mayank Dhama

Skip to main content