<iframe height="0" src="//www.googletagmanager.com/ns.html?id=GTM-ZWF6" style="display:none;visibility:hidden" width="0"></iframe> < div style="display:none;">< img src="//pixel.quantserve.com/pixel/p-13DPpb-yg8ofc.

gif" border="0" height="1" width="1" alt="Quantcast">< /div>

www.bmc.co m

BMC PATROL for

Microso ft Window s

Servers

Getti ng

Start ed Guid

e
Supportin g
BMC PATROL KM for Microsoft Windows

Operating System 4.3BMC PATROL KM for Microsoft Windows Active Directory 1.6BMC PATROL KM for Microsoft Windows Active

Directory Remote Monitoring1.7B MC PATROL KM for Microsoft Windows Domain Services 1.5BMC PATROL KM for Microsoft

Cluster Server 1.7BMC PATROL Cluster Configuration Wizard 1.5BMC PATROL KM for Microsoft COM+ 1.3BMC PATROL KM for Microsoft

Message Queue 1.4BMC PATROL KM for Event Management 2.8BMC PATROL KM for Log Management 2.6.10BMC PATROL Wizard

for Microsoft Performance Monitor and WMI 2.1BMC PATROL Adapter for Microsoft Office 1.1BMC PATROL Agent 3.8.50

October 2010

Contacting BMC Software

You can access the BMC Software

website athttp://www.bmc. com.From this website, you can obtain informationabout the company, its products, corporate offices, special events, and career opportunities.

United States and Canada

Address BMC SOFTWARE INC2101 CITYWEST BLVDHOUSTON TX 77042-2827USA Telephone 7139188800 or8008412031

Fax 7139188000

Outside United States and Canada

Telephone (01)7139188800 Fax (01)7139188000
Copyright 2007,

2009 - 2010 BMC Software, Inc.BMC, BMC Software, and the BMC Software logo are the exclusive properties of BMC Software, Inc., are registered with the U.S. Patentand Trademark Office, and may be registered or pending registration in

other countries. All other BMC trademarks, service marks, andlogos may be registered or pending registration in the U.S. or in other countries. All other trademarks or registered trademarks are theproperty of their respective owners.DB2

is the trademark or registered trademark of International Business Machines Corporation in the United States, other countries, orboth.Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their

respective owners.UNIX is the registered trademark of The Open Group in the US and other countries.All other trademarks belong to their respective companies.The information included in this documentation is the proprietary and

confidential information of BMC Software, Inc., its affiliates, orlicensors. Your use of this information is subject to the terms and conditions of the applicable End User License agreement for the productand to the proprietary and

restricted rights notices included in the product documentation.

Restricted rights legend

U.S. Government Restricted Rights to Computer Software. UNPUBLISHED -RIGHTS RESERVED

UNDER THE COPYRIGHT LAWS OFTHE UNITED STATES. Use, duplication, or disclosure of any data and computer software by the U.S. Government is subject torestrictions, as applicable, set forth in FAR Section 52.227-14,

DFARS 252.227-7013, DFARS 252.227-7014, DFARS 252.227-7015, andDFARS 252.2277025, as amended from time to time. Contractor/Manufacture r is BMC SOFTWARE INC, 2101 CITYWEST BLVD,HOUSTON TX 77042-2827, USA. Any contract notices

should be sent to this address.

Customer support
You can obtain technical support by using the BMC Software Customer Support website or by contacting

CustomerSupport by telephone or e-mail. To expedite your inquiry, see Before contacting BMC.

Support website
You can obtain technical support from BMC 24 hours a day, 7 days a week athttp://www.bmc. com/support .From thiswebsite, you can
s

read overviews about support

services and programs that BMC offers

s

find the most current information about BMC products

s

search a database for issues similar to

yours and possible solutions

s

order or download product documentation

s

download products and maintenance

s

report an issue or ask a question

subscribe to receive proactive e-mail alerts when new product notices are released
s

find worldwide BMC support center locations and contact

information, including e-mail addresses, fax numbers, andtelephone numbers

Support by telephone or email

In the United States

and Canada, if you need technical support and do not have access to the web, call 8005371813 orsend an e-mail message tocustomer_support @bmc.com.(In the subject line, enter SupID

:< yourSupportContract ID> ,such as SupID:12345). Outside the United States and Canada, contact your local support center for assistance.

Before

contacting BMC
Have the following information available so that Customer Support can begin working on your issue immediately:
s

product information

product name product version (release number) license number and password (trial or permanent)
s

operating system and environment information

machine type operating system type, version, and service pack or other maintenance level such as PUT or PTF system hardware configuration serial numbers related software

(database, application, and communication) including type, version, and service pack ormaintenance level
s

sequence of events leading to the issue

s

commands and options that you used

s

messages received (and the time and date that you received them) product error messages messages from the

operating system, such as

file system full

messages from related software

4 BMC PATROL for Microsoft

Windows Servers Getting Started

License key and password information

If you have

questions about your license key or password, contact BMC as follows:

s

(USA or Canada)

Contact the Order Services Password Team at 8008412031, or send an e-mail message

toContractsPasswor dAdministration@b mc.com.

s

(Europe, the Middle East, and Africa)

Fax your questions to EMEA Contracts Administration at +31203548702, or sendan e-mail

message topassword@bmc.co m.
s

(Asia-Pacific)

Contact your BMC sales representative or your local BMC office.

Contents5

Conte nts
Chapter 1

Product compone nts and capabilit ies17 PATROL for Windows Servers features. . . . . . .

............. ............. .... .18Centralized event filtering and notification. ............. ............. . . . . .18Ability

to deploy configuration settings . . . . . . . ............. ............. .18Built-in recovery actions. .............. ..............

.............. .... .18Predefined rulesets for common server types. . . . . . . . . ............. ....... .19Virtualization

with Hyper-V . . . .............. .............. ............ .19Product components . . . . .............. .............. ..............

....... .20PATROL KM for Microsoft Windows Operating System. . . . . . . ............ .21PATROL KM for Microsoft

Windows Active Directory . . . . . . ............. . .22PATROL KM for Microsoft Windows Active Directory Remote

Monitoring . . .28PATROL KM for Microsoft Windows Domain Services. . . . . . . ............. .30PATROL KM for Microsoft

Cluster Server . . ............. ............. . . . .30PATROL Cluster Configuration Wizard . . . . . . . ............. .............

.31PATROL KM for Microsoft Message Queue (MSMQ). . . . . . ............. . . . .31PATROL KM for Microsoft COM+. . . . . . . . . ..............

.............. . .31PATROL KM for Log Management . . . ............. ............. ........ .32PATROL KM for Event

Management . . . ............. ............. ...... .33PATROL Wizard for Microsoft Performance Monitor and

WMI. . . . . . . . . .... .34PATROL History Loader KM . . . . . . . . . . .............. .............. . . . . .34PATROL Adapter for

Microsoft Office ............. ............. ........ .34PATROL Agent . . . . . . . . . .............. .............. ..............

. . . .34Services . . ............... ............... ............... ............... . . .35Related documentation. . . .............. ..............

.............. . . . . . . .35Where to go from here. . .............. .............. .............. . . . . . . . . .35 Chapter 2 Installing

and migrating PATROL for Windows Servers37 Installation overview. . . . . . . ..............

.............. .............. .... .38Verifying installation requirements . . . ............. ............. ...........

.39System requirements. . . . .............. .............. .............. .... .39Additional componentspecific

requirements. . . . ............. ............ .40Accounts. . . . .............. .............. .............. .............. .43Preparing for

installation . . . . . .............. .............. .............. . . .49Turning off pop-up blocking software before installing. . . . . . .............

. .49Unsupported platform option in the installation utility user interface. . . . . . . . .50Extraneous target platform

options available in the installation utility userinterface . . . .............. .............. .............. .............

.50Checking for product patches or fixes before installing . . . . . ............. .. .50Determining how to install products . . . . . .

............. ............. . . . . .51 6 BMC PATROL for Microsoft Windows Servers Getting Started

Determining the version of the installation utility . . . . . . . . ............. .... .51Determining where to install the PATROL

Agent . . . . . . . . ............. .... .51Installing the PATROL Agent over an existing installation . . . . ............. .51Extracting

installation files after download. . ............. ............. ... .52Determining where to install KMs . . . . . . . . . .............

............. . . . .52PATROL Security levels . . .............. .............. .............. ...... .53Checking security levels . .

.............. .............. .............. . . . .54Assessing and implementing a different security level . . . . . . . . . ............

.54Default and custom installation types. . . . . . . . . ............. ............. . . . . .54Firsttime installation. ..............

.............. .............. .......... .55Installing for the first time . . . . .............. .............. ............. .55First-time

installation using Distribution Server. . . . . . . . ............. ......... .60Distribution Server features . . .............. ..............

.............. .60Importing a CD or customized installation package into Distribution Server. . .61Installing

with the Distribution Server (overview). . . . . ............. ....... .62Upgrading from an earlier version . . . . . . .

............. ............. ........ .63Automatic migration of console and agent customizations . .............

... .63Determining whether you can migrate KM customizations. . ............. . . .64Conditions for upgrading. . . .............

............. ............. .... .64Determining the location of PATROL. . . . . . . .............. .............. . .65PATROL for

Windows Servers upgrade scenarios. . . . . . ............. ......... .66Upgrading without saving KM customizations .

............. ............. .68Upgrading and preserving KM customizations . ............. ............. .68Preparing to

upgrade. . . . . . . . .............. .............. .............. .69Migrating customizations with the PATROL Configuration

Manager. . . . . . . . .70Creating an installation package of the migrated and merged KM. . . . ....... .70Moving files from the

PATROL_CACH E directories. . . . ............. ...... .71Migrating customizations manually. . . . . . ............. .............

..... .72Installing PATROL KM for Microsoft Cluster Server. . ............. ........... .73External cluster-level

agent architecture . . . . ............. ............. . . . .74Internal cluster-level agent architecture. . . . .............

............. . . . . .75How to Install the PATROL KM for Microsoft Cluster Server. . ............. .76Consideration s for using online

Help . . . . . . . . . ............. ............. . . . . .77Browser version required for viewing PATROL Console for UNIX Help . . . .

. .78Additional considerations for using online Help for UNIX . ............. ... .78Uninstalling PATROL for Windows Servers

............. ............. ....... .80Determining the version of the installation utility . . . . . . . . ............. ....

.80Uninstalling PATROL for Windows Servers on Windows. . . . . . ............ .81Where to go from here. . . . . . ..............

.............. .............. . . . . .85 Chapter 3 Loading and configuring PATROL for Microsoft

Windows Servers87 Preparing to use PATROL for Windows Servers. . . . . . . . ............. ......... .89Loading and

preloading KMs . ............. ............. ............. . . .90Loading the PATROL for Microsoft Windows Servers KMs . . .

............. .91Preloading KMs on the PATROL Agent. ............. ............. ....... .94Requirements for configuring

from the PATROL Console. . . . . . . ........... .97Configuring the PATROL KM for Microsoft Windows OS. . .

............. .... .101Enabling and disabling system monitoring. . . . . ............. ............ .102Configuring Windows events

monitoring. . . . . ............. ............. .103 Contents7 Configuring service monitoring . . . . .............

............. ......... .114Configuring process monitoring. . . . . ............. ............. ........ .117Creating

custom parameters . . . . . ............. ............. ........... .124Viewing event logs . . . . . . .............. ..............

.............. .. .125Configuring Blue Screen monitoring . . . . ............. ............. ..... .126Notifying

when disks are not present . . . . ............. ............. .... .126Providing nonaggregate values for a drive instance . .

............. ....... .127Configuring recovery actions. .............. .............. .............. . . .128About recovery actions.

.............. .............. .............. . . . . .128Built-in native recovery actions. . . . . . . . .............. .............. ....

.129Configuring built-in native recovery actions ............. ............. .. .130Configuring e-mail notification . . . . .

.............. .............. .......... .132Using notification scripts . . . . . . . . .............. .............. .........

.133Defining notification servers . . . . . . . . .............. .............. ...... .136Assigning notification servers for the

remote agents. . . ............. ...... .138Assigning notification targets for a PATROL alert. . ............. .........

.140Configuring the PATROL KM for Microsoft Active Directory. . . . . . ........... .141Configuring PATROL Wizard for

Microsoft Performance Monitor and WMI . . . .142Loading the PATROL Wizard for Microsoft Performance

Monitor and WMI .142Creating performance monitor parameters. . . . . ............. ............ .143Setting alarm

thresholds. . . . . . .............. .............. ............ .144Creating WMI parameters .............. .............. ..............

.. .144Configuring the PATROL KM for Log Management. . . . ............. ........ .147Stop and start monitoring

all default log files. . . . . . . . . . ............. . . . . . .149Stop monitoring a log file. . . . . . . . . . . .............. .............. . . . . . . .149Start

monitoring a log file. . . . . . . . . . . .............. .............. ...... .150Change the setup of a monitored file. . . .............

............. ...... .156Filter log file messages (create a search string). . . . . . . . ............. ...... .157Generate a

custom event when a search string is identified. . . . . . .......... .160Configure recovery actions for a log file . . . .............

............. ... .164Configuring the PATROL KM for Microsoft Cluster Server. . ............. . . . . .165Using

the PATROL Adapter for Microsoft Office to view reports. . ............ .166Displaying PATROL data by using the PATROL

Adapter for Microsoft Office167How to use the PATROL Adapter for Microsoft Office ............. ......

.168Built-in report templates. .............. .............. .............. ... .168Removing KMs from your console and

agent. . . . . . . . . ............. ......... .170Unloading KMs from a PATROL console . . . . . . . ............. ...........

.171Stopping preloaded KMs from running on the PATROL Agent. . . . . . . . . . . . .173 Chapter 4 Using the PATROL

Cluster Configurat ion Wizard175 Using the PATROL Cluster Configuration Wizard . . . . . . .

............. ...... .176Overview . . .............. .............. .............. .............. .176Preparing to use the PCC

Wizard. . . . . . . . ............. ............. . . . . .177Access requirements for running the PCC Wizard . . . . . . . ............. . . . .177Starting

the PCC Wizard . .............. .............. .............. . . .177How to use the PCC Wizard . . . . . . . ............. .............

......... .178Post-PCC configuration. . . . .............. .............. .............. .... .183Manually configuring the

PATROL Agent for clustering . . . ............. . . . . . .183Install the application on each cluster node . . . . . . . . . ............. . . . . . . . .183

8 BMC PATROL for Microsoft Windows Servers Getting Started

Install the PATROL Agent on each cluster

node. . . . . . . . . . ............. . . . .184Assign a unique port number . . . . . . . ............. ............. ........ .184Distribute

license file. . . . . .............. .............. .............. . . .184Define the PATROL cluster-specific environment variables. . . . . . .

......... .184Create and register a new service for the PATROL Agent ............. . . . . .185Define the PATROL Agent as a

member of the group. . . . . . . . . ............ .186PATROL cluster-specific environment variables for history and configuration . .

.189Variables . . . ............... ............... ............... ........... .189Operation. . . ............... ............... ...............

........... .190Example. . . . ............... ............... ............... ........... .191Unattended configuration of Cluster

Configuration Wizard . . . . . . . ........... .191 C h a p t e r 5 M o n i t o r i n g

r e m o t e h o s t s 1 9 3 Introduction. . . . .............. .............. .............. .............. .193Prerequisites

for remote monitoring . . . . ............. ............. ......... .195Authenticatio n. . . . . . . . . . . . . .............. ..............

.............. ... .195Configuring PATROL KM for Windows for remote monitoring . . . . ........... .195

Application classes to configure remote monitoring . . . . ............. . . . . . . . .196 Supported application

classes. . . . . . . . . .............. .............. ........ .196Object hierarchy for remote monitoring. . . . . .............

............. ..... .196Parameters for remote monitoring. . . . . ............. ............. .......... .197Supported

tasks for remote monitoring . . . . ............. ............. . . . . . . .198 Chapter 6 Troubleshoo ting PATROL

for Microsoft Windows Servers199 PATROL KM for Microsoft Windows OS problems. . . . . .

............. ....... .200Process or job object data not displayed. . . ............. ............. .... .200PATROL

Generates Event 560 and 562 in the Windows security event log. . . .201Event filter parameters not automatically acknowledged. .

............. . . . .201Newly installed protocols are not discovered. . . . . ............. .......... .201Event log summary

instance cannot be removed. . . . ............. ........ .202Windows event log does not work . . . . . . ............. .............

..... .202Multiple processes are selected when you select a single process . . ......... .203PATROL Agent has

DiscoveryStatus parameter in alarm. . . . . . . . . ......... .203Mount point monitoring and logical disk quotas does not work. . . . . . . . .

... .203PATROL KM for Event Management problems . . . . . . ............. .......... .204Too many email alerts are

being generated . ............. ............. .. .204Parameters settings lost after agent restart . . . ............. .............

. .205PATROL KM for Event Management not working as expected. . . . . . ....... .206AS_AVAIL ABILITY application not

displayed. . . . . . . .............. ...... .206Problems with all other KMs . . . . . . . . . . .............. .............. .......

.207Cannot add performance monitor counters with alarm ranges less than 1 . . . .207AdPerfColle ctor parameter display error

message. . . . . . . ............. .... .208Recovery action problems. . .............. .............. .............. ....

.209Recovery actions do not execute . . . . . . . . .............. .............. . . . .209Even though I select Do not ask me again PATROL

prompts before runningrecovery action. . . . . . . . . .............. .............. .............. . .209Gathering diagnostic information . . . .

............. ............. ........... .210Locations where you can find diagnostic information. . . . ............. . . . . .210

Contents9

Installation logs . .............. .............. .............. .......... .210Determining PATROL KM version number. .

............. ............. . .211 Appendix AAccessing menu commands, InfoBoxes,

and online Help213 Accessing KM commands and InfoBoxes . . . . . ............. ............. ... .214Accessing

online Help. . . . . .............. .............. .............. . . . . .215 Appendix BAgent configura

tion variables and rulesets2 17 Managing configuration variables. . . . . . .

............. ............. ........ .218PATROL for Windows Servers configuration variables . . . . . . ............. ...

.218PATROL KM for Microsoft Windows OS . . . ............. ............. . . .218PATROL KM for Microsoft

Windows Domain Services. . . . . . . ............ .241PATROL KM for Microsoft Active Directory . . . . . . .............

......... .244PATROL KM for Microsoft Cluster Server . . ............. ............. . . .248PATROL KM for

Microsoft Windows Message Queue. ............. ...... .253PATROL KM for Microsoft COM+. . . . . . . . . ..............

.............. .254PATROL Wizard for Microsoft Performance Monitor and WMI. . . . . . . . . ... .255PATROL for

Microsoft Windows Servers ............. ............. ..... .256PATROL for Microsoft Windows Servers rulesets. . . . . . . .

............. ...... .257PATROL KM for Event Management required . . . . . . . ............. ...... .257Using

PATROL Configuration Manager to apply rulesets. . ............. . . .257Server roles with predefined rulesets. . . . . . . .

............. ............. . .258Ruleset reference . . . . . . .............. .............. .............. . . . . .260Using PATROL

Configuration Manager . . . . . . ............. ............. . . . .269Using PCM to apply configurations changes to other agents. . . . . . . .

....... .269Manually creating or changing configuration variables . . . . . . ............. .270 A p p e n d

i x C P A T R O L f o r W i n d o w s . k m l f i l e s 2 8 1 PATROL for

Microsoft Windows Servers .kml files. . . . . . ............. ....... .282PATROL KM for Microsoft Windows OS . . .

............. ............. . . .282PATROL KM for Microsoft Windows Active Directory . . . . . . ............. .285PATROL

KM for Microsoft Windows Active Directory Remote Monitoring . .286PATROL KM for Microsoft

Windows Domain Services. . . . . . . ............ .286PATROL KM for Microsoft Cluster Server . . .............

............. . . .287PATROL KM for Microsoft COM+. . . . . . . . . .............. .............. .287PATROL KM for Microsoft

Message Queue. ............. ............. . . .288PATROL Wizard for Microsoft Performance Monitor and WMI. . . . . . . . .

... .288PATROL KM for Log Management . . . ............. ............. ....... .289PATROL History Loader

KM . . . . . . . . . . .............. .............. . . . .289PATROL KM for Event Management . . . ............. ............. .....

.289PATROL for Microsoft Windows Servers rulesets. . . . . . . . ............. . . . .290 Index 295 10 BMC PATROL

for Microsoft Windows Servers Getting Started Figures11

Figur

es
Upgrading overview for PATROL for Windows Servers . . . . . . . .............

. . .67PATROL KM for Microsoft Cluster Server with external CLA configuration . . . . . .75PATROL KM for

Microsoft Cluster Server with internal CLA configuration . . ... .75Collection architecture for remote

monitoring . . . . ............. ............. .194Object hierarchy for remote monitoring . . . . ............. .............

