Speakers: Samuel Erskine Syliance IT Services and Steve Beaumont Trustmarque
A book with practical tips and task steps brought to you from the European crew:
SCSM cumulative updates often require all management consoles to be updated once the infrastructure servers are updated. If you have a large amount of consoles this can be tedious.
See my previous post for infrastructure upgrade steps:
· Disable all connectors on the SCSM management server (CMDB)
· Create an Encryption key backup for all Management servers
· Backup all SCSM databases and the SSRS databases
· Backup all management packs
· Backup all DLLs for the custom MPs (e.g. Exchange connector)
· Install CU on DW
· Install CU on SCSM CMDB server and all secondary management servers
· Enable all Connectors
· Install CU on all consoles in use
· Install the Authoring Tool update on all systems with the Authoring tool installed on
An area often overlooked during deployment of infrastructure applications is, exclusions from real-time scanning engines.
Below is the list of files and directories recommended for exclusion for SCSM (based on Forefront Protection)
Service Manager 2010 Files and Folders
%ProgramFiles%\Microsoft System Center\Service Manager 2010\Health Service State\*
Service Manager 2010 Processes
%programfiles%\Microsoft System Center\Service Manager 2010\HealthService.exe
%programfiles%\Microsoft System Center\Service Manager 2010\Microsoft.Mom.ConfigServiceHost.exe
%programfiles%\Microsoft System Center\Service Manager 2010\MonitoringHost.exe
%programfiles%\Microsoft System Center\Service Manager 2010\Microsoft.Mom.Sdk.ServiceHost.exe
By Default only Service Manager Administrator role can see the reporting Icon in the Service Manager Console.
To allow other SCSM Console users to view reports, perform the following steps
In this blog I will share
A redirection link is provided to redirect users back to the home page if the new user request is selected. Thank you to Kenny Stanford for helping me out with the web updates.
EndUsers requesting a new AD user creation is not a scenario for customers I have engaged with and the update to the page has been done due to the additional steps required to remove the hardcoded link. Instead we took the approach of presenting the end user with a message and hyper-link explaining the feature is not in use (non developer approach and business solution).
In part I of this series we explored the link between current frameworks and how we do our real work. We also discussed how SCSM takes you from framework to real work with less risk and more business benefit by being customizable and portable. We introduced the Administration node of the console.