QMXom07 InstallGuide 400505

Quest Management Extensions
Operations Manager 2007 Edition
Installation Guide
For Windows 32-bit and 64-bit systems
Unleash the Power of System Center Operations Manager 2007 for

Complex, Heterogeneous Environments
QMX – Operations Manager 2007 Install Guide
© 2009 Quest Software, Inc. ALL RIGHTS RESERVED.

This guide contains proprietary information protected by copyright. The software described in this guide is furnished
under a software license or nondisclosure agreement. This software may be used or copied only in accordance with
the terms of the applicable agreement. No part of this guide may be reproduced or transmitted in any form or by
any means, electronic or mechanical, including photocopying and recording for any purpose other than the
purchaser's personal use without the written permission of Quest Software, Inc.
If you have any questions regarding your potential use of this material, contact:
Quest Software World Headquarters
LEGAL Dept
5 Polaris Way
Aliso Viejo, CA 92656 USA
www.quest.com
email: legal@quest.com
Refer to our Web site for regional and international office information.
TRADEMARKS
Quest, Quest Software, the Quest Software logo, Aelita, Benchmark Factory, Big Brother, DataFactory,
DeployDirector, ERDisk, Fastlane, Final, Foglight, Funnel Web, I/Watch, Imceda, InLook, InTrust, IT Dad, JClass,
JProbe, LeccoTech, LiveReorg, NBSpool, NetBase, PerformaSure, PL/Vision, Quest Central, RAPS, SharePlex,
Sitraka, SmartAlarm, Speed Change Manager, Speed Coefficient, Spotlight, SQL Firewall, SQL Impact, SQL
LiteSpeed, SQL Navigator, SQLab, SQLab Tuner, SQLab Xpert, SQLGuardian, SQLProtector, SQL Watch, Stat, Stat!,
Toad, T.O.A.D., Tag and Follow, Vintela, Virtual DBA, and XRT are trademarks and registered trademarks of Quest
Software, Inc. in the United States of America and other countries. All other trademarks and registered trademarks
used in this guide are property of their respective owners.
Disclaimer
The information in this document is provided in connection with Quest products. No license, express or implied, by
estoppel or otherwise, to any intellectual property right is granted by this document or in connection with the sale
of Quest products. EXCEPT AS SET FORTH IN QUEST'S TERMS AND CONDITIONS AS SPECIFIED IN THE LICENSE
AGREEMENT FOR THIS PRODUCT, QUEST ASSUMES NO LIABILITY WHATSOEVER AND DISCLAIMS ANY EXPRESS,
IMPLIED OR STATUTORY WARRANTY RELATING TO ITS PRODUCTS INCLUDING, BUT NOT LIMITED TO, THE
IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NON-INFRINGEMENT. IN
NO EVENT SHALL QUEST BE LIABLE FOR ANY DIRECT, INDIRECT, CONSEQUENTIAL, PUNITIVE, SPECIAL OR
INCIDENTAL DAMAGES (INCLUDING, WITHOUT LIMITATION, DAMAGES FOR LOSS OF PROFITS, BUSINESS
INTERRUPTION OR LOSS OF INFORMATION) ARISING OUT OF THE USE OR INABILITY TO USE THIS DOCUMENT,
EVEN IF QUEST HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. Quest makes no representations or
warranties with respect to the accuracy or completeness of the contents of this document and reserves the right to
make changes to specifications and product descriptions at any time without notice. Quest does not make any
commitment to update the information contained in this document.
®
Quest Management Extensions - Operations Manager 2007 Edition
Installation Guide
Quest QMX Base Framework Version: 4.0.0.505
Updated – August 2009
Page 2
Contents
About this Guide ........................................................................................................ 6
Conventions ........................................................................................................... 6
Product Name Change .......................................................................................... 6
About Quest System Center Solutions Group .............................................................. 6
About Quest Software, Inc. ...................................................................................... 7
Contacting Quest Software, Inc. ................................................................................ 7
Join the Community ............................................................................................. 7
Introducing QMX - Operations Manager 2007 ................................................................. 8
What is an Extension?.............................................................................................. 8
What is an Agentless Solution? ................................................................................. 8
Quest Agentless Solutions Are Open Source ............................................................... 9
How Agentless Extensions Work ................................................................................ 9
Agent-Based Solutions ............................................................................................. 9
Architectural Overview ........................................................................................... 10
About Your Trial Version......................................................................................... 11
Licensing QMX for Production Use ........................................................................ 12
Estimating Hardware Requirements ......................................................................... 12
Rule of Thumb ................................................................................................... 12
Test Results ...................................................................................................... 13
Running Large Scale ........................................................................................... 13
System Software Requirements .............................................................................. 14
Installing the Windows SNMP Services .................................................................. 15
Install the Operations Manager Components ................................................................ 17
Install the MS Operations Manager Console .............................................................. 17
Install the MS Operations Manager Agent ................................................................. 19
Install the QMX Components...................................................................................... 21
Install the Quest Base Framework ........................................................................... 21
Import the Quest Management Pack ........................................................................ 23
Install Extensions .................................................................................................. 27
Import Child Management Packs ............................................................................. 32
Configure OpsMgr SDK Communications ..................................................................... 35
Identify the SDK Service User .............................................................................. 35

Create a Domain User Group ............................................................................... 37
Add the SDK Service User to the Domain User Group ............................................. 40
Associate the Domain User Group ........................................................................ 42
Configuring Global Variables ................................................................................ 46
Configure the Extension ............................................................................................ 51
Specifying Hosts to Monitor .................................................................................... 51
Specify Host Information Manually ....................................................................... 51
Configuring the Fields on the _Hosts Tab ................................................................. 52
_Hosts Tab Tips ................................................................................................. 54
Validate the Extensions ............................................................................................. 55
Validate Target Machine Accessibility ....................................................................... 55
Starting an Extension ............................................................................................ 56
Monitoring Alerts ................................................................................................... 58
Monitoring Performance ......................................................................................... 61
Advanced System Administration ............................................................................... 70
Encrypt UserIDs and Passwords .............................................................................. 70
Enable Automatic Monitoring .................................................................................. 71
Cloning Extensions ................................................................................................ 72
Auto Discover Hosts .............................................................................................. 74
Auto Discover CLI-based Devices ......................................................................... 74
Auto Discover SNMP Devices ............................................................................... 77
Logging Security Events into ACS ............................................................................ 78
Using the Virtual Agent Jobs Tab ............................................................................. 79
Failover ............................................................................................................ 79
Troubleshooting ....................................................................................................... 83
Basic Troubleshooting Tips ..................................................................................... 83
Troubleshooting Checklist....................................................................................... 85
Alerts Are Missing .............................................................................................. 86
Performance Records are Missing ......................................................................... 87
SNMP Issues...................................................................................................... 87
Command Line Interface Issues ........................................................................... 90
Checking the Quest QMX Base Framework Version .................................................... 90
Upgrading the Quest QMX Base Framework .............................................................. 91
Page 4
Upgrading Extensions ............................................................................................ 94

Migrating From One Server to Another ..................................................................... 95
Gathering Diagnostic Information ............................................................................ 96
WMI Tuning for Large Scale Implementations ........................................................... 98
Getting Support ..................................................................................................... 101
Contacting Quest Support .................................................................................... 101
Joining the Community ........................................................................................ 101
Appendix A – QMX 64-bit Instructions for SNMP Extensions ......................................... 102
Converting from MS-Access to MS-SQL .................................................................. 102
Converting the database Using SQL .................................................................... 103
Converting the database Using SQL 2005 Express ................................................ 112
Converting the Database Using Microsoft Access .................................................. 116
Setting up SQL Security for QMX access ................................................................. 123
Using DOS to Set Security Permissions ............................................................... 123
Using SQL Server Management Studio to Set Security Permissions ......................... 126
Giving the Database SQL Server Access Rights ....................................................... 128
Appendix B - QMX on a Management Server .............................................................. 131
Authentication Setup Scenario A ........................................................................... 132
Create a Domain Computer Group ...................................................................... 132
Add Computers to the Domain Computer Group ................................................... 134
Associate the Domain Computer Group ............................................................... 136
Configuring Global Variables for Scenario A ......................................................... 139
Authentication Setup Scenario B ........................................................................... 142
Identify the SDK Service User ............................................................................ 142
Create a Domain User Group ............................................................................. 144
Add the SDK Service User to the Domain User Group ........................................... 147
Associate the Domain User Group ...................................................................... 149
Configuring Global Variables .............................................................................. 152
Page 5
About this Guide

IT professionals can now leverage their preferred tool for monitoring and proactive issue
resolution of Windows and non-Windows systems alike. Quest® Management Extensions -
Operations Manager 2007 Edition (formerly eXc Software eXctenders) extends the power of
Microsoft System Center Operations Manager 2007 (System Center Operations Manager
2007) to more than 240 non-Windows operating systems, applications, network
components, storage, security, and more.
This guide is intended for IT administrators who will be installing Quest ® Management
Extensions - Operations Manager 2007 Edition (QMX - Operations Manager 2007) for the
first time. By following the instructions presented in this guide, an IT administrator will be
ready to monitor non-Windows systems, devices, and applications from within the
Operations Manager Console.
Conventions
Quest Software, Inc. products support a number of different implementations of UNIX-like
operating systems. The terms ―Unix‖ or ―non-Windows‖ throughout this document is used to
encompass all UNIX and Linux operating systems. (See http://management-
extensions.org/kbcategory.jspa?categoryID=221 for a list of all platforms supported by QMX
- Operations Manager 2007.)
Product Name Change

Earlier versions of QMX - Operations Manager 2007 were developed using the terms MOM
and SCOM instead of Microsoft Operations Manager 2007 and System Center Operations
Manager 2007. Thus, you might see these terms in the code or directory paths.
Quest Software, Inc. purchased eXc Software and changed the name of this product from
eXc Software nonWindows MOM eXctenders to Quest® Management Extensions - Operations
Manager 2007 Edition (QMX - Operations Manager 2007). At that time, “Virtual Agents”
were re-named, ―Extensions”. While this guide uses the term Extension instead of Virtual
Agent, during the transition, you will see the usage of ―eXc Software‖ and ―Virtual Agents‖
in the user interface and in file directory paths.
About Quest System Center Solutions Group

With a comprehensive set of solutions that extend the powerful capabilities of the Microsoft
System Center family to heterogeneous environments, Quest Software enables IT
professionals to leverage System Center as the single, end-to-end platform for managing
physical and virtual IT environments across data centers, desktops and devices. For more
information on Quest‘s System Center Solutions group, please visit:
http://www.quest.com/system-center/
Page 6
About Quest Software, Inc.

Quest Software, Inc., a leading enterprise systems management vendor, delivers innovative
products that help organizations get more performance and productivity from their
applications, databases, Windows infrastructure and virtual environments. Quest also
provides customers with client management through its ScriptLogic subsidiary and server
virtualization management through its Vizioncore subsidiary. Through a deep expertise in IT
operations and a continued focus on what works best, Quest helps more than 100,000
customers worldwide meet higher expectations for enterprise IT. Quest‘s System Center
solutions enable the Microsoft System Center platform to serve as the comprehensive
systems management platform for organizations managing heterogeneous
environments. Together, an integrated platform improves IT productivity, increases return
on IT investments, and ensures compliance and service levels to help drive business
profitability. Visit Quest‘s System Center solutions at www.quest.com/system-center. Quest
Software can be found in offices around the globe and at www.quest.com.
Contacting Quest Software, Inc.

Phone 949.754.8000 (United States and Canada)
Email info@quest.com
Mail Quest Software, Inc.

World Headquarters
5 Polaris Way
Aliso Viejo, CA 92656
USA
Web site www.quest.com

SupportLink www.quest.com/support
Email to support@quest.com
Please refer to our Web site for regional and international office information.
Join the Community

Get the latest product information, find helpful resources, and join a discussion with the
QMX - Operations Manager 2007 team and other community members at:
http://www.management-extensions.org
Page 7
Introducing QMX - Operations Manager 2007

QMX - Operations Manager 2007 is the Quest Software, Inc. solution that extends the power
of Microsoft System Center Operations Manager 2007 to non-Windows systems, devices,
and applications using agentless extensions.
QMX supports other products within the Microsoft System Center product suite, including
Configuration Manager, Virtual Machine Manager and Data Protection Manager. In addition,
QMX also provides solutions for the Microsoft Enterprise Single-Signon product.
What is an Extension?
QMX Extensions are ―virtual agents‖ that extend the functionality of System Center
Operations Manager 2007 to non-Windows resources using an ―agentless‖ technology. An
Extension is made up of VBScript(s) and/or JScript(s) that call the Quest QMX Base
Framework APIs (most of which are exposed as ActiveX/COM objects) to perform such
actions as: SSH to a device, receive SNMP Traps, talk to the Microsoft MCF, and so forth.
QMX ships with a Configuration Tool. Within the QMX Configuration Tool, Extensions contain
configuration tabs. You must customize the fields in the configuration tabs associated with
the Extension. There are different types of Extensions. The most common Extensions use
the Command Line Interface (CLI) or Simple Network Management Protocol (SNMP). CLI
Extensions use SSH or Telnet. There are also Web services and API Extensions. Which
protocol gets used in an Extension is defined by the system, device, or application it is
monitoring.
While great effort has gone into simplifying how to configure each Extension, many
Extensions require background knowledge of the system, device, or application you want to
monitor.
If you do not understand how the system, device, or application interacts

with the Extension using SNMP, CLI, Web service, and so forth, consult with
a domain expert responsible for the system, device, or application. Quest
offers a community site where other users offer information, advice and
knowledge about Extensions. (See Join the Community) Or, contact the QMX
- Operations Manager 2007 support team at http://support.quest.com for
help.
What is an Agentless Solution?

An ―agentless‖ solution means that no software resides on the target platform like agent-
based solutions. Thus, to install them, you are not required to distribute any software to
your client machines, except in the case of the mainframe solutions (see the Note below).
And, because the Quest ―agentless‖ solutions are 100% Windows code and scripts, you can
easily modify them with basic Windows-based VBScript and/or Jscript experience.
Page 8
Note: IBM z/OS and IBM AS400 do not use agentless technology. When installing these
Extensions, you must distribute additional software to these systems.
Quest Agentless Solutions Are Open Source

