SCSM 2012 SP1 in a LAB – Installation (Part E – Install Service Manager Management Server)

[AdinE]

We are now finally ready to install Service Manager. As an FYI, Service Manager requires a minimum of 2 servers.

 

This is the largest deployment (as far as VMs go) even in a lab. This is because we cannot deploy Service Manager on a single server, even in a lab/POC environment.

 

In fact, even Microsoft’s single computer scenario, actually tells you to install it on a physical host with a VM for the warehouse! And that doesn’t even take into account the SharePoint server needed for the self-service portal.

 

So in our lab example, we will have 3 VMs. The first VM will have the Service Manager Management Server, Service Manager Database, and Service Manager Console. The second VM will have the Data Warehouse Management Server and the Data Warehouse Database. The third VM will be for SharePoint and the self-service portal.

 

Install Prerequisites

To start, before we will actually be able to install Service Manager Management Server, we have to install a few prerequisites.

§ .NET Framework 3.5 SP1

§ Microsoft SQL Server Analysis Management Objects

§ Microsoft Report Viewer Redistributable

§ Microsoft SQL Server Native Client

 

Install SCSM-MS (Management Server)

Start by either extracting the DVD contents, or mounting the ISO (the TechNet ISO is currently labelled as mu_system_center_2012_service_manager_with_sp1_x64_dvd_1348926). Start by opening your DVD drive, navigating to the corresponding architecture (i.e. x86 or amd64), and run the Setup.exe.

 

On the splash screen click the Service Manager Management Server install link.

 

On the Product Registration screen, enter the applicable information, including reading and accepting the license terms, and click Next.

 

On the Installation Location screen, you can change the install location if you want to, or accept the defaults, then click Next. From my personal experience, I have seen setups in Production environments have a dedicated HDD for the Operating System, and another for middleware.

 

The Prerequisite check will run, and inform you of any issues found. If there are issues detected, resolve them as indicated, and then click the Check Prerequisites Again button. Until everything passes (or if there are only Warnings left), you will not be able to continue with the installation. Once the prereq check passes, you can click Next to continue with the installation.

 

On the Service Manager database screen enter the SQL server name and select the appropriate instance, then click Next.

 

For this lab example, we are installing the Service Manager database on the same server as the Service Manager Management Server.

 

NOTE: You may encounter the following error when you get to the Service Manager Database screen. To understand more about this, see this TechNet article. According to Microsoft: “You can bypass this warning message and continue to install using the SQL_Latin1_General_CP1_CI_AS.” Read the article so that you are aware of why this occurs, etc.

 

This is particularly important if you plan on using Service Manager’s CMDB in connection with System Center Operations Manager (SCOM) and/or System Center Configuration Manager (SCCM).

When you encounter this Warning, just click OK.

 

Your Service Manager database screen should look something similar to this.

 

On the Management Group screen, provide a Management Group Name, and also add Group Administrators. It is easier if you create/add an Active Directory Security Group and add it as the Management Group Administrators, so that all you have to do is add users to the Security Group. Then click Next.

 

On the Service Manager Services screen, either accept the default of Local System Account, or choose to provide a Domain Account.

 

NOTE: If you choose to use a Domain Account, the Next button will be disabled until that account is successfully tested (via the Test Credentials button).

Make your applicable choice, and then click Next.

 

On the Service Manager Workflow Account screen, either accept the default of Local System Account, or choose to provide a Domain Account.

 

NOTE: If you choose to use a Domain Account, the Next button will be disabled until that account is successfully tested (via the Test Credentials button).

Make your applicable choice, and then click Next.

 

On the CEIP screen, you can choose to join the program or not. There may be concerns about sending Production-type data to Microsoft, however, I recommend joining the program as this is how Microsoft improves their software. If no one sent their experience information, then the tools we use would never be improved. Mark your choice and then click Next.

 

The Microsoft Update screen is new to System Center. Make your choice and click Next.

 

Review the information presented on the Summary screen, and click Install.

 

Once the installation in complete, ensure that the ‘Open the Encryption Backup or Restore Wizard after Setup Closes’ checkbox is selected. It is recommended to backup the encryption key as part of your disaster recovery planning.

 

 

Encryption Key Backup

When the Encryption Key Backup wizard launches, read the Introduction information and then click Next.

 

On the Backup or Restore screen, select ‘Backup the Encryption Key’ and click Next.

 

On the Provide A Location screen, it is recommended to store the Encryption Key backup in a secure location (i.e. a file server that is regularly backed up). Enter an applicable UNC path, along with a filename, and then click Next.

 

On the Provide A Password screen, provide a password for security purposes (and keep it in a secure location), and click Next.

 

Once the backup is complete, click Finish.

 

That completes the installation of Service Manager’s Management Server. We now need to install the Service Manager Warehouse Server.