..... .197Shipped rulesets in PATROL Configuration Manager . . . . . . ............. . . . . .260Using the child_list and

variable_list variables . . . . . . ............. . . . . . . . . . . .272 12 BMC PATROL for Microsoft Windows Servers Getting

Started Tables13

Table s
Monitored events

- DNS name registration . . . . ............. ............. . . . .26Core Active Directory service monitored events .............

............. . . . .26File replication service/group policy monitored events . . . . . . . . ............. . . .27Time synchronization

service monitored events ............. ............. . . . .27Kerberos monitored events .............. .............. ..............

..... .27Netlogon monitored events .............. .............. .............. ..... .28PATROL for Microsoft

Windows Servers Services . . . . . . ............. ........ .35System requirements for installing and using PATROL for Windows

Servers . . . .39Advanced user rights . . . . . .............. .............. .............. ..... .44Removing rights and

admin group membership from the PATROL Agent ...... .45Versions that you can migrate . .............. ..............

.............. . . .64Choosing an upgrade procedure . . . . . ............. ............. ........... .65Default values for

PATROL location variables . . . . . . ............. ............ .65KM file naming patterns . .............. ..............

.............. ...... .71Monitoring configuration options for PATROL KM for Microsoft Cluster Server . .74PATROL for

Microsoft Windows Servers .kml files . . . . . . ............. ...... .90Console functionality that requires local admin rights . . .

............. ........ .97PATROL KM for Microsoft Windows OS configuration tasks . . . . . . . . . ....... .101Enabling and

disabling system monitoring . . . . ............. ............. . . .102Event filter events:example . . .............. ..............

.............. . . .105Event filter options . . . .............. .............. .............. ........ .106Default service

monitoring flags . .............. .............. ............. .114Service monitoring options . . . . . . . . .............. ..............

.......... .115Configuratio n variable and service restart: combinations . . ............. ..... .116Process monitoring

options . . . . . . . . .............. .............. .......... .117Regular expression syntax .............. .............. ..............

..... .117Process control options . . .............. .............. .............. ...... .122Event details displayed

in the Windows Event Viewer dialog box . . . . ........ .126Built-in recovery actions . .............. .............. ..............

..... .129Selecting a recovery action instance . . . . . . . .............. .............. .... .131Recovery action

configuration options . . . . . . . ............. ............. ... .131Notification script location on Windows . . . . . . .............

............. ... .134Requirement s for notification server when using Windows e-mail clients . . . . . . .134Quick Config -

Notification Server dialog box properties . . ............. ..... .138Notification server properties . .............. ..............

.............. . .139PATROL Wizard for Microsoft Performance Monitor and WMI Tasks . . . . .... .142Reports for

PATROL KM for Microsoft Windows OS . . . ............. ....... .168Reports for PATROL KM for Microsoft Windows

Domain Services ........... .169Reports for PATROL KM for Microsoft Message Queue . ............. ....... .170Reports for

PATROL for Microsoft COM+ .............. .............. . . . . . .170 14 BMC PATROL for Microsoft Windows

Servers Getting Started

Information required by PCC . .............. .............. .............. . .178Cluster administration

properties . . . . . ............. ............. .......... .186PATROL cluster-specific environment variables . . . . . . .............

......... .189Operation of configuration and history environment variables . . . . . . .......... .190Parameters for remote

monitoring . . . . ............. ............. .......... .197Accessing KM Commands and InfoBoxes . . ............. .............

...... .214Accessing online Help . . . . .............. .............. .............. ..... .215PATROL KM for

Microsoft Windows OS variables . . . . . . ............. ....... .219PATROL KM for Windows Domain Services variables . . . . . .

............. ... .241PATROL KM for Microsoft Active Directory variables . . . . . . ............. ....

.244PATROL KM for Microsoft Cluster Server variables . . . . . . ............. ...... .248PATROL KM for Windows

Message Queue variables . . . . . . ............. .... .253PATROL KM for Windows COM+ variables ............. .............

..... .254PATROL Wizard for Performance Monitor and WMI variables . ............. . .255PATROL for Microsoft

Windows Servers variables . . . . . . ............. ...... .256Server roles . ............... ............... ............... ..............

.258Configuratio n variable locations . . . . . . .............. .............. ........ .260Application server ruleset . . . ..............

.............. .............. . . .261Terminal server ruleset . . . .............. .............. .............. ..... .262Remote

access / VPN server ruleset . . . ............. ............. .......... .263Print server ruleset . . . . . . . . .............. ..............

.............. . . . .263Domain controller ruleset .............. .............. .............. . . . . . . .263File server ruleset . . . ..............

.............. .............. .......... .264Mail server ruleset . . . . . . . . .............. .............. .............. . . . . .264DNS

server ruleset . . . .............. .............. .............. ......... .265WINS server ruleset . . . . . . . . .............. ..............

.............. . . .265DHCP server ruleset . . . .............. .............. .............. ....... .266Streaming media server

ruleset . . . . . . . . .............. .............. ....... .266SMS primary site ruleset . . . . . .............. .............. ..............

. . .267SMS site ruleset . . . . . . . . . ............... ............... ............... . . .268Special characters required for pconfig variables

............. ............. . . .271Example: adding a service to monitor . . . . . .............. .............. .... .273Example:

adding a process to monitor . . . . . ............. ............. ...... .274Example: adding an event filter to monitor . .............

............. ...... .276Example: changing parameter thresholds . . . . . ............. ............. ...

.278Understandi ng the THRESHOLDS rule . . . . . . . . . . ............. ............. .278Example: Inactivating or deactivating a

parameter . . . . . ............. ........ .279PATROL KM for Microsoft Windows OS NT_LOAD.kml file . . . . . . . . . .

....... .282PATROL KM for Microsoft Windows OS NT_BASE.kml file . . . . . . . . . . ....... .284PATROL

KM for Microsoft Windows OS NT_HYPERV.kml file . . . . . ......... .285PATROL KM for Microsoft

Windows Active Directory .kml file . . . . . . . . . . .... .285PATROL KM for Microsoft Windows Active Directory

Remote Monitoring .kml file286PATROL KM for Microsoft Windows Domain Services .kml file . . . . . . ........

.286PATROL KM for Microsoft Cluster Server .kml file . . . . . . . .............. .... .287PATROL KM for Microsoft COM+ .kml file .

.............. .............. . . . .287PATROL KM for Microsoft Message Queue .kml file . . . . . . ............. .....

.288PATROL Wizard for Microsoft Performance Monitor and WMI .kml file . . ..... .288PATROL KM for Log

Management .kml file . . . . . . . . . . . .............. . . . . . . .289 Tables15 PATROL History Loader KM .kml file . . . . . . . . . . . ..............

........... .289PATROL KM for Event Management .kml files . . . . . . ............. .......... .289PATROL for Windows Ruleset

.kml files . . . . . . .............. .............. .290 16 BMC PATROL for Microsoft Windows Servers Getting

Started Chapter 1Product components and capabilities17 Chapter

1
1

Prod uct comp

onen ts and

capa bilitie s

BMC PATROL for Microsoft Windows Servers Getting Started

provides the necessaryinform ation and instructions for installing and

configuring the PATROL forMicrosoft Windows Servers product (also referred to as PATROL for WindowsServers ). This chapter

provides a brief overview of PATROL for Windows Serversand covers the following topics:PATROL for Windows

Servers features. . .............. .............. ....... .18Centralized event filtering and notification. ............. .............

. . . . .18Ability to deploy configuration settings . . . . . . . ............. ............. .18Built-in recovery actions. ..............

.............. .............. .... .18Predefined rulesets for common server types. . . . . . . . . ............. .......

.19Virtualization with Hyper-V . . . .............. .............. ............ .19Product components . . . . .............. ..............

.............. ....... .20PATROL KM for Microsoft Windows Operating System. . . . . . . . ........... .21PATROL KM

for Microsoft Windows Active Directory . . . . . . ............. . .22PATROL KM for Microsoft Windows Active Directory

Remote Monitoring . . .28PATROL KM for Microsoft Windows Domain Services. . . . . . . ............. .30PATROL KM

for Microsoft Cluster Server . . .............. .............. . .30PATROL Cluster Configuration Wizard . . . . . . . . ..............

........... .31PATROL KM for Microsoft Message Queue (MSMQ). . . . . . ............. . . . .31PATROL KM for Microsoft COM+. . . . . . . . .

.............. .............. . .31PATROL KM for Log Management . . . . .............. .............. ..... .32PATROL KM

for Event Management . . . . .............. .............. . . . .33PATROL Wizard for Microsoft Performance Monitor and

WMI. . . . . . . . . . . . . .34PATROL History Loader KM . . . . . . . . . . .............. .............. . . . . .34PATROL Adapter for Microsoft Office

.............. .............. ...... .34PATROL Agent . . . . . . . . . ............... ............... ............... .34Services . . . . .

............... ............... ............... .............. .35Related documentation. . . .............. .............. ..............

. . . . . . .35Where to go from here. . .............. .............. .............. . . . . . . . . .35 PATROL for Windows Servers

features18 BMC PATROL for Microsoft Windows Servers Getting Started

PATR

OL for Windo ws Server

s feature s
The PATROL for Windows

Servers product allows you to monitor and manageMicrosof t Windows servers. The versions of Microsoft Windows servers

that aremonitored depend upon the version of the PATROL for Microsoft Windows Serversthat you are using. For a

complete list of supported platforms and versions, see the PATROL for Microsoft Windows Servers Release Notes .

Centraliz ed event filtering and notificati

on
With PATROL, you can centralize and correlate events. This ability enables you touse paging and

e-mail to bring issues to the experts' attention for quick resolution.For more information, see Configuring

e-mail notification on page132.

Ability to deploy configur

ation settings
PATROL for Microsoft Windows Servers supports the PATROL

ConfigurationM anager, which allows you to configure and deploy KM configuration settings toother servers in your environment. To

support the PATROL Configuration Manager,all PATROL for Microsoft Windows Servers configuration

settings are stored as agentconfigurati on variables. For a complete list of the agent configuration variables forPATROL for

Microsoft Windows Servers, seeAppendixB, Managing configurationvar iables.

Built-in

recovery actions
PATROL for Microsoft Windows Servers provides the following

automated, builtinrecovery actions. Recovery actions are corrective actions taken by PATROL when aparameter

reaches a set value. You can configure these recovery actions to runautomaticall y or only with operator intervention.

terminating a run-away process

s

clearing the temp directory

s

backing-up and clearing event

logs
s

restarting processes
s

restarting failed services

s

increasing available DFS

connections when utilization is high

s

increasing share connections when utilization is high

s

initiating WINS

scavenging when replication fails PATROL for Windows Servers featuresChapter 1Product components and

capabilities19
s

restarting the Windows Management Instrumentation (

WINMGMT.exe

) service

toensure that WMI data is available

s

restarting a PATROL Agent on a remote serverFor more information

about specific recovery actions, see the online Help, which youcan access from the PATROL console, or see Configuring

recovery actions onpage128.

Predefin ed rulesets

for common server types

PATROL for Microsoft

Windows Servers provides rulesets that provide appropriatemoni toring setups for common server types, such as a

file server or an applicationserve r. Using the PATROL Configuration Manager, you can automatically configurethe

server monitoring by applying these provided rulesets to the appropriate server.If necessary, you can then adjust

your configuration and save it in the ruleset, whichyou can then apply to other servers. For more information

about the rulesets andusing the PATROL Configuration Manager to manage your configuration, see Using PATR

OL Configuration Manager to apply rulesets on page257.

Virtualiza tion with

Hyper-V
Microsoft Windows provides virtualization called Hyper-V. PATROL KM forMicrosoft

Windows allows you to monitor and gather information about of HyperVentities by using the application classes and their

parameters. The new hypervisorplatfo rm works with Windows Server 2008 to create and manage a virtualinfrastruc ture.Hyper-V

consists of a 64bit hypervisor that can run 32bit and 64-bit virtualmachines concurrently. Hyper-V virtualization works with

single and multi-processor virtual machines and includes tools such as snapshots, which capture thestate of a running virtual

machine.The KM allows you to monitor the following Hyper-V entities:

Hypervisor
The product reports

information about the number of monitored notificationsregi stered with a hypervisor, the bootstrap and deposited pages,

and the partitions,virtual processors, logical processors, and the running partitions present. Product

components20 BMC PATROL for Microsoft Windows Servers Getting Started

Logical processors of

the system
The product reports information about the rate of the virtual processor contextswitches on a logical

processor, the rate of hardware and hypervisor interrupts on aprocessor, and the percentage of time that a processor spends in the

guest andhypervisor codes.

Partitions of the system

The product reports information

about the partitions present in the system, and thesummary and state of all the partitions. It reports the number of

virtual processorsassoci ated with a partition, the total memory allocated to a partition, the qualifieddomain name, the

operating system and its version, the service pack, and so on. Italso displays the process ID of the worker process

corresponding to the partitions,and the uptime of the partition.

Virtual processors of the partition

The product reports information about the virtual processors such as the resourcesavailab le to a partition and the number

of partitions that you can run at a time. Itdisplays the allocation of resources by the hypervisor to a partition when partitionscompet

e for resources. It reports the rate of hypervisor intercept messages. It alsoreports the percentage of time that a

processor spends in the guest and hypervisorcodes .

Virtual hard disks of a partition

The product reports information about virtual hard disks of a partition such as theirtype, size on the physical disk, maximum

size as viewable by the partition, and thepercentage of use of the types of virtual hard disks.

Produ ct compo nents

The PATROL for Windows Servers product includes components and KnowledgeMod ules (KMs) that manage and monitor

elements of your server environment. AKM is a set of instructions that the PATROL Agent uses to monitor objects in

yourenterprise. PATROL for Windows Servers includes the following components andKMs, which are described in the sections that

follow.
NOTE

To discover Hyper-V partitions and the data for each partition, the BMC PATROLAgent

default user must be added to the local administrator group. Product componentsCha pter 1Product components

and capabilities21
s

PATROL KM for Microsoft Windows Operating System

s

PATROL KM

for Microsoft Windows Active Directory

s

PATROL KM for Microsoft Windows Active Directory Remote

Monitoring
s

PATROL KM for Microsoft Windows Domain Services

s

PATROL Cluster Configuration

Wizard
s

PATROL KM for Microsoft Cluster Server

s

PATROL KM for Microsoft COM+

s

PATROL KM

for Microsoft Message Queue

s

PATROL KM for Event Management

s

PATROL KM for Log Management

PATROL Wizard for Microsoft Performance Monitor and WMI

s

PATROL Adapter for

Microsoft Office
s

PATROL Agent
s

PATROL History Loader KM

PATROL

KM for Microsoft Windows Operatin g System

The PATROL KM for Microsoft Windows OS monitors the availability of yourservers, which includes the following

elements:
s

disk space
s

disk drive usage

s

disk quotas and mount points

s

cache
s

CPU usage
s

memory usage
s

Windows event logs

s

Windows services
s

Window

processes
s

printer status
s

registry values
s

network usage
s

hypervisor
s

logical

processors
s

partitions
s

virtual processors
s

virtual hard disksWith the PATROL KM

for Microsoft Windows OS you can also perform the followingfunctio ns: Product components22 BMC PATROL

for Microsoft Windows Servers Getting Started

s

monitor and manage services

s

monitor system Stop errors and

manage dump files

s

create custom composite parameters that are based on existing parametersFor

information about configuring these features, see Configuring the PATROL KMfor Microsoft Windows OS

on page101.

PATROL KM for Microsoft Windows

Active Directory
The PATROL Knowledge Module for Microsoft Windows Active

Directory lets youmonitor and analyze your Microsoft Windows Active Directory environments.W hether you choose to

monitor and analyze one environment or many, PATROL KMfor Microsoft Windows Active Directory helps you

detect and notify if Microsoft Windows Active Directory generates errors orperforms slowly
s

monitor

performance of system resources

s

plan for capacity and availability

s

monitor all domain controllers

within a site
s

monitor all domain controllers between sites

s

anticipate and eliminate problems before

they become apparent to users of themonitored Active Directory environmentsFo r a brief description of

product features, see the sections that follow. For moredetailed information about how to use the product and complete descriptions of

theapplication classes and parameters, see the product online Help.

Managed systems
PATROL KM

for Microsoft Windows Active Directory monitors the performance of managed systems in a Microsoft Windows Active Directory

environment. A PATROLKM for Microsoft Windows Active Directory managed system is a Windows domaincontrolle r onto which

PATROL for Windows Servers has been installed.A managed system provides a view of its Microsoft Windows Active Directoryenviro

nment. Each managed system is responsible for monitoring MicrosoftWindo ws Active Directorys key indicators that are required to

ensure and maintainthe consistency of the Directory data and the desired level of service throughout theMicrosoft

Windows Active Directory forest. Product componentsCha pter 1Product components and capabilities23

Replicatio n monitorin g
PATROL KM for Microsoft Windows Active

Directory monitors the MicrosoftWindo ws Active Directory replication for errors and latency (to verify that

replicationoccur s within a reasonable time), both within a site (intrasite) and between sites(intersite) in the

configuration naming context and/or the domain context of thecurrent domain controller.Direct ory replication is monitored at

each managed system (domain controller). Thisfunctionalit y includes monitoring basic replication by creating synthetic

transactionsand verifying the replication of those transactions.

Intrasite replication monitoring

PATROL KM for Microsoft Windows Active Directory monitors the replication statusof the domain controller upon

which it is installed. It determines whether updatesfrom each domain controller within the site have been replicated

successfully and in atimely manner.

Intersite replication monitoring

Intersite replication

monitoring verifies that Microsoft Windows Active Directoryupdate s are successfully distributed between sites.

Each bridgehead server in a site ischecked to determine if Microsoft Windows Active Directory updates from othersites have

been successfully replicated to the bridgehead server. The intersitereplicati on interval is automatically determined at

each collection; it requires noconfiguration. However, if desired, you can override the automatic replicationinterv al determination,

on a site-by-site basis, by configuring the configurationdat abase (

pconfig

) variable,
/ActiveDirectory/ Configuration/

<site> /IntersiteReplicati onSchedule

. See the online Helpfor more information.

Replicatio n

collisions monitorin g
PATROL KM for Microsoft Windows Active Directory

enables users to configure theActive Directory object types that should be monitored for replication collisions. TheAD_AD_CN

F application class monitors replication collisions that occur duringreplicatio n when an object with the same Relative

Distinguished name is created inthe same container on two or more different domain controllers.

Replicatio n health monitorin g

PATROL KM for Microsoft Windows Active

Directory monitors the performance of Active Directory replication for the local server. The AD_AD_REPLI CATIONapplicat

ion class monitors this activity. Product components24 BMC PATROL for Microsoft Windows Servers Getting

Started

FSMO monitorin g
PATROL KM for Microsoft Windows Active

Directory monitors the availability of the forest-wide and domainwide flexible single master operations (FSMO) roles.

FSMO role connectivity monitoring

PATROL KM for Microsoft Windows Active Directory monitors the

connectivitystatu s of each of the five FSMO role holders from a domain controller. TheAD_AD_FS MO_ROLE_CO NNECTIVITY

application class monitors the domaincontrolle rs ability to locate and establish an LDAP connection with the FSMO

roleholder.

FSMO role placement monitoring

PATROL KM for Microsoft Windows Active Directory

monitors the placement of Active Directory FSMO roles in the domain and forest. TheAD_AD_FS MO_ROLE_PLA CEMENT

application class monitors the placement of these roles.

LDAP monitorin g

PATROL KM for Microsoft Windows Active Directory monitors LightweightDire ctory Access Protocol (LDAP) locally at each

monitored system for connectionavaila bility and response time. The AD_AD_LDAP application class monitors

theperformance of these LDAP requests.

SAM monitorin g
PATROL KM

for Microsoft Windows Active Directory monitors the Security AccountManager (SAM). SAM provides legacy NT

authentication support. TheAD_AD_SA M application class monitors these security requests.

Address

book monitorin g
PATROL KM for Microsoft Windows Active Directory

monitors the performance of Address Book requests made against the Microsoft Windows Active Directory server.The

AD_AD_ADDR ESS_BOOK application class monitors these requests.

Authentic ation

monitorin g
PATROL KM for Microsoft Windows Active Directory monitors Kerberos and

NTLMauthentica tion requests made against the Microsoft Windows Active Directoryserver. The AD_AD_AUTH ENTICATION

application class monitors these requests. Product componentsCha pter 1Product components and capabilities25

Domain Naming Service monitorin g

PATROL KM

for Microsoft Windows Active Directory verifies and monitors variousDNS record data for the Microsoft Windows Active

Directory server. TheAD_AD_DN S application class monitors the DNS specific information.

File Replicatio

n Service monitorin g
PATROL KM for Microsoft Windows Active Directory

monitors various aspects of file replication service health. The AD_AD_FRS application class monitors the FRSspecific