The QMX Extensions are open, accessible, and extendable using Microsoft scripting
technologies. Quest is fostering an open-source community around Extensions. For more
information visit: http://www.management-extensions.org
How Agentless Extensions Work

Think of these solutions as programmed human beings that follow orders, like a robot.
Extensions (that is, the script code) can log in to a system, type commands, read and
analyze responses, and take actions. They have built-in processes to create WMI events and
create performance records used by System Center Operations Manager and other
programs. The rest of the job is up to System Center Operations Manager 2007. Extensions
leverage a common software component called the Quest Base Framework.
The Quest QMX Base Framework provides services such as fault-tolerance, scheduling, task
management, security services, and so forth to all of the Extension solutions regardless of
the hardware platform. Extensions rely on the services and functions provided by this
software component.
The Quest solutions support the two most common agentless protocols: SSH/Telnet and
SNMP version 1/version 2: GET, SET, and the receipt of Traps (SNMP v1) and Notification-
Types (SNMP v2). (Note: QMX does not currently support SNMP v3.) Many Extensions also
use other industry-standard mechanisms such as web services, database calls, and native
APIs.
At a minimum, Quest solutions can:

poll intermittently to ensure there is connectivity between the computer where the
Quest solution resides and the target platform
convert Extension data into WMI format which allows QMX - Operations Manager
2007 to present the information as System Center Operations Manager 2007 alerts
create alerts and performance records from Extension data.

perform automated tasks on the target system.
QMX - Operations Manager 2007 is unique in that it does not require SNMP MIB compiles,
MOFs, namespace instantiation for the device type, or application, nor user-built scripts to
―tear apart‖ the inbound Extension data. The type of Extension Quest builds depends on the
capability of the device, application, operating system, solution requirements, and so forth.
Agent-Based Solutions
Quest also provides two agent-based solutions.
AS400 Extension for MOM/Operations Manager 2007
Page 9
MVS/ZOS Extension for MOM/Operations Manager 2007
Architectural Overview
QMX - Operations Manager 2007 uses a software architecture model similar to the Microsoft
.Net run-time and Java virtual machine architectures. This is aModel-view-controller (MVC)
architectural design pattern. In QMX - Operations Manager 2007, the Model equates to the
Extensions, the View is the Operations Console and the Controller is the Quest Base
Framework.
You must not run QMX - Operations Manager 2007 on a computer that is acting as a proxy
for (Microsoft) agentless Windows monitoring. Quest recommends that you run QMX -
Operations Manager 2007 on an agent-managed computer, as shown in the architecture
diagram below:
Page 10
In a test environment or small production environment, you can run QMX -

Operations Manager 2007 on a Root Management Server (RMS) which is
easier to set up because you do not need to change any of System Center
Operations Manager 2007 global variables. However, this installation guide
assumes you are NOT installing to an Operations Manager Management
Server. Rather, it assumes you are installing QMX on an Operations Manager
agent-based Windows computer (that is, a Windows computer running an
Operations Manager agent), which is the recommended installation for a
production environment. If you are installing to an Operations Manager
Management Server, please read Appendix B - QMX on a Management
Server which explains the options for a proof-of-concept installation.
Running QMX - Operations Manager 2007 on an OpsMgr agent-managed computer allows

for better load balancing of the solution and does not require you to run any software on
Management Servers which carry most of the workload for System Center Operations
Manager 2007. This allows for monitoring hundreds (or even thousands) of non-Windows
systems, devices, or applications with QMX
About Your Trial Version

To evaluate QMX - Operations Manager 2007, download the free trial version of the product.
The Trial version does not require a product activation key. By default, you have 30 days to
use it before the trial expires. The trial software only allows you to run Extensions against a
maximum of two DNS names simultaneously. If you want to monitor additional DNS names
or extend your trial period, you can ask Quest for an extended trial key by contacting your
Account Manager or go to: http://www.management-
extensions.org/thread.jspa?threadID=6576&tstart=0 , or email your request to:
SystemCenterSales@Quest.com .
You do not need to contact Quest for the 30-day, two-node trial. The trial period starts
automatically from the day you start using the software — no trial key is required.
During the trial period, you may configure multiple DNS names for your non-Windows
systems, but your trial version of QMX - Operations Manager 2007 will display an NT Event
Log message and will block additional Extensions from starting if you attempt to access
more DNS names than your trial license permits.
During the trial period you might see one or more of the following alerts in the Operations
Console:
SoftwareLicense002: Running in trial mode.
SoftwareLicense003: Running in trial mode (about to expire).
SoftwareLicense004: Microsoft perpetual license. If you are not Microsoft, you are
running this software illegally!
SoftwareLicense005: Clock appears to have been set backwards.
SoftwareLicense006: Trial period has expired.
Page 11
SoftwareLicense007: Software license has expired.
SoftwareLicense008: Error occurred processing the Software license.

SoftwareLicense009: Maximum connections reached. If this is a trial, you only get
two simultaneous connections.
Licensing QMX for Production Use

To purchase the product for production use, contact your Quest Software Sales
representative or email your request to: SystemCenterSales@Quest.com. Once you have
purchased the product, you will receive an email from License@Quest.com with instructions
on obtaining your permanent license key.
You do not need to uninstall the trial version. You only need to obtain and apply a
permanent license key to your existing installation.
Estimating Hardware Requirements

These specifications are typical for a dual-quad Agent box dedicated to QMX solutions:
Typical System Specifications
Operating System 64-bit
CPU
Memory1 32 Gigs
Jobs2 135
cscripts3
250 CLI
(QMX Extensions)
Run-time4 600 seconds
Use the above information to extrapolate the approximate system size for your
environment. Utilization scales linearly, for example if you are running only ¼ the number
of cscripts, you will need only ¼ the memory and the CPU.
Rule of Thumb
It is not enough for you to estimate how many QMX Extensions you will be running; you
must also know the type (such as CLI or SNMP) and the number of ―jobs‖ that are selected
to run by default in the __VirtualAgentJobs tab to determine the number (and frequency) of
cscripts. CLI-based solutions are more CPU intensive than SNMP-based solutions. Because
SNMP-based solutions mostly use memory and very little CPU, allocate around 17,000K of
memory per cscript.
Notes:
1
Memory: Monitoring logs use Memory but little CPU.
Page 12
2
Jobs: ―Time-zero‖ jobs (that is, jobs with a zero in the uint32RunEverXSeconds column of
the QMX Configuration Tool‘s __VirtualAgentJobs) use about 17,000K memory per cscript.
(Look in the __VirtualAgentJobs tab to see the number of jobs selected to run.)
3
cscripts: Each job listed in the __VirtualAgentJobs tab requires a cscript to run. Add one
to the total count of cscripts running for each job that has Run selected. For example, if a
Job name of ALL exists with Run selected for it, add one to the total cscript count. For CLI
solutions add one for the ―watchdog‖ job, a hidden job that is not listed in the
__ViruatAgentJobs tab. If the Logs job exists in the __VirtualAgentJobs tab and is selected,
add one for each log you intend to monitor.
Quest does not recommend running a load of more than ten cscripts on a
Management Server unless you are running a small trial or Proof of Concept.
In that scenario, the computer is not dedicated to QMX and Operations
Manager will utilize resources that would otherwise be available to QMX.
4
Run-time: If you decrease the run time to 300 seconds, the load will double.
Test Results
These were the results when running a system as described in the above table in a test
environment:
An average of 300 cscripts ran simultaneously. Many of these were LOGS jobs which
use Memory but almost no CPU.
The average CPU utilization was about 25%. The CPU did peak at 100%, but this was
rare and very infrequent which indicates that the CPU was the proper size for the
load.
Memory utilization hovered around 20% (6.5 Gigs).
Running Large Scale

You can add more load to your environment; that is, additional Extensions, logs, and so
forth. Using the ―Typical System Specifications‖ table in this section along with the
calculations, it would appear that you can run 1,200 cscripts of the types mentioned – a
majority of which are monitor log jobs. If you are running nodes that produce SNMP TRAPS,
you can reduce memory utilization by about 17000K per node by implementing our Large
Scale SNMP Solution. For example, in Cisco the job that waits for SNMP TRAPS is the
SNMPTRAP job; in older solutions it is referred to as the VIRTUALAGENT job. For more
information about the Quest Large Scale SNMP Solution see at http://management-
extensions.org/entry.jspa?externalID=100335&categoryID=251 for further information
about this solution).
WMI may not be capable of handling a load of 1,200. Quest has not tested
this exact scenario in a customer environment. In this example the CPU
would be pegged at 100%, which is not a good idea; memory would be at
Page 13
26.5 Gigs (83%) which is not a problem.
Quest does not recommend running QMX solutions in a Virtual environment

with less than two CPUs. If you use a single CPU, your computer may lock up
and your mouse could become unusable.
If you are running QMX on an Agent box and your numbers vary widely from the above, the
Quest development team would like to hear from you. Please open a ticket with Quest
Support (see Contacting Quest Support). Specify the CPU and Memory setup as well as the
operating system (32- or 64-bit) you are running. You can help yourself and all other
customers in the community (see Join the Community).
System Software Requirements

The following are the software requirements necessary to run QMX - Operations Manager
2007:
Microsoft Windows Server 2003 with SP2, Microsoft Windows Server 2008,
Windows XP or Windows Vista with the following Microsoft System Center
Operations Manager 2007 components installed:
o Operations Manager Console (See Install the MS Operations Manager

Console.)
o Operations Manager 2007 Agent, that is, the Health Service in the RTM
and SP1 versions and the System Center Data Access for R2 (See Install the
MS Operations Manager Agent.)
o Windows cscript engine version 5.7
Note: You cannot use the QMX feature for System Center Operations Manager
2007 Audit and Collection Services (ACS) on a Windows XP or Windows Vista
system.
To use an Extension which utilizes the Simple Network Management Protocol (SNMP)
protocol, your system needs:
Microsoft SNMP WMI Event Provider version 1.5. Install it from your Windows
Operating System CD or go to: http://msdn.microsoft.com/en-
us/library/aa393621(VS.85).aspx for step-by-step instructions.
Microsoft SNMP service and SNMP Trap Service. (See Installing the Windows
SNMP Services.)
Microsoft Database
o Microsoft Access for 32-bit systems only (or MS-Access Run Time which you
can download from: http://www.management-
extensions.org/entry.jspa?categoryID=251&externalID=2003.)
Page 14
o Microsoft SQL1 for 32-bit systems (optional) or 64-bit systems (required)
Note: You do not need MS-Access if you convert the database to Microsoft SQL. For
32-bit systems, MS-Access is the default and SQL is optional. 64-bit systems do not
support MS-Access, thus SQL is required.
If you are installing the Quest QMX Base Framework into a 64-bit Windows
Operating System and are planning to use any SNMP QMX Extension, please
follow the instructions in Appendix A – QMX 64-bit Instructions for SNMP
Extensions then return back to this section of the Installation Guide.
Installing the Windows SNMP Services

If you plan to run SNMP-based Extensions, you must ensure that you have the Microsoft
WMI SNMP Event Provider, the SNMP Service, and the SNMP Trap Service on the Windows
computer where you plan to install the QMX - Operations Manager 2007 solutions. For more
information about installing SNMP Services, see http://support.microsoft.com/kb/324263.
To install the SNMP components
1. From Start menu, navigate to Control Panel | Add/Remove Programs.

2. Click Add/Remove Windows Components in left navigation pane.
3. In the Windows Components Wizard, scroll down and select Management and
Monitoring Tools and click Details.
4. In the Management and Monitoring Tools dialog, select the Simple Network
Management Protocol (SNMP) and the WMI SNMP Provider and click OK.
Note: Within the ―Management and Monitoring Tools installation list‖, you will find
the Microsoft ―Network Monitor‖ (NetMon) program. Quest recommends using
NetMon during the SNMP test phase or for troubleshooting SNMP issues. For more
information about NetMon go to:
http://windowsitpro.com/article/articleid/96282/enabling-netmon-in-windows-
2003.html.
5. Click Next.
To customize the SNMP Service
1. Right-click your My Computer icon on your desktop and select Manage.

2. Navigate to Computer Management | Services and Applications | Services.
3. Double-click the SNMP Service.
4. Customize the Security and Traps tabs as necessary for your environment.
To start the SNMP Services
5. Right-click your My Computer icon on your desktop and select Manage.
1
For other potential options please refer to Appendix A
Page 15
6. Navigate to Computer Management | Services and Applications | Services.
7. Locate both the SNMP Service and the SNMP Trap Service and verify that they
both have a Startup Type of Automatic.
8. Restart (or Start) both services.
Page 16
Install the Operations Manager Components

Install the MS Operations Manager Console
Install the MS Operations Manager Agent
Install the MS Operations Manager Console

Before you attempt to install and deploy QMX - Operations Manager 2007, make sure that
your System Center Operations Manager 2007 environment is configured properly. The
Operations Console user interface components provide QMX - Operations Manager 2007
with the System Center Operations Manager 2007 SDK assemblies it needs.
To install System Center Operations Manager 2007 Operations Console
1. On the computer where you will run QMX - Operations Manager 2007, navigate to
the root of the System Center Operations Manager 2007 installation image or CD:
2. Double-click SetupOM.exe to start the Installation Wizard.
Page 17
3. Click Install Operations Manager 2007.
The wizard will lead you through the steps to install System Center Operations
Manager 2007 on your computer.
Page 18
4. At the Custom Setup dialog it asks you to select which System Center Operations
Manager 2007 components you want to install, select the User Interfaces.
Note: You can install other components, but you must at least install the Operations
Console user interface components.
Install the MS Operations Manager Agent

If you plan to run QMX - Operations Manager 2007 on a computer that is not a System
Center Operations Manager 2007 Management Server, you must install the System Center
Operations Manager 2007 Agent. QMX - Operations Manager 2007 needs the System Center
Operations Manager 2007 Agent to discover QMX - Operations Manager 2007 proxy
computer(s) for the non-Windows systems and devices you want to monitor.
Note: If you have installed QMX onto the OpsMgr Root Management Server or an OpsMgr
Management Server, please skip this section since the agent is automatically installed on
OpsMgr Management Servers.
Page 19
To install the System Center Operations Manager 2007 Agent
1. From the System Center Operations Manager 2007 Setup wizard Start page, click
Install Operations Manager 2007 Agent.
The wizard will lead you through the steps to install System Center Operations
Manager 2007 Agent on your computer.
2. Ensure that this computer shows up in the Operations Console under

