Getting Started

  • Article

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

Before you import the management pack

For the Remote Desktop Services Management Pack to function optimally, your computers must meet the following requirements:

  • Each RD Session Host server must be managed by Operations Manager 2007.

  • Each Remote Desktop license server must be managed by Operations Manager 2007.

  • Each RD Connection Broker server must be managed by Operations Manager 2007.

  • Each RD Web Access server must be managed by Operations Manager 2007.

  • Each RD Gateway server must be managed by Operations Manager 2007.

  • Each RD Virtualization Host server must be managed by Operations Manager 2007.

  • The Windows Server Base Operating System Management Pack must be installed on the computer running Operations Manager 2007 to use some of the Remote Desktop Services Management Pack features, including most of the performance views.

Files in this management pack

To monitor Remote Desktop Services, you must first download the Remote Desktop Services Management Pack from the Management Pack Catalog (https://go.microsoft.com/fwlink/?LinkId=82105).

The Remote Desktop Services Management Pack includes the following files:

File Name Description

Microsoft.Windows.Server.RemoteDesktopServices.2008R2.mp

Required for monitoring computers running Remote Desktop Services.

Microsoft.Windows.Server.RemoteDesktopServices.Library.mp

Required for discovering objects, monitoring objects, and viewing information.

OM2007_MP_RDS.doc

Includes additional information for the Remote Desktop Services Management Pack.

How to import the Remote Desktop Services Management Pack

For instructions about importing a management pack, see How to Import a Management Pack in Operations Manager 2007 (https://go.microsoft.com/fwlink/?LinkID=98348).

After the Remote Desktop Services Management Pack is imported, create a new management pack in which you store overrides and other customizations.

Create a new management pack for customizations

Most vendor management packs are sealed so that you cannot change any of the original settings in the management pack file. However, you can create customizations, such as overrides or new monitoring objects, and save them to a different management pack. By default, Operations Manager 2007 saves all customizations to the Default Management Pack. As a best practice, you should instead create a separate management pack for each sealed management pack you want to customize.

Creating a new management pack for storing overrides has 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.

For more information about sealed and unsealed management packs, see Management Pack Formats (https://go.microsoft.com/fwlink/?LinkId=108355). For more information about management pack customizations and the default management pack, see About Management Packs in Operations Manager 2007 (https://go.microsoft.com/fwlink/?LinkId=108356).