[-]
  
  
  
  
[-]
  
[-]
  
  
  
  
[-]
  
  
  
 
 
 
[-]
  
  
  
  
  
  
  
  
  
  
  
  
  
[-]
  
  
[-]
  
  
 
 
 
 
 
[-]
 [+]
 [+]
Updated on 10/10/2018
True Control Center Installation Guide
Running the Control Center Installer
Direct link to topic in this publication:

Running the Cireson Control Center Installer

To install the Cireson Control Center:

  1. Logon to the server that will host the Control Center with an account that has local Administrator rights.
  2. Navigate to the location containing the Control Center download.
  3. Double-click the Cireson Control Center x.x.x Setup.exe (where x.x.x is the version of Control Center).
  1. If the User Account Control dialog box is displayed, click Yes.

As the setup program is a self-extracing ZIP file, when you run it, it will automatically extract itself to the ConfigMgr Portal Installer folder located in the same location the ZIP file is located.


  1. Navigate to the ConfigMgr Portal Installer folder.
  2. Right-click Setup.exe and select Run as administrator
  3. If the User Account Control dialog box is displayed, click Yes.

The Welcome screen will then be displayed.


The Welcome screen contains the following three options:

InformationThe Prepare Offline Installer option will not be visible on computers with no Internet connection. 
    • Browse installer files - which will open the folder containing the Control Center installation files in Windows Explorer.
InformationThe remainder of this section assumes you want to install Control Center on a server that has Internet connectivity.
  1. Click Let’s get started!


If any on the prerequisites required by the Control Center are missing, or if there is already a pending reboot outstanding on the server (for example a patch requiring a reboot was previously applied), the Install Prerequisites screen will be shown.

If this screen is not shown proceed to Step 11.

  1. On the Install Prerequisites screen, click Install

Any required prerequisites will then be installed.


If your server requires a reboot following the installation of any missing Control Center prerequisites, you will see the Almost done! screen.



Reboot your server and restart the Control Center Setup.exe.



If your server does not need to be rebooted following the installation of any missing Control Center prerequisites, you will see the Success! screen stating Setup prerequisites have installed successfully. Click Restart Setup.


  1. Click Restart Setup and on the Welcome screen, click Let’s get started!

The Welcome screen will then be displayed.

  1. Click Let’s get started!
  1. On the Installer Method screen, click Next to accept the default option Install All Components.
InformationSelecting the Install All Components installation method will install the following components required by the Control Center:
  • Database
  • Website
  • Services 
It will also integrate with the Microsoft Deployment Toolkit (MDT) and SQL Server Reporting Services (SSRS).

The other two options on this screen are:

  • Select Components to Install - If you not want to install of the components required by the Control Center (such as the Control Center database, website, and services), select this option. Then, as shown below, you will be able to select which components you wish to install:


  • Import Existing Settings - If you have previously installed the Control Center, checking the Import Existing Settings checkbox will cause the installer to read in the values contained within the Configuration.xml file, which is created and updated every time the Control Center Installer is run.
Information

The remainder of this section assumes the default Install All Components option has been selected.

  1. Under the Configuration Manager Database Settings section of the Configuration page, in the Configuration Manager Database Server Name field, enter the name of the ConfigMgr database server.
InformationThe values entered do not get validated until you move to another field. If there is an issue, either a red or yellow triangle with an exclamation mark will be shown:
  • Red triangle () – A required value has not been entered
  • Yellow triangle () – A value has been entered incorrectly (for example a password)
If you are not using the Default SQL instance for your ConfigMgr site database, you should enter the server name followed by the SQL Server instance name hosting the ConfigMgr site database. For example:
<Server_Name>\<SQL_Instance_Name> 

Also, in a multi-site environment, this must be the Central Administration/Central Site and cannot be a Secondary Site.

 
  1. In the Configuration Manager Site Server (FQDN) field, enter the NetBIOS name of the ConfigMgr site server.
InformationIn a multi-site environment, this must be the Central Administration/Central Site and cannot be a Secondary Site.


  1. If you are using SQL authentication, select SQL Authentication from the Authentication Type dropdown list.