Administration | Device Management | Agent Managed in a healthy state. If
you do not see the computer in Agent Managed, see if it is in Pending
Management. If it is, right-click the agent and select Approve the agent
deployment and await a healthy state.
Verify that all System Center Operations Manager 2007 components in your
system are properly configured and functioning correctly before you
introduce QMX - Operations Manager 2007 to your environment.
Page 20
Install the QMX Components

Install the Quest Base Framework
Import the Quest Management Pack

Install Extensions
Import Child Management Packs
Install the Quest Base Framework

The Quest QMX Base Framework provides services such as fault-tolerance, scheduling, task
management, security services, and so forth to all of the Extension solutions regardless of
the hardware platform. Extensions rely on the services and functions provided by this
software component. Think of it as the SDK or Application Programming Interface (API) that
allows the solutions to read responses, issue commands, and so forth from and to your non-
Windows environment.
To install the Quest Base Framework
1. Go to the Trial Download: Quest Management Extensions - Operations Manager site

at: http://www.quest.com/quest-management-xtensions-operations-
manager/software-downloads.aspx
2. Complete the registration (first-time users, only).
3. Complete the survey and click Submit.
4. From the ―Others‖ tab on this web page, select any other documents you need.
5. From the ―Latest Version‖ table, select the non-Windows base framework for System
Center Operations Manager 2007 that is appropriate for your environment. You have
4 choices to choose from:
a. Quest QMX Base Framework for Windows 2003/XP – 32bit
b. Quest QMX Base Framework for Windows 2003/XP – 64bit
c. Quest QMX Base Framework for Windows 2008/Vista – 32bit

d. Quest QMX Base Framework for Windows 2008/Vista – 64bit
6. Click Save to download the .zip file to a location of your choice.
7. Extract all the files from the .zip.
8. Double-click the .exe file to start the Setup wizard.
Page 21
9. Click Install at the Quest Setup dialog to install the Runtime Libraries which the
Base Framework depends.
The Wizard leads you through the process of installing the Quest Base Framework.
10. Read and accept the Software License Agreement.
11. Select the Run the prerequisite checker option to ensure your system is ready.
12. Install the Base Framework to your systems hard drive (the default folder is
C:\Program Files\eXc Software\WMI Providers\nonWindows\
If you install the software into the default folder on the C:\ drive you will not
have to modify the Operations Manager 2007 management pack tasks later
in the installation process.
13. Click Close and review the QMX Prerequisite Checker Results (this will appear in
your default web browser after the installation completes. Be patient, sometimes it
may take up to a minute before the browser opens) for the Common Components,
QMX Components, and the MOM/OpsMgr Components.
14. If you are installing the 64-bit Quest Base Framework, please perform the sub-steps
below to make registry changes; if you are installing the 32-bit Base Framework,
skip this next step entirely.
To make registry changes for a 64bit QMX installation:

1. From the Start menu, select Run, enter ―regedit‖ in the Open box and click OK.
2. In the registry tree, expand HKEY_LOCAL_MACHINE. Check if there is already a

Key named Wow6432Node. If there is already a key with this name, skip to step 5.
3. Right-click SOFTWARE and select New | Key.
4. Enter ―Wow6432Node‖ as the New Key name and click Enter.
5. Right-click Wow6432Node and select New | Key.
Page 22
6. Enter ―eXc Software‖ as the New Key name and click Enter.
Note: There is a space between ―eXc‖ and ―Software‖.
7. Right-click eXc Software and select New | Key.
8. Enter ―nonWindows_WMI_Providers‖ as the New Key name and click Enter.

9. Right-click nonWindows_WMI_Providers and select New | String Value.
10. Enter InstallationDirectory as the New Value name.
11. Double-click InstallationDirectory to open the Edit String dialog and enter
C:\Program Files\eXc Software|WMI Providers\nonWindows (or the path
where you installed QMX) in the Value data box.
Import the Quest Management Pack

The eXcSoftware.nonWindows.mp management pack is a standard System Center
Operations Manager 2007 management pack that contains rules for monitoring the status of
non-Window systems, devices, and applications in your enterprise. The management pack
generates alerts and performance metrics from data generated by the Extensions.
Import eXcSoftware.nonWindows.mp management pack from the hard drive where you
installed QMX - Operations Manager 2007. If you did a typical installation, it is in:
C:\Program Files\eXc Software\WMI Providers\nonWindows\MOM\
OpsMgr2007\eXcSoftware.nonWindows.mp. Note that Quest also ships the management
pack as unsealed (eXcSoftware.nonWindows.xml). This is provided for you to review how
the management pack is implemented. However, you should not load the unsealed
management pack into Operations Manager.
Page 23
To import the management pack
1. In the Operations Console, select the Administration navigation button.
2. In the tree view, right-click Management Packs and select Import Management
Packs.
Page 24
3. Browse to C:\Program Files\eXc Software\WMI

Providers\nonWindows\MOM\OpsMgr2007 (or to the path where you
installed QMX), select eXcSoftware.nonWindows.mp, and click Open.
The Import Management Packs dialog displays.
Do not import the .xml management pack unless you are instructed to do so
by Quest support engineers.
Page 25
4. Click Import.
Page 26
5. When you see the message that ―All Management Packs successfully imported‖, click
Close.
If the import was not successful, please contact http://support.quest.com

and a support engineer will assist you in troubleshooting your environment
and setup.
Once you import the management pack you are ready to install and configure the
Extension(s).
Install Extensions
After you install Quest QMX Base Framework and have imported the Quest Management
Pack, you can run any of the QMX Extension solutions. In other words, one Quest QMX Base
Framework supports all of the Extensions. You will not need to download or reinstall the
Quest QMX Base Framework again unless you are upgrading it. From this point forward, you
only need to install Extensions onto the Windows server(s) where you installed the Quest
Base Framework.
One Quest QMX Base Framework supports all of your Extensions. If you have
already installed the Quest QMX Base Framework previously, you do not
need to download or reinstall it again.
Page 27
QMX - Operations Manager 2007 Extensions have not changed from Microsoft
Operations Manager 2005 Virtual Agents. This backwards compatibility allows
you to continue using Microsoft Operations Manager 2005 until you are ready
to move to System Center Operations Manager 2007.
To install Extensions
1. Go to the Management-Extensions Community Forum site at:

http://www.management-extensions.org.
2. Click the appropriate Download link in the Community Index box, or enter a key
word in the Search box.
Page 28
3. Click the name of an Extension to download.
4. Click Download Extension.
5. Save the Extension installation file (.msi) to a directory on the file system of the
Windows server where you installed the Quest Base Framework.
6. Double-click the .msi file to start the Extension Setup wizard.
Page 29
Note: You must install all of the Extensions as sub-folders to the Quest QMX Base
Framework folder (the default path is C:\Program Files\eXc Software\WMI
Providers\nonWindows\Virtual Agent Library\MOM\) otherwise the Extensions
will not display in the Configuration Tool.
If you installed the 64-bit Quest QMX Base Framework, please perform the sub-steps
below (if you installed on a 32-bit system, please skip this next step entirely):
Note: The 64-bit installation process targets the ―Program Files (x86)‖ folder as the
root folder for the installation directory when installing to the default boot drive
(usually the C: drive). Note: Quest recommends that you accept the default folder
(that is, the Program Files (x86) folder since the Windows installer ignores any
changes you make to the Folder name anyway).
Once you have completed this 64-bit installation, you must manually move the
Extension folder that you just created from the ―Program Files (x86)‖ folder (the 32-
bit Program Files folder tree) to the ―Program Files‖ folder (the 64-bit Program Files
folder tree). The easiest way to do this is to use Windows Explorer to cut the folder
from the ―Program Files (x86)‖ path and then paste it in the ―Program Files‖ path
since this is where the 64-bit QMX base framework is installed. This is shown in the
next two screen shots:
Page 30
Note: Cut each Extension from ―Program Files (x86)‖ folder and paste it in the
―Program Files‖ folder.
Page 31
Once you have moved the Extension folders into the 64-bit ―Program Files‖, the
Quest Software Configuration Tool will work exactly the same as the 32-bit version.
Once you install the Extension, you are ready to start monitoring systems, devices, and
applications using System Center Operations Manager 2007. However, you may want to
import ―child‖ management packs for the Extension(s) you have just installed, if one is
associated with the Extension. (See Import Child Management Packs.) If an Extension does
not have an associated ―child‖ management pack, this does not impact monitoring
functionality. The ―child‖ management pack simply allows for automatic and extended
grouping and views of that Extension type.
Import Child Management Packs

You must import the base eXcSoftware.nonWindows.mp management pack before you
install any Child Management Packs (as described in Import the Quest Management Pack).
Many Extensions have yet another management pack, a child management pack, which has
customized views within the Operations Manager console specific to that Extension solution.
While these views are highly desirable, they are not necessary. You can import them at a
later time.
You download child management packs from the same Web page from which you
downloaded the Extension. Since the child management packs are not sealed, they are XML
files.
Page 32
Note: Not all Extensions have child management packs. If the Extension you are installing
does not have one, it will not have Step 3 in the instructions.
Use your Web browser‘s ―Save As‖ option to save the .xml file (the child management pack)
to your hard drive. Import it into Operations Manager 2007 using the regular management
pack import wizard.
After you import the child management pack, select the Monitoring view, navigate to non-
Windows system/devices and notice that the additional folder added below the general
―non-Windows‖ views:
Page 33
Note: Learn more about these additional Views in Monitoring Performance .
Before you can start monitoring systems, devices, and applications using System Center
Operations Manager 2007 you must setup the communication between QMX - Operations
Manager 2007 and the OpsMgr SDK Service running on the OpsMgr Root Management
Server (RMS).
Page 34
Configure OpsMgr SDK Communications

QMX - Operations Manager 2007 uses the System Center Operations Manager 2007 SDK
service to generate dynamic OpsMgr diagram nodes and dynamic OpsMgr Management Pack
rules for the non-Windows systems, devices, and applications. Once you have installed the
QMX - Operations Manager 2007 components, you must configure how to authenticate to
the OpsMgr SDK Service running on the Operations Manager RMS.
Note: In Operations Manager R2, Microsoft renamed the OpsMgr SDK

service to the ―System Center Data Access‖ service. In this document, we
will use the term ―OpsMgr SDK‖ but if you are running Operations Manager
R2, it means the ―System Center Data Access‖ service.
For more information, read How to Connect an OpsMgr SDK Client to the
SDK Service at: http://msdn2.microsoft.com/en-us/library/bb437582.aspx.
There are four possible ways to configure the security settings to the OpsMgr SDK service.
Since this installation guide assumes you are installing into a production environment, this
section presents the scenario where QMX is installed on an Operations Manager agent
Windows computer. (See Appendix B - QMX on a Management Server for more information
about installing to an Operations Manager Management Server for a proof-of-concept
installation.)
Note: Please keep in mind that the System Center Operations Manager 2007 architecture
defines only one SDK service which always runs on the Root Management Server (RMS).
Below are the steps required to setup the OpsMgr SDK communications.
(Note: Skip any steps that have already been completed in your environment):
Identify the SDK Service User
Create a Domain User Group
Add the SDK Service User to the Domain User Group
Associate the Domain User Group
Configuring Global Variables

Before you start, make note of the SDK Service User name. You‘ll need that information
later in the process.
To identify the SDK Service User
1. From the Operations Manager 2007 Root Management Server, right-click the My
Computer icon on your desktop and select Manage.
Page 35
2. Navigate to Services and Applications | Services.
3. Right-click OpsMgr SDK Service and choose Properties.
4. Select the Log On tab.
Page 36
Note: The user account in the This account box. In this example it is ommssdka.
5. Close the OpsMgr SDK Service Properties dialog.
6. Minimize the Computer Management window for now.

To create a new domain user group
From a system from which you can administer the domain where System Center Operations
Manager 2007 is installed,
1. From the Start menu, navigate to Control Panel | Administrative Tools | Active
Directory Users and Computers.
2. In the Active Directory Users and Computers domain controller window, navigate to
the domain.
Page 37
3. Right-click Users and choose New | Group to create a new user group.
Page 38
4. Enter a name for the Domain User Group in the Group name box.
Note: You can use any name, but for the purposes of this demonstration, use
QMXusers.
5. Leave the default options and click OK.
6. Leave the Active Directory Users and Computers window open for the next task.
Page 39

To add the SDK service user to the domain user group
1. Right-click the name for the Domain User Group you just created (QMXusers in this
example) and select Properties to add the user(s) that the Operations Manager
2007 SDK Service runs as to the newly created domain user group.
Page 40
2. In the Members tab, click Add.
3. In the Users, Contacts, or Computers dialog, ensure that Users or Users or Other
objects is in the Select this object type box.
4. Enter the SDK Service User Name in the Enter the object names to select box and
click OK. For the purposes of this example, enter ommssdka, the SDK Service User
name you made note of in Identify the SDK Service User.)
Page 41
5. Click OK.
6. Close the Active Directory Users and Computers domain controller window.

Once you have created the QMXusers Active directory Users Group and have added the
OpsMgr SDK Service User to it, you must associate this domain user group with the System
Center Operations Manager 2007 Administrator user role.
To associate the domain user group with the Administrator user role
1. Open the Operations Console, select the Administration navigation button.
Page 42
2. Under the Security folder in the tree view, click User Roles.
3. In the results pane, right-click Operations Manager Administrators and select

Properties.
Page 43
4. Click Add to add a member to the user role.
5. Enter the Domain User Group name you just created (QMXusers in this example) and
click OK. (See Create a Domain User Group.)
Page 44
6. Click OK and return to the Operations Console.
7. Restart the System Center Operations Manager 2007 SDK Service running on the
Root Management Server. (See Restarting the SDK Service for instructions.)
To finish setting up the security you must now configure the global variables in the Quest
QMX Base Framework using the QMX Configuration Tool. These global variables tell QMX
how to authenticate to the OpsMgr SDK service.
Start the QMX Configuration Tool

To start the QMX Configuration Tool
1. From the Start menu, navigate to All Programs | eXc Software | WMI Providers
| non-Windows | Configuration Tool.
Note: Quest recommends that you make a short cut to the Configuration Tool on
your desktop.
Page 45
When you mouse-over any blue text or buttons, ―flyover‖ help displays for
your convenience. To turn this feature off, go to the View menu and choose
ToolTips or click Ctrl+Z.
2. Expand System Center and select MOM.
All the QMX - Operations Manager 2007 Extension solutions that you have installed are
listed under the MOM folder.