information.

Group policy monitorin g

PATROL KM for Microsoft

Windows Active Directory detects when a user account inone or more Group Policy Objects (GPO) cannot be resolved to a

security identifier(SID). The AD_AD_GPO application class reports this condition.

Lost and

found objects monitorin g

PATROL KM for Microsoft Windows Active

Directory monitors for the presence of objects in the LostAndFound container in the domain naming context of the domaincontroller

. The AD_AD_LOST_ AND_FOUND_ OBJECTS application class monitorsfor lost and found objects.

Event monitorin g
To measure the overall health of the domain controllers,

PATROL KM for MicrosoftWindo ws Active Directory configures the PATROL KM for Microsoft Windows OS

tomonitor various events pertaining to

s

DNS name registration

s

Core Active Directory service

File replication service and group policy

s

Time synchronization service

s

Kerberos
s

Netlogon

Events monitored by parameter s

Some parameters now monitor specific Active Directory events. See the Help for thePATROL KM for Window Active Directory

for information about these parameters. Product components26 BMC PATROL for Microsoft Windows Servers Getting

Started

Events monitored for specific areas of

failure
The following tables contain event information that is classified by specific areas of failure.

DNS name registration

To identify failures with the DNS name registration, PATROL KM for

WindowsActive Directory configures PATROL KM for Microsoft Windows OS to obtain eventinformatio n, as shown

inTable1.

Core Active Directory service

To identify failures with the core Active Directory

service, PATROL KM for MicrosoftWindo ws Active Directory configures PATROL KM for Microsoft

Windows OS toobtain event information, as shown inTable2.

File replication service and

group policy
To identify failures with the file replication service and group policy, PATROL KMfor Microsoft Windows Active

Directory configures PATROL KM for MicrosoftWindo ws OS to obtain event information, as shown

inTable3. Table1Monito red events DNS name registration Event LogSource EventSign ificance

SystemDNSAPI 11154, 11166domain controller does not have rights to performa secure dynamic update.S y s t e m DNSAPI11150 , 11162DNS

server timed outSystemDN SAPI11152, 1 1 1 5 3 , 11164, 11165Zone or currentlyconnected DNS server does notsupport dynamic

update.S y s t e m DNSAPI1115 1 , 1 1 1 5 5 , 11163, 11167A resource record for the domain controller is notregistered in DNS.S y s t e m N E TLOGON5773 DNS locator

record is not registered because t h e primary DNS server does not support dynamicupdate.S ystemNETLO GON5774A DNS domain

controller locator record i s n o t registered.

Table2Core Active Directory service monitored events

Event LogSource EventSign ificance DirectoryServicea l l sourcesSeverity = errorprimary error events for

Active DirectoryS y s t emLSASSS everity = errorLocal security authority is the core securitysubsystem for Active Directory.

Product componentsCha pter 1Product components and capabilities27

Time synchronizati on service

To identify events that may indicate problems maintaining uniform time in theActive Directory forest, PATROL KM

for Microsoft Windows Active Directorymonito rs the events shown inTable4.

Kerberos
To identify events that many

indicate problems with Kerberos, the defaultauthentic ation protocol, PATROL KM for Microsoft Windows Active Directorymonito

rs the event shown inTable5

Net Logon
To identify events that may indicate problems with Net Logon service and

protocol,which is required for proper domain controller functionality, PATROL KM forMicrosoft Windows Active Directory

monitors the events shown inTable6 onp a g e 2 8 . Table3File replication service/group policy

monitored events
Event logSource EventSign ificance FRSall sourcesSev erity

= errorsynchroniz es policy between all domaincontrollers in the forestA p p l i c a t i o nUSERENVSev e r i t y = errorUser =Systemapplies group policy and

profiles on domaincontrollers ApplicationS CECLISeverit y = errorSecurity Configuration Engine error messages

Table4Time

synchronizati on service monitored events

Event logSource EventSign ificance SystemW32T

IMESeverity = errorSeverity =warningproblem maintaining uniform time throughoutthe Microsoft Windows Active Directory forest

Table5Kerber os monitored events

Event LogSource EventSign ificance S y s t e m K D C S e v e r i t y

= errorcritical Kerberos Distribution Center serviceerror messages Product components28 BMC PATROL

for Microsoft Windows Servers Getting Started

PATROL KM for Microsoft

Windows Active Directory RemoteM onitoring

The PATROL Knowledge Module (KM) for Microsoft Windows Active DirectoryRemot e Monitoring product provides remote

enterprise monitoring of ActiveDirectory objects. The Active Directory is the core feature of distributed systems

inMicrosoft Windows Servers.The primary focus of PATROL KM for Microsoft Windows AD Remote Monitoring isto

monitor remote sites, domain controllers in those sites, and FSMO roles frommember servers of a domain in the network.For a

brief description of product features, see the sections that follow. For moredetailed information about how to use the product

and complete descriptions of theapplication classes and parameters, see the product online Help.

FSMO

monitorin g
PATROL KM for Microsoft Windows AD Remote Monitoring monitors both

theforest-wide and domainwide Flexible Single Master Operation (FSMO) roles.Active Directory supports multi-

master replication of the directory data between alldomain controllers in the domain. This model takes domain

configuration changesmade at any domain controller in the domain and automatically propagates thosechanges to each of the

domain controllers in the domain.Howeve r some changes do not lend themselves to a multi-master environment.

Onedomain controller, the operations master, accepts requests for such changes. Theoperations master roles can be moved

between domain controllers within the domainand are referred to as Flexible Single Master Operation (FSMO) roles.

In any ActiveDirectory forest, there are five FSMO roles that are assigned to one or more domaincontrolle r. Some FSMO roles must

appear in every forest, while other roles mustappear in every domain within the forest.The following operations

master roles must appear in every forest:

s

schema master
s

domain naming master Table6Netlog on monitored

events
Event logSource EventSign ificance SystemNETL OGONSeverit y = error 5705,5723critical

NETLOGON service errors Product componentsCha pter 1Product components and capabilities29

The following

operations master roles must appear in every domain:

s

relative ID master
s

infrastructure master

primary domain controller (PDC) emulator

LDAP monitorin g
Lightweight

Directory Access Protocol (LDAP) is monitored locally at the managednode. LDAP response time is measured as the

amount of time required to establish anLDAP connection to a domain controller. Longer connect times may

indicate aheavily loaded domain controller. To eliminate network latency, response time forperforming an LDAP bind operation is

measured on the domain controller beingtested.

DNS name registratio n

This product monitors the Domain Name System (DNS) for the following records:
s

A DNS address

record (A record) that matches the IP address of the domaincontrolle r and is registered with the DNS server.
s

A DNS LDAP service location (SRV) record that matches the host name of thedomain controller and is registered with the DNS

server.To obtain information about this record, the KM sends the following query to thedefault DNS server: _ldap._tcp.dc._

msdcs. fullyQualifiedDom ainName.

s

A global catalog LDAP SRV record that matches the host name of the

globalcatalog for the domain controller and is registered with the domain controller.To obtain information about this

record, the KM sends the following query to thedefault DNS server: _ldap._tcp.dc._ msdcs. fullyQualifiedFores tRootDomainName.

Sites and domain controller

This product monitors sites and domain controllers from

a member server machine of the domain in which it resides. It monitors all the sites of the domain or any specificsite in the global

catalog for the site. It also monitors values of site domain controllers.The domain controller monitoring checks the

connectivity and the response time tothe server using LDAP bind.
NOTE

Domain controllers and the client must be

able to locate and establish an LDAP connectionwith the FSMO role holders. Product components30 BMC PATROL

for Microsoft Windows Servers Getting Started

PATROL KM for Microsoft

Windows Domain Services

The PATROL KM for Microsoft Windows

Domain Services monitors the availabilityof the following Microsoft Windows domain controller resources:

domain controllers
s

member serversPATROL KM for Microsoft Windows Domain Services

monitors:
s

Distributed File System (DFS)

s

Dynamic Host Configuration Protocol (DHCP) service availability and

lease usage
s

Domain Name Service (DNS)

s

remote server connectivity

s

replicated directories
s

shared directories
s

trust relationships
s

Windows Internet Naming Service (WINS)For

instructions on how to monitor these features, see the PATROL KM for MicrosoftWindo ws Domain Services online Help system.

PATROL KM for Microsoft Cluster Server

The PATROL KM for Microsoft Cluster Server component monitors, analyzes, andmanages activities of a

Microsoft server cluster. The PATROL KM for MicrosoftCluster Server allows you to obtain the current status of all essential

cluster objectsand perform cluster operations using a cluster-level agent that is installed on a serverthat is outside of the

cluster or on a node that is inside of the cluster. Using thePATROL KM for Microsoft Cluster Server, you can monitor the following

clusterfeatures:
s

all clusters in a domain (only available when the agent is outside of the cluster)
s

individual

clusters
s

cluster communication networks

s

cluster network interfaces

s

cluster nodes
s

cluster objects and resources

s

cluster groups
s

workload data
s

group resources
s

quorum device Product

componentsCha pter 1Product components and capabilities31

For more information about specific functionality

that supports these features see thePATROL KM for Microsoft Cluster Server online Help.

PATROL

Cluster Configur ation Wizard

The PATROL Cluster

Configuration Wizard provides an easy-to-use interface withwhich you can configure the PATROL Agent for failover in a

Microsoft Cluster Serverenvironm ent. While guiding you through the process, the wizard collects therequired

configuration data and updates the system environment to integrate thePATROL Agent into the cluster.Configuri ng the PATROL

Agent for failover support allows you to record historydata for a clustered application in the same history database. This

feature preventsyou from having to reconcile the two different history files that are normally createdwhen an application is

failed-over from one node to another. For more information,see How to use the PCC Wizard on page178.

PATROL KM for Microsoft Message Queue

(MSMQ)
The PATROL KM for Microsoft Message Queue monitors message activity andstatus, which

includes monitoring of
s

MSMQ service
s

MSMQ queues
s

MSMQ messages
s

MSMQ

roundtrip message timeFor instructions on how to monitor these features, see the PATROL KM for MicrosoftMessa

ge Queue KM online Help system.

PATROL KM for Microsoft

COM+
The PATROL KM for Microsoft COM+ provides functionality to monitor MicrosoftCOM+

(COM+) on a Windows Server.The PATROL KM for Microsoft COM+ product monitors and manages the followingfunctio

ns for Windows servers:

s

monitors the COM+ run-time environment

s

monitors the status of COM+ applications

Product components32 BMC PATROL for Microsoft Windows Servers Getting Started
s

manages the MS

DTC service by providing the ability to start or stop the service

s

monitors Windows COM+ log events

s

monitors

Windows log events related to the Microsoft Distributed TransactionCoor dinator (MS DTC) service and monitors the MSDTC service

statusFor instructions on how to use these features, see the PATROL KM for MicrosoftCOM+ KM online Help system.

PATROL KM for Log Manage ment

The PATROL KM for Log Management monitors text, script, named pipe, and binaryfiles in your environment.

The KM provides the following monitoring features:

s

automatically monitors key log files

s

monitors files that do not currently exist on the system

s

monitors log files with dynamic names using wild card

characters
s

monitors the size of log files

s

monitors the growth rate of log files

s

monitors the

content of log files

s

monitors the state of log files

s

monitors the age of the log files

s

monitors log

files using numeric comparisonsThe PATROL KM for Log Management also provides the following managementfeat

ures:
s

triggers alerts when a log file exceeds a specified size

s

triggers alerts when a text string or regular

expression is discovered within a logfile

s

creates automated recovery actions when a log file exceeds an

acceptable size orgrowth rate

s

configures log searches to ignore subsequent alerts for a specified

number of polling cycles if the searchfinds a matching string or regular expression in a log file override an ignored alert if

the search finds a matching string or regularexpressio n more than n times before the ignore setting is completed specify the

number of log scan cycles after which a WARN or ALARM state isautomatically changed to OK Product componentsCha pter 1Product

components and capabilities33

s

creates robust searches by using NOT and AND statements with the text

strings orregular expressions in the log search

s

alerts for log file age

s

sets multiple schedules for multiple polling

cycles per log file

s

disables/enables default log monitoringYou can set up the following predefined

recovery actions to execute when monitoredlog files exceed a specified size or growth rate.
s

clear and back up log files

s

delete files
s

run in attended and unattended modesTo get started with the PATROL KM for Log Management,

see Configuring thePATROL KM for Log Management on page147. For detailed instructions, see the BMC PATROL KM

for Log Management User Guide

and the PATROL KM for LogManagement online Help system.

PATROL KM for Event Manage ment

PATROL for Windows Servers provides event notification and centralized alertmanagement features. With the PATROL

KM for Event Management, you canperform the following tasks:

s

configure notification (email, paging,

trouble-ticket, or custom) for PATROL alerts

s

configure PATROL to send notifications to an enterprise

console
s

configure recovery actions for alarm, warning, and information events

s

reword

notification messages and customize message content

s

specify the maximum number of events displayed

in the console
s

use wildcards to represent instance names when setting up parameters

s

configure PATROL to

monitor the availability of hosts

s

manage PATROL parameter thresholds and polling

schedules
s

configure blackout periods for notification and for availability monitoring

s

integrate with

the AlarmPoint notification software using provided scripts

s

integrate with any command line email client, paging solution,

compiledexecuta ble, or script. Sample scripts are provided.To get started with the PATROL KM for Event Management, see Configuring

emailnotification on page132. For more detailed instructions and reference information,see the

PATROL KM for Event Management User Guide

. Product components34 BMC PATROL for Microsoft

Windows Servers Getting Started

PATROL Wizard for

Microsoft Performa nce Monitor and WMI

The PATROL Wizard for Microsoft Performance Monitor and WMI is a powerful buteasy-to-use tool that allows

you to create new, userdefined PATROL parametersbased on Microsoft's Performance Monitor counters or

Windows ManagementInst rumentation (WMI) data. You can also set alarm and warning thresholds for eachparameter

you create.This functionality allows you to monitor performance counters and WMI data thatare not typically

monitored by PATROL. For more information, see Configuring PATROL Wizard for Microsoft Performance

Monitor and WMI on page142, or thePATROL Wizard for Microsoft Performance Monitor and WMI online

Help .

PATROL History Loader KM

The PATROL History Loader KM extracts PATROL KM parameter history and loadsit into your relational database

management system (RDBMS). Once PATROL historydata is stored in an RDBMS, you can perform complex

analysis and statisticalplannin g on all monitored activity. For more information, see the PATROL History

Loader Knowledge Module User Guide.

PATROL Adapter for

Microsoft Office
The PATROL Adapter for Microsoft Office component allows you to

connect to aPATROL Agent and gather information without a PATROL Console.With the PATROL Adapter for

Microsoft Office, you can evaluate PATROL data byusing Microsoft Excel. The PATROL Adapter for Microsoft Office

collects data fromPATROL parameters on local or remote hosts and displays the data as a MicrosoftExcel chart or graph.

You also can create HTML output for Web display.For more information, see the PATROL Adapter for Microsoft Office User Guide.

For alist of PATROL Adapter for Microsoft Office reports, see Displaying PATROL databy using the PATROL

Adapter for Microsoft Office on page167.

PATROL Agent
PATROL for

Windows Servers includes the PATROL Agent. The PATROL Agentmonitors a system according to the instructions

provided by loaded PATROL KMs.You can display the information gathered by the PATROL Agent on the PATROLConsol

e. For more information, see the PATROL Agent Reference Manual . ServicesChapte r 1Product components

and capabilities35

Servic es
The PATROL for Microsoft

Windows Servers product uses the following services:

Relate

d docum entatio n

For additional information about PATROL for Windows Servers, see the online Helpfor the component of interest and refer to the

PATROL for Microsoft WindowsServers release notes. For information about the PATROL for Windows Servers

parameters, see the product Help or the PATROL Parameter Reference Manual . Foradditional information about PATROL,

see the following documentation:

s

Help for your PATROL Console

s

PATROL Fundamentals

HelpTo view the complete PATROL documentation library, visit the support page on theBMC Software Web site

athttp://www.b mc.com/s uppor t. Log on and select aproduct to access the related documentation. To log on if you are a first-time

user and have purchased a product, you can request apermanent user name and password by registering at the Customer

Support page. Tolog on if you are a first-time user and have not purchased a product, you can request atemporary user

name and password from your BMC Software sales representative.

Where

to go from here
The following table suggests

topics that you should read next: Table7PATRO L for Microsoft Windows Servers

Services
Service Component or KMInstalled and Runs by Default? P A T R O L A g e n t P A T

R O L A g e n t y e s T he PATROL MCSMonitor ServicePATROL KM for MicrosoftCluster Serverno If you

want informatio n about...Se e... how to install the PATROL for Windows ServersproductCh

apter2, Installing and migrating PATROL forWindows Servers how to load and configure the components using aPATROL consoleChapter3,

Loading and configuring PATROL forMicrosoft Windows Servers Where to go from here36 BMC PATROL for Microsoft

Windows Servers Getting Started troubleshooting configuration problemsChapter6 , Troubleshooting PATROL for

MicrosoftWindow s Servers PATROL for Windows Servers agent configurationvaria bles and predefined rulesetsAppendix B, Agent

configuration variables andrulesets KMs included in each PATROL for WindowsServers .KML fileAppendixC, PATROL for Windows .kml

files If you want informatio n about...Se e... Chapter 2Installing and

migrating PATROL for Windows Servers37 Chapter

2
2

Instal ling and

migr ating PAT

ROL forWi ndow

s Serv ers

This chapter provides the information that you need to install PATROL for WindowsServers . For additional information

about the PATROL installation process, see the PATROL Installation Reference Manual . The following topics are

discussed in thischapter:Insta llation overview. .............. .............. .............. .......... .38Verifying installation

requirements . . . .............. .............. ......... .39System requirements. . . . .............. .............. ..............

.... .39Additional componentspecific requirements. . . . ............. ............ .40Accounts. . . . . ...............

............... ............... .......... .43Preparing for installation . . . . . .............. .............. .............. . . .49Turning off

pop-up blocking software before installing. . . . . . ............. . .49Unsupported platform option in the installation utility user

interface. . . . . . . . .50Extraneous target platform options available in the installation utility userinterface . . . . ...............

............... ............... ......... .50Checking for product patches or fixes before installing . . . . . . ............. . .50Determining

how to install products . . . . . . ............. ............. .... .51Determining the version of the installation utility. . . . . . . . .

............. ... .51Determining where to install the PATROL Agent. . . . . . . . . ............. . . . .51Installing the PATROL

Agent over an existing installation . . . . ............. .51Extracting installation files after download. . ............. .............

... .52Determining where to install KMs . . . . . . . . . . .............. .............. .52PATROL Security levels . . ...............

............... ............... . . . .53Checking security levels. . . .............. .............. .............. . . .54Assessing and

implementing a different security level. . . . . . . . . . ........... .54Default and custom installation types ............. .............

............ .54First-time installation. . . . . . ............... ............... ............... . . .55Installing for the first time . ..............

.............. .............. . . .55First-time installation using Distribution Server. . . . . . . . ............. ......... .60Distribution

Server features. . .............. .............. .............. .60Importing a CD or customized installation package into

Distribution Server. . .61Installing with the Distribution Server (overview) . . . . . ............. ...... .62Upgrading

from an earlier version . . . . . . . . .............. .............. . . . . . .63 Installation overview38 BMC PATROL for Microsoft

Windows Servers Getting Started

Automatic migration of console and agent customizations . .............

... .63Determining whether you can migrate KM customizations. . ............. . . .64Conditions for upgrading. . . ..............

.............. .............. . .64Determining the location of PATROL. . . . . . . .............. .............. . .65PATROL for Windows Servers

upgrade scenarios. . . . . . ............. ......... .66Upgrading without saving KM customizations . . .............

............ .68Upgrading and preserving KM customizations . . ............. ............ .68Preparing to upgrade. . . . . . . .

.............. .............. .............. .69Migrating customizations with the PATROL Configuration Manager. . . . . .

. . .70Creating an installation package of the migrated and merged KM. . . . ....... .70Moving files from the PATROL_CACH

E directories. . . . ............. ...... .71Migrating customizations manually. . . . . . ............. ............. .....

.72Installing PATROL KM for Microsoft Cluster Server. . ............. ........... .73External cluster-level agent

architecture . . . . ............. ............. . . . .74Internal cluster-level agent architecture. . . . ............. .............

. . . . .75How to Install the PATROL KM for Microsoft Cluster Server. . ............. .76Considerations for using online Help . . . . . . . . . .

.............. .............. . .77Browser version required for viewing PATROL Console for UNIX Help . . . . . .78Additional

considerations for using online Help for UNIX . ............. ... .78Uninstalling PATROL for Windows Servers ..............

.............. ..... .80Determining the version of the installation utility . . . . . . . . ............. .... .80Uninstalling

