Server Names & Roles
SQL-01: SQL Database Services, SQL Analysis Services, SQL Reporting Services.
SM-01: Management Server
DW-01: Data Warehouse Management Server
SMP-01: Self Service Portal
SQL 2016 Enterprise with SP2 will be the base standard for all SQL Database, Analysis, and Reporting services.
In AD, create the following accounts and groups, according to your naming convention:
DOMAIN\Srv-SMSrv Service Manager Server Service Account
DOMAIN\Srv-SMWf Service Manager Mail Enabled Workflow Account
DOMAIN\Srv-SMRep Service Manager Reporting and Analysis Account
DOMAIN\Srv-SQL SQL Service Account
DOMAIN\Service Manager Admins SM Administrators security group
Add the three SM service accounts, and the domain users who will be Service Manager Admins to the “Service Manager Admins” Group. Also add the “Service Manager Admins” domain group to the Local Administrators group on each server.
Obviously change the naming conventions to meet your organisational requirements.
Service Manager setup requires some prerequisites. Before starting with Service Manger 2016 installation, make sure that these are installed. The following prerequisites are required to successfully install Service Manager 2016:
- .NET Framework 3.5 – Installed from Server Manager (you may require the Server 2016 media in order to install this feature)
- Report Viewer 2008 – This is located in the Service Manager 2016 media prerequisites folder
- SQL Server 2014 Analysis Management Objects – https://www.microsoft.com/en-gb/download/details.aspx?id=42295
- SQL Server 2012 Native Client – https://www.microsoft.com/en-gb/download/details.aspx?id=29065
Now you start the Service Manager installation. Click Service Manager management server under the Install section:
Enter your product registration details and product key if applicable:
Select the default installation location unless you wish to change it:
If you installed all the necessary prerequisites, you should see a similar screen to this, if not ensure you carry out the required actions install any missing items:
Next you need to specify SQL Server and Instance name where Service Manager will create the main database. Note i am installing the databases on a stand alone SQL server in this series of articles and Service Manager 2016 also supports SQL AlwaysOn installations:
Note: The Service Manager Sizing Helper Tool is provided as a downloadable utility, the Service Manager Sizing Helper tool can help to establish the number of Server Manager servers you need and assist with sizing your databases. The tool is a graphical utility that is part of the Service Manager Job Aids documentation set. You can download the Service Manager Sizing Helper Tool from http://go.microsoft.com/fwlink/?LinkId=186291.
Note that if you are using the default collation (SQL_Latin1_General_CP1_CI_AS), you will receive the following warning. It basically warns you that support for multiple languages in Service Manager is not possible when using the default collation:
Now define the name of the new Service Manager management group. They must be unique and not the same as the DW server or Operations Manager management groups! Also specify the administrators group you created earlier:
Enter the credentials of the Service Manager Service Account (In this case its Srv-SMSrv). This will be the Operational System Account and becomes the logon account for the “System Center Data Access Service” and “System Center Management Configuration service”.
This account should already be a member of the Local Admin group on the SM server as you should of added the Service Manager Admins group to the servers earlier in this article.
Now enter the credentials of the Service Manager Workflow Account (In this case Srv-SMWf). This account is used for all the workflows and is made a member of the Service Manager Workflows user role.
By default Microsoft now collects diag and usage data. This can be turned off later but click next to continue the installation:
Click Install to start the installation:
After 15 minutes or so the installation should complete, click close and the Encryption Backup or Restore wizard should start:
You MUST backup the encryption key as it is used to encrypt sensitive information in Service Manager and is required should you ever need to perform a management server restore. Save it somewhere safe, NOT on the Service Management Servers!
One configuration step often missed is setting the SPNs (Service Principle Names) for Service Manager. Note, the account completing the install doesn’t has permission to create the SPN as its not a Domain Admin!
If the SPNs aren’t registered you will notice an event log warning is registered. The event ID is 26371 “The System Center Data Access Service failed to register an SPN”.
To check the SPNs registered to your service account you can use the SETSPN command:
SETSPN –l DOMAIN\SMServiceAccount
Where domain is your domain and SMServiceAccount is the Service Manager Server Service Account.
You can see above there are no SPN’s registered therefore in order to register them run the following commands:
setspn –A SMServiceAccount/SMSERVERNAME DOMAIN\SMServiceAccount
setspn –A SMServiceAccount/SMSERVERNAME.fqdn.name DOMAIN\SMServiceAccount
setspn –A Srv-SMSrv/IC-OR-SM-01 INDICIUM\Srv-SMSrv
setspn –A Srv-SMSrv/IC-OR-SM-01.indicium.cloud INDICIUM\Srv-SMSrv
Now when you run:
SETSPN –l DOMAIN\SMServiceAccount
You can see the SPN has been registered.