Insert content= here. Describe what this management pack can provide to customers.=

Document Version

This guide was written based on the 0.0.0.0 version of the = name Management Pack.

Revision History

Release Date	Changes
Date	Original release of this guide
update example: June 25, 2007	Example: New topics in this release: · Role-Based Security in Operations Manager 2007= · Using Certificates with ACS in Operations Manager 200= 7 · Security Considerations for Agentless Management in Operat= ions Manager 2007 · Web Console Security · Appendix A - List of Operations Updated topics in this release:= · Account Information · Authentication and Data Encryption

Release Date

Changes

Date

Original release of this guide

update example: June 25, 2007

Example:

New topics in this release:

· Role-Based Security in Operations Manager 2007=

· Using Certificates with ACS in Operations Manager 200= 7

· Security Considerations for Agentless Management in Operat= ions Manager 2007

· Web Console Security

· Appendix A - List of Operations

Updated topics in this release:=

· Account Information

· Authentication and Data Encryption

Introduction to the Name Management Pack

The primary audience for manageme= nt pack guides is the Operations Manager administrator and application owner (for example, the Exchange administrator).

Insert content= here. Provide a brief overview of the management pack. T= he introduction should discuss what technology is managed by the management pa= ck and discuss the high visibility or unique features that the make this management pack worth having.

Getting the Latest Management Pack and Documentation