PATROL for Windows Servers on Windows. . . . . . ............ .81Where to go from here. . . . . . .............. ..............

.............. . . . . .85

Install ation overvi

ew
This chapter contains instructions for installing PATROL for Windows

Servers. Foradditional installation instructions, see the following documents: C o m p o n e n t S e e

PATROL KM for Event Management

PATROL KM for Event Management User Guide

PATROL KM for Log Management

PATROL KM for Log Management User

Guide

PATROL History Loader KM

PATROL History Loader Knowledge Module User Guide

PATROL Perform Agent for MicrosoftWindow s Servers

Getting Started with PATROL for Microsoft WindowsServers Performance

Verifying installation requirementsCh apter 2Installing and

migrating PATROL for Windows Servers39

Verifyi ng

install ation require ments

Before installing PATROL for Windows Servers, verify that your environment meetsthe following types of requirements:

system requirements
s

requirements for specific PATROL for Microsoft Windows Servers

components
s

account requirements

System requirem ents

Verify that the target computer meets the installation requirements listed inTable8on page39 . These requirements

apply to all PATROL for Windows Serverscompone nts. Table8System requirements for installing

and using PATROL for Windows Servers (Part1of2)

R c u n e e i t s o u r R e q r e m e s C o

m m e n t s operatingsystemsF or an updated list of supported operatingsystems, see the

PATROL for Microsoft WindowsServers

Release Notes

.security levelsAll security levels are supported. For more information about PATROL security,seePAT ROL Security

levels on page53.The PATROL Security Level is set duringthe installation of the PATROLinfrastru cture components. If yourproduct contains the

PATROL Agent,you are able to select the security level.Make sure that the level that you select iscompatible with the rest of your enterprises

PATROL installation.PATR OLproductsFor an updated list of supported operatingsystems, see the

PATROL for Microsoft WindowsServers

Release Notes

.l i c e n s e Y o u must have a valid demonstration l i c e n s e (typically good for 30 days) or a permanentlicense to run your

PATROL products.If you do not have a permanent license,contact your BMC Software salesrepresentativ e or the BMC SoftwareContract

Administration department.ports( UDP/TCP)If you are installing an agent or console withPATROL for Windows Servers, you mustspecify the port number to connect to all

theagent computers.The default port number for agents is3181.The default port number for theRTServer is 2059. Verifying

installation requirements40 BMC PATROL for Microsoft Windows Servers Getting Started

Addition

al compone ntspecific requirem

ents
The following requirements are specific to the PATROL for Microsoft WindowsServers components

shown.

PATROL KM for Microsoft Windows Domain

Services
To monitor network protocols and to use the following domain monitoringpara

meters and management features, you must have the SNMP service installed:
s

NT_DHCP parameters
s

WpReplicationF ailures parameter

s

executing the WINS Database Scavenging menu command

(UNIX

only)browser tosupport onlineHelp forPATROLConso le forUNIXUse Netscape Navigator version 3.01 4.78 to useonline Help with PATROL for

UNIX. Browser version required for viewingPATROL Console for UNIX Help onp a g e 7 8 b r o w s e rsThis product uses an installation

utility t h a t requires a browser. For a list of supportedbrowser s, see the

PATROL Installation Reference Manual

.disk spaceneeded to install151 MB

for an agent(without components and KMs)151 MB for a console(without components and KMs)242 MB for an agent(with all solution components and

KMs)116 MB for a console(with all solution components and KMs)Monitor(for Console)256-color display800 x 600 resolutionF i l e systemFAT or N T F S Network

TCP/IP network protocol

Table8System requirements for installing and using PATROL for Windows Servers

(Part2of2)
R e s o u r c e R e q u i r e m e n t s C o m m e n t s Verifying installation

requirementsCh apter 2Installing and migrating PATROL for Windows Servers41

As a default, the SNMP service is

configured to accept SNMP packets from any host.If the service is configured to accept packets from hosts, then the local host IP

addressor hostname must be added to the list of hosts. It is not sufficient to add localhost orthe loopback address 127.0.0.1.At a

minimum, the SNMP community string must have READ permissions. Toinitiate the WINS Database Scavenging

menu command, the community string musthave WRITE permissions as well.On Windows 2000 servers, the community

string must be an ASCII character string.Microsoft Windows 2000 does not support non-ASCII characters in communitystring

s.For the NT_DHCP application class to work, the default PATROL Agent accountmust have full access to

%PATROL_HOM E%

and all subdirectories. On Windows2003 and later, the default PATROL Agent account

must also be a member of theDHCP Users group.

PATROL KM for Microsoft

Windows OS
This section contains additional requirements for using the PATROL KM

forMicrosoft Windows OS.

Process monitoring
To monitor processes, the PATROL Agent must have

access to the following hive andall subkeys:HKLM\SO FTWARE\Micr osoft\Windows NT\perflib

Event log

monitoring
To discover event logs, the PATROL Agent must have access to the following hiveand all subkeys:HKLM\Cu

rrentControlSet \Services\Event log\ PATROL Agent 3.6 or later has access. No additional configuration is needed.

PATROL KM for Microsoft Windows Active Directory

PATROL KM for Microsoft Windows Active Directory now requires the PATROLKM for Microsoft Windows Operating

System 3.9.20 or later for full support. If youare running a release earlier than 3.9.20 , the KM fails prediscovery

and writes amessage to the mwd.log file, as well as to the system output window (SOW) .

If you arerunning 3.9.

, the KM is discovered, but the Event Log parameters are not available. Verifying installation requirements42

BMC PATROL for Microsoft Windows Servers Getting Started

PATROL KM for Windows Active Directory requires that the

Event Log componentof PATROL KM for Microsoft Windows Servers is active. By default the Event Logcomponent

is active. For more information, see Configuring Windows eventsmonitorin g on page103.PATR OL for Windows

Servers monitors Microsoft Windows Active Directory onlywhen Microsoft Windows Active Directory is running on

domain controllers.PAT ROL KM for Microsoft Windows Active Directory supports the Read OnlyDomain

Controller support on Microsoft Windows 2008.

PATROL default account required

permissions
Monitoring replication within the configuration naming context requires that thePATROL Agent

defaultAccount have sufficient Active Directory permissions tocreate a container object and child container objects in the

configuration namingcontext of the forest in which the domain controller resides. The account must havefull control

of the created objects.The PATROL Agent defaultAccount must be granted permission to Create ContainerObject s in the

Configuration NC and to give Full Control to the created containerobject and its children.Monito ring replication within the

domain naming context requires that the PATROLAgent defaultAccount have sufficient Active Directory permissions to create acontainer

object and child container objects in the domain naming context of thedomain in which the domain controller resides. The

account must have full control of the created objects.The PATROL Agent defaultAccount must be granted permission to Create

ContainerObject s in each Domain NC and to give Full Control to the created container objectand its children.

PATROL KM for Microsoft COM+

PATROL KM for Microsoft COM+ now

requires the PATROL KM for MicrosoftWindo ws Operating System 3.9.10 or later for full support. If you are running

arelease prior to 3.9.10 the KM is discovered, but the Event Log parameters are notavailable.

PATROL

KM for Microsoft Cluster Server

The PATROL KM for Microsoft

Cluster Server requires that

NT_BASE.kml

or
NT_LOAD.kml

is loaded. These files are included with PATROL KM

for MicrosoftWindo ws OS. Verifying installation requirementsCh apter 2Installing and migrating

PATROL for Windows Servers43

BMC Software recommends that you preload

NT_BASE.kml

or
NT_LOAD.kml

on thecluster agent machine. For more information about preloading, see Preloading KMson the PATROL

Agent on page94.

PATROL KM for Microsoft Windows

Active Directory Remote Monitorin g

The local node

(or member server) provides a client view of the Active Directoryobjects . The data provided for each managed node is collected

within the context of the domain of which the managed node is a member.To display information about Active

Directory objects, the managed node must meetthe following requirements:

s

PATROL Agent 3.6.00 or later

must be installed.
s

Default account for the PATROL Agent must be a domain user account.

PATROL

Adapter for Microsoft Office

To use PATROL Adapter for Microsoft

Office, you must load a supported version of Microsoft Excel. To see which versions of Microsoft Excel are supported, see theRelease

Notes for the version of PATROL Adapter for Microsoft Office that you areinstalling or have installed.

Account s
This section describes how to set up a PATROL installation

account for Windows.

PATROL Agent default account

PATROL

requires a dedicated user account, known as the PATROL Agent defaultaccount, in the Windows environment. The PATROL

Agent default account mustexist in the Windows environment before you install PATROL. The PATROL Agentdefault

account can be either a local or a domain account:

s

Stand-alone workgroup servers must use a local user

account as a PATROL Agentdefault account.

s

Servers that are trusted members of a domain can use either a

local or a domainaccount.
s

Domain controllers must use a PATROL Agent default account that is also adomain

account. Verifying installation requirements44 BMC PATROL for Microsoft Windows Servers Getting Started

KM functions performed
The PATROL Agent uses the PATROL Agent default account to perform thefollowing

KM functions:
s

collect information from performance counters

s

collect information

from the Windows event log

s

self-tune for peak performance and non-intrusive use of the

processor
s

access systemlevel information

s

make debuglevel output available from the PATROL

KM applications
s

access the command interpreter for operatingsystem-level commands

s

create and

remove processes in the process table for collecting performance data

Advanced user rights

To enable the PATROL Agent to perform these advanced functions, the PATROLAgent default account might need the advanced user

rights shown inTable9. Theserights are not used during installation, but the PATROL Agent requires these rightsto operate and

perform certain functions after installation. The installation utilityautomatica lly grants these rights to the PATROL Agent default account.

NOTE

If you are not using the PATROL Agent default account as a Console connection account, youwill need to have the Log on locally

account rights for the connection account.PATROL Agent first tries to log on locally; if this fails, it tries to connect to the console byusing the network login rights.

Table9Advan ced user rights (Part1of2)

Advanced User Right Agent Dependency Act as part of operating

systemenables PATROL to perform as a secure, t r u s t e d part of the operating systemD e b u g programsen ables PATROL to

debug lowlevel objectsIncr ease quotasenabl es PATROL to increase object quotasLog on as a

serviceallo ws the PATROL Agent to be started as a service so that it will start on system bootLog on locally (Windows

2000)Allow log on locally (Windows 2003)allows PATROL to log on at the computerM a n a g e auditing and security logallows PATROL to

monitor the Security e v e n t log Verifying installation requirementsCh apter 2Installing and migrating

PATROL for Windows Servers45

Administrativ e rights
BMC Software recommends that you make the PATROL Agent

default account amember of the local Administrators group of the computer where the agent willreside. On a domain

controller, BMC Software recommends that you make theaccount a member of the domain Administrators group.However,

you can choose to remove the PATROL Agent default account from thelocal or domain Administrators group. You could also

remove the advanced userrights described inTable9 on page44. However, if you do so, the PATROL

Agentcannot perform all of its tasks.Table10 on page45shows the PATROL for MicrosoftWindo ws Servers tasks

that the Agent cannot perform when the followingrestrict ions are placed on the PATROL Agent default account:
s

The account is in a domain user group or local user group, but is not in the domainor local administrators group.
s

The account does not have all of the advanced user rights noted inTable9 onp a g e 4 4 .
Profile system performanceen

ables PATROL to use the Windows p r o f i l i n g capabil itiesR e p l a c e a process level tokenenables PATROL to modify a security

a c c e s s token for a process

Table10Remo ving rights and admin group membership from the PATROL

Agent (Part1of3)
K f W a n a n M e o r d n o E c t f r k o u d t e

PATROL KM forMicrosoft Cluster ServerThe cluster KM does not function. Noauthentication to the cluster can beperformed.To be fully functional, the

agent outsideof the cluster can be in the admin groupand contain all of its rights, while theagents within the cluster are removedfrom the administrators group and donot

have the seven advanced userrights. The monitoring user accountdoes not have the Logon As Batch Job user right.

Table9Advan ced user rights (Part2of2)

Advanced User Right Agent Dependency Verifying installation

requirements46 BMC PATROL for Microsoft Windows Servers Getting Started PATROL KM forWindows OperatingSystemR

estart Service recovery action does notexecute. Message in system outputwindow indicates access denied andinability to restart service.The

PATROL Agent default accountmust be in the local or domain

Admins

group. Granting a specific user right

isnot

a valid

workaround.If the PATROL Agent default accountlacks the

Debug Programs

right, cannotmonitor the status of processes.Add the

Debug Programs

right to thePATROL Agent default account.Members hip in the

Administrators

group not needed.The Terminate Process and

RestartProcess recovery actions do not work.Add the

Debug Programs

right to thePATROL Agent default account.Backup Event Log and

Clear Event Logrecovery action does not work.Add the user right
Backup files and directories

to the PATROL Agentdefault account

For the security eventlog, you must also add the user right
Manage auditing and security log.

Logical disk quotas and mount pointsdo not

work.The PATROL Agent default accountmust be in the local or domain

Admins

group.The Clean Temporary Directoriesrecover

y action does not execute.Assign read/write permissions on thetemp directory to the PATROL AgentDefault account.Unable to monitor the security eventlog.

The NT_EVENTLOG applicationdisplay s a message in the_DiscoveryStat us parameter.Add the user right

Manage auditing and security log

to the PATROL

Agentdefault account
.

Blue Screen KM unable to detect a bluescreen condition.The PATROL Agent default accountmust be in

the local or domain

Admins

group. Granting a specific user right

isnot

a valid workaround.PAT ROL KM forMicrosoft

WindowsDomain ServicesShares are not monitored. Parametersare not discovered.Add the PATROL Agent defaultaccount to the
Account Operators

,
Print Operators,

or
Server Operators

built-ingroup.The Increase connections allowed oShare recovery action associated withthe

ShConnPercent parameter does notwork.Add the PATROL Agent defaultaccount to the

Account Operators

,
Print Operators,

or

Server Operators

builtingroup.DFSRoot Replica does not work whenchecking alternate domain controller.Paramet ers are unavailable and

inalarm.Grant the advanced user right l

og onlocally

to the PATROL Agent defaultaccount.On Windows 2003, the NT_DHCPapplica

tion class does not work.Add the PATROL Agent defaultaccount to the
DHCP Users

group.

Table10Remo ving rights

and admin group membership from the PATROL Agent (Part2of3)

K M E f

f e c t W o r k a r o u n d a n d n o t e s Verifying installation requirementsCh

apter 2Installing and migrating PATROL for Windows Servers47

Creating a separate account

Although you can use an existing Windows user account, BMC Softwarerecom mends that you create a separate Windows user

account for PATROL.

PATROL KM forMicrosoft WindowsActive DirectoryAD disk space used does not work. Grant the PATROL

Agent defaultaccount the following permission onthe DSA Working Directory and itssubdirectories:
List Folder Contents/Read Data

.The KM reads the

registry to obtain theDSA Working Directory. It needsaccess to the following registry keysand subkeys:HKEY_L OCAL_MACHINE \SYSTEM\ CurrentControlSe

t\Services\NTDS Configuration NC replication checkingdoes not work.Grant the PATROL Agent defaultaccount sufficient Active Directorypermissi ons to create a

container objectand child container objects in theconfiguration naming context of theforest in which the domain controllerresides. Grant the

PATROL AgentdefaultAcco unt permission to CreateContainer Objects in the ConfigurationNC and to give Full Control to thecreated container object

and itschildren.Domai n NC replication checking doesnot work.Grant the PATROL Agent defaultaccount sufficient Active Directorypermissi ons to create a

container objectand child container objects in thedomain naming context of the domainin which the domain controller resides.Grant the PATROL

AgentdefaultAcco unt permission to CreateContainer Objects in each Domain NCand to give Full Control to the createdcontainer object and its children.

Table10Remo ving rights and admin group membership from the PATROL Agent

(Part3of3)
K M E f f e c t W o r k a r o u n d a n d n o t e s Verifying

installation requirements48 BMC PATROL for Microsoft Windows Servers Getting Started

PATROL

KM for Microsoft Cluster Server account

The PATROL

KM for Microsoft Cluster Server can be configured to use an externalclusterlevel agent or an internal cluster-

level agent (CLA). The account the KM usesto connect to and manage a cluster depends upon which configuration you

use.Regardless of which configuration you use, however, the configuration must have thefollowing characteristics:

cluster account must be a domain account

s

cluster account must have access permission to the cluster

all local agents in the cluster must use the same port numberAn external CLA configuration requires a user-

defined cluster account separate fromthe PATROL default account. This account must have cluster administrativepri vileges. The

PATROL MCS Monitor Service (

McsService.exe

) also runs under thisaccount.An internal CLA configuration

can use either a separate userdefined cluster account(a domain account with cluster administrative privileges) or, when

certainrequireme nts are met, it can use the PATROL default account.When installed, if the PATROL KM for Microsoft Cluster Server

does not discover aseparate cluster account, it checks the PATROL agent default account for thefollowing required

characteristics:
s

it must be a domain account

s

it must have permission to access the clusterIf these requirements are

in place, the Cluster KM uses the PATROL agent defaultaccount to access the cluster and to communicate with the agents

running on all othernodes in the cluster, and the PATROL MCS Service runs under this account.This account information is

not replicated to other nodes so, if you want the ClusterKM to use the PATROL agent default account to monitor the cluster,

theserequiremen ts must exist for every PATROL agent default account on every node inthe cluster.To discover the PATROL KM

for Microsoft Cluster Server you require the

Logon as abatch job

privilege for cluster account and PATROL Default

Account.

WARNING

Do not use a built-in Windows domain or local Administrator account as the PATROL defaultaccount.

Such account usage causes files created by PATROL to be owned by theAdministrator, which could result in security or file access problems. Preparing for

installationChap ter 2Installing and migrating PATROL for Windows Servers49

Console connectio

n accounts
BMC Software recommends that you create a separate account, in addition to

thePATROL default account, for PATROL console operators who do not needadministrati ve privileges. Operators can

use this account to connect the console to theagent. If you want to configure KMs from the console, however, the

consoleconnecti on account may need administrative rights. For more information, see Requiremen ts for configuring

from the PATROL Console on page97.

Prepar ing for

install ation
BMC Software recommends that you first install PATROL for

Windows Servers on alimited number of development or test machines, then configure and test PATROLfor Windows

Servers before installing it onto production machines.Before you install, you must
s

ensure that popup blocking

software is turned off before installation (seep a g e 4 9 )

s

determine if you are using an unsupported platform option

in the installationutilit y user interface (seep a g e 5 0 )

s

determine the extraneous target platform options available

in the installationutilit y user interface (seep a g e 5 0 )

s

check for product patches or fixes before installing

(seep a g e 5 0 )
s

verify if you are installing PATROL Agent on top of an existing installation (seep a g e 5 1 )
s

determine the order in which you must extract the installation files after download(seep a ge52)
s

determine how

to install products (seep a g e 5 1 )

s

ensure you are using the appropriate version of the installation

utility (seep a g e 5 1 )
s

understand where to install the PATROL Agent and KMs (seep a g e 5 1 )

s

understand

PATROL security options (p a g e 5 3 )

s

choose between Default and Custom installation options

(seep a g e 5 4 )

Turning off popup blocking

software before installing

Before installing the PATROL for Microsoft Windows

Servers solution or any of itscomponents, you must turn off pop-up blocking software. Popup blocking softwareinterfer

es with the functioning of the installation utility. Preparing for installation50 BMC PATROL for Microsoft Windows

Servers Getting Started

Unsuppo rted platform option in

the installati on utility userinter face

If you use the installation utility to build an installable image, the

Windows NT 4.0(Intel)

platform option is also displayed

in the Select Platforms dialog box. Thisplatform is not supported by the PATROL for Microsoft Windows Servers solution.

Extraneo us target platform options available

in theinstall ation utility user

interface
If you use the installation utility to build an installable image, the followingextrane ous target

platform options are displayed in the Select Platforms dialog box:

s

Windows NT 4.0 (Intel)

s

Above Windows

2003 (Intel)
s

Above Windows 2003 (Itanium)

s

Above Windows 2003 (Opteron/EM64T)

None of the preceding

platforms are supported by the PATROL for MicrosoftWindo ws Servers solution. Do not select these target platforms when building

aninstallable image.

Checkin g for product patches

or fixes before installing

Product fixes or patches are often available through the

BMC Software Web site.Patches correct problems that are found after a product is released. BMC Softwarerecomm ends that you check the

product page for PATROL for Windows Servers onthe BMC Software Customer Support Web page to determine

whether a patch isavailable before you begin installing a product.

WARNING

Do not select the Windows NT 4.0 (Intel)

platform when building an installable image. Preparing for installationChap ter 2Installing and migrating PATROL for Windows

Servers51

Determin ing how to install products

You can install

products on the computer on which you are running the installationutilit y (local installation), create an installable image

of products, use the serveronlyoption , or use the Distribution Server. An installable image is a fully configuredprodu

