Best Practices

The following are best practices from this chapter:

• Deploy System Center Operations Manager 2007 R2 for monitoring Lync Server 2010.

• Install the Windows Operating System, Active Directory, DNS, IIS, and Exchange management packs into OpsMgr to monitor network systems and applications that Lync Server 2010 depends on.

• Deploy Operations Manager Components on Windows 64-bit and SQL 64-bit for optimal performance.

• Create override management packs for each application management pack, such as the Lync Server 2010 management pack. Don’t use the default management pack.

• Take future expansion and relevance of hardware into account when sizing servers for OpsMgr deployment.

• Keep the installation of OpsMgr on a separate server or a set of separate dedicated member servers that do not run any other separate applications.

• Use SQL Server Reporting Services to produce custom reports using OpsMgr’s reporting feature.

• Start with a single management group and add on additional management groups only if they are absolutely necessary.

• Use a dedicated service account for OpsMgr.

• Allocate adequate space for the databases depending on the length of time needed to store events and the number of managed systems.

• Monitor the size of the OpsMgr database to ensure that it does not increase beyond the bounds of acceptable size.

• Leverage the reporting database to store and report on data over a long period.

• Modify the grooming interval to aggressively address environmental requirements.

• Configure synthetic transactions to monitor the end-user experience and latency of service delivery.

• Configure OpsMgr to monitor itself.