InformationThe Authentication Type configures the authentication method used by the Control Center to access the ConfigMgr site database in order to read and write data. By default, Windows Authentication is selected. However, the SQL Authentication option is provided if you have a SQL login you would like to use.


  1. In the Configuration Manager Database Name field, enter the name of the ConfigMgr site database (e.g. CM_<site_code>).


  1. If you are using SQL Authentication, complete the SQL Login and SQL Password fields with their respective values that will allow the Control Center to access your ConfigMgr site database.


  1. Under the ControlCenter Database Settings section, in the ControlCenter Database Server Name field, enter the name of the SQL Server that will host the Control Center’s database.
InformationIf you are not planning to use the Default SQL instance for your Control Center database, you should enter the server name followed by the SQL Server instance name that will host the Control Center database. For example:

<Server_Name>\<SQL_Instance_Name>

  1. In the ControlCenter Database Name field, if necessary change the suggested default name of ControlCenter for the Control Center database.


  1. If you are using SQL authentication, select SQL Authentication from the Authentication Type dropdown list.


  1. If you are using SQL Authentication complete the SQL Login and SQL Password fields with their respective values.


  1. Click Next.


  1. Under the Reporting Services Database Settings section of the Configuration page, in the Reporting Services Database Server Name field, enter the name of the server hosting SQL Server Reporting Services (SSRS).

  1. In the Reporting Services Database Name field, enter the name of the SSRS database (for example ReportServer).

  1. If you are using SQL authentication, select SQL Authentication from the Authentication Type dropdown list.

  1. If you are using SQL Authentication, complete the Reporting Services Login and Reporting Services Password fields with their respective values.

  1. Under the MDT Database Settings section, in the MDT Database Server Name field, enter the name of the SQL Server hosting the MDT database.

  1. In the MDT Database Name field, enter the name of the MDT database (for example MDT).

  1. If you are using SQL authentication, select SQL Authentication from the Authentication Type dropdown list.

  1. If you are using SQL Authentication, complete the SQL Login and SQL Password fields with their respective values.

  1. Click Next

  1. Under the Web Site Settings section of the Settings page, in the Application Pool Identity field, enter the user account name (prefixed with the domain name), that will be running the IIS Application Pool used by the Control Center. For example, Cireson\Cireson Control Center
InformationAs you start typing in this field, the Installer attempts to autocomplete it for you. 

  1. In the Application Pool Account Password field, enter the password for the Control Center service account created in the "Account and group requirements" section.

 

  1. In the License Key field, enter your unique license key.
Information

You do not need a license key to install the Control Center. If you do not enter a valid license key when prompted by the Installer, you will install a 30-day trial version of the Control Center.

After your 30-day trial has ended, if you wish to continue using the Control Center you will need to contact the Cireson Customer Success Team to request your unique License Key to convert the Trial version to the Licensed version.

The Cireson Customer Success Team can be contacted at customersuccess@cireson.com 

The process for converting from the Trial version of the Control Center to the License Version is covered in "Appendix B - Converting from the Trial to the Licensed Version of the Cireson Control Center"

 

  1. In the Portal Administrators Group field, enter the name of the local or Active Directory group/user that will have full access to the Control Center. For example, <domain_name>\Cireson Control Center Admins
InformationAs you start typing in this field, the Installer attempts to autocomplete it for you. 


 

Information

If the Control Center Installer detects that the server is already running IIS and the Default Web Site is running on port 80, you will see the red triangle containing an exclamation mark as shown below.


If you expand Advanced Website Settings and hover over the triangle it will inform you:

The site ‘Default Web Site’ is already using port 80.


You should either:
  • Specify a different port for the Control Center website

OR

  • Reconfigure the default website to use a different port other than port 80.
  1. If you do not wish to configure any advanced website settings, click Next and go to Step 39.
  2. Click Advanced Website Settings.


  1. Make any required changes (such as the directory the Control Center should be installed to, the website name/port, and host name).
InformationFrom version 3.0.7, the Control Center Installer will automatically populate the Host Name field with the recommended value of ControlCenter. This field can be left empty if there is no other website running on the same port whose hostname is also blank. 