ct image that you can use to install products to multiple computers. With aninstallable image, you can create one product image

with one pass through theinstallation utility and then use that image to install to remote computers in yourenvironmen

t.For more information about creating, distributing, and installing installable images,and about using the ctltool, see the

PATROL Installation Reference Manual

Determin ing the version

of the installati on utility

The version of the installation utility included on the CD or

Electronic ProductDownloa d (EPD) image you use to install this product might differ from a versionincluded on another

product CD or from a version that you downloaded from theBMC Software Electronic Product Download (EPD)

website. You should use theversion of the installation utility that comes with the product that you are installing.To determine the

version of an installation utility, perform the following steps:

1
Open a command prompt.

2
Navigate to the directory where the installation utility is located.

3
Enter
Setup.exe -v

(Windows) or
setup sh -v

(UNIX).

Determin ing where to

install the PATROL Agent

Install the PATROL Agent

on each computer that you want to monitor. Wheninstalling the PATROL Agent, select Managed System as the system

role during theinstallation.

Installing the PATROL Agent

over an existing installati on

If you are installing the

PATROL Agent over an existing installation, any manualmodificat ions that you made to the
agent.reg

file are not applied to the

newinstallation. You must manually reapply the modifications after the new installation. Preparing for installation52

BMC PATROL for Microsoft Windows Servers Getting Started

Extractin g

installati on files after downloa d

This section is relevant only if you downloaded the PATROL for Microsoft WindowsServers solution from the BMC Electronic

Product Download (EPD) website,

http://www.bmc. com/ega/

.When extracting multiple components that you downloaded

from the BMC EPDwebsite, you must extract them in the order shown:1.installa tion utility (always extract first)2.PATROL

KM for Event Management3.P ATROL History Loader KM4.PATROL KM for Log Management5.P ATROL Perform Agent for

Microsoft Windows Servers6.PATR OL Agent for Microsoft Windows Servers7.PATR OL for Microsoft

Windows Servers (always extract last)

Determin ing where to

install KMs
You install the KMs to multiple target computers in the PATROL environment.

Eachtarget computer requires different KM related files and information, depending onthe computers system role in

the PATROL architecture. When you run theinstallation utility on a target computer, you must select the appropriate system rolefor

that computer. The installation utility then installs the appropriate files to thattarget computer based on the system role

selected.Install KMs that you want to use on

EXAMPLE

If you downloaded the following components, you must extract them

in this order:1.installatio n utility (extract first)2.PATROL KM for Log Management3.PA TROL Agent for Microsoft Windows Servers4.PATRO

L for Microsoft Windows Servers (extract last) PATROL Security levelsChapter 2Installing and migrating PATROL for

Windows Servers53
s

Computers hosting a PATROL AgentEach computer that you want to

monitor should, at a minimum, have the PATROLAgent and the PATROL KM for Microsoft Windows OS. You might want

to installother KMs to monitor specific server types such as Exchange Servers, MicrosoftSQL Servers, Domain Controllers,

Cluster Servers, Terminal Servers, and so on.When installing these KMs on the PATROL Agent computer, select Managed System

as the system role during the installation.

s

Computers hosting a PATROL consoleInstall every

KM that you want to use on each PATROL console computer.When installing these KMs on a PATROL console

computer, select Console Systems as the system role during the installation.
s

Computers hosting a PATROL

Console ServerIf you use the PATROL Console Server, install every KM that you want to use onthe PATROL

Console Server computer. Install the same KM and the same versionof the KM that is running on the PATROL Agents.When

installing these KMs on a PATROL Console Server computer, select CommonServices as the system role during the installation.For

more information about the PATROL consoles and PATROL Console Server orRTserver, see the products

respective online help systems and the followingdocum ents:

s

PATROL Central Operator - Web Edition Getting

Started
s

PATROL Central Operator Microsoft Windows Edition Getting Started

s

PATROL Console Server and

RTserver Getting Started

s

PATROL Configuration Manager User Guide

s

PATROL Console for UNIX User

Guide
s

PATROL Console for Microsoft Windows User Guide Understanding the Basics of PATROL, Volume 1, 2, and 3

PATR OL Securit y

levels
You can secure the data passed between PATROL components and restrictunauthori

zed users from accessing your data by implementing PATROL security.You can select from five security levels when you

install PATROL. Default and custom installation types54 BMC PATROL for Microsoft Windows Servers Getting

Started

Agents, console servers, and consoles must operate at the same security level tocommunicate with each other.

When you install agents, console servers, or consolesthat need to communicate with previously installed versions of

these components,che ck the security level of the previously installed components and be sure to installthe new

ones at the same level.

Checkin g security levels

To check the security level of a previously installed agent, console server, or console,perform the following steps:

1
From the command line switch to the path on the computer that you want to check:
%BMC_ROOT%

\common\securi ty\bin\Windows -x86

2
Run the following command to display the security policy

of the current machine:The security level is displayed in the security level field of the output.

Assessin

g and impleme nting a different security

level
Review the security level definitions in the PATROL Security User Guide beforeinstalling PATROL to

determine the appropriate security level for your components.If you want to implement a new security level after having

previously installedPATRO L security, see the PATROL Security User Guide for instructions.

Defaul t and custo m

install ation types

The installation utility prompts

you to select one of the following installation types:

s

The
Default

installation type uses default

values for all optional configurationinf ormation. It prompts you only for mandatory configuration information.

Thistype is for any or all of the following situations: You are new to the PATROL product that you are installing and you have

anagent or console already installed in the default directories. You are performing a first-time installation (you

are not upgrading), and youare installing into the default product installation directories.
esstool policy -a First-time

installationChap ter 2Installing and migrating PATROL for Windows Servers55

s

With the
Custom

installation type,

you can install individual components of theproduct. It requires that you specify all configuration information. This type is

forany or all of the following situations: You want to install individual components rather than the entire product. You

want to specify the following settings:

s

the port numbers that components use to communicate with each other
s

a security level greater than basic security

s

any other product settings that a user might want to change You

are upgrading PATROL for Windows Servers from a previously installedversion. You are installing into an existing

PATROL environment that is not in thedefault installation directory.With each installation type, you can always deselect

any components that you do notwant to install.

Firsttime

install ation
The installation utility offers two types of installations:

Default and Custom. For adescription of the two types of installations, see Default and custom installationtypes on page54.

Installing for the first time

You can install PATROL for Windows Servers using

either the Default or Custominstallati on type. Regardless of the type of installation you choose, you must repeatthis

installation process for each computer on which you want to install PATROL forWindows Servers.
NOTE

If you are installing PATROL for Windows Servers to an existing PATROL Agent or Consoleenvironme nt that is not in the default

installation directory,
use Custom. Do not use Default

.Default will automatically install the agent or console with PATROL for Windows Servers

andoverwrite your existing installation.

NOTE

By default, the Default installation type configures the PATROL Agent to connect

throughport 3181. If you want to connect the agent from a different port, you must use the Custominstallatio n type. First-time

installation56 BMC PATROL for Microsoft Windows Servers Getting Started

Before you begin

s

You first should install on a limited number of computers in the test environment,tes t the installation thoroughly, and then install in

your production environment.

s

You must have created the PATROL default account.

s

If you want to install PATROL

for Windows Servers on a computer runningWindow s 2000 with Citrix Metaframe, you must have access to a

second computerthat runs a browser that is supported by the installation utility.

Toinstall

using the default installation type1

Close the Service Control Manager window and the

Control Panel window.

2
From the PATROL for Microsoft Windows Servers CD or from an

installationimag e that has been electronically downloaded from an EPD site and extracted,run
setup.exe

.When installing

on a Windows Server in application mode or with CitrixMetaframe installed, perform the following steps to launch the

installation utility:

A
From a command line, change to the directory where the installation utility islocated

and enter the following command to change to installation mode:

change user/install

Enter the following command to start the installation Web server

setup.exe serveronly

A message box

is displayed that shows the URL to use to connect to theinstallation Web server.

C
On another computer with a browser, start

the browser.

D
Connect to the installation Web server from the browser to start the installationutilit y by using the

URL that is displayed in the message box on the computeron which you are installing the product.

3
In the Welcome

to the Installation Utility window, click

Next

to begin yourinstallation.

4
Review the

license agreement, select

Accept

, and click
Next

to continue.

5
In the Select

Installation Option window, select

I want to install products on thiscomputer now

and click
Next

to continue. First-time installationChap ter 2Installing and migrating PATROL for Windows Servers57

In the Select Type of Installation window, select

Default

and click
Next

to continue.

In the Specify Installation Directory window, accept the default directory and click
Next

to continue.

8
In the Select System Roles window, select any or all of the following roles toindicate the components that you want to

install and click

Next

:
s

If you are installing to a computer that hosts or will host only a

PATROLConsol e for Windows, select

Console Systems

.
s

If you are installing to a computer that

hosts or will host a PATROL Agent,select

Managed Systems

.
s

If you are installing to a

computer that hosts or will host the PATROL CentralOperator Web Edition, or the PATROL Console Server select

Common Services

9
From the Select Products and Components to Install window, select

componentsthat you want to install or accept the defaults and click

Next

10
In the PATROL

Default Account Properties window, enter the user name andpassword that you want to use for your PATROL default account

and click
Next

.This window is displayed only when you are installing a product that requires aPATROL

logon.You should have created this account manually before you began to installPATROL. (For more information,

see Accounts on page43.)

11
In the Review Selections and Install window, review your selections and, to makechanges,

click
Back

or, to start installing, click

Start Install

.A status window opens that contains current

messages, current milestones, andpercentage complete.

12
When the status window reports that the

installation is 100% complete, click

Next

to view the results window. (

Next

does not appear

until the installation is 100%complete.)

13
(Optional)

In the results window, click

View Log

to review the

details of theinstallation.

14
Click
Finish

to close the installation utility. First-time

installation58 BMC PATROL for Microsoft Windows Servers Getting Started

Toinstall using the

custom installation type1

Close the Service Control Manager window and the Control Panel

window.

2
From the PATROL for Microsoft Windows Servers CD or from an installationimag

e that has been electronically downloaded from an EPD site and extracted,run
setup.exe

.When installing on a Windows

Server in application mode or with CitrixMetaframe installed, perform the following steps to launch the installation

utility:

A
From a command line, change to the directory where the installation utility islocated and enter the

following command to change to installation mode:

change user/install

B
Enter the

following commands to start the installation Web server:

setup.exe serveronly

A message box is displayed that

shows the URL to use to connect to theinstallation Web server.

C
On another computer with a browser, start the browser.

D
Connect to the installation Web server from the browser to start the installationutilit y by using the URL that is

displayed in the message box on the computeron which you are installing the product.

3
In the Welcome to the

Installation Utility window, click

Next

4
In the Review License Agreement

window, review the license agreement, select

Accept

and click
Next

In the Select Installation Option window, select

I want to install products on thiscomputer now

and click

Next

6
From the Select Type of Installation Window, select
Custom

and click

Next

7
In the Specify Installation Directory window, enter the directory where

theproducts that you select will be installed and click

Next

.The PATROL product directory is appended to the

path that you enter in this step.You will specify the PATROL product directory instep10 on page59.

8
In the Select System Roles window, select any or all of the following roles toindicate the components that you want to

install and click

Next

: First-time installationChap ter 2Installing and migrating PATROL for Windows

Servers59
s

If you are installing to a computer that hosts or will host a PATROL Console,select
Console System

.
s

If you are installing to a computer that hosts or will host a PATROL Agent,select
Managed System

.
s

If you are installing to a computer that hosts or will host the PATROL CentralOperator

 Web Edition or the PATROL Console Server, select

Common Services

.For more information about the

PATROL consoles and PATROL Console Server orRTserver, see the following documents:
s

PATROL Central

Operator Web Edition Getting Started

s

PATROL Central Operator Microsoft Windows Edition Getting Started

s

PATROL Console Server and RTserver Getting Started

9
From the Select Products and Components to Install window,

select the items thatyou want to install, and click

Next

10
In the Provide the PATROL 3. x

Product Directory window, enter in the PATROL3. x Product Directory field the directory in

which you want to install PATROL forWindows Servers as appropriate for your installation.This directory is

appended to the base directory path that is shown in the BMCProducts Installation Directory field entered instep7 on page57 .

11
If the PATROL Default Account Properties window appears, enter the user nameand password that

you want to use for your PATROL default account and click
Next

. This window is displayed only when you are

installing a product thatrequires a PATROL logon.You should have created this account manually before

you started the installationproce ss. (For more information, see Accounts on page43.)

12
In the Complete the Confirm

BMC Product Startup Information window, performthe following steps (this window does not appear if you are not

installing into amanaged system):

A
In the
Specify the Current Agent Port Number

field, enter the

port number thatyou want the PATROL Agent to use. The default is 3181.

B
In the
Restart the PATROL agent

automatically?

field, click
Yes

or
No

.
NOTE

If your previous installation used a

different port number, change the default to thecurrent port number for the PATROL Agent. First-time installation using

Distribution Server60 BMC PATROL for Microsoft Windows Servers Getting Started

13
In the Review

Selections and Start Install window, review the selections and, tomake changes, click
Back

or, to start installing, click

Start Install

14
When the status window reports that the installation is 100% complete, click

Next

to view the results window. (

Next

does not appear until the installation is 100%complete.)

15
(Optional)

In the results window, click

View Log

to review the details of theinstallation.

16

Click
Exit

to close the installation utility.

First-

time install ation using

Distrib utionS erver

The PATROL for Windows

Servers can be installed locally to a single computer orremotely to multiple computers using the Distribution Server.The

details of how to install a product across an enterprise to multiple machines byusing Distribution Server are

beyond the scope of this book. However, this sectiondoes describe how to import the PATROL for Windows Servers product

into theDistribution Server. It also provides a highlevel overview of the enterpriseinstall ation process.

Distributi on Server features

You use the Distribution

Server to perform remote installations or uninstallations of BMC Software distributed systems products across multiple

systems from a centrallocation. With the Distribution Server you can perform the following actions:
s

Install, uninstall, upgrade, and reinstall products on remote systems from onecentral location.
s

Create collections of products and system groups to distribute multiple productsto multiple systems in one

distribution.
s

Schedule a distribution for a specific date and time.

s

Maintain multiple product versions to be

distributed. First-time installation using Distribution ServerChapter 2Installing and migrating PATROL for

Windows Servers61
s

View reports to check distribution status, gather distribution data, and

diagnosisproble ms.To import PATROL for Windows Servers into the Distribution Server, perform thefollowing tasks: Importing

a CD or customized installation package intoDistribution Server on page61.

Importin

g a CD or customiz ed installati on

package intoDistri bution Server

This task describes how to

import components into the Distribution Server fordeployment to multiple locations.

Before you

begin
s

The customized installation packages that resulted from Creating an installationpack

age of the migrated and merged KM on page70 must be accessible to theDistribution Server.
s

Ensure that you

use the Distribution Server version 7.1.01 or later.

Toimport components in to the Distribution

Server1
Using the Distribution Server Manager, connect to the Distribution Server.

In the Distribution Server tab area, click the

Components

tab.

3
In the list area, click the

Import

button.

4
Navigate to the location where the components are located and click
Next

5
Select the directory that contains the
Products

directory (do not select the

Products

directory itself).If the components are not accessible on a local drive, you can specify them by usingthe NFS name and path.

EXAMPLE

Assuming that you copied the CD image into a directory called merged_CD and then, aftermigrating your

customizations and creating a customized installation package, you copied theupdated package to the directory containing the CD image, the

resultant directory structurewould resemble merged_CD\Pro ducts\pokchm . You would select the directory merged_CD .

First-time installation using Distribution Server62 BMC PATROL for Microsoft Windows Servers Getting

Started

6
Select the check boxes for the components that you want to import and click
OK

7
Click
Import

to import the selected components.

Where to go from here

To remotely install PATROL for Windows Servers throughout your enterprise, usethe instructions in the

Distribution Server Getting Started Guide

. For an overview of thatprocess, see Installing with the Distribution

Server (overview).

Installing with the Distributi on

Server (overvie w)
Once you have imported the PATROL for Windows

Servers into the DistributionServ er, you must perform the following tasks within the tool. The tasks can begrouped into three stages.

Toset up products1
Import components into the Distribution Server repository on the

Components

tabof the Distribution Manager.

2
Arrange components in collections on the

Collections

tab of the DistributionMan ager.

3
Configure the collections on the
Configurations

tab of the Distribution Manager.

Toset up systems1
Create accounts in the operating system of the

computers to which you want todistribute PATROL for Windows Servers.

2
Add accounts and create

profiles for the systems on the

Systems

tab of theDistribution Manager.

3
Add the systems and install the

Distribution Client on the

Systems

tab of theDistribution Manager.

4
Arrange systems in system

groups on the
Systems

tab of the Distribution Manager. Upgrading from an earlier versionChapter 2Installing and

migrating PATROL for Windows Servers63

Todistribute products1
Distribute configurations of collections to

system groups on the

Distributions

tab of the Distribution Manager.

2
Run reports to review

distributions on the
Reports

tab of the Distribution Manager.For detailed instructions about how to

perform remote installations with theDistribution Server, see the Distribution Server Getting Started Guide .

Upgra ding from an

earlier versio n
If you have a previous version

of PATROL for Windows Servers installed on thetarget computer, you have the following options for upgrading to the

new version of PATROL for Windows Servers:

s

Upgrading without saving KM customizations

on page68
s

Upgrading and preserving KM customizations on page68Figure1 on page67describe

s the general process of upgrading to a new version of PATROL for Windows Servers and migrating any customizations.

Automati c migratio n of console

and agent customiz ations

Only customizations

to Knowledge Modules must be migrated.Wheth er you choose to save and migrate your KM customizations

or not, thecustomizatio ns you have made to the following components are preserved andincorporated into the new

version automatically:
s

agents stored in the agent configuration file

s

consoles stored in the console

cache files
NOTE

Customized Knowledge Modules and PSL files are also stored in the cache but they are
not

automatically

preserved and incorporated. Upgrading from an earlier version64 BMC PATROL for Microsoft Windows Servers Getting

Started

Determin ing whether you can

migrate KM customiz ations

Before migrating

customizations, you must determine whether or not yourcustomizati ons to PATROL for Windows Servers can be migrated to the

new versionof PATROL for Windows Servers. SeeTable11to determine whether migration issupported for

your current version of PATROL for Windows Servers.

Conditio ns for

upgradin g
UseTable12to help you choose an upgrade procedure. Table11Versi

ons that you can migrate

C o m p o n e n t V e r s i o n PATROL for Windows Servers2.1.0

1 and l a t e r PATROL KM for Windows OperatingSystem3. 7.00 and laterPATROL KM for Windows Domain Services 1.1.00 and laterPATROL KM

for Microsoft Windows ActiveDirectory1.5 .00

a

, 1.5.01 and later

a

When the PATROL KM for Microsoft

Windows Active Directory is installed on a server thathas PATROL KM for Windows Domain Services 1.3.00, 1.4.00, or 1.4.01 installed, theapplication

classes that begin with

NT_AD

are automatically disabled. These disabledapplicatio n classes are recorded in the configuration variable

/AgentSetup/disa bledKMs .P A T R O L History Loader KM1.5.02 and l a t e r PATROL KM for Event Management2.

7.08 and l a t e r PATROL KM for Microsoft Message Queue1.1.00 and laterPATROL KM for Microsoft Cluster

Server1.1.00 and laterP A T R O L KM for Microsoft COM+1.2.00 and l a t e r PATROL Wizard for Microsoft PerformanceMonit

or and WMI2.0.04 and laterIf you created .km files and parameters usingan older version of this component, they willcontinue to work, even after loading the

newKM. Upgrading from an earlier versionChapter 2Installing and migrating PATROL for Windows Servers65

Determin ing the location of PATROL

During the installation process, the PATROL installation utility records where itinstalls PATROL components in

environment variables. To function properly,various components of the PATROL product require the information stored in

thesevariables. Two important variables are PATROL_HOME and PATROL_CACH E .Throughout this section, all

references to
PATROL_HOME

represent
%PATROL_HOM E%

and all references to

PATROL_CACH E

represent
%PATROL_CAC HE%

Default values for PATROL

location variables
If you do not specify a location for the PATROL installation, the installer uses

thefollowing pre-programmed default locations and stores these locations inenvironment variables.

Viewing

environme nt variables set by PATROL

To view the

value of
PATROL_HOME

,
PATROL_CACH E

and other environmentvari ables, perform the following

procedure: Table12Choo sing an upgrade procedure Use this procedure If you have this situation

Upgrading without saving KMcustomization s

s

have not made any customizations to the KM files in your

previousversion of PATROL for Windows Servers

s

want to overwrite customizations you made to the KM files with thedefault values of the new version

of PATROL for Windows Servers

s

have a currently installed version of PATROL for Windows Serversthat cannot be migrated (SeeTable11 on

page64)Upgradin g and preserving KMcustomization smade customizations to the KM files in your previously installed versionof PATROL for

