In addition to the general recommendations for testing Management Packs that are described in the Microsoft Operations Manager 2007 Deployment Guide, this section lists testing and piloting tasks that are appropriate for the SMS 2003 Management Pack. For more information, see the Operations Manager 2007 web page (http://go.microsoft.com/fwlink/?LinkID=83259).

Testing Tasks

  • Verify that the SMS 2003 computer groups are populated with computers running SMS 2003.

  • After enabling the relevant rules, ensure that the views and reports in Operations Manager 2007 are functioning properly. These include views relating to SMS processing rates and SMS backlogs.

  • By default, some rules related to other Management Packs, such as the IIS and SQL Server Management Packs, are disabled in the SMS 2003 Management Pack. Depending on what additional Management Packs you have deployed, you should review these disabled rules to identify any rules that you might want to enable in your environment.

  • By default, all performance measuring rules are disabled to minimize the impact on the agent’s CPU, memory, and network resources. These rules can be enabled for more in-depth monitoring of the agent.

  • Some of the SMS scripts that run on an SMS Provider computer, an SMS site database server, or access an SMS site database do not run in agentless mode. Verify that all computers in the Microsoft SMS 2003 Provider and Microsoft SMS Site Database Server computer groups are configured as agent-managed computers. Also, because some of these scripts may proxy events, verify that these agents are configured to enable proxying.

Pilot Testing Tasks

  • Verify that the deployment or upgrade process for the SMS 2003 Management Pack completed successfully from the previous version.

  • Verify and edit custom thresholds for your environment using the Health Monitor view of the performance threshold.

  • Enable performance rules in stages to evaluate the impact that these rules have on Operations Manager 2007 performance.

  • Verify that the SMS 2003 computer groups are populated with computers running SMS 2003.

  • After enabling the relevant rules, ensure that the views and reports in Operations Manager 2007 are functioning properly. These include views relating to SMS processing rates, processing totals, and SMS backlogs.

  • By default, some rules related to other Management Packs are disabled. Depending on what additional Management Packs you have deployed, you should review the disabled rules to identify any rules that you might want to enable in your environment.

  • By default, some performance rules are disabled to minimize the impact on the agent’s CPU, memory, and network resources. These rules can be enabled for more in-depth monitoring of the agent.

  • Verify that SMS 2003 script execution-based events are not generated. These typically indicate problems with access permissions for the script.

  • Verify that the sizing of the DCAM and SQL Server are sufficient for your production load.

  • Verify operations processes and personnel requirements.

  • Verify that paging and e-mail notification is working properly.

  • Verify that the permissions that Operations Manager 2007 is using are sufficient to run properly, without being excessive.

  • If the Operations Manager 2007 agent is not specified to run under the LocalSystem account, then ensure that the minimum security rights have been met. For more information, see the "Configuring Agent Computers to Run in Low Privilege Scenarios" section in the Deploying the Operations Manager 2007 Agent section in this guide.

  • Verify that the SMS Server and SMS Client roles appear in the State view. Click a computer that is hosting each of these roles and check that components are visible in the instance pane.

  • Verify that SMS Administrator console tasks are working by clicking a task. If the task fails to execute, check that the SMS 2003 SP2 Administrator console has been installed and that the logged on user has logged off, and then logged on again at the completion of the console installation.

  • In the State view, click an SMS Server and an SMS Client to verify that the Roles page shows the appropriate role(s) and property data.

  • In the Monitoring pane, navigate to Microsoft Systems Management Server (SMS) 2003, and then click SMS 2003 Site Hierarchy Diagram. Verify that all site systems are displayed for sites that have the Operations Manager 2007 agent installed locally on their SMS Provider. If a site system does not appear, check the SMS Administrator console to see if the site system was discovered by the site and appears in the All Systems collection.

After you complete your pilot testing, export the SMS 2003 Management Pack to back up the changes that you made to the Management Pack.

See Also