Module 10:

Deploying Service Manager

1
Lesson objectives
Sizing the Environment (performance
impact)
Installation and Setup
High Availability
SQL Best Practices
Troubleshooting

2
Sizing the Environment

3
Service Manager 2010 Performance and
Scale
Good results from scale and
performance testing for both 20K
and 50K user/computer profiles
Larger scale possible for scenario-
specific solutions

4
 Service Manager 2010 Performance and Scale
Service Manager Performance Testing
Criteria Test Details
Performance Time to Over 60 scenarios evaluated across every SM
Complete Task feature
Load Continuous UI Actual consoles running in loop creating
and Workflow incidents and change requests resulting in UI
Load and workflow load
Standard 20K users & 200K CIs and 2M+ rows in DB;
Data Profile computers Used 4 machines with recommended
40-50 standard hardware (Dual quad-core CPUs,
consoles 8GB RAM)
Large Scale 50K users & 500K CIs, 5M+ rows in DB;
Data Profile computers Standard hardware, except 32GB RAM for
80-100 database servers
consoles 5
 Recommended Deployment Topologies
Management
Required: Group DW_C
Windows Svr 2008/R2
SQL 2008 SP1 Web Analyst Console
Portal
Separate
Components for
Better Performance
Increase # of
SSRS
Servers to Address
Scale
Introduce NLB and DW Databases

Clusters for Portal Server Management Server

DW Management
Web Portal
Availability SMDB Server
SSRS
Connect Multiple SM DWDBs
Mgt Groups to Same
Workflows
DW
SM Database
Manageme
Management nt Group B
Group A

6
Performance Impact
Reconcile Data from Connectors
AD
Operations Manager
Configurations Manager
Self Service Portal
Initial loading of portal home page
Create Request
Approve Change
Create or edit Hardware Asset
Launch Reports

7
Performance Questions
How many servers do I need? (components)
 Should I use on or two or even three SQL
servers?
 How many Service Manager servers should
I use (performance not HA)
 Where should I put the Self Service Portal?

8
Performance Questions
Number of CI
Number of CI being added pr month
Number of concurrent users
Number of Incidents pr day / week / year
Number of changes pr day / week / year
Integration points (Connectors)

9
Service Manager Sizing Helper
This sizing tool
helps you plan for a
Service Manager
2010 hardware
deployment.
Specifically, the
sizing tool:

10
Service Manager Sizing Helper
Helps to give you
an idea of the type
of hardware such as
individual
computers, CPU,
free and used hard
drive space, and
RAID level that is
needed for
different usage and
deployment
scenarios.
11
Service Manager Sizing Helper
Provides topology
diagrams for each
scenario, which
map the hardware
to scenarios such as
single server, 2
server, 4 server, and
more than 4
servers.

12
Service Manager Sizing Helper
Helps you calculate
free and used hard
drive space needed
for a scenario,
based on what you
input. The
calculation is an
estimate, not a
fixed value that you
must meet.

13
Service Manager Sizing Helper

14
Service Manager Sizing Helper

15
Service Manager Sizing Helper

16
Service Manager Sizing Helper

17
Installation and Setup

18
Software Requirements
Management Server
The 64-bit edition of
Windows Server 2008 Standard or Enterprise
Microsoft .NET Framework version 3.5 with SP1

Service Manager database & data warehouse

The 64-bit version of SQL Server 2008 SP1
SSRS component of SQL Server 2008 SP1