Windows Servers and want to save those customizationsand migrate them to the new version of PATROL for Windows Servers

Table13Defaul

t values for PATROL location variables

VariableD efault value
PATROL_HOME C:\Program

Files\BMC Software\
<PATROL_directory > PATROL_CACHE

%HOMEDRIVE% \%HOMEPATH%\
<PATROL_directory >

PATROL for

Windows Servers upgrade scenarios66 BMC PATROL for Microsoft Windows Servers Getting Started

Using the

control panel1
Select
Control Panel

using one of the following menu paths:

s

Start => Settings

=> Control Panel .

s

Start => Control Panel.

2
Open the System

application.

3
Select the Advanced tab.

4
Click
Environment Variables

5
Scroll through the System Variable list box to view the variables.The System

application displays PATROL_CACH E only if it is set to a value otherthan its default value.

PATR OL for Windo ws

Server s upgrad escen

arios
Figure1 illustrat es the following PATROL for Windows Servers upgrade scenarios.
s

not migrating customizations

s

migrating customizations manually

s

migrating customizations then installing

the product using one of the followingtools: Common Installation Utility for local installations Distribution Server for

remote installations PATROL for Windows Servers upgrade scenariosChapt er 2Installing and migrating PATROL for

Windows Servers67

Figure1Upgra ding overview for PATROL for Windows Servers

Savingcustomizations?I nstall PATROL forWindows Servers

usinginstructions inInstalling for the firsttime on page55Shut down agent andconsole, remove previousversion from PATROL_CACHE and PATROL_HOME directorieson agent and consolecomputer.

YesNomigrating

Back up PATROL_HOME and PATROL_CACHE directories and note allcustomizations.Instal l PATROL forWindows Servers usinginstructions inonpage55.Shut down agent and console,remove previous version of

theproduct from PATROL_CACHE and PATROL_HOME directorieson agent and consolecomputers.

manually
Manually change settingsor PSL files to match yourcustomizations for theprevious version.Installing over

anexisting PATROL forWindows Serversinstallation?

YesNo
Migrating customizations manually on page72 Import merged package into the Distribution Server and start installer using instructions inImporting a CD or

customized installation package into Distribution Server on page61.Upgrading without saving KM customizations on page68
YesNo

Can you migrate?Determining whether you can migrate KM customizations

onpage64

PATROL for Windows Servers upgrade scenarios68 BMC PATROL for Microsoft Windows Servers Getting

Started

Upgradin g without saving KM

customiz ations
If you do not want to save any customizations of

.km

files, PSL code, alarmthresholds, or events, you can simply install the new version of PATROL forWindows

Servers over your previous version after moving or deleting PATROL forWindows Servers files from the

PATROL_CACH E . SeeFirst -time installation onp a g e 5 5 for instructions.Whe n installing PATROL for Microsoft

Windows Servers over an existing version, if you stop PATROL services manually (not normally required) before

running theinstallation program, stop the PATROL Agent service (

PatrolAgent.exe

) first, followedby any other PATROL

services.

Upgradin g and preservi ng KM

customiz ations
Use the appropriate task in this section if you want to upgrade to the

new version of PATROL for Windows Servers and you want to preserve any customizations youhave made to the

.km

files in the previous version of PATROL for Windows Servers.You must first migrate your customizations

from the old version of PATROL forWindows Servers to the new version, and then install the result into yourenvironmen

t. You should complete this process on a limited number of computers inthe test environment first, test the merged KMs

thoroughly, and then deploy them toyour production environment.

NOTE

Customizations applied using PATROL

Configuration Manager or operator overrides areautomatically saved in the agent configuration database. They will take effect automaticallyunle ss the parameter

name or application name has changed. In either of those cases, youmust reapply the customizations.
NOTE

To upgrade and preserve

customizations, you must either migrate your customizationsma nually or use the PATROL Migration Tools version 3.5 to create a customized

installationpackag e. If you are using the Distribution Server to install the merged customization package,ensure that you have the latest version of the product

installed as well as any availablepatches. PATROL for Windows Servers upgrade scenariosChapt er 2Installing and migrating

PATROL for Windows Servers69

Preparin g to upgrade
Whether you are

upgrading and migrating customizations or simply upgrading, youmust first back up the current installation. If

the
.kml

file or any of the

.km

files for thenew version of PATROL for Windows Servers has a

different file name from theprevious version, you must remove those files from the list of KMs that are preloadedon the

PATROL Agent.

Before you begin

If you plan to migrate your customizations, determine whether you can

migrate froma previous version of PATROL for Windows Servers. SeeTable11 on page64todetermi ne whether migration is

supported for your current version of PATROL forWindows Servers.

Toback up the current

installation
Back up your customizations so that you can restore the current installation if youwant to roll back your

upgrade.

1
Shut down any PATROL Agents, consoles, and related services that are currentlyrunnin

g.

2
Ensure that no one is accessing any PATROL files or directories.

Perform a full backup of the directories where PATROL files are typically stored.These directories are listed in the

following table:

Where to go from here

If you are migrating customizations manually, go to Migrating

customizationsm anually on page72. F i l e t y p e D i r e c t o r y

executables and data PATROL_HOME

for agent and console installation directoriesconsole customizations PATROL_CACH E for the console working cache PATROL for

Windows Servers upgrade scenarios70 BMC PATROL for Microsoft Windows Servers Getting Started

Migratin g customiz ations with the

PATROL Configur ationMan ager

BMC Software recommends that

if you have customized KMs that thesecustomizati ons should be migrated to PATROL Configuration Manager

rulesets.PATRO L Configuration Manager rulesets allow you to manage customizations toKMs, depending on the type of

customization.
s

If you have localized parameters or global parameters that have customized polltimes or

thresholds, use the AS_CHANGESP RING KM to migrate thesecustomizati ons into PATROL Configuration

Manager rulesets as described in the PATROL Configuration Manager User Guide .

s

If you have created custom recovery actions, follow these steps:1.Ensure that you have made a record of your customizations

and have backed upthe customized files in the

PATROL_HOME

and
PATROL_CACHE

directories.2.Uni nstall the old

version of PATROL for Microsoft Windows Servers.3.Install the new version of PATROL for Microsoft Windows

Servers as describedin the section Installin g for the first time on page55.4.Ensure that you have made a record of your custom

recovery actions.5.Use the Recovery Action Event Management commands as described in the PATROL Configuration

Manager User Guide

to migrate your custom recoveryactions to the PATROL Configuration Manager.

Creating an installati on package

of the migrated and mergedK M

After you have migrated and merged your customizations, you must create aninstallation package that can be used with the installation

utility to install locally onone computer or with Distribution Server to install remotely on multiple computers.

1
Copy the entire contents of the PATROL for Windows Servers CD to a temporarydirect ory on a hard drive on a

server. You can delete this temporary directory afteryou have successfully created an installable image.

2
Navigate to the
packaged_results

directory for the merged package and open the

.ppf

file with a text editor. Write

down the file name in the first line of the

.ppf

file.This file name is the name of the directory that you will look for

in the
Products

directory of the CD image. PATROL for Windows Servers upgrade scenariosChapt er 2Installing

and migrating PATROL for Windows Servers71

3
Rename the
packaged_results

directory with the file name

that you found in the

.ppf

file in the previous step.

4
Copy the renamed directory to the

Products

directory of the temporary directorythat you used in Step 1. You will be replacing the files there with the merged

filesthat contain your customizations.

5
Copy the PATROL for Windows Servers CD image to the

server that you will useto install PATROL for Windows Servers.

Where to go from here

s

Remove the files

in the
PATROL_CACHE

directory by following the instructions in Moving files from the PATROL_CAC HE directories.

Install PATROL for Windows Servers from the target server by following theinstructions in Installing for the first time

on page55.
s

Import the customized version of PATROL for Windows Servers into theDistribution

Server by following the instructions in Importing a CD orcustomized installation package into Distribution

Server on page61.

Moving files from the PATROL

_CACHE directori es
Before you install, you must move the current PATROL for

Windows Servers filesfrom the PATROL_CACHE directory for the console. If you do not, old product filesin

PATROL_CACHE

are loaded instead of the newly installed files from PATROL_HOME .Copy the PATROL for Windows

Servers files with the naming patterns shown inTable14to a directory outside the PATROL installation and delete them from PATROL_CACHE

\knowledge

and PATROL_CACHE
\psl

EXAMPLE

If pokckm/8.5.00/030 107-233044

was listed in the first line of the .ppf file, you would use pokckm as the directory name.

Table14KM

file naming patterns (Part1of2)

C o N n p r o m p n e n t a m i g a t t e n

PATROL KM for Microsoft Windows OS

s

NT_*
s

PATROL*
s

RECOVERY*PAT ROL KM for COM+

s

Com* PATROL for Windows Servers upgrade scenarios72 BMC PATROL for Microsoft Windows Servers Getting

Started

Migratin g customiz ations

manually
If you have made customizations to the PATROL Script Language (PSL) code, you must

manually migrate those customizations. This task contains a procedure formanually migrating each kind of

customization.

Tomigrate customizatio ns to KM files manually1

Ensure that you have made a record of your

customizations and have backed upthe customized files in the

PATROL_HOME

and
PATROL_CACHE

directories.

2
Uninstall the old version of PATROL for Windows Servers.

3
Install the new

version of PATROL for Windows Servers as described in thesection Instal ling for the first time on page55.

4
Identify and record the coding changes, which represent your customizations, inPATROL for Windows

Servers by comparing the content of the ASCII files in thenewly installed PATROL for Windows Servers version

with the content of thecustomized ASCII files with the same name that is saved in the directory to whichyou moved the old version.

PATROL KM for Microsoft Message Queue

s

MQ*
s

MSMQ*PATROL KM for Microsoft Windows Domain Services

s

MSDM*
s

NT_*
s

NTD_*PATROL KM for Microsoft Windows Active Directory

s

AD*
s

MWD*PATROL

for Microsoft Cluster Server

s

MCS*PATROL KM for Event Management

s

AS*
s

EVENT*PATROL KM for Log

Management
s

LOG*
s

PMG*PATROL History Loader KM

s

H*.km
s

H*.psl
s

History-*
s

History_Loader*
s

Hist*
s

COM_DEB_*
s

COM_STAT_*PA TROL Wizard for Microsoft Performance

Monitor andWMI
s

NT_WMI*
s

NT_PERFMON*

Table14KM file naming patterns (Part2of2)

C o m p

o n e n t N a m i n g p a t t e r n Installing PATROL KM for Microsoft Cluster

ServerChapter 2Installing and migrating PATROL for Windows Servers73

5
Incorporate your

customizations to the new PATROL for Windows Servers byperforming the following steps:

Restart the PATROL console.

B
Load the newly installed PATROL for Windows Servers.

C
Using a PATROL developer console, enter the customizations that youidentified

instep4 on page72 ,one by one.

Tomigrate customized PSL code

Customizations made to

PATROL Script Language (PSL) code are not automaticallymi grated. These customizations may be embedded in
.km

files or stored in separate

.psl

files. Migrate these customizations manually, using the following guidelines:

If you modified
.psl

files that were shipped by BMC Software, you must manuallyre-edit the PSL code in

the new KM by using a PATROL developer console toreapply your changes.

s

If you modified

PSL code embedded in a

.km

file, that code will be overwrittenwhen you install a new version of the product.

You must manually edit the new

.km

files by using a PATROL developer console to reapply your

changes.
s

If you created a new PSL file (not shipped by BMC Software) outside of a
.km

file,Installing

PATROL for Microsoft Cluster Server

Installi ng

PATR OL KM for Micros

oft Cluste rServe r

Install the PATROL KM for Microsoft Cluster Server component only if you plan tomonitor and manage a Microsoft server

cluster.The PATROL KM for Microsoft Cluster Server can monitor your Microsoft ClusterServer environment using an external

cluster-level agent or an internal clusterlevelagent (CLA). To help you decide which of these options is best for your

environment,Ta ble15 on page74 provides you with the characteristics of each of these options. Installing PATROL KM for

Microsoft Cluster Server74 BMC PATROL for Microsoft Windows Servers Getting Started

External

clusterlevel agent architect ure

The external CLA uses a three-tier architecture, as shown inFigure2 on page75, andhas components that you install

inside and outside of a cluster. The external CLAuses a cluster-level agent machine that resides outside the

cluster to collect data fromthe cluster nodes in all of the clusters you monitor.Althoug h the external cluster-level agent can

monitor one or more clusters, BMCSoftware recommends that you monitor no more than ten clusters from one cluster-level

agent for performance reasons. A cluster can be monitored by only one clusterlevel agent. Table15Monito ring

configuration options for PATROL KM for Microsoft ClusterServer

Monitoringconfi gurationChara cteristics external CLAThe

following statements apply to an external CLA configuration:

s

allows you to use the same CLA to monitor multiple clusters

s

maintains both the configuration and history files outside of thecluster; history is not interrupted during a failover
s

requires a CLA computer that

resides outside of the clusterinternal CLAThe following statements apply to an internal CLA configuration:
s

monitors only the underlying cluster

s

does not provide an uninterrupted history; configuration and historyfiles are stored on a local drive and,

therefore, are not shared with thenew quorum owner after a Cluster Group failover
s

automatically replicates the configuration

information to all the nodesin the cluster

s

does not require a computer that resides outside of the cluster to runthe CLA
s

allows the KM to

use the PATROL agent default account when certainrequiremen ts are satisfied
s

easier to set up and configure Installing PATROL KM for

Microsoft Cluster ServerChapter 2Installing and migrating PATROL for Windows Servers75

Figure2PATR

OL KM for Microsoft Cluster Server with external CLA configuration

Internal

clusterlevel agent architect ure

The internal CLA uses a twotier architecture, as shown inFigure3 . Figure3PATR OL KM for Microsoft

Cluster Server with internal CLA configuration While the PATROL KM for Microsoft Cluster Server

(MCS KM) is loaded on all of theagents on all of the nodes in the cluster, only the MCS KM on the quorumowningnode actively

monitors the cluster.

Node 1Node 2Cluster 2Node 1Node 2Cluster 1Install the PATROL KM for Microsoft Cluster Server and aInstall the PATROL KM forCluster-levelagent

computerMicrosoft Cluster Server, and Install the PATROLKM for Microsoft Cluster Server, PATROLPATROL Agent here.Agent, and OS KM here.Install the PATROL KM for

MicrosoftCluster Server, PATROLAgent, and OS KM here.Install the PATROLKM for MicrosoftCluster Server, PATROLAgent, and OS KM here.Install the PATROLKM for MicrosoftCluster Server,

PATROLAgent, and OS KM here.PATROL Console here.

Node 1 - quorum owner

Node 2Cluster 1
Install the PATROL Console here.Install the Agent,MCS KM, andMicrosoft WindowsOS KM on all nodesin the cluster

Installing

PATROL KM for Microsoft Cluster Server76 BMC PATROL for Microsoft Windows Servers Getting Started

How to Install the PATROL KM for

Microsoft Cluster Server

Before you begin installing the PATROL KM for

Microsoft Cluster Server, you musthave the following completed:

s

know the user name and password of the

cluster connection account

s

installed the PATROL KM for Microsoft Windows OS and loaded the

NT_BASE.kml
s

installed the PATROL Agent

Cluster connectio n account

For each cluster,

the cluster connection account (specified in the clusteradministr ator) must have the appropriate permissions and trusts to

establish asession with the cluster. For more information about the cluster account, see PATROL KM for

Microsoft Cluster Server account on page48.You can verify that the cluster connection account has the appropriate

permissions bylogging into the cluster-level agent with the selected account and connecting to thecluster with either the Microsoft

Cluster Administrator GUI or the

cluster.exe

command-line tool.For information about how the PATROL Agent

supports an application in a clusterenvironm ent and what type of failover tolerance the agent provides, see the PATROL Agent

Reference Manual

Support for Quorum Configura

tions in a failover cluster

PATROL KM for Microsoft Cluster Server has added

support for the MicrosoftWindo ws server 2008 cluster.

Support for external CLA

s

Node and File share Majority

Node and Disk Majority

s

Node Majority
s

No Majority: Disk only

NOTE

If you use Windows Server

2008 as an external CLA, you must install Failover Clustering toolsfrom Server Manager. By default, the cluster.exe is not present in

Windows 2008 nonclustercomputer. Considerations for using online HelpChapter 2Installing and migrating PATROL for

Windows Servers77

Support for internal CLA

s

No Majority: Disk only

Installatio

n process
The PATROL KM for Microsoft Cluster Server installation process consists of thefollowing

tasks:

1
Install the following components on each cluster node:
s

PATROL Agent
s

PATROL KM for Microsoft Cluster Server

s

PATROL KM for Microsoft Windows

2
This task is only

required if you are using an external CLA.

Install the followingcompo nents on each computer that contains an external cluster-

level agent:
s

PATROL Agent
s

PATROL KM for Microsoft Cluster Server

3
Install the PATROL KM

for Microsoft Cluster Server on the computer that hasyour PATROL Console. This component can exist on the same computer

as theexternal cluster-level agent or on a cluster node.

Consi deratio

ns for using online Help

If you plan to install the UNIX version of PATROL for Windows Servers on aPATROL Console for UNIX, you must

install the supported version of the Helpbrowser separately if it is not already installed.
WARNING

Do not load the

PATROL KM for Microsoft Cluster Server on a virtual agent. Considerations for using online Help78 BMC PATROL for Microsoft

Windows Servers Getting Started

Browser version required

for viewing PATROL Console forUNIX

Help
The appropriate one of the following browsers is required to view PATROL Help inPATROL

version 3. x :
s

UNIX: Netscape Navigator version 3.01 through 4.78

s

Red Hat Linux:

Netscape Navigator version 4. x PATROL Help does not support Netscape Navigator 6.0.

Installatio n requireme nt
You must install Netscape Navigator on

the computer where the PATROL consoleresides. You can install Netscape anywhere on your UNIX computer as

long as thebinary is in the path.

Download location
Netscape Navigator is supplied by

Netscape Communication s Corp. You can locatethe browser at

http://home.netsc ape.com/downloa d

Addition al consider ations for using

online Help for UNIX

When you select Help from the PATROL Console for

UNIX, it may take a fewseconds for the Help browser to launch. Two windows will be displayed. First, theNetscape

Navigator window is displayed as an icon, and then a browser window thatcontains the Help is displayed.In addition, you

must be aware of the following restrictions:

s

Netscape Navigator displays warning messages when

it is invoked multiple timeswithin the same user account because of its filelocking mechanism. It will,however,

continue functioning.
s

By default, when Netscape Navigator starts, it uses a private color map. As aresult, you

might experience color flashing on your workstation. If so, you can setthe value of PATROL_BRO WSER so that the colormap

option is not specified.Howev er, some subsequent color requests might fail and the online Help will beimproperly

displayed.
s

The Exceed for Windows product by Hummingbird Communication Ltd. may notalways

display the Help files properly. Considerations for using online HelpChapter 2Installing and migrating PATROL for Windows

Servers79

Consult your Netscape Navigator documentation for specific platform requirementsand restrictions.

Required environm ent variables settings for the

browser
The LANG, PATH, and PATROL_BRO WSER environment variables must be set forthe

Help browser to run properly. The following sections describe these variables.

LANG variable
The UNIX

LANG environment variable must be set to C so that Netscape Navigatorwill work properly. Otherwise, you might

experience product failures.

PATH variable
The PATROL user account PATH variable must contain the location of the directorycontaini

ng the Netscape files. If the directory containing the Netscape files is not inthe path, add the directory to the PATROL user

account path.This requirement applies only to the PATROL user account on the PATROL consolecompute r.

PATROL_BR OWSER variable

When PATROL starts the Help browser, it uses the command in thePATROL_BR

OWSER environment variable. As a default, the PATROL_BRO WSERenvironm ent variable contains the following

command: Type of shellExport command for LANG variable

B o u r n e L A N G = C export

LANGK o r n e x p o r t L A N G = C C s e t e n v L A N G = C Type of shellExport

command for PATH variable B o u r n e P A T H = $ P A T H :

/netscape_location

export PATHK o r n e x p o r t

P A T H = $ P A T H :
/netscape_location

C s e t e n v P A T H = $ P A T H :
/netscape_location

Uninstalling PATROL for Windows

Servers80 BMC PATROL for Microsoft Windows Servers Getting Started

To use different arguments, set the value of

PATROL_BRO WSER to the appropriatestring .

Uninst alling

PATR OL for Windo ws

Server s
To uninstall PATROL for Windows Servers, you can

use the Windows Add/RemovePro grams functionality or the installation utility that you used to install the product.

Determin ing the version of the installati

on utility
To determine the version of the installer, perform the following procedure.

Access a command prompt and navigate to the appropriate location:(Windo ws) <BMC_ROOT>
\Uninstall