Before you configure the Global Variables you must encrypt the UserID and Password for
the SDK Service User. (See Create a Domain User Group).
Encrypting the UserID and Password

To encrypt the username
1. In the Configuration Tool, open the Tools menu:
Page 46
2. Select the Encryption option.
3. Enter the SDK Service User Name into the Text to encrypt box. This is the user name
you made note of in Identify the SDK Service User. For this example, enter
ommssdka. Please only enter the short (NETBIOS) name for this domain userid. DO
NOT specify the userid in Domain\Userid or Userid.domain.com format.
Note: This is the domain UserID running the System Center Operations Manager
2007 SDK service on the Root Management Server.
4. Enter a file name for the encrypted SDK Service User Name in the File to encrypt to
box. For example, enter SDKuser.txt.
Page 47
Note: You can change the default location for your encryption file by clicking the
three-dot Browse button next to the File to encrypt box.
5. Click OK.
To encrypt the password

1. From the Tools menu, select the Encryption option.
2. Enter the password for the SDK Service User into the Text to encrypt box. In this
example, enter Pa$$word.
Note: This is the Password for domain UserID running the System Center Operations
Manager 2007 SDK service on the Root Management Server.
3. Enter a file name for the SDK Service User Password in the File to encrypt to box.
For example enter SDKuserPassword.txt.
4. Click OK.
Setting the Global Variables for OpsMgr SDK Communications

To configure global variables
1. In the Configuration Tool expand the System Center folder and click MOM.
2. Select the OpsMgrGlobalVariables tab:
Page 48
3. Set the System Center Operations Manager 2007 global variables as follows:
a. g_strMOMManagementServerName - Enter the NetBios name of the
System Center Operations Manager 2007 Root Management Server where the
SDK Service is running. In this example it is OM07RMS.
b. g_strMOMServerDomainName - Enter the NetBios domain name where

System Center Operations Manager 2007 Root Management Server is
running. In this example it is ACME.
c. g_strMOMUserId - Click the three-dot Browse button and navigate to the

SDK Service User Name encryption file you created in Encrypting the UserID
and Password.
This is the domain UserID running the System Center Operations Manager
2007 SDK service on the Root Management Server. In this example it is
SDKuser.txt.
Note: You must specify this value as an encrypted file. If the three-dot
Browse button is not responsive, manually type file: plus the path and file
name containing the encrypted UserID. For example enter: file:C:/Program
Files /eXc Software/WMI
Providers/nonWindows/Encryption/SDKuserId.txt.
You must use forward slashes (/) as the path separators.
d. g_strMOMPassword - Click the three-dot Browse button and navigate to the

SDK Service User Password encryption file you created in Encrypt UserIDs
and Passwords.
This is the Password for domain UserID running the System Center
Operations Manager 2007 SDK service on the Root Management Server. In
this example it is SDKuserPassword.txt.
Page 49
Providers/nonWindows/Encryption/SDKuserPassword.txt.
4. Click the Save button.
Validating the Global Variables for OpsMgr SDK Communications

To validate the global variables you defined in the section above:
1. In the Configuration Tool main menu, select Tools->Debug->Test Connection for

OpsMgr SDK.
2. Click the Go button (which will run the ―Connect to OpsMgr SDK‖ test)
3. Ensure that the test returns successful. If not, go back to the previous section and
validate the global variables you defined. Note, that the output of the ―Connect to
OpsMgr SDK‖ test will give you helpful hints as to why the connection failed.
You are now ready to configure the Extensions. (See the ―Configure the Extension‖ section.)
Page 50
Configure the Extension

Specifying Hosts to Monitor
Configuring the Fields on the _Hosts Tab
Specifying Hosts to Monitor

Specifying a host to monitor is your first step in configuring an Extension. You can specify
hosts manually or by using auto-discovery. During the trial period, typically you would
manually specify hosts to monitor. (See Auto Discover Hosts for more information about the
auto-discovery option.)
Specify Host Information Manually

To manually specify hosts
1. Start the QMX Configuration Tool.
2. In the tree view, navigate to the MOM folder and select the Extension (shown as a
subfolder to the MOM folder) you want to configure:
Note: If you cannot expand the MOM folder, you have not yet installed any
Extension(s) or you have installed Extension(s) but have put them in a directory that
is not under the directory where the QMX Base Framework has been installed.
The __Host tab displays the list of host (systems and/or devices) that QMX - Operations
Manager 2007 is monitoring. When you first install QMX - Operations Manager 2007, by
default it lists sample host(s). To add hosts, clone a sample host and modify it to your
requirements.
Many of the QMX Extensions provide sample host entries with a default
status of ―Disabled‖. Quest provides these samples for you to use as a
starting place. Clone the ones that most closely match your environment
requirements. (Look in the Notes field for some hints!) If you do not need
Page 51
these entries, Quest recommends that you leave them disabled for possible
future cloning needs.
To define a system, device, or application to monitor
Note: Use the Select (or sometimes listed as Clone/Remove) checkbox in conjunction with
the CLONE or REMOVE buttons to either create a new (cloned) entry or delete (remove) an
existing entry.
1. Select the Clone Remove check box next to the sample host.
2. Click CLONE.
3. Click SAVE.
Once you have cloned a host entry you are ready to customize the fields on __Hosts tab.
(Refer to Configuring the Fields on the _Hosts Tab for instructions.)
Configuring the Fields on the _Hosts Tab

The values in the fields on the __Hosts tab allow the Extension to connect to the host
(system, device, or application) you want to monitor. The __Hosts tab fields vary depending
on the Extension. The following describes the possible fields in a __Hosts tab.
To define a host
1. Enter the following:

Disable: Unselect the Disable checkbox.
Use the Disable checkbox to prevent the auto-start function from starting the
Extensions against the selected hosts. Note that any disabled host entry appears on
the left side of the screen with a pound sign (#) in front of the DNS name. (See
Enable Automatic Monitoring for more information about the auto-start function.)
DNS Name: Enter the DNS name in the DNS name box.
Each host you want to monitor requires that you supply the DNS Name. If you do not
have DNS available, make up a name and put it in the Windows
C:\WINDOWS\system32\drivers\etc\hosts file; otherwise, you can add it by means
of DNS management to your Forwardees list. Entries made in
C:\WINDOWS\system32\drivers\etc\hosts are available immediately. No need to
restart any service or reboot.
Note: We have seen in some customer sites that using a Fully Qualified Domain
Name (FQDN) for the ―DNS Name‖ does not work in OpsMgr 2007. Therefore, we
have modified the QMX Configuration Tool to use only NetBios (short) names.
Login Prompt: Enter a Login Prompt so QMX - Operations Manager 2007 knows
what to look for on the screen once the Telnet/SSH connection is made. (See _Hosts
Tab Tips for more details.)
Page 52
Some devices are set up without a Login Prompt required because the device
immediately requests a Password. In that case, enter ―ssword‖ in the Login Prompt
and enter ―NOUSERID‖ in the UserId box. The device will send the Password Prompt
twice, but it will still result in a successful login. The default Login Prompt is ―partial
text‖ of the Login (or username or Password) Prompt since some devices use Initial
Capitals and others do not. Log in manually to any device following this logic: Telnet
or SSH to the DNS name, look for the Login Prompt text (which might be ―ssword‖)
on the screen, respond with the login UserId, look for the Password Prompt on the
screen, and respond with the Login Password.
QMX provides support for authenticating to a CLI system/device using one of three
methods:
1. Clear text userid and/or password (not recommended)
2. Encrypted userid and/or password
3. Public/private key authentication (see

http://www.quest.com/Quest_Site_Assets/Documents/QMXom_Authenticatio
nConfigurationGuide_3.pdf for details)
In a future release, we will make LDAP available in QMX by means of Active
Directory authentication.
UserId: Enter the UserId so QMX - Operations Manager 2007 can respond to the
Login Prompt.
Password Prompt: Enter a Password Prompt so QMX - Operations Manager 2007

knows what to look for on the screen once the Telnet/SSH connection is made. (See
_Hosts Tab Tips for more details.)
Password: Enter the Password so QMX - Operations Manager 2007 can respond to
the Password Prompt.
Port: Enter the port number you want to use to connect to the non-Windows host
system. Typically Telnet uses port 23; while SSH uses port 22.
Secure Connection: Unselect the Secure Connection checkbox to use Telnet; select
the Secure Connection checkbox to use SSH.
Run Watchdog: In a production environment you would select the Run Watchdog
option to stop the Extension(s) when a network connection to a designated target
device is lost. The Watchdog would then restart the Extension when network access
is restored. This ensures the non-Windows State view is accurate in Operations
Manager 2007. Quest highly recommends you always run the watchdog.
Trap, Read, and Write Community: To receive the devices SNMP traps that get
converted to System Center Operations Manager 2007 alerts, QMX - Operations
Manager 2007 requires the SNMP Trap Community name and the SNMP Read
Community name. This allows the SNMP (Trap) solution to check connectivity
between the computer on which the QMX Extension solution is installed and the
Page 53
target device (ex: a Cisco Router, Switch, Firewall, and so forth). The Write
Community name is optional since QMX solutions do not perform SNMP SETs by
default (although they have the capability to do so). The SNMP community names
are case sensitive and must match the name(s) contained in the Windows SNMP
Service's Security tab and in the device configuration. It is best to ask your System
Administrator for the proper case sensitive names. You must configure the device to
THROW SNMP Traps to the IP address of the Windows computer where the QMX
solution is installed. You must also configure the device to accept SNMP GETs.
Initial State: Always set the Initial State to RUNNING.

Notes: The Notes are a free form area that you can use at your discretion.
2. Click SAVE.
Whenever you make changes to the __Hosts tab, click SAVE, wait for the
―successfully saved to disk‖ message then stop and restart the Extension for the
host(s) you just modified for the changes to take effect.
Once you have defined the systems, devices, or applications you want to monitor, you are
ready to test the Extension. (See the ―Validate the Extensions‖ section.)
_Hosts Tab Tips

If you are prompted for a ―login‖ or ―Login‖ when you use a ―Telnet‖ or ―SSH‖ session, set
the Login Prompt to ―ogin‖. If you are prompted for a ―password‖ or ―Password‖ when you
use a ―Telnet‖ or ―SSH‖ session, set the Password Prompt to ―ssword‖.
That is, leave off the starting letter(s). This is to accommodate the fact that some devices
use initial capitals and others do not. If you are prompted for anything else, set the Login
Prompt or Password Prompt to whatever word it prompted you for, less the first
character(s). For example, if you open a DOS command shell and enter you ―telnet
CiscoRouter‖ (assuming you have a device named CiscoRouter) and it returns ―Username‖
or ―username‖, enter ―sername‖ as the Login Prompt. Then, set the proper UserId in the
UserID field.
Page 54
Validate the Extensions

Validate Target Machine Accessibility
Starting an Extension
Monitoring Alerts
Monitoring Performance
Validate Target Machine Accessibility

Before you start monitoring your devices, verify that you can access the target hosts.
To Test Connectivity
2. In the tree view, navigate to System Center | MOM.
3. Open an Extension in the Configuration Tool tree view, such as LinuxSuSe.
4. Right-click the host, such as sles1, and select Test Connection.