19
Software Requirements
Service Manager Console
32 bit (where available or 64 bit
Windows Server 2008 or 2003 (SP2)
Windows Vista (Home Basic, Home Premium,
Business, Ultimate, or Enterprise)
Windows XP Professional x64 Edition operating
system or Windows XP Professional operating
system
Microsoft .NET Framework 3.5 with SP1*

20
Software Requirements
SQL Server
Microsoft SQL Server 2008 SP1
Microsoft SQL Server 2008 Standard Edition or SQL
Server 2008 Enterprise Edition SP1
Service Account configured as Local System
SQL Server Reporting Services (MSSQLSERVER)
service configured and running

21
Software Requirements
SQL Server Collections supported
Windows Locale LCID Collation
English 0x409 Latin1_General_100_CI_AS

Chinese_Taiwan 0x404 Chinese_Traditional_Stroke_Count_100_CI_AS

Chinese_PRC 0x804 Chinese_Simplifies_Pinyin_100_CI_AS

French 0x40C French_100_CI_AS
German_Standard 0x407 Latin1_General_100_CI_AS

Italian_Standard 0x410 Latin1_General_100_CI_AS

Japanese 0x411 Japanese_XJIS_100_CI_AS

Korean 0x412 Korean_100_CI_AS
Portuguese_Brazilian 0x416 Latin1_General_100_CI_AS

Russian 0x419 Cyrillic_General_100_CI_AS

Spanish_Modern_Sort 0xC0A Modern_Spanish_100_CI_AS

22
Databases
Component DB Name Content
Service Manager ServiceManager Configuration items, work
database items, incidents
Service Manager data DWStagingAndConfig These three databases
warehouse DWRepository comprise the data warehouse.
DWDatamart The extract process populates
the SCCMDB database which is
transformed into a proper
format in the SCDW database
which, through the load
process becomes the content
for the SCDM database.

23
Network Considerations
Web Portal

443

>150 ms Latency
Diff. Domain
Portal Server
Terminal Server
SM Management
a y
2W 1433
Server

SM DB

5724 1433

WAN Same LAN

24
Port Assignments for Service
Manager
Service Manager Piece A Port Number & Direction Service Manager Piece B
Service Manager console 5724 ---> Service Manager management server*
Service Manager console 5724 ---> Data warehouse management server
Service Manager management
1433 ---> Remote Service Manager database
server
Service Manager management
5724 ---> Data warehouse server
server
Service Manager management Operations Manager 2007 Alert and CI
5724 --->
server connectors
Service Manager management
389 ---> Active Directory Connector
server
Data warehouse server 1433 ---> Remote data warehouse database server
SQL reporting service server 1433 ---> Remote data warehouse database server
Data warehouse server 1433 ---> Remote Service Manager database server
Web browser 443 ---> Self-Service Portal
Self-Service Portal 1433 ---> Service Manager database
Web browser 80 ---> SQL Server Reporting Services

25
Deployment on Virtualized Fabric
DOs:
8+ GB of Memory (RAM) for Management Servers
2+ CPUs for each Management Server
2+ CPUs for each SQL Server
If CPU Utilization is Near 100 percent, Add Virtual CPUs
DON’Ts:
Don’t put SM and DW DBs on Same VM
Don’t use Dynamic Virtual Hard Drive (VHD)
Don’t Allocate More Virtual CPUs than the Number of
Available Logical CPUs

26
SM and OM Coexistence
Components Details
Management Servers cannot coexist on the same machine
Consoles can coexist on same machine. Install SCOM
console first.

2007 R2 Agent on SM Supported, SCOM agent must be Installed

Management Servers after SM Management Server
2007 SP1 Agent on SM Not Supported
Management Servers
OM MP Service Manager 2010 MP (for OM) will be
shipped within 60 days of SM RTM

27
Prepare for Service Manager
Deployment
Create an Active Directory group
Make sure that the SQL instances used for
Service Manager databases are using port
number 1433
If you are installing the databases on a
remote computer running SQL Server, the
user running Setup on must be a domain
user with local administrator permissions on
the SQL Server computer
Verify that reporting Services is running
28
Account Considerations
Consider Domain account over Local admin
Management Server
Management group administrators
Service Manager account
Workflow account
Data Warehouse
Management group administrators
Service Manager account
Reporting account

29
Localization SM Server
Languages in V1.0 (+60 days):
1. English 7. Simplified Chinese
2. German 8. Traditional Chinese
3. French 9. Russian
4. Japanese 10.Italian
5. Spanish 11.Portuguese (Brazil)
6. Korean

30
High Availability

31
Multi-Server

Service Manager SQL Server with

management server Service Manager Database

Service Manager
PRIMARY management server

`
Management SECONDARY
Service
(Workflow)

Data Access
Management Group A
Service

32
Multi-Server
Service Manager Server workload can be divided in the
Multi-Server setup
Data Access can run on Service Manager Server 1
Management Service (workload) can run on Service
Manager Server 2

Service Manager Service Manager

management server management server

PRIMARY `
SECONDARY

Management Service Data Access

(Workflow) Service Management Group A

33
HA for the Management
Server
A NLB can be put in front of the management servers
Setup experience is different from standalone database
cluster setup
Documentation is provided to setup NLB

34
High Availability
SQL Servers
High Availability can be done in the following
way
Windows Cluster of SQL (no-touch)
Log Shipping
Mirroring

Self Service Portal

NLB can be put in front of the SSP portal

35
SQL Best Practices

36
SQL Best Practices
1. Characterize I/O workload of application
2. Determine reliability and performance
requirements for the database system.
3. Determine hardware required to support
the decisions made in steps 1 and 2
4. Configure SQL Server to take advantage of
the hardware in step 3
5. Track performance as workload changes

37
SQL Best Practices
Always use Page Checksum to audit data integrity.
Consider using compression for read-only
filegroups for higher storage efficiency.
Use NTFS for security and availability of many SQL
Server features.
Use instant file initialization for performance
optimization.
Use manual file growth database options.
Do NOT use “auto shrink”
Use partitioning (available in Enterprise Edition)
for better database manageability.

38
SQL Best Practices
Storage-align indexes with their respective base
tables for easier and faster maintenance.
Storage-align commonly joined tables for faster
joins and better maintenance.
Choose your RAID level carefully.
For optimized I/O parallelism, use 64 KB or 256 KB
stripe size
Directly attached I/O is recommended for small-
to medium-sized servers
SAN systems are recommended for larger servers.
NAS systems are not recommended. Use iSCSI
instead.
39
SQL Best Practices
Store transaction logs separate from data files. Do
not stripe on the same disk as the data files.
For large bandwidth demands on the I/O bus, use
a different bus for the transaction log files.
The number of data files within a single filegroup
should equal to the number of CPU cores.
Place SQL DB (Master Temp) on separate
Database

40
Troubleshooting

41
Troubleshooting
Setup
Windows Event Viewer is primary source of
troubleshooting Service Manager outside of
console
Applications & Services Logs -> Operations Manager log
UI issues sometimes also in Event Viewer under
Windows Logs -> Application log
Setup issues have separate log
Found in .\users\<username>\appdata\local\Temp
With UI issues, first try closing and reopening
console
Also try “Restore Down” in UI for some dialogs
Many issues resolved after restarting services
42
Troubleshooting
Prerequisite Checker
Open Log File which can be found in the %Temp%
directory and find prereqreport.xml
Run Debug View Tool while running prerequisite
checker
http://www.sysinternals.com/Utilities/DebugView.
html
Setup
Open Log File which can be found in the %Temp%
directory and look for ‘value 3’ return code

43
Troubleshooting
Service Account
Distributed Install Caveat
Users cannot use Local System for Data Access
and Config service if the SQL service is running
under Domain account

Active Directory; Service failed to register an

SPN error
Remember to run: Setspn.exe –A
MSOMSDK/<RMS FQDN> domain\username

44
Troubleshooting
Management Server
Event ID: 29102 Management Service asking for
new configuration
Event ID: 29102 Management Service running
on “MS" has contacted Management
Configuration Service to get configuration.
Event ID: 21025 Management Service received
new configuration

45
Troubleshooting
Reporting Server
Check to see if you can open
http://<servername>/reports and
http://<servername>/reportserver
Run Reporting Services Configuration Manager to
verify SQL Reporting Services is healthy

46
Summary and Class Discussion
Understand how to Deploy Service
Manager
Understand Performance Impact
Understand Software Requirements
Hardware Sizing
Understand Upgrade Scenarios
Understand the need for High Availability
Know how to perform Troubleshooting

47
Deploying Service Manager
Review Questions
What costs performance in Service
Manager?

How should you size an implementation?

What is SQL best practice in connection

with Service Manager?

48
Hands on Lab

Service Manager
Installation

49
 © 2008 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.
The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not
be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation.
MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

50