(UNIX) <BMC_ROOT>
/Uninstall

2
Type the following command and press ENTER.(Windo

ws)
uninstall.exe -v Type of shellExport command for PATROL_BRO WSER variable BournePATRO

L_BROWSER= netscape display $DISPLAY install i c o n i c export LANGK o r n e x p ort PATROL_BRO WSER=netsca

pe -display $DISPLAY install iconicC s e t e n v PATROL_BR OWSER=nets cape -display $DISPLAY i n s t a l l - iconic

EXAMPLE

For a Korn shell:

export PATROL_BROW SER=/usr/local /bin/netscape raise

WARNING

If you use a

different version of the installation program to uninstall the product than theversion that you used to install the product, you might remove files that are

needed toperform uninstallation of other BMC Software products. Uninstalling PATROL for Windows ServersChapter

2Installing and migrating PATROL for Windows Servers81

(UNIX)
./uninstall.sh -v

Uninstalli

ng PATROL for Windows Servers

on Windows
You can use the option that is appropriate for what you want to uninstall to

uninstallPATRO L for Windows Servers. The following procedures describe how to uninstallproduct s from a Windows

environment and all related log files.

Touninstall individual products1

From the
Uninstall

directory in your BMC Software product installation directory,doubleclick

uninstall.exe

to launch the installation

utility in uninstall mode.When installing on a Windows Server in application mode or with CitrixMetaframe installed,

perform the following steps to launch the installation utilityin uninstall mode:

A
From a command line,

change to the directory where the installation utility islocated and enter the following command to change to installation

mode:
change user/install

B
Change to the
Uninstall

directory and enter the following

command to start theinstallation Web server:

uninstall.exe serveronly

A message box is displayed that shows the URL

to use to connect to theinstallation Web server.

C
On another machine with a browser, start the browser.

D
Connect to the installation Web server from the browser to start the installationutilit y by using the URL that is

displayed in the message box.The Welcome window is displayed. Click

Next

Select the installation directory from which you want to remove a product, andclick
Next

NOTE

As an option, you can launch the installation utility in uninstall mode by choosing Start =>Settings => Control Panel => Add/Remove Programs

and doubleclicking BMC SoftwareTools in the Add/Remove Programs Properties dialog box.

Uninstalling PATROL for Windows Servers82 BMC PATROL for Microsoft Windows Servers Getting Started

3
Select the product or products that you want to uninstall, and click
Next

4
Review your selections and click
Uninstall

.After the uninstallation is complete, a window is

displayed that tells you whetherthe uninstallation was successful.

Toretain log files and configuration

files
This task describes how to uninstall the PATROL product but retain log files, whichcontain history for

future analysis, and configuration files for redeployment.

1
Uninstall all products as described

in Touninstall individual products onp a g e 8 1 .

2
Locate the
uninstall.ctl

file in the following

directory.
%PATROL_HOM E%

\Uninstall\Instal l\instdata

3
Open the
uninstall.ctl

file in a text

editor, and edit the

/BMC/Base

variable to specifythe name of the directory from which you removed the products instep

1.

4
Open a command line prompt.

5
Change to the following

directory.
%PATROL_HOM E%

\Uninstall\Instal l\ instbin

6
Enter the following command.

thorinst.exe uninstall path to control file -log path to log file -output path to output log file

Use the

following table to help determine the log file and output log file locations: O p t i o n D e s c r i p t i o n V

a l u e -logsends the log information t o a s t a n d a r d log fileThis file contains all installation statusinformation. any valid path and file name

(with a .txt extension)If a space exists in the path, the entirepath must be enclosed in quotationmarks.outputsends the log information

to an outputlog fileThis file contains all messages about theprogress of the installation that arenormally sent to standard output.any valid path and file

name (with a .txt extension)If a space exists in the path, the entirepath must be enclosed in quotationmarks. Uninstalling

PATROL for Windows ServersChapter 2Installing and migrating PATROL for Windows Servers83

Example

If
C:\Program Files\BMC Software

is your product installation directory, you wouldchange to the

C:\Program Files\BMC Software\Uninst all\ Install\instbin

directory andenter the following command:This

action would remove all installation files and directories except those that areused by the utility at the time the uninstallation

was performed. Log files,configurati on files, and user-modified files would also be retained.

Touninstall

all log files and configuration files

This task describes how to remove all PATROL

products and related log files andconfiguration files from your Windows computer. Once these files have beenremoved, you cannot

recover them unless you have made a back-up copy of theinstallation.

1
Uninstall all products as described

in Touninstall individual products onp a g e 8 1 .

2
Locate the
uninstall-all.ctl

file in the following

directory.
%PATROL_HOM E%

\Uninstall\Instal l\instdata

3
Open the
uninstall-all.ctl

file in a text

editor, and edit the

/BMC/Base

variable tospecify the name of the directory from which you removed the

products instep 1.

4
Open a command line prompt.

5
Change to the

following directory.
%PATROL_HOM E%

\Uninstall\Instal l\instbin

6
Enter the following

command.
thorinst.exe uninstall path to control file -log path to log file -output path to output log file

thorinst.exe uninstall C:\Program Files\BMCSoftw are\Uninstall\I nstall\instdata\ uninstall.ctl logZ:\Network

Logs\MyLogs.t xt -output Z:\NetworkLog s\MyLogs.out Uninstalling PATROL for Windows Servers84 BMC PATROL

for Microsoft Windows Servers Getting Started

Use the following table to help determine the log file and

output log file locations:

Example
If
C:\Program Files\BMC Software

is your product installation

directory, you wouldchange to the

C:\Program Files\BMC Software\Uninst all\Install\instbi n

directory

andenter the following command:This action would remove all installation files and directories. The files that wereused to

perform the uninstallation will be marked for deletion and will be removedwhen the computer on which the products were

uninstalled is rebooted. O p t i o n D e s c r i p t i o n V a l u e
-logsends the log information to

a s t a n d a r d log fileThis file contains all installation statusinformation. any valid path and file name (with a .txt extension)If a space exists in the

path, the entirepath must be enclosed in quotationmarks.outputsends the log information t o a n o u t p u t log fileThis file contains all messages about

theprogress of the installation that arenormally sent to standard output.any valid path and file name (with a .txt extension)If a space exists in the

path, the entirepath must be enclosed in quotationmarks.

thorinst.exe uninstall C:\Program Files\BMCSoftw are\Uninstall\I

nstall\instdata\ uninstallall.ctl logZ:\Network Logs\MyLogs.t xt -output Z:\NetworkLog s\MyLogs.out

Where to go from hereChapter 2Installing and migrating PATROL for Windows Servers85

Where to go from here

The following table lists other topics and where you can find them: T o p i c S o u r c e o f I n f o r m

a t i o n overview of the PATROL for WindowsServers featuresChapter1, Product components and capabilities settin g up and configuring

PATROL forWindows ServersChapter3, Loading and configuring PATROL forMicrosoft Windows Servers, and PATROL

forWindows Servers component online Helpinstructions about how to access theKM menu commands, InfoBoxes andonline HelpAppendixA,

Accessing menu commands,InfoBo xes, and online Help information about PATROL forWindows Servers configurationvaria bles and predefined

rulesetsAppendix B, Agent configuration variables andrulesets listin g of the KM included with eachPATROL for Windows Serverscomponent

AppendixC, PATROL for Microsoft WindowsServers .kml files step-bystep procedures and detaileddescriptio ns of the applications,para

meters, and InfoBoxesPATRO L for Windows Servers component onlineHelp Chapter 3Loading and configuring

PATROL for Microsoft Windows Servers87 Chapter

3
3

Loadi ng and

confi gurin g

PAT ROL forMi

cros oft Wind

ows Serv ers

This chapter provides information about how to begin using and configuring thePATROL for Microsoft Windows

Servers components. The following topics arediscussed in this chapter:Preparin g to use PATROL for Windows Servers

............. ............. . . . .89Loading and preloading KMs . . . . . . . . . . .............. .............. . . . . .90Loading the PATROL for

Microsoft Windows Servers KMs . . . . . . . . . ....... .91Preloading KMs on the PATROL Agent . .............. ..............

.... .94Requirements for configuring from the PATROL Console. . . . . . . ........... .97Configuring the PATROL

KM for Microsoft Windows OS. . . ............. .... .101Enabling and disabling system monitoring. . . . . .............

............ .102Configuring Windows events monitoring. . . . . ............. ............. .103Configuring service monitoring . . . . .

.............. .............. ...... .114Configuring process monitoring. . . . . .............. .............. ......

.117Creating custom parameters . . . . . .............. .............. ......... .124Viewing event logs . . . . . . ..............

.............. .............. .. .125Configuring Blue Screen monitoring . . . . . .............. .............. . . .126Notifying

when disks are not present . . . . ............. ............. .... .126Providing nonaggregate values for a drive instance . . . . . . .

............. .. .127Configuring recovery actions. .............. .............. .............. . . .128About recovery actions.

.............. .............. .............. . . . . .128Built-in native recovery actions. . . . . . . . .............. .............. ....

.129Configuring built-in native recovery actions ............. ............. .. .130Configuring e-mail notification . . . . .

.............. .............. .......... .132Using notification scripts . . . . . . . . .............. .............. .........

.133Defining notification servers . . . . . . . . .............. .............. ...... .136Assigning notification servers for the

remote agents. . . ............. ...... .138Assigning notification targets for a PATROL alert. . ............. .........

.140Configuring the PATROL KM for Microsoft Active Directory. . . . . . ........... .141Configuring PATROL Wizard for

Microsoft Performance Monitor and WMI . . . .142Loading the PATROL Wizard for Microsoft Performance

Monitor and WMI .142Creating performance monitor parameters. . . . . ............. ............ .143Setting alarm

thresholds. . . . . . .............. .............. ............ .144 88 BMC PATROL for Microsoft Windows

Servers Getting Started

Creating WMI parameters . . . . . .............. .............. ........... .144Configuring the PATROL

KM for Log Management . . . ............. ......... .147Stop and start monitoring all default log files. . . . . . . . . . .............

. . . . . .149Stop monitoring a log file. . . . . . . . . . . .............. .............. . . . . . . .149Start monitoring a log file. . . . . . . . . . . ..............

.............. ...... .150Change the setup of a monitored file . . ............. ............. ....... .156Filter log file

messages (create a search string) . . .............. ........... .157Generate a custom event when a search string is identified. . . . . .

.......... .160Configure recovery actions for a log file. . . . .............. .............. . .164Configuring the PATROL KM for

Microsoft Cluster Server . . ............. . . . . .165Using the PATROL Adapter for Microsoft Office to view reports . .............

.166Displaying PATROL data by using the PATROL Adapter for Microsoft Office167How to use the PATROL Adapter for

Microsoft Office. ............. ...... .168Built-in report templates. .............. .............. .............. ...

.168Removing KMs from your console and agent . . . . . . . . . ............. ......... .170Unloading KMs from a PATROL console

.............. .............. . . . .171Stopping preloaded KMs from running on the PATROL Agent . . . . . . . . . . . . .173 Preparing to use

PATROL for Windows ServersChapter 3Loading and configuring PATROL for Microsoft Windows Servers89

Prepar ing to use PATR

OL for Windo ws Server

s
If PATROL for Windows Servers has not been installed, seeChapter2, Installing and

migrating PATROL for Windows Servers. After installing, return to this sectionfor information about how to configure the

components.Bef ore configuring the PATROL for Windows Servers components, you should verifythat the following

software requirements are met:

s

A supported version of a PATROL Console version 3.x and

PATROL for WindowsServers must be installed on the computer you want to use for the PATROLConsol e.

A supported version of the PATROL Agent and PATROL for Windows Serversmust be installed on the computer you

want to monitor and manage.

s

If you are using PATROL Central Operator Microsoft Windows Edition

orPATROL Central Operator Web Edition, the KMs that you want to use must beinstalled on the computer hosting the

PATROL Console Server.You should also verify that you have access to all required information about

themonitored domain controllers or Windows servers.

NOTE

In this chapter, the term Knowledge

Module (KM) is usually equivalent to a .kml file. A .km file is equivalent to an application class, which is a subset of a KM or

.kml file.
NOTE

For supported versions of PATROL products, see the release notes for the version of PATROLfor

Microsoft Windows Servers that you are installing.

EXAMPLE

If you want to monitor the operating system, ensure that you

have the PATROL Console andthe PATROL KM for Windows OS installed on the console machine and the PATROL Agentand the PATROL KM for Windows OS

installed on the agent machine. Preparing to use PATROL for Windows Servers90 BMC PATROL for Microsoft Windows

Servers Getting Started

Loading and preloadi ng KMs

When you load a KM from the PATROL Console for Windows or the PATROLConsol e for UNIX, the KM files are loaded on all the

PATROL Agents to which theconsole is connected. The KM icons appear in the console, usually under each agenticon, during

discovery. Each PATROL Agent then collects data based on theinstructions defined in the KM.Preloading KMs is a PATROL Agent

feature that causes KM files to continue to runon the agent when no consoles are connected. KMs that are not preloaded

collect dataonly while a PATROL console is connected to the PATROL Agent.

Determini ng which

KMs to load
Before you can use the KMs that you have installed, the KM files must be loaded

intothe PATROL console so that the products applications, commands, and parametersappea r in the PATROL

console.Table16 lists the KM files in this product that you canload. You can find the steps for loading KM files in Loading the

PATROL forMicrosoft Windows Servers KMs on page91.

Determini ng which

KMs to preload
Preloaded KMs collect data as long as the PATROL Agent runs, even when noPATROL

console is connected. When you view a preloaded KMs data collectionhistory , you will not see any gaps that would

otherwise occur (because of the consoles absence).By default, no

.kml

files are preloaded on the PATROL Agent.

To use the
.kml

filesdescribed inTable16, add them to the preload list for the appropriate PATROLAgents and load them

on the console. You can find the steps for loading andpreloading KMs in the following sections:
s

Loading the PATROL for Microsoft Windows Servers KMs on page91

s

Preloading KMs on the

PATROL Agent on page94 Table16PATR OL for Microsoft Windows Servers .kml

files (Part1of2)
. k m l f i l e C o m p o n e n t D e s c r i p t i o n COM.kmlPATR

OL KM for Microsoft COM+ loads application classes to m o n i t o r COM+ packagesH I S T O RY.kmlPATR OL History Loader

KMloads application classes to m o n i t o r PATRO L KM parameter historyM S M Q . k mlPATROL KM for Microsoft M e s s a g e Queuel

oads application classes to monitorMicrosoft Message Queue (MSMQ) Preparing to use PATROL for Windows ServersChapter

3Loading and configuring PATROL for Microsoft Windows Servers91

Loading the

PATROL for Microsoft Windows Servers

KMs
This section provides instructions for loading the PATROL for Microsoft WindowsServers

KMs on each of the PATROL consoles.

Before you begin

Make sure you have met the following

requirements:
s

the components that you want to load on the agent and console computers areinstalled
s

the agents to which you want to load components are running

s

the PATROL Console is running

NT_LOAD.kmlNT _BASE.kmlNT_H YPERV.kmlPATROL KM for Windows OS loads application classes to monitor theoperating systemMWD_ACT

IVE_Directory_M N.kmlPATROL KM for Windows ActiveDirectorylo ads the application classes to monitorActive DirectoryN T D . k mlPATROL

KM for Windows D o m a i n Service sloads application classes to monitor thedomain controller resourcesMCS_L oad.kmlPATROL KM for

Microsoft Cluster Serverloads application classes that are used tomonitor Microsoft server clustersNT_PERF MON_WIZARD.k mlPATROL

Wizard for MicrosoftPerform ance Monitor and WMIloads application classes that are requiredto use the PATROL PerfMon and WMIWizardEVEN

T_MANAGEMEN T.kmlPATROL KM for Event Managementload s application classes required toconfigure alerts, such as e-mail or pagingnotification sL O G . k m l P A T

ROL KM for Log Management loads application classes required t o configure log monitoring

Table16PATR OL for Microsoft Windows Servers .kml files (Part2of2)

. k m l

f i l e C o m p o n e n t D e s c r i p t i o n Preparing to use PATROL for Windows Servers92

BMC PATROL for Microsoft Windows Servers Getting Started

Toload KMs on the PATROL

Console for Windows Servers1

Choose
File => Load KM

from the PATROL Console menu

bar.

2
Select one or more of the
.kml

files inTable16 on page90that correspond to thecomponents

that you want to load. For detailed information about the applicationclass es that are loaded with these

.kml

files, seePATROL for Microsoft WindowsServers .kml files on page282.

3
Click

OK

Toload the KM on a PATROL Console for UNIX1

Choose

File=>Load KM

from the PATROL Console menu bar.

2
Select one or more of the
.kml

files inTable16 on page90that correspond to thecomponents that you want to load. For detailed information about the

applicationclass es that are loaded with these

.kml

files, seePATROL for Microsoft WindowsServers

.kml files on page282.

3
Click
Open

.
NOTE

If you have installed PATROL

KM for Microsoft Windows OS over a previous version, thefirst time you load the KM, several minutes may be required to migrate forward existingconfigurat

ion settings. If the KM icons do not appear within 10 minutes, open and read theinformation in the PATROL system output window.
NOTE

Unless you are an advanced PATROL user, use the .kml files to load product componentfiles. Loading individual

.km files can break the interdependencies between the .km files.
NOTE

If you have installed PATROL KM for Microsoft

Windows OS over a previous version, thefirst time you load the KM, several minutes may be required to migrate forward existingconfigurat ion settings. If the

KM icons do not appear within 10 minutes, open and read theinformation in the PATROL system output window.
NOTE

Unless you are an

advanced PATROL user, use the .kml files to load product componentfiles. Loading individual .km

files can break the interdependencies between the .km files. Preparing to use PATROL for Windows ServersChapter

3Loading and configuring PATROL for Microsoft Windows Servers93

Toload the KM on PATROL

Central Operator Windows Edition1

In the
Common Tasks

tab of the Operator

Console Module Taskpad, click the

LoadKnowledge Module(s)

icon.PATROL Displays the Load Knowledge Module(s)

Wizard.

2
To start the wizard, click
Next

3
From the

Managed System screen, select the managed system that you want toload KMs on.

4
From the Knowledge

Modules screen, select the KMs that you want to load. Fordetailed information about the application classes that are

loaded with these

.kml

files, seePATROL for Microsoft Windows Servers .kml files on

page282.

5
Click
Finish

.The KMs that you selected are loaded on the managed system, added

to yourmanagemen t profile, and displayed in the PATROL Central Operator tab.

Toload the

KM on PATROL Central - Web Edition

PATROL Central - Web Edition has a Loading KMs

feature that enables you tocontrol which KMs are loaded on which computers.

1
From the Monitored

Systems page, click the

Load/Unload KMs

button.The Load KMs page opens, listing each computer on which a

PATROL Agent hasbeen installed.

2
Select the computers on which you want to load KMs, and click

Next

.The Load KMs page displays a list of available .

km

and .
kml

files.If you selected more

than one computer, the only .

km

and .
kml

files that are listedare the ones that have

been installed on all of the selected computers. If a particular.

km

or .
kml

file was

installed only on one computer, you must choose thatcomputer by itself to load the file.

3
Select the .

km

or .
kml

files that you want to load.

4
Click
Finish

.PATROL loads

the selected KMs on the selected computers. Preparing to use PATROL for Windows Servers94 BMC PATROL

for Microsoft Windows Servers Getting Started

Preloadi ng KMs on the

PATROL Agent
If you want your KMs to continue collecting data even when no

console is running,you must preload your KMs on the PATROL Agent. A preloaded KM is a KM that isloaded by the

PATROL Agent at startup and runs as long as the PATROL Agent runs.To preload a KM, add it to the agents preload list. You can

update the preload list byusing one of these methods:

s

use the PATROL Configuration Manager to

apply one of the predefined rulesets tothe PATROL Agent (see PATROL for Microsoft Windows Servers rulesets onpage257)

using the wpconfig or xpconfig utility

Preloadin g using the

wpconfig utility
This section describes how to use the wpconfig utility to preload KMs on thePATROL

Agent. For information about the wpconfig ir xpconfig utility, see the PATROL Agent Reference Manual .

Before you begin

s

The PATROL Agent must be running.

s

The wpconfig utility must be

installed on a computer that can access machines thatare running the PATROL Agent over the network.
s

You must have permission to modify the configuration change file (

.cfg

).

Touse

wpconfig to preload a KM from the PATROL Console for MicrosoftWin dows1

From a

Windows command window, type

wpconfig.

The wpconfig window is displayed.

2
From the menu

bar, choose
Tools => Get Configuration

.
NOTE

If you want to load a . km or .

kml file that was not listed in Step 2, ensure that the KM isinstalled on the appropriate computer and select only that computer in Step 2.

Preparing to use PATROL for Windows Servers96 BMC PATROL for Microsoft Windows Servers Getting Started

