Documente Academic
Documente Profesional
Documente Cultură
Monitoring your
Microsoft Dynamics CRM
Infrastructure with
System Center
Operations Manager
2009
Prepared for
Dynamicsbase
Prepared by
Edwin Senjobe Ssentoogo
Director: Freshpangolin Ltd
SCOM alerts are based on real world problems and solutions developed by domain
experts and Windows error reporting is linked to latest resolution knowledge. For
illustration purposes the diagram below shows the Asynchronous Service Architecture,
a small part of the CRM 4.0 Architecture. The Asynchronous architecture is monitored
in the SCOM deployment for CRM 4.0.
SCOM components
Operational Database consists of operational data and configuration data for a
management group. A Root Management Server is used for configuration management.
Management Agents discover, collect, analyse and manage servers’ and clients’ alerts so
as to resolve issues and can also wake failed systems. A Reporting Server provides
reports for the management group and is displayed in the SCOM console.
Deploying SCOM
To setup SCOM OpmMgr and RMS databases, SCOM is deployed on a MS SQL Server
where the Action, SDK and Service Accounts are specified. A webconsole is deployed
specifying the SQL instance, the database name and SQL Listening port, plus provide
relevant accounts. With installation complete, an Administrator has to logon to the
SCOM server to complete the setup by configuring Discovery and select the managed
objects in addition to configuring computers and devices to manage, and importing
management packs1.
Operations Manager 2007 Reporting is setup by installing the data reporting data
warehouse and reporting server for reports and dashboards. It is recommended to
install the Data Warehouse and Reporting Server on separate servers. A SQL Server
Instance is used for the Audit Collection Service and Audit Collection Database setup
and enablement.
1
Refer to MOM 2005 Conversion for Dynamics CRM 4.0
Roles have to be created to manage the SCOM system. Roles are integrated with Active
Directory and they can manage tasks authorised for specified roles.
Notifications can be delivered individually via Email, Pager, Instant Messaging, Session
Initiation Protocol, Short Message Service support (SMS) and SMTP via the Notification
Device Wizard.
SCOM can be integrated with AD for Security Discovery and Agent Management
enabling agent deployment and configuration automatically. The SCOM Discovery
Wizard feature uses LDAP identify devices in the Directory to manage agents
automatically. The MOMADAdmin tool is used to integrate with AD by creating an
admin access point with the ability to specify exclusions through the ADSI Edit2 tool.
2
Active Directory® Service Interfaces Editor (ADSI Edit) is a Lightweight Directory Access Protocol (LDAP) editor used to manage objects and attributes in
Active Directory. It provides a view of every object and attribute in an Active Directory forest and is used to query, view, and edit attributes that are not exposed
through other Active Directory Microsoft Management Console (MMC) snap-ins.
The power of SCOM lies in the End-to-End visibility of the health and performance of
the CRM architecture. This powerful feature empowers support staff to have a complete
view of their supported environment, with access to easily accessed information on how
to resolve issues affecting their CRM environment in case of an IT issue. They are
empowered to take proactive action regarding issues before users can start calling or
before systems actually fail, ensuring short Mean Time To Identify (MTTI) and Mean
Time to Repair (MTR).
Note
SCOM has the capability to monitor non Microsoft technology through Operations
Manager Connector Framework. It does this through the bi-directional synchronised
partner connector solutions that connects to the third party management packs.
3
An additional step is required in SCOM 2007 for backward compatibility.