The best practices are collected and created by the OpsMgr team with feedback of the communication, Customers and MVP’s so the real world scenarios really get back in the following optimization tips.
- Never connect agent directly to the Root Management server.
- Never connect gateway server directly to the Root management server.
- R2 improvement note: SCOM 2007 R2 gateway server will support up to 1500 agents.
- Always run 64bits hardware, 64 bits OS and 64bits SQL.
- Always consider bandwidth considerations for core OpsMgr component and agents.
- R2 improvement note: RMS can be clustered after RMS is deployed as a single server.
Cross platform (R2):
- Provision management server(s) specifically for non windows monitoring
- Operations Database, don’t increase the default 7 days
- Operations Database, Consider reducing performance and event data to 4 or 5 days
- Data warehouse, use the data warehouse MP reports to examine your DW content.
- ACS Database,
- R2 improvement note: Microsoft Data warehouse report MP will be loaded on install.
- Use alert aging to reduce false positive
- Always configure a SMTP failover host for the notification
- Ensure RMS communication with the communication channel (don’t forget your RMS cluster node!).
- R2 improvement note: 5 concurrent command limit will be removed
- R2 improvement note: Immediately send and alert from the management console.
- Never put the RMS in Maintenance Mode (MM).
- Never put an object longer in MM than it needs to be, due to loss of perf data and availability data.
- R2 improvement note: Computer, Health service and Health Service watcher will be in MM from the console and scripts.
- Don’t run the console on the management server
- Avoid using /clearcache
- Create a terminal server jump box where all your tooling is up to date with a single upgrade location.
- Make upgrade scenarios much easier.