Using wpconfig to remove KMs from the Agent preload

list
If you want to remove a KM or application class so that it no longer runs on thePATROL Agent, remove

the corresponding
.kml

or
.km

file from the agent preloadlist, as described in this

task.

Before you begin

s

The PATROL Agent must be running.

s

The wpconfig

utility must be installed on a computer that can access machines thatare running the PATROL Agent over the network.

You must have permission to modify the configuration change file (

.cfg

).

Touse

wpconfig to remove a KM from the preload list in the PATROL Consolefor Microsoft

Windows1
From a Windows command window, type
wpconfig.

The wpconfig window is displayed.

2
From the menu bar, choose
Tools => Get Configuration

.The Get Configuration dialog box is displayed.

3
In the
Host Name

field, enter the name of a computer hosting the PATROL Agentand click

OK

.The wpconfig utility gets the PATROL Agents configuration.

4
In the left pane, click the

AgentSetup

folder.The variables in the

AgentSetup

folder are displayed in the right pane.

5
Scroll down the

variable list and double-click the preloadedKMs variable.The Modify Variable dialog box is displayed.

6
In the

Change Entries

field, doubleclick the highlighted

REPLACE

line.The Change Entry dialog box is displayed.

7
In the
Type

field, leave
REPLACE

. Preparing to use PATROL for Windows

ServersChapter 3Loading and configuring PATROL for Microsoft Windows Servers97

8
In the

Value

field, delete the

.kml

file names that you want to remove from thepreload list. SeeAppendixC, PATROL for

Windows .kml files for a list of theKMs that are available in this product.

9
Click
OK

to close the

Change Entry dialog box.

10
Click
OK

to close the Modify Variable dialog box.

11
From the
Tools

menu, choose
Apply Configuration

.The Apply Configuration dialog box is

displayed.

12
Click
OK

to apply your updated configuration to the PATROL Agent.

13
Save your changes to the configuration change file by clicking the
Save

button.

14
Close the wpconfig window.

Require ments

for configuri ng from the PATROL

Console
When using the PATROL Console to configure or manage the PATROL KM forMicrosoft

Windows OS, verify that the console connection account, the account thatyou use to connect to the agent, meets the

following requirements:
s

is a member of the local Administrators group on the agent computer

s

has the right

Log on as a Batch Job

assignedIf the console connection account does not meet these requirements, the

featuresdescribe d inTable17are not available. Table17Conso le functionality that requires local admin

rights (Part1of4)
K M F u n c t i o n a l i t y M e n u c o m m a n d B e h a v i o r PATROL KM

forMicrosoft ActiveDirectoryRu nning the ADOperations reportAD OperationsReport System Output details the need for asufficient connection

account. One cangrant read/write permission to theconnection account to %PATROL_HO ME%\Patrol\tmp forthis to work or add the

connecting userto the

Server Operators

group on theagent machine.PATROL KM forMicrosoft ClusterServerDelet ing accountinformatio

nDelete AccessInformation Message is displayed with failure toremove account information. Preparing to use PATROL for

Windows Servers98 BMC PATROL for Microsoft Windows Servers Getting Started PATROL KM forWindows

DomainServicesR unning anavailability reportwith the RemoteServers KMAvailability ReportA blank report is displayed. This reportuses Agent

history data. Give theconnecting account full access to the %PATROL_HO ME%\tmp directorystructure Running a ServerInformation reportwith the

RemoteServers KMServer InformationReport A blank report is displayed. Give fullaccess to the %PATROL_HO ME%\tmp directory structure to the

connectingaccount .Displayinginform ation about auser using the UsersKMDisplay UserInformationA blank report is displayed. Give theconnecting account full access

to the %PATROL_HO ME%\tmp directorystructure Stopping or Startingthe WINS serviceStart/Stop WINSServiceA message is displayed

detailing theinability to access the resource. Add theconnecting account to the built-in
Administrators

group on the Agentmachine.Sta

rting or stoppingthe DFS serviceStart/Stop DFSServiceMessa ge is displayed indicating inabilityto access service. Add the connectingaccount to the built-in

Administrators

group on the Agent machine.Running the DFSOperations reportDFS OperationsReport Report is blank. Give the

connectingaccount full access to the %PATROL_HO ME%\tmp directorystructure, or add the account to the
Server Operators

group on the Agentmachine.

Table17Conso le functionality that requires local admin rights (Part2of4)

K M F u n c t

i o n a l i t y M e n u c o m m a n d B e h a v i o r Preparing to use PATROL for Windows ServersChapter

3Loading and configuring PATROL for Microsoft Windows Servers99 PATROL KM forWindows DomainServices,

continued

Starting or stoppingthe DFS ReplicaserviceStar t/Stop ReplicaDFS ServiceMessage is displayed indicating inabilityto access service. Add the

connectingaccount to the built-in

Administrators

group on the Agent machine.Disconne cting DFSusersView/Di sc.Connected UsersUsers are

not disconnected. Add thePATROL Agent default account to the

Account Operators

,
Print Operators

or
Server Operators

built-in

group.Compressin g theDHCP databaseCompres s DHCPDatabaseM essage is displayed indicating inabilityto access database. Add the

connectingaccount to the built-in

Administrators

group on the Agent machine.Starting or stoppingthe DHCP serviceStart/Stop DHCPServiceMes

sage is displayed indicating inabilityto access service. Add the connectingaccount to the built-in
Administrators

group on the Agent machine.Stopping

or Startingthe DNS serviceStart/Stop DNSServer ServiceA message is displayed detailing theinability to access the resource. Add

theconnecting account to the built-in

Administrators

group.PATROL KM forCOM+Starting or Stoppingthe DTCStart/Stop DTCServiceAcces

s Denied message is displayed.Add the connecting account to thebuilt-in

Administrators

group on theAgent machine.Viewing applicationpropert

iesView applicationpropert iesAn unable to view message is displayed.Add the connecting account to thebuilt-in
Administrators

group.PATROL

KM forMSMQStarting or stoppingthe MSMQ serviceStart/Stop MSMQServiceAcc ess Denied message is displayed.Add the connecting

account to thebuilt-in
Administrators

group on theAgent machine.

Table17Conso le functionality

that requires local admin rights (Part3of4)

K M F u n c t i o n a l i t y M e n u c o m m a n d B e h a v i

o r Preparing to use PATROL for Windows Servers100 BMC PATROL for Microsoft Windows Servers Getting

Started

Supplying an imperson ation account

On Windows 2000, the user right Act as part of the operating system is also required bythe PATROL Agent when it impersonates an

account. That is, when it uses an accountthat you enter to perform the requested action. If the agent default account has thisright

and

it has the user right Log on as batch job , but PATROL still cannot perform therequest, you may need to

also assign the user right Bypass traverse checking to thePATROL Agent default account.
PATROL KM forMicrosoftWind

ows OSConfiguring BlueScreen KM (NT_BSK)system recoveryactionsSe t System RecoveryActionsA pop-up window displays a messagestating

that the connecting user musthave administrator privileges.Config uring BlueScreen monitoring(NT_B SK)Configure BlueScreenMonito ringYou can use

the three options providedto configure the KM. The KM looks forthe crash dump file as well as the event(ID 6008).Configuring Windowsoperatin g

systemquotasConf igure OperatingSystem QuotasThe KM prompts you to supply anadministrative account that includes theuser right

Log on as batch job

on thePATROL Agent machine.For more information, see Supplying animpersonation account on page100.Managin g

Windowsservices, such asstarting and stoppingservices or changingservice startupproperties Manage WindowsOperatin g

SystemServicesTh e KM prompts you to supply anadministrative account that includes theuser right
Log on as batch job

on thePATROL Agent

machine.For more information, see Supplying animpersonation account on page100.Viewing the Windowssecurity event logWindows

EventViewerYou can view event logs, other than thesecurity event log, but you cannotchange properties. Add the right
Manage Auditing And Security Log

to the agentaccount and the console connectionaccount .Managing Windowsevent logsWindows EventViewerThe KM prompts you to supply

anadministrative account that includes theuser right

Log on as batch job

on thePATROL Agent machine.For more information, see Supplying

animpersonation account on page100Viewing serverbasedreportsO S ReportsBlank Microsoft Excel spreadsheets a r e displayed.

Table17Conso le functionality that requires local admin rights (Part4of4)

K M F u n c t

i o n a l i t y M e n u c o m m a n d B e h a v i o r Configuring the PATROL KM for Microsoft Windows

OSChapter 3Loading and configuring PATROL for Microsoft Windows Servers101

Config

uring the PATR OL KM

for Micros oftWin dows

OS
The following section describes how to configure key features of the PATROL KM

forMicrosoft Windows OS. For more detailed step-bystep configuration instructions,see the PATROL KM for

Microsoft Windows OS online Help.For information about PATROL KM for Microsoft Windows OS configuration

tasks,see the referenced sections inTable18 on page101. For more information aboutaccessing KM menu

commands, see Accessing KM commands and InfoBoxes onpage214. Table18PATR OL KM for Microsoft

Windows OS configuration tasks

T k e c m d a s n o a P s M u m n a

g e configure Windows eventmonitoringFr om the PATROL Console, access the Windows Eventapplication and choose the KM menu

command ConfigureWindo ws Event Monitoring .103configure service monitoringFrom the PATROL Console, access the Services

applicationand choose the KM menu command Configure ServiceMonitorin g .114configure processmonitoring From the PATROL Console, access

the Processes applicationand choose the KM menu command Configure ManualProcess Monitoring .117configure built-in recoveryactionsFr

om the PATROL Console, access the host application andchoose the KM menu command Configure Recovery Actions .130create custom

parametersFrom the PATROL Console, access the CompositesColla pplication and choose the KM menu command CreateExpression s

.124v i e w e v e n t logsFrom the PATROL Console, access the Windows E v e n t application and choose the KM menu command

WindowsEvent Viewer .125configure blue screenmonitoringF rom the PATROL Console, access the NT_BSK applicationand choose the KM menu command

Configure Blue ScreenMonitorin g .126notify when disks are notpresentFrom the PATROL Console, access the NT_PHYSICAL_

DISK_CONTAIN ER and the NT_LOGICAL_DI SK_CONTAINER applications and choose the KM menu command Acknowledge .126 Configuring the

PATROL KM for Microsoft Windows OS102 BMC PATROL for Microsoft Windows Servers Getting Started

Enabling and disabling system monitori

ng
This section describes how to enable and disable the monitoring of basic serversystems.

By default, the monitoring for all discovered systems is enabled. To disableor enable monitoring, use the menu command shown

inTable19. The menucommand displays a dialog that allows you to exclude or include systems frommonitoring. For additional

instructions, click the

Help

button available on the dialog. Table19Enabli ng and disabling system

monitoring
SystemMoni tored by defaultTo enable or disable processorsall processors discovered on

thesystemFrom the PATROL Console, access the Processors applicationand choose the KM menu command EnableDisableProcessor Monitoring

.physicaldisksall physical disks discovered onthe systemFrom the PATROL Console, access the Physical Disksapplication and choose the KM menu

command Enable-Disable Physical Disk Monitoring .logicaldisksall logical disks discovered onthe systemFrom the PATROL Console, access the Logical

Disk application and choose the KM menu command Enable-Disable Logical Disk Monitoring .To monitor logical disks, PerfMon counters

must be enabled.For more information, see Monitoring logical or physicaldisk drives. pagefilesall pagefiles discovered on

t h e systemFrom the PATROL Console, access the Pagefiles applicationand choose the KM menu command Enable-Disable PagefileMonitori ng

.event logsall event logs listed in theregistryFrom the PATROL Console, access the Windows Eventsapplication and choose the KM menu

command Enable-Disable Windows Event Log Monitoring .To monitor the security event log, the PATROL Agent defaultaccount must have the

user right
Manage auditing and securitylog

.network protocolsall network protocols that areinstalled on the systemFrom the PATROL Console,

access the Network Protocolsapplicati on and choose the KM menu command Enable-Disable Protocol Monitoring .network

interfacesall network interfacesdiscover ed on the systemFrom the PATROL Console, access the Network Interfacesapplicati on and choose the

KM menu command Enable-Disable Network Interface Monitoring .p r i n t e r s a l l printers discovered on t h e systemFrom

the PATROL Console, access the Printers applicationand choose the KM menu command Enable-Disable PrinterMonitorin g . job objectsall

job objects discovered on thesystemFrom the PATROL Console, access the Job Objects applicationand choose the KM menu command Enable-Disable

JobObject Monitoring . Configuring the PATROL KM for Microsoft Windows OSChapter 3Loading and

configuring PATROL for Microsoft Windows Servers103

Monitorin g logical

or physical disk drives

If no data appears for the NT_LOGICAL_

DISK application class, run one of thefollowing diskperf commands from a command-line window to ensure that

theMicrosoft diskperf counters are enabled:

s

diskperf -yv

for Windows 2000 (restart required)

s

diskperf -y

for Windows Server 2003 (no restart required)For the platforms shown above, Microsoft requires that

you restart the system afterrunning the

diskperf

command. For more information, see Microsoft Knowledge

Basearticle Q262937, PRB: RegQueryValueE x() May Not Return Disk PerformanceCou nters.

Configuri

ng Windows events monitori ng

To monitor for specific Windows events, PATROL allows you to create event filters.Event filters specify the type of

events to monitor and how to monitor them. You cancreate event filters by specifying the types of events that you want to monitor basedon

the events source, ID, type, and content. However, before you can create a filterfor a Windows event, you must enable the monitoring

of that Windows event log. If the events you want to monitor have unregistered sources, but you can manually addthose events.Once you

have enabled the monitoring of the Windows Events, you can set up a filterto scan the event log for specific events. For example, you

might want to monitor theWinMgmt events. The event filter options provided using the
Configure

WindowsEvent Monitoring => Create Filter

or =>
Modify Filter

menu commands from aWindows Event instance

enable you to set up the monitoring of an event in manydifferent ways.You can remove a Windows event filter at any

time, and you can turn off an eventfilter.See the following topics for more information:
s

Enable and disable

monitoring of Windows events on page104

s

Display events with unregistered sources on

page104
s

Example: creating an event filter to monitor WinMgmt events on page105

s

Event filter options on page105

s

Turning off an event filter on page114 Configuring the PATROL KM for

Microsoft Windows OS104 BMC PATROL for Microsoft Windows Servers Getting Started

Enable

and disable monitorin g of Windows events

Before you can create an event filter, you must enable the monitoring of the Windowsevent log. By default, all Windows

event logs are monitored if they are registered inthe Windows registry at the following location:HKLM\ SYSTEM\Curre

ntControlSet\Se rvices\Eventlog To enable or disable Windows event log monitoring, access the Windows Eventsapplicatio

n and choose the KM menu command

Enable-Disable Windows Event LogMonitoring

Display

events with unregister ed sources

When using the

PATROL KM for Microsoft Windows OS graphical interface to createan event filter, the events that you choose to monitor must

have registered eventsources. Unregistered sources do not appear in the interface. To work around thisproblem, follow these

steps to display an unregistered source in the interface so that itcan be selected.

1
Using the Configure

Windows Event Log Monitoring => Create Filter menucommand, create a new filter. In the Create Filter dialog box, select the

FilterProperty Source, and deselect the option to Automatically include new sources . Thissets the following agent

configuration variable to 0:
/PSX__P4WinSrv s/PWK__PKMfor MSWinOS_confi g/ /EventLogMonito ring/
eventlog

/EventFilters/
filtername/

IncludeAllSource s

2
Using PATROL Configuration Manager or the wpconfig

utility, manually add theunregistered event source to the following agent configuration variable.
/PSX__P4WinSrv

s/PWK__PKMfor MSWinOS_confi g/ /EventLogMonito ring/

eventlog

/EventFilters/
filtername/

SourceList/list

3
Apply the change to the PATROL Agent. Configuring the PATROL KM for Microsoft Windows OSChapter

3Loading and configuring PATROL for Microsoft Windows Servers105

Example: creating

an event filter to monitor WinMgmt events

Assume that you

want to create an event filter that monitors for the following events:You want to be notified immediately when these

particular events occur. However,you want to be notified only when the event is related to the
perfproc.dll

performancelibr

ary, not any other performance counter libraries.In addition, you do not want to be flooded with events, so if

these events aregenerated multiple times within a short period, you want to be notified only once.Finally, if these events are

detected, you want PATROL to remain in alarm until thealarm is acknowledged by an operator.Using the Event filter

options presented in the

Configuring Windows Event Monitoring=> Create Filter

dialog boxes, you can create a filter with all of

the properties proposedin this example.

Event filter options

When you

choose the
Configure Windows Event Monitoring => Create Filter

or =>
Modify Filter

menu commands from a Windows

Event instance, you are presentedwith several filter options.Table21 on page106provide s you with the name,descriptio

n, and associated configuration variables for the event filter options youcan select. Table20Event filter events:examp

le
Eventt y p e E v e nt s o u r c e Eventc ategoryEventI D Description ErrorWinMg mtNone37W MI ADAP

was unable to load t h e perfproc.dll performance library due to anunknown problem within the library: 0x0E r r o r W i n MgmtNone41

ADAP was unable to process the perfproc.dllp erformance library due to a time violation inthe collect functionE r r o r W inMgmtNone

61WMI ADAP was unable to process t h e perfproc.dll performance library due to a timeviolation in the open function Configuring the

PATROL KM for Microsoft Windows OS106 BMC PATROL for Microsoft Windows Servers Getting Started

Table21Event

filter options (Part1of8)

O p t i o n D e s c r i p t i o n Configurationvar iables Filter name A unique name that represents the

event filter.If you change the filter name, you will lose the historical datastored under the old name.The filter name must contain fewer than 127 characters.child_li

stFor moreinformation, see Using the child_listvariable onpage271. Description A description of the event filter.You can change the

description at any time.FilterDescript ion Report the numberof events.... If you select this option, PATROL monitors the number of events

that match the filter criteria during each collection cycle.Depending on which event types the filter monitors, thefollowing parameters are

used to report this data:

s

ELMError
s

ELMWarning
s

ELMInformation
s

ELMStatus
s

ELMSuccessAudit
s

ELMFailureAudit
s

ELMOtherTypesE ventReport Notify PATROLimmedi ately.... If you select this option, PATROL immediately

updates theappropriate parameter when an event matches the filter criteria.Dependin g on which event types the filter monitors, thefollowing

parameters are displayed in an alarm state when anevent matches the filter:
s

ELMErrorNotifica tion
s

ELMFailureAudit Notification

ELMNotification (This parameter is active only when youhave selected both of the following options: Notifyimmediatel y
and

consolidate event types. For moreinformation, see the description in Event Type tab section of this table.)
s

ELMWarningNotif

icationFor more information about these parameters, see the PATROLKM for Microsoft Windows OS online Help.NA Source filter

properties Source Registered sources for which events can be monitoredNA Select/Deselectso urce(s) for

thisfilter applications running on the server that PATROL is currentlymonitori ngSourceList/list Configuring the PATROL KM for

Microsoft Windows OSChapter 3Loading and configuring PATROL for Microsoft Windows Servers107

AutomaticallyInc lude NewSources If you select this option, this event filter automatically monitorsany new applications that are added to the systemIncludeAllS

ources Disable CaseSensitivity If you select this option, the event filter makes filter comparisonsin a case-independent mannerFilterDisab leCase

Event Type filter properties Select Event Typesto monitor the Windows event types monitored by this event filterEventType

Consolidate eventtypes... If you select this option, events of different types (Warning,Informa tion, and Error, for example) are reported using oneparameter:

ELMStatus (or ELMNotification if you have alsochosen to be notified immediately when the event occurs).If you want to have separate

parameters for each event type thatcan alarm independently, deselect this option.Consolidat eEventTypes Event ID filter properties

Enter a WindowsEvent ID or a rangeof IDs The Microsoft Windows event IDs that you want to monitorwith this filter.To specify a range of event IDs,

separate the beginning andending of the range with a dash. For example, to monitor events100 through 200, enter 100200.EventIdList/li st

Include allWindows event IDsin the list specifies that all of the Windows event IDs in the list aremonitored by the event filterIncludeAllEv

entIds Include allWindows event IDsexcept those in thelist specifies that all of the Windows event IDs except those in thelist are monitored by the

event filterSelect this option when there are certain event IDs that you arenot interested in monitoring and you want to exclude them fromthe event filter.IncludeAllE

ventIds Event Handling filter properties Annotate graphparameter... annotates the PATROL parameter graphs associated with

thisevent filter with information about the eventYou can display the annotations by placing the cursor over thegraph data points.Annotation

Table21Event filter options (Part2of8)

O p t i o n D e s c r i p t i o n Configurationvar iables
scribd. scribd. scribd. scribd. scribd. scribd. scribd. scribd. scribd. scribd. scribd. scribd. scribd. scribd. scribd. scribd. scribd. scribd. scribd. scribd.