Note: Some Extensions have more detailed Test Connection interfaces since they
support multiple connection protocols.
Page 55
5. Verify that the test connection succeeded and then you may close the Test
Connection window. If the Test Connection was unsuccessful, go back to the Hosts
tab and verify the settings (user prompt, userid, password prompt, password, etc)
are correct.
Note: You can also test with the other menu options such as Ping, Nslookup, SSH,
and so forth,
Once you have validated the connectivity, you are ready to start the Extension.
The next two sections below show how to manually start and stop an Extension against a
host. While this is desirable for testing, in a production environment, you would rely on
OpsMgr to start and maintain the monitoring for you (see the subsection "Enable Automatic
Monitoring" in the "Advanced System Administration" section below).
Starting an Extension
To start an Extension
1. In the Configuration Tool, navigate to the Extension in System Center | MOM.
Page 56
2. Right-click the host, such as sles1, and select Start.
Note: After the Extension starts, the device icon in the Configuration Tool turns
green and (under Windows 2003 and XP) DOS windows appear in your Windows
Taskbar. The DOS windows in the Windows Taskbar represent the monitoring jobs to
the devices you have configured QMX - Operations Manager 2007 to monitor.
Unfortunately, under Windows 2008 and Vista, you will be unable to see the DOS
windows in your Windows Taskbar. This is due to the heightened security model in
Page 57
these operating systems. You can view these console sessions to help you
understand how the QMX Extension solutions work, however, in a production
environment, you would configure the sessions to run as hidden background tasks
(see the VirtualAgentJobs tab for the extension to set the jobs to hidden).
3. Click the DOS window icon to open it.
If you are 'term-served' (that is, Microsoft Terminal Services) to the Windows
computer where the QMX - Operations Manager 2007 solutions are installed,
you will not see the DOS windows unless you are in 'console' mode (this is
achieved from the 'term-serving' device by means of Start|Run|mstsc
/console. (If you have Vista, go to Start|Run|mstsc /admin).
The screen shot above shows an example of what the DOS windows might show.
This particular job is a MONITORLOG job showing an open connection monitoring the
syslog for errors on the recently configured sles1 host.
To stop an Extension
1. In the tree view, navigate to the MOM | LinuxSuSe.
2. Right-click sles1 and select Stop.

Note: When the Extension stops, the device icon changes back to blue.
Monitoring Alerts
Now you can open your Operations Console and watch for the alerts.
To watch for the alerts
1. Open the Operations Console.

2. Select the Monitoring navigation button.
Page 58
3. In the console tree, navigate to Monitoring | non-Windows system/devices.
4. Click non-Windows Alerts.
Note: Running an Extension does not necessarily mean you will get alerts. No alert
will appear if nothing is wrong.
For the next demonstration, it is assumed that you are monitoring a SUSE Linux Enterprise
Server called sles1.
To force an alert
1. Open the MONITORLOG window.
2. Open the sles1 system, and position windows so that you can see both the sles1
system command terminal and the MONITORLOG window.
Page 59
3. At the sles1 command line, enter logger ―major security issue‖.
4. Look in the MONITORLOG window and validate that the Extension picked up the log
entry.
5. In the Operations Console, in the Monitoring view, navigate to non-Windows

system/devices | non-Windows Alerts and watch for the alert to appear.
Page 60
Monitoring Performance
When you imported the ―Child‖ management pack (see Import Child Management Packs) for
your Extension, it added some additional views including a Core Dashboard view:
Page 61
Note: This assumes you imported the ―child‖ Management Pack for LinuxSuSe.
The initial state of the Core Dashboard has three performance counter windows, but nothing
is defined, yet. We need to define what counters you want to graph and the time range for
the LinuxSuSe Performance Processor, LinuxSuSe Performance FileSystem, and LinuxSuSe
Performance Memory views.
To design the Core Dashboard

1. In the tree view, select the LinuxSuSe Performance Processor view:
Page 62
2. Select the counters you want to graph. In this example, click the total, user, and
system counters.
Page 63
3. Right-click the LinuxSuSe Performance Processor window and click Select time
range.
Page 64
4. Select 4 hours and click OK.
5. In the tree view, select the LinuxSuSe Performance FileSystem view:
Page 65
6. Select the counters you want to graph. In this example, click the /dev/hda2 and
udev counters.
7. Right-click the LinuxSuSe Performance FileSystem window and click Select time
range.
9. In the tree view, select the LinuxSuSe Performance Memory view:
Page 66
10. Select the counters you want to graph. In this example, click the PERCENT swap
used, PERCENT physical used, PERCENT used by Applications, and PERCENT
free for Applications counters.
11. Right-click the LinuxSuSe Performance Memory window and click Select time
range.

a. In the tree view, select LinuxSuSe Core Dashboard and see how this looks
now:
Page 67
Note: You can configure the appearance of the Core Dashboard.
You can configure the appearance of the Core Dashboard to show different views and
different performance counters.
To configure the Core Dashboard views
1. Right-click LinuxSuSe Core Dashboard and choose New to see how you can
reconfigure the Core Dashboard:
Page 68
Page 69
Advanced System Administration

Encrypt UserIDs and Passwords
Enable Automatic Monitoring

Cloning Extensions
Auto Discover Hosts
Logging Security Events into ACS
Using the Virtual Agent Jobs Tab
Encrypt UserIDs and Passwords

For security reasons Quest Software recommends that you encrypt the UserIDs and
Passwords for use with QMX - Operations Manager 2007 whenever possible. It uses a two-
step 1024-bit RSA encryption: first you create a file containing the encrypted UserId or
Password, and then you specify that encryption file in the UserID or Password box when
defining the host in the Configuration Tool.
To encrypt UserIDs or Passwords
2. From the Tools menu, select Encryption.
Page 70
3. Enter the UserID or Password in the Text to Encrypt box.
4. Click [...], the Browse button, to select a directory path in which to store the
encrypted text, enter a filename, and click Open.
5. Click OK on the Encryption Tool dialog.
Specifying an Encrypted Text File

In the Configuration Tool, many of the tabs allow you to specify an encrypted text file or
clear text. However, in some cases you must specify an encrypted text file such as when
configuring the global variables (see Configuring Global Variables). When you see a small
light blue button next to the text field you know you can specify an encrypted text file:
The encrypted file name must be prefixed with ―file:‖ and you must change any single ―\‖ to
a ―/‖ or to ―\\‖ since the javascript code that parses these files treats the single ―\‖ as an
escape.
To specify an encrypted text file
1. Click the small light blue button [...] to the right of the file name.
2. Select the encrypted file and click Open.
Note: This feature is not always available (due to a currently unknown issue with
Internet Explorer settings [we are working on this]). If the light blue button does not
work for you, simply type the file into the entry field. Please remember to prefix the
file name with ―file:‖. So, for example, if the file is named
C:\encryption\MyPassword.txt, the entry field would need to look like:
file:C:\encryption\MyPassword.txt
Enable Automatic Monitoring

Once you have verified that the Extensions are properly configured and functioning, you can
enable them to start automatically. Automatically having the monitoring start is desirable if
Page 71
the Windows computer where QMX is running is rebooted or if someone restarts the WMI
service.
To enable automatic monitoring
1. In the tree view, select the MOM folder.

2. In the details pane, click the GlobalVariables tab.
3. Select the g_boolAutomaticallyStartVirtualAgents checkbox.
4. Click Save.
If you select the auto-start feature, all hosts that are not disabled will automatically start
when the computer is started or when you restart the WMI or System Center Operations
Manager 2007.
This may not be desirable during a trial as you probably want manual control
for testing. Furthermore, exceeding the number licenses available will result
in license errors and failure to start the excess ―hosts‖.
Cloning Extensions
When you install an Extension for a device type such as LinuxSuSe, you download a set of
.xml files (for most CLI solutions) and an .mdb file (for most SNMP solutions) which control
the solution's configuration. QMX - Operations Manager 2007 gives you the ability to clone
Extensions for different purposes.
Let‘s assume a data center has two groups of Linux Red Hat servers. One group has Apache
Web Server running on it and the other has a Mail Server running on it. Without the ability
to clone an Extension, you would have to specify the same threshold settings for both
groups. However, with the ability to clone whole Extensions, you can set the thresholds for
a mail server on one cloned Extension one way and then set different threshold settings for
a Web server on another cloned Extension.
Page 72
When you clone an Extension, it becomes a ―sub-type‖ of the same class, each with its own
set of tabs. On the file system, it is a sub-folder to where the Extension is installed. Thus,
each would have its own tabs which you can uniquely specify.
To clone an Extension
2. In the tree view, navigate to the MOM folder.
3. Right-click an Extension for a device type and select Clone VA.
4. Enter a name for the new Extension and click OK.
The cloned Extension is an exact replica of the one you cloned, including the device entries.
Thus, the same device will be in multiple groups.
To delete duplicate devices

1. In the cloned device's Extension, select the Clone Remove box for the duplicate
device and click REMOVE.
Page 73
2. Click SAVE.
Auto Discover Hosts

Use the Autodiscovery feature to simplify the process of specifying a list of hosts.
Autodiscovery automatically discovers all hosts in a specified subnet group or TCP/IP
address range. There are two auto-discovery modes: CLI (Command Line Interface) and
SNMP (Simple Network Management Protocol). QMX - Operations Manager 2007 starts the
correct auto-discovery mode for each Extension. When you start Autodiscover, the title of
the Window indicates whether you have a CLI-based device or an SNMP-based device:
Auto Discover CLI-based Devices
Auto Discover SNMP Devices
Auto Discover CLI-based Devices

To use Autodiscovery for a CLI-based solution
1. Right-click the Extension folder and select Autodiscovery.
Page 74
The CLI Auto-discovery dialog opens:
2. Select either the Range or Subnet Discovery mode.

If you select Range, enter the TCP/IP address range.
Page 75
If you select Subnet, enter Network and Subnet mask information.
3. Browse to select the Output Hosts XML file.

Note: By default the process saves the configuration information to the __Hosts.xml
file located in the C:\Program Files\eXc Software\WMI Providers\nonWindows\Virtual
Agent Library\MOM directory for the Extension. Therefore, you only need to change
this field to test the Autodiscovery results without changing the existing host records
already defined in the __Hosts tab
4. Select Merge to add on the new information rather than overlay the existing
information that was gathered on one or more prior Autodiscovery runs.
Note: If this is the first range or subnet for which you are doing Autodiscovery for
this particular device type, leave Merge unselected.
5. Enter the Ping timeout value in milliseconds.
Note: If your network is slow, increase the Ping timeout value to more than 500
milliseconds.
6. Unselect the Device is Pingable, if the device is not pingable.
7. Enter the SSH port number; the default is 22.
8. Enter the Telnet port number; the default is 23.

9. Enter the Default UserID for the service account that is common to all hosts being
discovered. If all of the hosts do not have a common service account, you must run
Autodiscovery for each service account.
10. Enter the Default Password for the service account.
11. Enter the CLI Command to issue. This helps QMX - Operations Manager 2007
determine what type of system it is. For example, you can enter a command that will
help you identify unique hosts.
12. Enter the Expected response, a case-sensitive text string that must be contained
in the output of the CLI command issued to the host.
Note: You can supply multiple expected responses by separating each of them with
a vertical bar (―|‖). Specifying multiple expected responses is useful if you have
multiple versions of a system type.
13. Select Invoke debugger to start Visual Studio in debug mode. This option is
generally used by Quest Support.
14. Click Process.

15. Wait for the ―Auto-discovery process has completed‖ message.
16. From the Configuration Tool, right click the Extension folder in the tree view and
select Refresh.
Once you auto-discover the hosts you are ready to customize the fields on the __Hosts tab.
Page 76
Auto Discover SNMP Devices

To use Autodiscovery for a SNMP-based solution
1. Right-click the Extension folder and select Autodiscovery.
The SNMP Auto-discovery dialog opens:
2. Select either the Range or Subnet Discovery mode.
If you select Range, enter the TCP/IP address range.

If you select Subnet, enter Network and Subnet mask information.
3. Browse to select the Output Hosts XML file.
Note: By default the process saves the configuration information to the __Hosts.xml
file located in the C:\Program Files\eXc Software\WMI Providers\nonWindows\Virtual
Agent Library\MOM directory for the Extension. Therefore, you only need to change
this field if you needed to test the auto-discovery results without changing the
existing host records already defined in the __Hosts tab.
4. Select Merge, to add on the new information rather than overlay the existing
information that was gathered on one or more prior Autodiscovery runs.
Note: If this is the first range or subnet for which you are doing Autodiscovery for
this particular device type, leave Merge unselected.
Page 77
5. Enter the Ping timeout value in milliseconds.
Note: If your network is slow, increase the Ping timeout value to more than 500
milliseconds.
6. Unselect the Device is Pingable, if the device is not pingable.

7. Select Create device EVEN IF SNMP GET fails. This option allows you to create a
device in spite of this SNMP GET failure and fix the problem later.
8. Enter the Default SNMP Read Community Name. QMX - Operations Manager
2007 uses this value to perform the SNMP Get request so your SNMP capable devices
must share a common SNMP Read Community Name or else you must perform
several runs of the Autodiscovery program. The accepted practice of the SNMP
device manufacturers is to set the factory default to ―public‖.
9. Enter the Default SNMP Trap Community Name, (optional).
10. Enter the SNMP OID to query. This helps QMX - Operations Manager 2007
determine what type of system it is.
11. Enter the Expected response, a case insensitive text string that must be contained
in the output of the SNMP Get request when issued to the device.
Note: You can supply multiple expected responses by separating each of them with
a vertical bar (―|‖). Specifying multiple expected responses is useful if you have
multiple versions of a device type.
12. Select Invoke debugger to start Visual Studio in debug mode. This option is
generally used by Quest Support.
13. Click Process.

14. Wait for the ―Auto-discovery process has completed‖ message.
15. From the Configuration Tool, right click the Extension folder in the tree view and
select Refresh.
Once you auto-discover the hosts you are ready to customize the fields on the __Hosts tab.
Logging Security Events into ACS

You can enable QMX - Operations Manager 2007 to log non-Windows security events into
System Center Operations Manager 2007 Audit and Collection Services (ACS). By enabling
the Local Security Policy property named ―Audit object access‖ to ―Failure‖. QMX -
Operations Manager 2007 will write the non-Windows security events into the Windows
Security Event Log. A non-Windows security event is defined by associating the Security
SML Class to the alert. For CLI solutions, this can be done in the logs monitoring and for
SNMP, traps can be configured for a particular SML Class by using the Message Filter DB.
Page 78
To enable the Local Security Policy
1. From the Start menu, navigate to Control Panel | Administrative Tools | Local
Security Policy.
2. Navigate to Security Settings | Local Policies | Audit Policy.

3. Right-click Audit object access.
4. Under Audit these attempts, select Failure in the Audit Object Access Properties
dialog, and click OK.
Using the Virtual Agent Jobs Tab

The options on the __VirtualAgentsJobs tab are primarily used by developers who want to
do in-depth Extension customization. Quest support also uses the settings on this tab to
create solutions and to assist you in debugging.
Typically you will not need to modify anything on the __Virtual Agent Jobs tab. The
__Virtual Agent Jobs tab defines the monitoring schedule and jobs which will perform the
monitoring tasks. This configuration information is exposed for customers who want to
extend the monitoring functionality for their unique requirements.
If you write customization scripts to enhance your Extension(s) why not

share them on the www.management-extensions.org Community site!
Failover
The Failover feature in QMX automatically switches the workload from a failed ―primary‖
QMX system to a ―backup‖ QMX system to ensure there is no monitoring interruption. Both
QMX systems must be in the same Management Group and have identical QMX versions. To
see what state a QMX system is in (relative to Failover); look in the lower right hand corner
of the QMX Configuration Tool. There is an icon and associated text called Failover. The
Failover state can be: Standalone (that is, this QMX system is not participating in a QMX
Failover scenario), Primary or Backup.
Once Failover is configured, the primary system sends a heartbeat packet to the backup
system every minute. If, after 3 minutes, the backup system does not receive a heartbeat
packet from the primary system, it will assume control of the Extensions. The backup
system will continue to function as the primary until it receives another heartbeat packet
from the primary system again. Once this happens, the backup system gives control of the
monitored system(s) back to the primary and reverts back to its backup role.
To setup Failover, identify one QMX system as the primary computer and another as the
backup computer. Note: there must be only one primary and one backup computer. If you
are configuring Failover in your production environment, be sure that you have enabled the
global variable g_boolAutomaticallyStartVirtualAgents on both the primary and backup
computers (see the subsection "Enable Automatic Monitoring" in the "Advanced System
Administration" section below).
Page 79
To configure the primary QMX system for Failover
1. Start the QMX Configuration Tool on the primary computer.
2. From the Configuration menu, select Failover.
3. Select This computer is the primary computer and click Apply.
To configure the backup QMX system for Failover
1. Start the QMX Configuration Tool on the backup computer.
2. From the Configuration menu, select Failover.
Page 80
3. Select This computer is the backup computer.
4. Click Sync with Primary.
Note: This function utilizes the xcopy command so be sure that you do not have any
Extension configuration files on the backup system that you would like to keep.
5. Confirm the Backup Synchronization warning.
Note: When you click Yes, a DOS command prompt window opens and waits for you
to click Enter before starting xcopy. The files that are copied start at the base Virtual
Agent Library directory (C:\Program Files\eXc Software\WMI
Providers\nonWindows\Virtual Agent Library) and then traverses through all the
subdirectories underneath it. At a minimum, you must have a primary failover
system setup first. Once the primary-to-backup relationship is established (that is,
once you click the Apply button), Sync with Primary can perform the xcopy
because creating the failover relationship creates the network file share, if it does not
yet exist.
To validate the Failover setup
Once you have the primary and backup computers configured, you can test that the failover
feature is working properly by ―tricking‖ QMX into thinking that a failover has occurred by
following these steps:
1. On the primary computer, go back into the failover dialog and uncheck the ―This
computer is the primary computer‖ checkbox and then click the Apply button.
2. Wait for up to 20 minutes and verify that the backup computer has assumed the
primary role. On the backup computer, you will see the hosts in the Configuration
Tool tree view turn from blue to green. Waiting for 20 minutes accommodates for the
maximum 3 minutes it takes for the failover to occur plus the maximum 15 minutes
Page 81
it takes for the automatic monitoring to occur (see

g_boolAutomaticallyStartVirtualAgents).
3. Once you have validated step 2, now go back to the primary computer and check the
―This computer is the primary computer‖ checkbox and then click the Apply button.
4. Wait for up to 20 minutes and verify that the backup computer has returned to the
backup role (the icons will return to blue) and that the primary computer has
returned to the primary role.
Page 82
Troubleshooting
Basic Troubleshooting Tips
Troubleshooting Checklist
Checking the Quest QMX Base Framework Version
Upgrading the Quest QMX Base Framework
Upgrading Extensions
Migrating From One Server to Another
Gathering Diagnostic Information
WMI Tuning for Large Scale Implementations
Basic Troubleshooting Tips

Before you start troubleshooting:
1. In the QMX Configuration Tool, unselect the

g_boolAutomaticallyStartVirtualAgents checkbox in the MOM GlobalVariables
tab, if it is enabled. (See Enable Automatic Monitoring for more information.)
2. Right-click the MOM folder in the Configuration Tool and choose Stop ALL to stop all
extensions. (Or, you can restart the WMI Service.)
3. If you have an issue regarding something in the Operations Manager Console, you
should clear its cache.
To clear the Operations Manager Console cache
a. Right-click the Operations Manager shortcut icon and select Properties.
Page 83
b. On the Shortcut tab, Add ‖ /clearcache to the end of the Target string, if it
does not already exist.
Note: Add a space before the forward slash.
c. Close the Operations Manager Console and re-open it.
4. If you have an issue related to excessively high CPU utilization check what the
utilization is without any Extensions running. If utilization is high without any
Extensions running, it will only be worse when they are running. For example, you
might find that dw20.exe (Dr. Watson) is utilizing an inordinate amount of CPU on an
Agent computer where the Extensions are installed, even when none of them are
running. In that case, disable Dr. Watson.
To disable Dr. Watson (dw20.exe),
a. From the Start menu, select Run, enter regedit.exe in the Open box, and
click OK.
b. Locate and select the following registry key:

HKEY_LOCAL_MACHINE\Software\Microsoft\Windows
NT\CurrentVersion\AeDebug.
Page 84
c. Delete the AeDebug key. If dw20.exe is currently running, you can either wait
for it to complete or use Windows Task Manager to force it to terminate. It is
possible for multiple copies to be running. Once terminated, they will not
restart again since you deleted the required registry key.
5. Another typical issue: Event Log entries with ID 353 can indicate a CPU utilization
issue. Quest does not recommend starting more than three or four Extensions by
using the Start option from the context menu. It is best to use the auto-start
feature. Using the auto-start feature stages the Extensions by starting them one at a
time, pausing between starts to give some amount of time to load balancing (by
means ofintermittent starts). When you use the right-click menu‘s Start option, it
starts all the Extensions at once causing high CPU utilization.
6. Clear all Active Alerts from the Operations Manager non-Windows view so that you
can have a fresh start.
To limit the amount of data produced during your troubleshooting session,

Quest recommends that you troubleshoot one device/application/OS issue at
a time.
Troubleshooting Checklist
This section explains what to do specifically for the ―Top 4‖ reported problem areas in QMX -
Operations Manager 2007.
Before you attempt to troubleshoot any issue, ensure that you are running
the latest Quest QMX Base Framework, Extension, and Base Management
Pack, and have successfully imported any respective Child Management
Pack(s) that apply to your installation. It is possible that an Extension might
require functionality that does not exist in down-level QMX components.
Page 85
These are the most common problems users run into:
1. Alerts Are Missing

2. Performance Records are Missing
3. SNMP Issues
4. Command Line Interface Issues
Alerts Are Missing

To check if alerts are missing
1. In the QMX Configuration Tool, check the solution‘s Comparator and Alert Threshold
settings in the PerformanceMetrics tab to see if you have selected any of them.
2. In the QMX Configuration Tool, verify the settings in the solution‘s AlertFilter tab.
3. In the Operations Manager Console, navigate to Authoring | Management Pack
Objects | Rules and check that the ―Alert Collection Rule‖ is enabled and has no
overrides.
4. In the Operations Manager Console, navigate to Administration | Security |User

Roles and verify that the SDK user is listed as an Operations Manager Administrator.
5. Ensure that you see Events in the non-Windows Events View (or any other
appropriate child view) as in our implementation. Note: Every Alert is first an Event;
no Event means no Alert. If you have followed the preceding steps, and have an
Event without an Alert, contact support2).
2
In the case of the Cisco solution, if you have enabled any item(s) in the CriticalInterfaces
tab, this could cause ―missing alerts‖ (which could intentionally be missing due to those
settings).
Page 86
Performance Records are Missing

Note: There are both Performance and Reporting records.
To check if performance or reporting records are missing
1. For Performance records, in the PerformanceMetrics tab of the Configuration Tool,

check that you have opted to produce Performance Records. For UNIX/Linux devices
performance records are always recorded (it is not optional); for most other
solutions you must select the Graph option.
2. For Reporting records, in the MOM OpsMgrGlobalVariables tab of the QMX

Configuration Tool, ensure that the g_boolWriteOpsMgrPerfMetricsToDWDB
Value box is selected.
3. Test the connection between the solution and the specified agent by right-clicking
the solution in the Configuration Tool and choosing Test connection.
4. Test the connection to the OpsMgr SDK, Management Pack, and non-Windows
Proxy(s) by opening the Tools menu and choosing Debug | Test Connection for
OpsMgr SDK.
5. Remove JalaSoft3 and/or Veeam management packs, if either is installed, as these
can occasionally block performance records from getting through.
6. Ensure that you are running Windows as an English operating system with a Regional
Setting of English. Running an English operating system with a Regional setting of
Czech will possibly create some performance records since some regional settings
use a comma instead of a period in a real number. For example, with a regional
setting of Czech, a percentage of ―10‖ will create a performance record whereas
―10,1‖ will not. Operations Manager expects ―10.1‖ not ―10,1‖. Change the regional
setting to English or contact support for a workaround.
SNMP Issues
To check SNMP issues
1. In the QMX Configuration Tool, check the DebugLog by right-clicking the solution and
choosing ―Show log‖.
3
Not necessary if you are running JalaSoft XIAN R2
Page 87
2. Check NT Event Viewer for warnings and errors, particularly the Application, non-
Windows, and Operations Manager Logs.
3. In the QMX Configuration Tool, check the solution‘s _Host tab to ensure it is setup to
allow GETs/TRAPs and that it is set to throw TRAPs to the box where the solution is
installed.
To receive the device Traps that get converted to Operations Manager 2007
alerts, QMX – Operations Manager 2007 requires the SNMP Trap
Community name and the SNMP Read Community name. This allows the
SNMP (Trap) solution to check connectivity between the computer on which
the QMX solution is installed and the target device (the Cisco Router, Switch,
Firewall, and so forth). The Write Community name is optional since the
QMX solutions do not perform SNMP SETs by default. The SNMP community
names are case sensitive and must match the name(s) contained in the
Windows SNMP Service‘s Security tab and in the device configuration.
4. Check that the Windows SNMP Service is running on the computer where you have
the QMX solutions installed and that it is set to start automatically. Also, in the QMX
Configuration Tool‘s Security tab, verify which IP or DNS names are allowed by the
Community Names. (Note: Community Names are case sensitive.)
5. Check that the Windows SNMP Trap Service is running on the computer where you
have the QMX solutions installed and that it is set to start automatically.
6. In Add or Remove Windows Components | Management and Monitoring

Tools | Details, check that WMI SNMP Provider is installed.
Page 88
7. In the Configuration Tool, verify that the Community Name(s) for the solution match
the Windows SNMP Service Community Name(s).
8. Verify that the SNMP GETs work:
a. In the Configuration Tool, right-click the solution and choose Test

Connection.
b. If the target is a physical device, use iReasoning (http://ireasoning.com) to

do a GET for sysDescription. If the target is not a physical device, use a valid
target Read-allowed OID. Or, you can use ―Walk‖.
c. Validate SNMP Device accessibility: Because SNMP requires that you configure
both the Windows side and the SNMP device side, Quest recommends using
NetMon4 since it can show traffic flows in either direction.
d. In the Configuration Tool, right-click the solution and choose Trace route if
you suspect a firewall might be blocking the port (port 161 is the default).
e. To run diagnostics on the monitored device, in the Configuration Tool, right-

click the solution and choose Run Diagnostics. Attach the output to a Quest
Support Case using Quest SupportLink at: http://support.quest.com.
9. Check to see if SNMP TRAPs work:

a. In the Configuration Tool, right-click the solution and choose Test
Connection.
b. In the Configuration Tool‘s _Host tab, check the solution‘s Read Community
names are valid. An Authentication TRAP may occur using an invalid Read
Community Name.
c. Validate that you can force a TRAP. Sometimes the device, application or
operating system has a TRAP test tool; sometimes restarting a service on the
remote node causes a TRAP; sometimes starting the Extension using an
invalid Read Community name and then doing a Test Connection forces a
TRAP; or alternatively wait for a period of time for a TRAP to occur.
d. Validate SNMP Device accessibility. Because SNMP requires that you configure
both the Windows side and the SNMP device side, Quest recommends using
NetMon since it can show traffic flows in either direction.
If a TRAP appears in NetMon that does not appear in the DOS Window
representing the TRAP Extension (that is, it does not appear as an expected
alert), then assuming you have already taken all the actions described in
‗Alerts are Missing‘, either install the WMI SNMP Provider, if it is not installed;
or, if it is installed, remove it and reinstall it. After either action, restart WMI,
the SNMP Service, the SNMP TRAP Service, and the Extension, in that order.
4
If NetMon does not start on a computer to which you are term-served into with the
―console‖ or ―admin‖ switch, log off and log back in without the switch set.
Page 89
e. In the Configuration Tool, right-click the solution and choose Trace route if
you suspect a firewall might be blocking port 162.
f. To run diagnostics on the monitored device, in the Configuration Tool, right-
click the solution and choose Run Diagnostics. Attach the output to a Quest
Support Case using Quest SupportLink at: http://support.quest.com.
Command Line Interface Issues

1. In the Configuration Tool, right-click the solution and choose Test Connection.
2. Validate that you can reach the remote device using either a Telnet or Putty (SSH)
session. If you can not reach the device, application, or operating system with those
tests, you will not be able to reach it with our Extensions. Check that you have the
right settings in the Configuration Tool for the Login Prompt, Password Prompt, and
that the Secure Connection checkbox is selected. When it is selected, that means
you will connect to the non-Windows host system using SSH; if it is not selected it
means you will connect by means of Telnet.
3. In the QMX Configuration Tool, check the DebugLog by right-clicking the solution and
choosing ―Show log‖.
4. To run diagnostics on the monitored device, in the Configuration Tool, right-click the
solution and choose Run Diagnostics. Attach the output to a Quest Support Case
using Quest SupportLink at: http://support.quest.com.
Checking the Quest QMX Base Framework Version

Before you call support, verify that you have the latest version of the Quest Base
Framework.
To verify your version of the Quest Base Framework
Page 90
2. From the Help menu, select Base Framework Version.
3. Compare your version with the latest Base Framework version at:
http://www.quest.com/quest-management-xtensions-operations-manager/release-
information.aspx.
4. Upgrade the Quest QMX Base Framework if you do not have the latest version.
Upgrading the Quest QMX Base Framework

You use the same Quest QMX Base Framework for all of the System Center products that
Quest supports.
Page 91
Quest recommends that you upgrade the Quest QMX Base Framework each
time you upgrade or download a new Extension. The Quest QMX Base
Framework is always evolving with new enhancements and bug fixes and it is
possible that an Extension might require functionality that does not exist in a
down-level Quest Base Framework.
To upgrade your Quest QMX Base Framework
1. Before you upgrade the Base Framework, save all .xml files so that you can restore
any customized variable settings once you have completed the upgrade:
a. Assuming that the Quest QMX Base Framework is installed on C:, copy all the
.xml files from C:\Program Files\eXc Software\WMI
Providers\nonWindows\Virtual Agent Library\MOM to C:\Program
Files\eXc Software\WMI Providers\nonWindows\Virtual Agent
Library\MOM\Backups.
Note: There will be an .xml file for each Global Variable tab that you see in
the QMX Configuration tool. For example, there will be an .xml file for the
_GlobalVariable.xml tab, the MOMGlobalVariables.xml tab, and the
OpsMgrGlobalVariables.xml tab:
2. Start the Configuration Tool.
Page 92
3. Stop any running Extensions.

4. On the MOM GlobalVariables tab, unselect the g_boolAutomaticallyStartVirtualAgents
and g_boolUseOpsMgrSingleton global variables, if they are selected, and click Save.
5. Close the Configuration Tool.
6. From the Start menu, navigate to the Control Panel |Add or Remove Programs
and remove the current version of Quest QMX Base Framework.
Older versions of Quest QMX Base Framework are called ―eXc Software
eXctender Event Provider for non-Windows...‖; newer versions are called
―Quest QMX base framework for Windows…‖.
7. Download and install the latest Quest QMX Base Framework from:
http://www.quest.com/quest-management-xtensions-operations-manager/software-
downloads.aspx.
a. Click Save to download the .zip file to a location of your choice.
b. Extract all the files from the .zip.
c. Double-click the .exe file to start the Setup wizard.
Note: You must install the latest Base Framework to the same directory as the
previous version so that existing Extensions will work properly.
8. Restore any customized variable settings you had before the upgrade.
a. Verify the values for the Global Variables by opening the
_GlobalVariable.xml file and the OpsMgrGlobalVariables.xml file that you
copied before you started (see step #1).
b. Compare the values for each variable in the .xml file to the corresponding
variables in both the GlobalVariable tab and the OpsMgrGlobalVariable tab in
the QMX Configuration Tool.
c. For Values that were overwritten by the upgrade, copy the values from the
.xml file and paste the content into the Value box of the Configuration Tool.
9. Restart the Windows Management Instrumentation service:
a. Right-click the My Computer icon on your desktop and select Manage.
b. Navigate to Services and Applications | Services.
c. Right-click Windows Management Instrumentation and select Restart.
d. Close the Computer Management window.
10. Start the Configuration Tool.
11. If you unselected the g_boolAutomaticallyStartVirtualAgents and
g_boolUseOpsMgrSingleton global variables on the MOM GlobalVariables tab in step
#4, re-select them and click Save.
12. Wait approximately 3-5 minutes for the non-Windows Proxy Discovery to complete
inside the Operations Manager Console.
13. Re-start the Extension(s).
Page 93
Upgrading Extensions
To upgrade Extensions
1. Before you upgrade an Extension, be sure to save all the .xml (configuration) files so
that you can restore your customized configuration files and scripts:
Providers\nonWindows\Virtual Agent Library\MOM\<Extension> to
C:\Program Files\eXc Software\WMI Providers\nonWindows\Virtual Agent
Library\MOM\<Extension>\Backups.
Quest recommends that you always keep backups of your .xml files.
2. Upgrade the Quest Base Framework. (See Upgrading the Quest QMX Base
Framework.)
Quest recommends that you upgrade the Quest QMX Base Framework each
time you upgrade an Extension. The Quest QMX Base Framework is always
evolving with new enhancements and bug fixes and it is possible that an
upgraded Extension might require functionality that does not exist in a down-
level Quest Base Framework.
4. In the MOMGlobalVariables tab, unselect the

g_boolAutomaticallyStartVirtualAgents checkbox, if it is enabled.
5. Stop the Extension you are upgrading. (See Starting an Extension.)

7. From the Start menu, navigate to the Control Panel | Add or Remove Programs
and remove the Extension you are upgrading.
Note: All Extension names begin with ―QMX Monitor_…‖.
8. Download and install the Extension. (See Install Extensions.)
9. Restore the customized configuration files and scripts:
Providers\nonWindows\Virtual Agent
Library\MOM\<Extension>\Backups to C:\Program Files\eXc
Software\WMI Providers\nonWindows\Virtual Agent
Library\MOM\<Extension>.
Page 94
Normally, when you restore the .xml files, your custom configuration
settings, such as thresholds, will work fine with the upgraded Extension.
However, in some cases where Quest has changed the .xml file format, your
custom scripts will not work in the new Extension. Before you restore the
.xml files, check the Extension download page for any special instructions
regarding what steps you need to take to restore your settings.
11. Re-enable the g_boolAutomaticallyStartVirtualAgents variable in the

MOMGlobalVariables tab.
12. Start the Extension.
Migrating From One Server to Another

To move from one server to another
1. Contact your Quest Sales Rep to obtain a new license key as the old one will not
work when you put the Base Framework on new machine.
2. From the Configuration Tool‘s Configuration menu, select Failover and set the Old
Server as QMX Failover Primary computer.
3. On New Server, select the MOM OpsMgrGlobalVariable tab‘s

g_boolDontDiscoverThisQMXProxy variable.
Page 95
4. From the QMX Failover dialog, set the New Server as the backup computer.
5. On the New Server, from the QMX Failover dialog, click Sync with Primary to copy
all QMX solutions from the Old Server to the New Server.
6. On the Old Server, select the g_boolDontDiscoverThisQMXProxy variable.

7. On the New Server, unselect the g_boolDontDiscoverThisQMXProxy variable.
Gathering Diagnostic Information

To Run Diagnostics on the monitored device
2. Navigate to System Center | MOM and select the Extension, such as LinuxSuSe.
Page 96
3. Right-click a device, such as sles1, and select Run Diagnostics.
A Windows Script Host dialog displays, ―Starting Diagnostics. Please wait. You will be
notified when Diagnostics are complete.‖
4. Click OK and wait for the ―Diagnostics Completed‖ notification.
To gather diagnostic information
2. Navigate to System Center | MOM and select the Extension, such as LinuxSuSe.
Page 97
3. Right-click a device, such as sles1, and select Clear Log.
The Show Log and Clear Log menu items are unavailable when no log file
exists. If Show Log is not available, proceed to the next step.
4. Right-click the device and select Start, to manually start the Extension.
5. Wait at least 10 seconds.

6. Right-click the device again and select Show log.
QMX - Operations Manager 2007 opens the Debug log in Notepad or in SMS Trace, if
it is set up.
Note: It continues to append diagnostic information to the log until you select Clear
log or until a QMX event rule clears it due to age or size.
WMI Tuning for Large Scale Implementations

If you plan to connect to more than 100 systems or any other devices or applications, Quest
recommends that you change the WBEM Property values. You use the Windows
Management Instrumentation Tester to reconfigure the ProviderHostQuotaConfiguration
property values.
Page 98
Windows Management Instrumentation (WMI) Tester, also called WBEMTest,

is a general-purpose tool for viewing and modifying WMI classes, instances,
and methods during the development of Windows Management
Instrumentation (WMI) providers and WMI applications.
To change the WBEM property values
1. In the GlobalVariables tab, unselect the g_boolAutomaticallyStartVirtualAgents

checkbox, if it‘s enabled.
Note: This flag indicates to System Center Operations Manager 2007 that it should
automatically start all enabled hosts within all the Extension folders.
2. In the Configuration Tool, right-click MOM and select Stop All to stop all the
Extensions that are running.
4. From the Start menu, select Run, enter wbemtest, and click OK.
5. In the Windows Management Instrumentation Test dialog, click Connect.
6. Enter root in Namespace box and click Connect.
7. Click Open Instance.

8. In the Get Object Path dialog, enter __ProviderHostQuotaConfiguration=@ and
click OK.
9. Select the Local Only checkbox.
10. Double-click the HandlesPerHost property.
11. Enter 409600 in the Value box and click Save Property.
12. Double-click the MemoryAllHosts property.
14. Double-click the MemoryPerHost property.
16. Double-click the ProcessLimitAllHosts property.
18. Double-click the ThreadsPerHost property.
20. Click Save Object.
21. Click Exit.

22. Restart the Windows Management Instrumentation service:
Page 99
a. Right-click the My Computer icon on your desktop and select Manage.
b. Navigate to Services and applications | Services.

c. Right-click the Windows Management Instrumentation and select
Restart.
d. Close the Computer Management window.
24. Re-enable the g_boolAutomaticallyStartVirtualAgents flag in the

MOMGlobalVariables tab.
Page 100
Getting Support
Contacting Quest Support
Joining the Community
Contacting Quest Support

Quest Support is available to customers who have a trial version of a Quest product or who
have purchased a commercial version and have a valid maintenance contract. Quest
Support provides around the clock coverage with SupportLink, our web self-service.
SupportLink http://support.quest.com
From SupportLink, you can do the following:
Quickly find thousands of solutions (Knowledgebase articles/documents).
Access FAQs
Download patches and upgrades.
Seek help from a Support engineer.
Update or view support requests.
View the Global Support Guide for a detailed explanation of support programs, online
services, contact information, and policy and procedures. The guide is available at
http://support.quest.com/pdfs/Global Support Guide.pdf.
When you contact Support please include the following information:
1. The software you are working with.
2. The versions you have installed.
3. The Windows versions you have installed: XP, 2003 Server, 2003 Server R2, and so
forth,
4. The name of your Microsoft System Center Operations Manager 2007 Contact.
5. How many non-Windows resources you are monitoring.
6. Any information you feel is appropriate about your System Center Operations
Manager 2007 environment or test lab setup.
Joining the Community

Get the latest product information, find helpful resources, and join a discussion with the
QMX - Operations Manager 2007 team and other community members at :
http://www.management-extensions.org/index.jspa.
Page 101
Appendix A – QMX 64-bit Instructions for SNMP

Extensions
Converting from MS-Access to MS-SQL
Setting up SQL Security for QMX access
Giving the Database SQL Server Access Rights
Converting from MS-Access to MS-SQL

The QMX SNMP Extensions for MOM/Operations Manager use a Microsoft Access database to
properly format SNMP Traps to display as MOM/Operations Manager alerts. Microsoft Access
uses a database driver called Jet. However, Microsoft did not port the Jet database driver
from 32-bit to 64-bit. Therefore, you need to port the MOM/Operations Manager Access
database to either Microsoft SQL Server Desktop Engine (MSDE) or SQL Express or
Microsoft SQL Server 2005 (or 2008). MSDE and SQL Express are free from Microsoft. All of
these versions of SQL have true 64-bit implementations.
Running on a SQL server that is on a different Windows computer than QMX

has security implications. If you are planning your QMX deployment, you
may want to consider installing the SQL server directly onto the same
Windows computer as where QMX is installed. Please read the section below
―Setting up SQL security for QMX access‖ before proceeding.
Every QMX SNMP MOM/Operations Manager Extension has a file in its root directory folder
named MessageFilterDB.mdb. This is the Microsoft Access database.
There are three methods of converting from MS-Access to MS-SQL:
Converting the database Using SQL
Converting the database Using SQL 2005 Express
Converting the Database Using Microsoft Access
Page 102
Converting the database Using SQL

You can convert Access MessageFilterDB.mdb from Access to SQL 2005 or 2008 using the
SQL Server Management Studio:
To convert the database using SQL
1. From the Start menu, navigate to All Programs | Microsoft SQL Server 2005 (or
2008) | SQL Server Management Studio:
2. Connect to the database.
Page 103
3. In SQL Server Management Studio, right-click Databases select New Database….
4. Enter the new Database name.
Note: The run-time logic of the Extension looks for a specific name for this
database. Its name must be the name of the folder where the SNMP
MOM/Operations Manager Extension resides with the suffix of
―_MessageFilterDBSQL‖. In this example, we are converting the
MessageFilterDB.mdb for the Novell eDirectory solution. The root directory folder
name for this solution is ―eDirectory‖. Thus, you must name this SQL database:
―eDirectory_MessageFilterDBSQL‖.
5. Click OK to save the new database.
Now that you have created the SQL database, it is time to import the data from the
Microsoft Access MessageFilterDB.mdb database.
To import data into the new database
1. Right-click the new database name.
2. Select Tasks | Import Data….
Page 104
The SQL Server Import and Export Wizard starts.
3. Click Next.
Page 105
4. Select Microsoft Access as the Data source.
5. Browse to select the new database you just created.
Page 106
6. Select the SQL Native Client for the Destination.
7. Enter the Database name.
8. Click Next.
Page 107
9. Select Copy data from one or more tables or views.
10. Click Next.
Page 108
11. Select Source and click Next.
Page 109
12. Select Execute immediately and click Next.
Page 110
13. Verify the choices you made in the wizard and click Finish.
Page 111
Converting the database Using SQL 2005 Express

You can convert Access MessageFilterDB.mdb from Access to SQL 2005 Express using the
SQL Server Management Studio as mentioned above or using SQL Express Management
Studio by following these steps:
To convert the database using SQL Express
1. From the Start menu, navigate to All Programs | Microsoft SQL Express | SQL
Server Management Studio:
Page 112
2. Connect to the database.
3. In SQL Server Management Studio, right-click Databases select New Database….
4. Enter the new Database name.
5. Click OK to save the new database.
Page 113
Now that you have created the SQL database, it is time to import the data from the
Microsoft Access MessageFilterDB.mdb database.
To import data into the new database

1. Navigate to the extension directory and open the eDirectory_MessageFilterDBSQL.sql
file. It will have the name of the extension you are working with, for example
Cisco_MessageFilterDBSQL.
Page 114
2. Click Open.
3. Click Execute.
Page 115
4. Close Management Studio.
Converting the Database Using Microsoft Access

If you have the full version of Microsoft Access on your 64-bit Operating System, you can
convert Access MessageFilterDB.mdb from Access to SQL 2005 using the Upsizing wizard.
To convert the database using Microsoft Access
1. Open the MessageFilterDB.mdb in the Extension root folder.
The Trap Editor opens by default.
Page 116
2. Click the red X in the upper right corner to close ―Trap Editor‖.
Page 117
To start the Upsizing Wizard
1. From the Tools menu, select Database Utilities | Upsizing Wizard.
Page 118
2. Select Create a new database and click Next.
Page 119
3. Match the name of the new SQL database you are about to create with the name of
the folder where the SNMP MOM/Operations Manager Extension resides. These must
match exactly!
Page 120
4. Click >> to export all the tables to SQL Server and click Next.
5. Select Indexes, Validation rules, Table relationships, and Use DRI.
6. Click Next.
Page 121
7. Accept the defaults and click Next.
8. Click Finish.
A progress bar displays while it up-sizes your database from Access to SQL. When it
is completed, expect to see the following error:
Page 122
9. This is acceptable; just click OK.
Setting up SQL Security for QMX access

After you have the QMX Extension database(s) defined in SQL, if your SQL server is running
on a different server than where QMX is running, you will need to give the system running
the QMX Extension(s) permission to access to the SQL database(s).
You can set the SQL Security either by using a DOS command or by using the SQL Server
Management Studio. The following is a step-by-step example of using DOS; an example of
using SQL Server Management Studio follows.
In this example we continue to work with the eDirectory Extension which determines the
exact name of the database. The domain name is MMS and the computer running QMX is
named WINDOWS2003. All of the commands add a ―$‖ to the end of the computer name.
Using DOS to Set Security Permissions

To assign security permissions using DOS
1. Open a DOS command prompt on the server running SQL.
Note: You must be logged into the server as a SQL administrator.
2. From the DOS command prompt, enter the following command:

Osql –E –S localhost
Page 123
3. At the Osql command prompt (in the screen shot above, it is ―1>‖), type:
a. CREATE LOGIN [MMS\WINDOWS2003$] FROM WINDOWS WITH

DEFAULT_DATABASE=[eDirectory_MessageFilterDBSQL]
b. Click Enter.
c. Type GO and click Enter.
Page 124
4. From the Osql command prompt, enter each of the following lines:
USE [eDirectory_MessageFilterDBSQL]
GO
CREATE USER [MMS\WINDOWS2003$] FOR LOGIN [MMS\WINDOWS2003$]
GO
USE [eDirectory_MessageFilterDBSQL]
GO
EXEC sp_addrolemember N‘db_datareader‘, N‘MMS\WINDOWS2003$‘
GO
exit
5. If you have SQL Server Management Studio installed you can verify the above steps
by navigating to Security | Logins and verify that the computer system running
the QMX solutions is listed in the Logins folder as shown below:
Page 125
Note: The computer name will have a $ appended at the end of it.
Using SQL Server Management Studio to Set Security Permissions

To accomplish the same procedure as explained above, you can also use SQL Server
Management Studio to set security permissions.
To assign security permissions using SQL Server Management Studio
1. From the Start menu, navigate to All Programs | Microsoft SQL Server
200[5|8] | SQL Server Management Studio.
2. Connect to the SQL instance where the database resides.
3. Create a new SQL login account for the Windows server running QMX – Operations
Manager as shown below:
Page 126
4. Associate the SQL login account to the database, as shown below:
Page 127
Giving the Database SQL Server Access Rights

After you have converted the Microsoft Access MessageFilterDB.mdb to SQL 2005, the new
SQL database is now ready to be accessed by the QMX Extension run-time logic. Now it‘s
time to modify the SNMP Extension script that accesses the SQL server. This script is named
CommonRoutinesSNMPVirtualAgent.js and is located in: C:\Program Files\Quest
Software\WMI Providers\nonWindows\Extension Library\MOM. Before you start you can
use SQL Server Management Studio (SQL 2005) to see the database:
Page 128
To modify the SNMP Extension script
1. Using the Windows Explorer, navigate to C:\Program Files\eXc Software\WMI

Providers\nonWindows\Virtual Agent Library\MOM.
2. Right-click the CommonRoutinesSNMPVirtualAgent.js script and select Edit.
3. Find the line where it says, ―XP64‖ (this is line number 22):
Page 129
4. Change ―XP64‖ to the name of your server that is running SQL.
Depending on the Service Principal Name(s) defined on your domain controller, you
might need to specify a fully qualified name here instead. For example, you might
need to specify XP64.MMS.COM instead of just XP64. If you are not sure, try the
short name first and then check the Extension log file to see if the database
successfully opens. If it did not, try using the fully qualified name.
Note: You can not use localhost.
5. Start the Extension and verify the Debug Log to ensure there are no errors when
connecting to the database.
Page 130
Appendix B - QMX on a Management Server

QMX – Operations Manager 2007 uses the System Center Operations Manager 2007 SDK
service to generate performance metrics for the non-Windows systems, devices, and
applications. Once you have installed the QMX components, you must configure the
authentication.
Note: Quest does not recommend these setup scenarios except for a proof-of-concept.
These set up scenarios are typically a single Windows computer (all in one) running all the
Operations Manager components which would not be appropriate for a production
environment.
There are four possible ways to configure authentication:
System Center Operations Manager 2007

SDK RunAs Account
QMX Installed on
LocalSystem Domain User
Account Account
System Center
Operations
Manager 2007
Valid Valid
Root
Management (Scenario A) (Scenario B)
Server (RMS)
System Center
Operations
Manager 2007
Agent
Not valid Valid
1
(Scenario D ) (Scenario C)
1
You cannot run the System Center Operations Manager 2007 SDK as the
LocalSystem Account on the Root Management Server and run QMX -
Operations Manager 2007 on a System Center Operations Manager 2007
Agent system. Thus, the Scenario D configuration is not possible. Scenario A
requires the least amount of configuration.
Page 131
Note: Please keep in mind that the System Center Operations Manager 2007 architecture
defines only one SDK service which always runs on the Root Management Server (RMS):
A. Install the QMX - Operations Manager 2007 solution (Quest QMX Base Framework
and Extensions) directly on the System Center Operations Manager 2007 Root
Management Server (RMS) and run the System Center Operations Manager 2007
SDK service as the LocalSystem Account.
Note: The LocalSystem account is a predefined local account used by the service
control manager. It has extensive privileges on the local computer, and acts as the
computer on the network.
B. Install the QMX - Operations Manager 2007 solution (Quest Base Framework and
Extensions) directly on the System Center Operations Manager 2007 Root
Management Server (RMS) and run the System Center Operations Manager 2007
SDK service as a domain user account.
Note: A domain user account enables the service to take full advantage of the
service security features of Microsoft Windows and Microsoft Active Directory Domain
Services.
The following sections explain the Scenario A and B setup scenarios.
Authentication Setup Scenario A

Authentication Setup Scenario A is where QMX - Operations Manager 2007 is installed on
the System Center Operations Manager 2007 Root Management Server and the System
Center Operations Manager 2007 SDK RunAs Account is LocalSystem.
Create a Domain Computer Group

Add Computers to the Domain Computer Group
Associate the Domain Computer Group
Configuring Global Variables for Scenario A
Create a Domain Computer Group

To create a new domain computer group
From a system in which you can administer the domain where System Center Operations
1. Navigate to Start | Control Panel | Administrative Tools | Active Directory

Users and Computers.
the domain.
Page 132
3. Right-click Computers and choose New | Group to create a new computer group.
4. Enter QMXcomputers in the Group name box.
Page 133
Note: You can use any name, but for the purposes of this example, we have used
QMXcomputers.
Add Computers to the Domain Computer Group

To add computers to the domain computer group
1. Right-click QMXcomputers and select Properties to add the computer(s) that will
run the Quest Base Framework to the newly created domain computer group.
3. In the Select users, Contacts, or Computers dialog, click Object Types.
Page 134
4. Select Computers, unselect the other options, and click OK.
5. Enter computer name(s) of system(s) running QMX - Operations Manager 2007 and
click OK. In this example it is OM07RMS.
Page 135
6. Click OK.
Associate the Domain Computer Group

Once you have created the QMXcomputers Active Directory Computer Group and have
added the computer(s) that will run the Quest Base Framework to it, you must associate
this domain computer group with the System Center Operations Manager 2007
Administrator user role.
To associate the domain computer group with the Operations Manager

Administrators user role
Page 136

Properties.
Page 137
4. Click Add to add a group to the user role.
5. Enter the newly created group name, such as ―QMXcomputers‖ and click OK.
6. Click OK at the User Role Properties dialog and return to the Operations Console.
Root Management Server.
Restarting the SDK Service

1. Right-click the My Computer icon on your desktop and select Manage.
Page 138
3. Right-click the OpsMgr SDK Service and select Restart.
4. Close the Computer Management window.
Base Framework using the Configuration Tool.
Configuring Global Variables for Scenario A

To configure global variables for authentication setup Scenario A
1. Start the QMX Configuration Tool on the Root Management Server.
Page 139
2. Expand the System Center folder and select MOM.
4. For Scenario A, change the System Center Operations Manager 2007 global variables
as follows:
Page 140
a. g_strMOMManagementServerName - In Scenario A, leave this value as ―.‖

This is equivalent to localhost. This value is the NetBios name of the System
Center Operations Manager 2007 Root Management Server where the SDK
Service is running.
b. g_strMOMServerDomainName - Enter the domain name where the System
Center Operations Manager 2007 Root Management Server is running.
c. g_strMOMUserId - In Scenario A, leave this value blank.

d. g_strMOMPassword - In Scenario A, leave this value blank.
5. Click Save.
You are now ready to configure the Extensions. (See the "Configure the Extension‖ section.)
Page 141
Authentication Setup Scenario B

Authentication Setup Scenario B is where QMX - Operations Manager 2007 solution is
installed directly on the System Center Operations Manager 2007 Root Management Server
(RMS) and the System Center Operations Manager 2007 SDK RunAs Account is a Domain
User Account.


Before you start, make note of the SDK Service User name. You‘ll need that information
later in the process.
To identify the SDK Service User
7. From the Operations Manager 2007 Root Management Server, right-click the My
Computer icon on your desktop and select Manage.
Page 142
9. Right-click OpsMgr SDK Service and choose Properties.
10. Select the Log On tab.
Page 143
Note: The user account in the This account box. In this example it is ommssdka.
11. Close the OpsMgr SDK Service Properties dialog.
12. Minimize the Computer Management window for now.

To create a new domain user group
From a system from which you can administer the domain where System Center Operations
7. From the Start menu, navigate to Control Panel | Administrative Tools | Active
Directory Users and Computers.
the domain.
Page 144
9. Right-click Users and choose New | Group to create a new user group.
Page 145
10. Enter a name for the Domain User Group in the Group name box.
Note: You can use any name, but for the purposes of this demonstration, use
QMXusers.
12. Leave the Active Directory Users and Computers window open for the next task.
Page 146

To add the SDK service user to the domain user group
7. Right-click the name for the Domain User Group you just created (QMXusers in this
example) and select Properties to add the user(s) that the Operations Manager
2007 SDK Service runs as to the newly created domain user group.
Page 147
9. In the Users, Contacts, or Computers dialog, ensure that Users or Users or Other
objects are in the Select this object type box.
Page 148
10. Enter the SDK Service User Name in the Enter the object names to select box and
click OK. For the purposes of this example, enter ommssdka, the SDK Service User
name you made note of in Identify the SDK Service User.)
11. Click OK.

Once you have created the QMXusers Active directory Users Group and have added the
Operations Manager SDK Service User to it, you must associate this domain user group with
the System Center Operations Manager 2007 Administrator user role.
Page 149
To associate the domain user group with the Administrator user role
Properties.
Page 150
11. Click Add to add a member to the user role.
12. Enter the Domain User Group name you just created (QMXusers in this example) and
click OK. (See Create a Domain User Group.)
Page 151
13. Click OK and return to the Operations Console.
Root Management Server. (See Restarting the SDK Service for instructions.)
Base Framework using the Configuration Tool.

Before you configure the Global Variables you must encrypt the UserID and Password for
the SDK Service User you just created. (See Encrypting the UserID and Password).
Setting the Global Variables for Scenario B

To configure global variables for authentication setup Scenario B
1. In the Configuration Tool expand the System Center folder and click MOM.
Page 152
3. Set the System Center Operations Manager 2007 global variables for Scenario B:
a. g_strMOMManagementServerName - Leave this value as ―.‖ This is

equivalent to localhost. This value is the NetBios name of the System Center
Operations Manager 2007 Root Management Server where the SDK Service is
running.
b. g_strMOMServerDomainName - Enter the domain name where System

Center Operations Manager 2007 Root Management Server is running. In this
example it is ACME.
c. g_strMOMUserId - Click the three-dot Browse button and navigate to the

SDK Service User Name encryption file you created in Encrypting the UserID
and Password.
This is the domain UserID running the System Center Operations Manager
2007 SDK service on the Root Management Server. In this example it is
SDKuser.txt.
Providers/nonWindows/Encryption/SDKuserId.txt.
d. g_strPassword - Click the three-dot Browse button and navigate to the

SDK Service User Password encryption file you created in Encrypting the
UserID and Password.
Page 153
This is the Password for domain UserID running the System Center
Operations Manager 2007 SDK service on the Root Management Server. In
this example it is SDKuserPassword.txt.
Note: You must specify this value as an encrypted file.

4. Click Save and watch for the ―OpsMgrGlobalVariables successfully saved to disk‖
message.
You are now ready to configure the Extensions. (See the ―Configure the Extension‖ section.)
Page 154

QMXom07 InstallGuide 400505

Transféré par

Informations du document

Description originale:

Titre original

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

QMXom07 InstallGuide 400505

Transféré par

Droits d'auteur :

Formats disponibles

Quest Management Extensions

Operations Manager 2007 Edition

Unleash the Power of System Center Operations Manager 2007 for

© 2009 Quest Software, Inc. ALL RIGHTS RESERVED.

Identify the SDK Service User .............................................................................. 35

Upgrading Extensions ............................................................................................ 94

About this Guide

Product Name Change

About Quest System Center Solutions Group

About Quest Software, Inc.

Contacting Quest Software, Inc.

Mail Quest Software, Inc.

Web site www.quest.com

Join the Community

Introducing QMX - Operations Manager 2007

If you do not understand how the system, device, or application interacts

What is an Agentless Solution?

Quest Agentless Solutions Are Open Source

How Agentless Extensions Work

At a minimum, Quest solutions can:

create alerts and performance records from Extension data.

MVS/ZOS Extension for MOM/Operations Manager 2007

In a test environment or small production environment, you can run QMX -

Running QMX - Operations Manager 2007 on an OpsMgr agent-managed computer allows

About Your Trial Version

SoftwareLicense002: Running in trial mode.

SoftwareLicense003: Running in trial mode (about to expire).

SoftwareLicense006: Trial period has expired.

SoftwareLicense007: Software license has expired.

SoftwareLicense008: Error occurred processing the Software license.

Licensing QMX for Production Use

Estimating Hardware Requirements

Typical System Specifications

Operating System 64-bit

Run-time4 600 seconds

Memory utilization hovered around 20% (6.5 Gigs).

Running Large Scale

26.5 Gigs (83%) which is not a problem.

Quest does not recommend running QMX solutions in a Virtual environment

System Software Requirements

o Operations Manager Console (See Install the MS Operations Manager

o Microsoft SQL1 for 32-bit systems (optional) or 64-bit systems (required)

Installing the Windows SNMP Services

To install the SNMP components

1. From Start menu, navigate to Control Panel | Add/Remove Programs.

To customize the SNMP Service

1. Right-click your My Computer icon on your desktop and select Manage.

3. Double-click the SNMP Service.

5. Right-click your My Computer icon on your desktop and select Manage.

6. Navigate to Computer Management | Services and Applications | Services.

8. Restart (or Start) both services.

Install the Operations Manager Components

Install the MS Operations Manager Agent

Install the MS Operations Manager Console

To install System Center Operations Manager 2007 Operations Console

2. Double-click SetupOM.exe to start the Installation Wizard.

3. Click Install Operations Manager 2007.

Install the MS Operations Manager Agent

To install the System Center Operations Manager 2007 Agent

2. Ensure that this computer shows up in the Operations Console under

Install the QMX Components

Import the Quest Management Pack