Joseph Carson, Product Manager, Server Monitoring Summary: This is a brief guideline to how customers should create Custom Monitor Packs and suggestions on what they should do prior to exporting or importing them into a Production Environment. Monitor Pack Suggestions: Customers can submit any type of Monitor Pack that other customers may find useful. Monitor Packs can vary from a single custom rule and metric to complex rules and metrics. These packs can be SharePoint Packs, IIS Packs or even Blackberry Enterprise Server Pack. Exporting Monitor Packs: When exporting a Monitor Pack please either disable the monitor pack or remove the target that the Monitor Pack is applied to. This will prevent customers when importing the monitor packs from immediately being deployed. Importing Monitor Packs: When importing Monitor Packs we suggest that you first import the custom monitor pack onto a UAT (User Acceptance Test) machine or Test Server to make sure you evaluate the rules and make sure that the target that the pack is applied to is the one that you want to apply the pack to. Use the Import Monitor Pack to import the pack and also DO NOT enable overwrite existing items when running the import. Disclaimers Symantec will make these Monitor Packs available as is. Symantec will not perform any Quality Assurance testing on Monitor Packs made available thru Symantec Connect. It is the responsibility of the customer to provide internal qualification of said Monitor Pack prior to rolling out into a live production environment. Please report any bugs or problems associated with any Monitor Pack downloaded from Symantec Connect. You may report problems via the Symantec Connect portal. Please note that Symantec will not provide technical or development support for any issue reported. Symantec will utilize customer feedback during its regular maintenance of Monitor Packs available via Symantec Connect.
Windows 2003 Monitor Pack