How to Install System Center 2012 with the Unified Installer
Updated: May 13, 2016
Applies To: System Center 2012 - Unified Installer
In this procedure, you run the System Center 2012 – Unified Installer on a computer from which you will use the Unified Installer to deploy Service Manager 2012 components for evaluation. You will have to provide a location of the component installation media and the prerequisites for the components.
To install Service Manager 2012
Log on to the computer by using an account that has administrative credentials.
On the Unified Installer installation media, right-click setup.exe, and then click Run as administrator to open the System Center 2012 Wizard.
On the System Center 2012 page, click Install System Center.
On the Product Registration page, read the Microsoft Software License Terms, and, if applicable, click I have read, understood, and agree with the terms of the license agreement, and then click Next.
On the Component Selection page, select the Service Manager 2012 components to install, and then click Next.
On the Component Media Location page, click Browse, navigate to the folder where you stored the installation media—specifically, to the component’s setup executable file—select it, and then click Next.
Note
Specifying a mapped drive for installation files is not supported. You must specify location by universal naming convention (UNC) or by copying the installation files to a local hard disk drive.
If you are installing Configuration Manager, complete steps 7a and 7b; otherwise, continue with step 7b:
On the Configuration Manager License Terms page, click I accept these License Terms for the prerequisites that you will be using, and then click Next.
On the Prerequisite License Terms page, click I accept these License Terms for the prerequisites that you will be using, and then click Next.
On the Perquisite Media Location page, do the following:
In Please specify the media location for Microsoft .NET Framework 4 Extended, click Browse, and then navigate to the drive and folder where you stored .NET Framework 4.
In the Please specify the media location for SQL Server 2008 R2 Database Engine Services, click Browse, and then navigate to the drive and folder where you stored SQL Server 2008 R2.
Continue specifying the location for the other prerequisites, and when you are finished, click Next.
On the Installation Destination Location page, accept the defaults, and then click Next.
Note
Due to constraints for the path name, the destination location for DPM cannot be changed.
On the Servers page, type the name of the server or servers that will host the Service Manager 2012 components, and then click Next.
Note
For this release, you must use a computer short name when you are specifying the computer that will host a System Center 2012 component. Do not use a fully qualified domain name (FQDN) or an IP address when you are defining a target computer.
Note
The computer names must be unique. You can install only one component per computer.
On the Service Accounts page, in Installer Account, perform either of the following:
Click Yes to use the same account for all of the components, and then click Next.
Click No, specify a different account for each component, and then click Next.
Note
For the Installer Account, the Domain and Account name cannot be changed. For the Service Manager Administrator Role Group, no password is needed.
Depending on which components you select—for example, Operations Manager or Service Manager—you might be presented with a Component Specific Questions page. If so, provide the requested information (for example, the management group name), and then click Next.
On the Communications and Updates page, indicate your preferences for the Customer Experience Improvement Program, Error Reporting, and Microsoft Update, and then click Next.
On the Installation Validation page, examine the settings, and then click Install.
When installation is complete, click Next
Note
The deployment progress bar times out after two hours. Some installations may exceed the default time-out period. In these cases, your installation might still be running in the background. You can confirm that by checking the local system installation logs.
On the Deployment Summary Report page, click Finish.
See Also