You can find the Name Management Pack in the System Center Operations Manager 2007 Catalog (http[A2] ://go.microsoft.com/fwlink/?LinkId=3D82105).=

This fwlink is maintained by the Operations Manager 2007 documentation team and points to the location of the management pack catalog.

What's New

= The following features are new in this release of the Name Management Pack:

· = List updates since the previous releas= ed version of the management pack.

Changes in This Update

Delete this section for the first= release of a new management pack. This section is where you document changes between versions of a management pack.

Use this section to list specific= fixes, changes, and additions in this update to a management pack. Customers have expressed great interest in being informed of specific changes made in a revision of a management pack. Depending on the type and amount of informat= ion, you can use a bulleted list or a table.

When you are re-releasing a manag= ement pack and the guide already contains a "Changes in This Update" section, add the new changes under the heading "Changes in This Update", and re-title the existing section to "Changes in the <= ;Version> Update". This provides customers with a cumulative source of changes.<= o:p>

The 0.0.0.0 version of the Name Management = Pack includes the following changes:

List changes here...

Supported Configurations

Discuss the supported and unsuppo= rted versions and configurations of the technology that the MP monitors. This could include things like ver= sions of the product/technology or configurations of the systems being monitored (i.e. x86, x64, ia64, clustered, virtualized, domain-joined, etc.). If clustering specifically is supp= orted, then the guide should be very specific about what it takes to get the appropriate monitoring configured for both the physical systems, as well as= the virtual (clustered) resources.

The Name Management Pack for Operations Manager 2007 supports the following configurations:

Important: include a statement of= the supported scale of the management pack. For example: This management pack supports up to <number&= gt; <things>.

Getting Started

Provide brief summary of contents= of this section. If no optional configuration is needed for this management pack and you are going to delete the optional configuration section of this guide, include a statement here that lets the customer know that no additional configuration is required after the management pack is imported.

This section describes the actions you should take bef= ore you import the management pack, any steps you should take after you import = the management pack, and information about customizations.

Before You Import the Managem= ent Pack

This is an optional section. If t= here are no decisions or actions to take before installation, promote the "File= s to Download", "Recommended Additional Management Packs" and "Other Requirements" sections to Heading 3 level.

Before you import the Name Management Pack, note the following limitations of the management pack:

· = <Note any restrictions; for example, no support of agentless monitoring>

· = <Note any lack of support for common configurations; for example, the Active Directory Management Pack does not support monitoring across multiple forests>

Before you import the Name Management Pack, take the following actions:

· = Decide <description of any decisions th= at need to be made prior to importing the management pack>

· = Change <description of settings that mu= st change before the management pack is installed>

· = Configure <any user accounts that need to = be set up, such as any required Run As accounts or profiles>.

Files in This Management Pack=

List all downloadable files that = are part of the management packs and indicate whether they are optional or required.= The fwlink is maintained by the Operations Manager 2007 documentation team.

To monitor <application name>, you must first download the Name Management Pack from the Management Pack Catalog, loc= ated at http://go.microsoft.com/fwlink/= ?LinkId=3D82105. The Name Management Pack includ= es the following files:

· = <Management Pack File Name>

· = <Management Pack Reports File Name, if applicable>

· = <Management Pack Guide file name>= ;

If your management pack requires = the OpsMgr 2007 MOM 2005 Backward Compatibility Update, list it here. The follo= wing is a sample of the appropriate text; update version number and link if appropriate.The fwlink is maintained by the Operations Manager 2007 documentation team. If the up= date is not reqired, delete the following paragraph and note.

Before you import the Name Management Pack, you must install the updated Microsoft Operations Manager 2005 Backward Compatibility Management Pack, version 6.0.5000.16 (http://go.microsoft.com/fwlink/?LinkId=3D98874).

Note

If you do not install the updated Microsoft Operations Manager 2005 Backward Compatibility Management Pack before you install the = Name Management Pack, your install= ation will fail.

Optional section. Briefly list ot= her management packs that a user might download to perform complete service-oriented monitoring of this server role or technology. For example, Active Directory Management Pack users might also want to monitor DNS and w= ould need to download the DNS Management Pack. The Windows Server 2008 Operating System Management Pack provides basic monitoring functionality for the operating system and should be recommended for all management packs.=

Do not discuss how to integrate d= ifferent management packs here, because that is beyond the scope of the document. Include pointers to additional management pack documentation, as appropriat= e.

Other Requirements

Optional section. Delete if the management pack has no requirements other than Operations Manager requireme= nts.

Indicate whether or not anything = else beyond the management pack is required to get the management pack to work. = For example, this section indicates whether or not Helper Objects or Version X = of .NET Framework must be installed on the managed node or Operations Manager server for the management pack to work.&nb= sp; Do not reproduce Operations Manager requirements here.

How to Import the Name Management Pack

For instructions about importing a management pack, se= e How to Import a Ma= nagement Pack in Operations Manager 2007 (http://go.microsoft.com/fwlink/?LinkId=3D142351).

The fwlink is maintained by the Operations Manager 2007 documentation team.

If your management pack has steps= other than the standard importing steps, include them here. At the end of this section, the user should have a running management pack.

After the Name= Management Pack is imported, follow these procedures to finish your initial configuration:

1. Create a new management pack = in which you store overrides and other customizations.

2. <Insert additional instructions or links to subsections.>

Create a New Management Pack = for Customizations

Most vendor management packs are sealed so that you ca= nnot change any of the original settings in the management pack file. However, y= ou can create customizations, such as overrides or new monitoring objects, and save them to a different management pack. By default, Operations Manager 20= 07 saves all customizations to the default management pack. As a best practice, you should instead create a separate management pack for each sealed manage= ment pack you want to customize.

Creating a new management pack for storing overrides h= as the following advantages:

· = It simplifies the process of exporting customizations that were created in your test and pre-production environments to your production environment. For example, instead of exporting a default management pack that contains customizations from multiple management packs, you can export just the management pack that contains customizations of a single management pack.

· = You can delete the original management pack without first needing to delete the default management pack. A management pack that contains customizations is dependent on the original management pack. This dependency requires you to delete the management pack with customizations before you can delete the original management pack. If all of your customizations are saved to the default management pack, you must delete the default management pack before= you can delete an original management pack.

· = It is easier to track and update customizations to individual management packs= .

Optional Configuration

Add topics to this section as nec= essary to cover any optional configuration step-by-step procedures you have. Some common configuration topics are provided.

Describe how to configure the man= agement pack once it is installed. This section includes information such as the following:

· = Which rules and monitors might need to be enabled or updated= to support some of the monitoring scenarios.

· = Which parameters in rules, monitors, scripts, or responses m= ight typically be modified.

· = The following is an example topic for this section: <= /p>

Setting the Intersite Replica= tion Latency Threshold Value

The intersite replication latency threshold is the maximum amount of time that can be required for a change to replicate across the entire forest. This value is typically monitored to en= sure that basic help desk procedures, such as resetting passwords or performing replication from corporate headquarters to a branch office, are completed within a reasonable amount of time.

Set the intersite maximum latency threshold value to one-third of the number of minutes specified in your ser= vice level agreement or to the maximum number of minutes it takes for data to replicate across your forest, whichever is smaller.

Enabling Performance Threshol= d Rules

Delete this se= ction if not applicable to your management pack.

It is very difficult to deliver a performance threshol= d rule that is suitable for most environments; therefore, most performance thresho= ld rules are initially disabled. The following table lists the performance threshold rules that we recommend you enable. Before you enable a performan= ce threshold rule, you should baseline the relevant performance counters, and = then apply the appropriate overrides to define and enable a suitable threshold f= or your environment.

The following rule threshold ranges and intervals repr= esent the recommended minimum and maximum values for most environments.

Rule Name<= /p>	<Label as appropriate for your data, such as Threshold or Recommended Values or Default Values>=
<Rule Name 1>	<data>
<Rule Name 2>	<data>

Tuning Performance Threshold = Rules

Delete this se= ction if not applicable to your management pack.

The following table lists performance threshold rules = that have default thresholds that might require additional tuning to suit your environment. You should evaluate these rules to determine whether the defau= lt thresholds are appropriate for your environment. If a default threshold is = not appropriate for your environment, you should baseline the relevant performa= nce counters, and then adjust the threshold by overriding them.

Rule Name<= /p>	Default Threshold
<Rule Name 1>	<value>
<Rule Name 2>	<value>

Enabling Advanced Trending and Diagnostics Performance Rules

Delete this se= ction if not applicable to your management pack.

The optional performance rules listed in the following= table are disabled because they collect performance data that is useful only for advanced trending and diagnostics scenarios. To use these performance rules, set overrides to enable them.

Rule Name<= /p>	<Label as appropriate for your data, such as Recommended Values or Default Values>=
<Rule Name 1>	<data>
<Rule Name 2>	<data>

For more information, see How to Override a = Monitor ( http://go.microsoft.com/fwlink/?LinkId=3D108556).

Slow WAN Links or Large Branc= h Office Deployments

Delete this se= ction if not applicable to your management pack.

<List any s= pecial steps for slow links or large deployments here.>

Security Considerations

You may need to customize your management pack. Certai= n accounts cannot be run in a low-privilege environment or must have minimum permissio= ns.

Provide information relating to s= ecurity for this management pack. Include anything that is needed in the way of “User Roles”, “Run As accounts”, or “Run As p= rofiles”. Some information may be included in the subtopics for this section.<= /p>

Low-Privilege Environments

Provide instructions for any customizations that need to be done for your management pack to work in situations where accounts have restricted authorization. Be clear about what parts of the monitoring (if any) do not work if the Run As account(s) are n= ot local admin. Some customers spend significant time trying to accomplish a 1= 00% low-rights scenario for all MPs.

A low-privilege agent action account must meet the fol= lowing requirements:

· = < list requirements here, such as Mem= ber of the local users group, Member of the local Performance Monitor users group,= or Granted Log On Locally rights>

The following management pack tasks cannot be run usin= g a low-privilege account. These tasks require that the Action account have Adm= in user rights on the agent computer:

· = <list tasks here, if applicable>=

Run As Profiles

Describe each Run As profile incl= uded in this management pack. Include the rules, tasks, or monitors associated with each profile. Add any recommendations for assigning Run As account credenti= als to a profile.

Understanding Management Pack Operations

This section should provide the c= ustomer with an understanding of what the MP is doing and what the results they see= in the Operations Console mean.

<Provide a = brief overview of the highlights of the management pack monitoring capabilities.>

Objects the Management Pack D= iscovers

The Name Management Pack discovers the object types described in the following table. Not all of the objects are automatically discovered. Use overrides to disco= ver those that are not discovered automatically. For information about discover= ing objects, see the "Object Discoveries in Operations Manager 2007" topic in Operations Manager 2007 Help (http://go.microsoft.com/fwlink/?LinkId=3D108505).

Category

Object Type=

Discovered Automatically

SQL Server Roles

SQL Server 2005 DB Engine

Yes

SQL Server Roles

SQL Server 2000 DB Engine

No

Entries in table are examples. Don’t use a table if unnecessary. Delete unneeded columns; for exampl= e, if all discoveries are automatic, say so in the lead-in rather than have a column that has the same value for every row.

Use the following procedure to enable or disable autom= atic discovery. The procedure enables the SQL 2005 Agent Job as an example.=

To use an override to change the setting for auto= matic discovery

1.   In the Authoring pane, expa= nd Management Pack Objects, and then click Object Discoveries.

2.   On the Operations Manager toolbar, click Scope, and then filter the objects= that appear in the details pane to include only SQL Server objects.

3.   In the Operations Manager toolbar, use the Scope button to filter the list = of objects, and then click SQL Server Agent Job.

4.   On the Operations Manager toolbar, click Overrides, click = Override the Object Discovery, and then click For all obje= cts of type: SQL 2005 Agent.

5.   In the Ove= rridesProperties dialog box, click the Override box for the Enabled parameter.

6.   Under Mana= gement Pack, click New to create an unsealed vers= ion of the management pack, and then click OK, or select= an unsealed management pack that you previously created in which to save this override. As a best practice, you should not save overrides to the Default Management Pack.

After you change the override setting, the object type= will be automatically discovered and will appear in the Monitoring pane under SQL Server.

Classes

The purpose of this topic is to i= ntroduce the customer to the design and structure of this particular management pack= . We recommend a diagram of the classes.

The following diagram shows the classes defined in this management pack.

<insert gra= phic>

How Health Rolls Up

The purpose of this topic is to e= xplain the relationships of components and their health states in this management pack. We recommend a diagram of the health roll up.

The following diagram shows how the health states of components roll up in this management pack.

<insert graphic>

Key Monitoring Scenarios

This section provides a list of t= he key features, benefits, and scenarios that this management pack provides to customers. You should list the rules/monitors that implement the monitoring= for each scenario.

This material is for the applicat= ion owner (such as the database administrator) who wants to know the details of= how we monitor their application. Include how to configure the MP for different monitoring scenarios, such as in a stand-alone and cluster/farm scenario or single/multiple forest monitoring. Most likely larger customers will need to handle several scenarios in the same MG/MP, provide simple examples of how = they can do that.

The following is an example of ho= w you may want to convey key monitoring scenarios for the customers.

The SQL Server Management Pack for Operations Manager 2007 includes a number of key monitoring scenarios that are configurable. The following table lists those scenarios and indicates the elements of the monitoring scenario that can be modified.

Scenario

Configurable Elements=

Block analysis

Modify the time threshold, which by default is one m= inute.

Database configuration monitoring

Enable this monitoring feature and configure the dat= abase configuration settings that you want to apply to your environment.

Troubleshooting

List issues and associated fixes = or workarounds. When possible, use an Issue/Cause/Resolution approach. Dependi= ng on the type and amount of content, use tables, lists, or headings to make t= he page easy for the user to read and navigate. You can also create topics wit= hin this section if that is most appropriate for your content.

Appendix: Reports

Describe the reports included wit= h the management pack.

The following reports are included in this management = pack. Allow up to thirty minutes for reports from a new management pack to appear= in the Reporting console.

Appendix: Scripts

Customers often request additional details about the scripts included in a management pack. At a minimum, we recommend you list and describe the included scripts. For an example of a g= ood script reference, see http://www.microsoft.com/technet/opsmgr/2005/library/dirmgmtpack/dirmgmtpac= kmom_5.mspx.

Category	Object Type=	Discovered Automatically
SQL Server Roles	SQL Server 2005 DB Engine	Yes
SQL Server Roles	SQL Server 2000 DB Engine	No

Scenario	Configurable Elements=
Block analysis	Modify the time threshold, which by default is one m= inute.
Database configuration monitoring	Enable this monitoring feature and configure the dat= abase configuration settings that you want to apply to your environment.