Also, if you check the Let setup automatically register hostname in DNS (requires DNS permissions) checkbox, the Installer will register the entered hostname in DNS (provided the account you are using to run the Installer has the required permissions to DNS.

 

  1. Click Next
  2. Under the Hosting Service Settings section of the Settings page, either:
  • In the Service Account and Service Account Password fields, enter the account name (including the domain name), and password of the account you wish to run the Hosting Service (the recommended option). 

OR

  • Check the Use LocalSystem checkbox to run the Hosting Server under the context of the Local System account.
InformationThis option should only be used if you are installing the Control Center on the same server that is hosting SQL as the Control Center Installer does grant SQL permissions to the machine account.


InformationThe Control Center installs a Windows service called Cireson ConfigMgr Portal Hosting Service which is used to run both the Caching and Deployment services (and potentially others in the future). The hosting service can either be run under the context of the Local System account, or if you prefer, under the context of a specific user account.

If you are using SQL authentication for the Control Center and decide to run the Hosting service under a specific account, the Hosting service does not require any additional permissions. However, if you are using Windows authentication for the Control Center and decide to run the Hosting service under a specific account, the account will need the same permissions as the Application Pool Identity account.

If you plan to run the Hosting Service on a server other than the SQL server, you will need to grant the computer account of the server running the Hosting Service the same permissions as the Application Pool account.
  1. If required, set the required port in the Deployment Service Port field.

  1. If required, set the required port in the Cache Service Port field. By default, this will match the Deployment Service Port, but it can be any open port.

  1. Click Next.

  1. On the Platform Settings page, configure the settings for each item:
InformationDetails of these accounts and their requirements can be found in the "Optional Accounts" topic of the "Account and group requirements" section.

At a minimum, we recommend you create and configure the Remote Manage Account.
  • Platform Service Account - Enter the username and password for this account. Or if you want to use the Application Pool account instead (to save having to create and manage a separate account for the Platform Service Account), simply check the Use App Pool checkbox.
  • Configuration Manager Account - Enter the username and password for this account. Or if you want to use the Platform Service Account instead (to save having to create and manage a separate account for the Configuration Manager Account), simply check the Use Platform Account checkbox (the Platform Service Account and Platform Account are one and the same account).
  • Remote Manage Account - Although you can check the Use Windows Auth checkbox to use the App Pool account instead of having to create and manage a separate account for the Remote Manage Account, we recommend you create and configure a dedicated account to use for the Remote Manage Account who's username and password you should enter in the relevant fields.
InformationSee the "Remote Manage Account" topic in the "Account and group requirements" section for details of the requirements for the Remote Manage Account. 
  • AD Sync Account  - Enter the username and password for this account. Or if you want to use the Platform Service Account instead (to save having to create and manage a separate account for the Platform Service Account), simply check the Use Platform Account checkbox (the Platform Service Account and Platform Account are one and the same account). 
  • Active Directory Location (LDAP format) - Enter the Active Directory location from which you want the Control Center to retrieve data from in Lightweight Directory Access Protocol (LDAP) format. For example:
LDAP://OU=<organizational_unit_name>,DC=<domain_name>,DC=<domain_suffix>

For example, if the you wanted to retrieve the data from the ConfigMgr Users Organizational Unit (OU), in the Cireson.com domain, you would enter the follow:

LDAP://OU=ConfigMgr Users,DC=Cireson,DC=com

The Control Center will search the specified location and any child containers.

Information

If you want to retrieve the data from your entire Active Directory domain, simply specify the root container of your Active Directory.

  1. Once you have configured the relevant settings, click Next.
  2. On the License Agreement page, you will need to check the I Accept the Terms of the License Agreement checkbox in order to indicate your acceptance of the agreement and to be able to proceed with the installation. Once you have checked this, click Install.

The installation will begin, showing progress on the progress bar.

Once the Installer has completed successfully without any errors or warnings, the Success! message will be displayed.


If the installer encountered any problems, the Some problems have occurred! screen is displayed. Review each problem consulting the Control Center installation log (accessed by clicking View Log), as necessary, until the issue is resolved. Then retry the installation.


  1. Click Launch Portal to launch the Control Center (you can also click View Log to review the installation log).

The Control Center Dashboard will be opened in your browser.

This completes the installation of the Cireson Control Center using the installer. Complete the tasks in the "Post Installation Configuration of the Cireson Control Center" section to complete the installation of the Control Center.