Quest® Management Xtensions - Configuration Manager 2007 Edition

Version 2.2

Release Notes

September 2009

 

Contents

Welcome to QMX - Configuration Manager 2007 Edition

New in this Release

Resolved Issues and Enhancements

Known Issues

Third-Party Known Issues

System Requirements

Global Operations

Getting Started

For More Information

 

Welcome to QMX - Configuration Manager 2007 Edition

Quest® Management Xtensions - Configuration Manager 2007 Edition (QMX - Configuration Manager 2007) is comprised of an Unix, Linux, or Mac OS X Agent installed on a managed host and extensions to the Configuration Manager Console.

The QMX - Configuration Manager 2007 Agent is designed to work and act like the Microsoft® System Center Configuration Manager 2007 Client. It is based on OpenWBEM, a Unix-based implementation of WBEM/CIM standards (defined by the DMTF) just as WMI is a Windows-based implementation of the same standards.

Through the use of the Configuration Manager Console extensions, the managed Unix, Linux, or Mac OS X systems work much the same as the Windows systems. They show up in collections, the hardware and software information is exposed by means of the Resource Explorer, the data works in standard reports, and so forth.

 

Back to Top

New in This Release

New Features since the release of QMX - Configuration Manager 2007 2.1:

  1. Support for New Microsoft Solution Releases

  2. New Platform Support:

  3. Platform Deprecation:

    QMX - Configuration Manager 2007 2.2 no longer supports the following platforms which have reached their End of Life because the OS vendor themselves no longer support them:

  4. New Features and Enhancements:

    1. Software Distribution Wizard Enhancements:

      • Distribute Upgrade Packages. By default, the QMX Software Distribution Wizard now allows you to distribute Upgrade Packages if a previous version of the software is already installed.

      • Custom Command Line. The RPM package type dialog now allows you to edit the command line.

      • New Design on Package Type Dialogs. The AIX InstallP package type dialog allows you to choose Installp package files rather than Browse for them.

      • Help Buttons were added to the Software Distribution Wizard. Quest has made the Administrator's Guide Help available to the end user by adding Help buttons to the Software Distribution Wizard.

    2. Six New Columns in the Queries. QMX has added six new columns in the Queries that provide additional information about Hardware and Software Inventory:

      • SMS Assigned Sites

      • IP Addresses

      • IP Subnets

      • Operating System Name and Version

      • Last Logon User Domain

      • Last Logon User Name

    3. Four New clienttool Options:

      QMX has added four new clienttool options to help you troubleshoot:

      • --disable-software-metering - Provides the ability to disable metering by setting the umi.metering_poll_interval to 0. Note: You must restart the Agent after running this option.

      • --enable-software-metering [arg] - Provides the ability to enable metering by setting the umi.metering_poll_interval to [arg] seconds. (The default is 10.) Note: You must restart the Agent after running this option.

      • --set-custom-inventory-timeout <arg> - Sets the maximum runtime (timeout) for custom inventory scripts to [arg] seconds (default is 60 seconds). This is for hardware inventory NOIDMOF scripts and for scripted software inventory

      • --check-client - Troubleshooting tool that checks the format of the settings in the qmxcm.conf file and validates the directory permissions, basic CIMOM functionality, and MP (or MP Proxy) connectivity to ensure the QMX Agent is functioning properly.

    4. Single Sign-On for Remote Tools. Quest has enhanced the Remote Tools chapter of the Administrator's Guide by adding the procedure for how to enable single sign-on for Remote Tools.

    5. VAS 3.5.1 Support. QMXcm 2.2 installs the latest release, VAS 3.5.1, a maintenance release that rolls up all the fixes since 3.5.0 shipped last November

    6. Troubleshooting Scripts Available. Quest has included four utility scripts for your convenience at the root of the distribution media in the /scripts directory:

      • Detach.sh allows Software Distribution to finish before it attempts to restart the Agent.

      • disable_software_metering.sh allows you to disable software metering which could help to reduce CPU usage on your system.

      • reenable_software_metering.sh allows you to re-enable software metering.

      • snapshot.sh helps you perform troubleshooting tasks.

    7. Enhanced Software Inventory:

      Quest has enhanced the software inventory processes in two ways:

      • Product Details now includes data that was previously only collected by means of the Software Inventory rules. Previously the Hardware Inventory scan only put data in the Add/Remove Programs node. Now, Hardware Inventory does two scans: one for the Add/Remove Programs information and the other for Product Details.

        Because the Product Details data is now automatically placed in the Resource Explorer's Software node, standard Software Inventory reports report data without the need to create Software Inventory rules. (Note: File Details are not captured in Hardware Inventory scan, so you may need to create additional Software Inventory rules to report File Details not captured in Add/Remove Programs.)

      • Directory-based Matching. Software Inventory now allows you to create Non-Windows Inventory Collection rules to search for directory names in addition to filenames. This is useful for matching Mac OS X applications such as iCal.app which is a directory name. Note: Due to the nature of directories, Product Details are not typically available.

 

Back to Top

Resolved Issues and Enhancements

The following is a list of issues addressed and enhancements implemented in this release of QMX - Configuration Manager 2007 Edition.

Resolved an issue where software distribution failed on packages with spaces in the name (applies only to .pkg distributions).
N/A QMX Menu Options Are No Longer Available for Windows. Resolved an issue where Remote Tools and Distribute Non-Windows actions were available for Windows systems. These options are now only available for supported non-Windows platforms.
CR #16233 License Allocations Are Calculated Properly. Resolved an issue where QMXcm was counting obsolete clients against license allocations. QMXcm 2.2 now only allocates licenses to active clients.
CR #16358 Policy Updates Manage Indication Filters Properly. Resolved an issue where QMXcm failed to create, delete, or update indication filters properly. Now, QMXcm 2.2 updates indication filters every time it does a policy update
CR #16730 SW Distribution Wizard Allows Command Line Edition. QMXcm 2.2 allows you to edit the command line when distributing RPM packages with the Software Distribution Wizard. This not only allows you to specify more options, but also makes it possible for you to use the Wizard for upgrades.
CR #17013 MP Proxy Installs When the SQL Database is Not on the Site Server. Resolved an issue where the MP Proxy installer could not validate the certificate because it was looking on the SQL server instead of the Site Server for that information.
CR #17048 SSL Sockets Close Properly. Resolved an issue where Discovery, Software Distribution, etc. failed because QMXcm did not close SSL sockets under certain conditions.
CR #17097 Removing Console Extensions No Longer Removes the MP Proxy. Resolved an issue where removing the 2.1.0 Console Extensions to do an upgrade to 2.2 also automatically removed the MP Proxy, forcing you to reinstall the MP Proxy. QMX - Configuration Manager 2.1.1 fixed this issue so that removing the QMX Console Extensions no longer uninstalls the MP Proxy.
CR #17199 Software Metering Reports Domain Information Properly. Resolved an issue where Software Metering Reports were not reporting Domain information properly for Active Directory users. QMXcm 2.2 now reports the FullUserName@DomainName for all Active Directory users.
CR #17132 Mac Collections and Queries Now Display x86 systems. Resolved an issue where Mac Collections and Queries were not showing Mac 10.4 x86-64, and Mac 10.5 x86-64 clients. Note: You must now delete the old Collections and Queries and replace them with the revised Collections and Queries for this fix to take effect.
CR #17267 The Agent, when running in Mixed Mode, no longer requires an FQDN for the host. Resolved an issue where policy update required the host to have a resolvable FQDN. Now, when requesting a policy update, QMXcm sends up a resolvable FQDN, if it is available; otherwise, it uses the short name.
CR #17426 MP Proxy Now Installs on a Secondary Site Proxy Management Point. Resolved an issue where the QMX MP Proxy wouldn't install on a Secondary Site Proxy Management Point.
CR #17614 Upgrade Does Not Change the Port Number. Resolved an issue where the upgrade procedure reset the port to the default of 80.
CR #17638 Mac OS X 10.5 Servers are no longer listed in the "All Mac OS X Desktop x86 Systems" collection. Fixed the "All Mac OS X Desktop x86 Systems" collection so it does not include the 10.5 Server systems. Note: You must now delete the old Collections and Queries and replace them with the revised Collections and Queries for this fix to take effect.
CR #17692 Software distribution no longer fails when a space is in the name (Mac-specific).

 

Back to Top

Known Issues

The following is a list of issues known to exist at the time of QMX - Configuration Manager 2007 Edition 2.2 release.

 

Client

CR#17091 QMX - Configuration Manager 2007 2.2 automatically installs a VAS 3.5.1 client to extend the identity management capabilities of Microsoft Active Directory to non-Windows systems. However VAS 3.5.1 (or earlier) does not support Mac OS X 10.6. Therefore, if you are running QMX - Configuration Manager on a Mac OS X system, you must uninstall VAS before you upgrade to Mac OS X 10.6.

 

Back to Top

Third-Party Known Issues

The following is a list of third-party issues known to exist at the time of QMX - Configuration Manager 2007 2.2 release.

 

Client

CR#33296 Client reports only one processor on ESX Server 3.0.0 system with multiple CPUs. This is an issue with ESX 3.0.0 that is fixed with ESX 3.0.1.
Workaround: Upgrade to ESX 3.0.1 or higher.

Discovery

CR#44272 SMS Active Directory Discovery method cannot collect VAS-enabled machines. Thus, QMX for SMS added the Active Directory discovery component in the Client Installation wizard to work around this problem with the SMS Active Directory Discovery Agent.
If enabled, SMS's native Active Directory System Discovery Agent reports a warning message in System Status (Systems Status | Site Status | [site code-name] | Component Status) similar to the following example when it cannot recognize a VAS-enabled machine:

=============================================================================

SMS Active Directory System Discovery Agent reported errors for n objects. DDR's were generated for 0 objects that had errors while reading non-critical properties. DDR's were not generated for 9 objects that had errors while reading critical properties.
Possible cause: The SMS Service might not have access to some properties of this object. The container specified might not have the properties available.


Solution: Please verify the Active Directory schema for properties that are not replicated or locked. Refer to the discovery logs for more information.

=============================================================================

(Note: The n objects is a number of VAS-enabled machines.)
You can ignore this message. It is not an error condition in QMX for SMS. The SMS Active Directory Discovery service is an SMS component. When it sees a VAS-enabled computer in Active Directory, it doesn't add it to the collection, instead it outputs a warning message similar to the one in the above example.

Hardware Inventory

CR#25347 Resource Explorer does not show Install Date for Sun patches in "Add/Remove Programs".
Reason: Sun does not provide this data.
CR#25524 Resource Explorer does not collect information about Keyboard and Pointing Devices in RHEL 2.1 when x11 is not installed on the system.
Reason: QMX - Configuration Manager 2007 relies on x11 to collect the data.

Installation

CR#28524 You can join sparse-root zones to Active Directory if the sparse-root zone does not share /opt, /etc, or /var with the Global Zone.
Note: If you do not have the sparse-root zone configured properly, do not select the Join Unix clients to Active Directory by using vastool option during installation. This will cause the installation to fail.
If you are installing QMX - Configuration Manager 2007 into a sparse-root zone where /usr/lib is shared read-only and later want to use VAS, you will have to configure PAM. (Please refer to the VAS documentation on how to configure PAM properly.)
Reason: VAS
CR#31990 When you delete QMX - Configuration Manager 2007 from a SLES 10 machine and try to reinstall it, the installation fails because it cannot create owcimomd group. This is because it was not deleted properly and is still in the system cache. This issue only occurs if system is joined to Active Directory with VAS.
Workaround: wait for about an hour or just reboot the machine before the next installation attempt.
CR#32651 When a client is un-joined from Active Directory, its Kerberos ticket becomes invalid in the Windows cache preventing Single Sign-On from working in the Client Installation Wizard. This disables any other functionality that relies on Single Sign-On. Single Sign-On will be broken for several hours, until the invalid ticket expires. After installation you will be able to use Single Sign-On.
Workaround: Logoff/Logon on Windows side or run the klist.exe utility to remove the invalid ticket.

Software Inventory and File Collection

CR#25256 Wrong slash in the path name. The reverse slash (\) is used in the file path in the Resource Explorer under Software | Collected Files.
Reason: Resource Explorer

 

Back to Top

System Requirements

  • System Center Configuration Manager 2007 Requirements:

  • QMX Requirements

    • Management Point

      • System Center Configuration Manager 2007 SP1, SP2, and R2

      • Windows Server 2003 (including R2) 32-bit and 64-bit (for Mixed mode only.)

        Note: In native mode, QMX - Configuration Manager 2007 Management Point Proxy supports only Windows Server 2003 32-bit.

      • Windows Server 2008 SP1 and SP2 32-bit and 64-bit; and R2

      • IIS 6 or IIS 7

    • Configuration Manager Console Requirements

      • Windows XP, Windows 7

      • Windows Server 2008 SP1 and SP2 32-bit and 64-bit; and R2

      • 10 MB of available hard disk space

      • Display resolution of 1024x768 or greater

    • Native Mode Requirements

      • System Center Configuration Manager 2007 SP1

      • IIS 6 or newer configured to run 32-bit ASP.net applications.

      • .NET framework 2.0

      • Visual Studio 2005 SP1 C++ Runtime Libraries

      • Management Point API

      • ASP.NET

  • QMX - Configuration Manager 2007 Agent Requirements:

    • CD-ROM drive (for attended installation)

    • Minimum system requirements

      • Platform: 400 MHz or higher CPU

      • Memory: 256 MB or more recommended

      Platform Processor Version Supported /opt/quest Space /var Space1 /etc Space /tmp Space2 Memory Approx. Total Installed Size
      Apple Mac OS X 5 PPC Server & Desktop 10.4, 10.5 190 MB 22 MB + 40 MB for logs 1 MB 160 MB 256 MB ~250 MB
      Apple Mac OS X x86 Server & Desktop 10.4, 10.5, 10.6 190 MB 11 MB + 40 MB for logs 1 MB 160 MB 256 MB ~250 MB
      CentOS x86 & x86-64 4.0 & 5.0 80 MB 11 MB + 40 MB for logs 1 MB 64 MB 256 MB ~130 MB
      Hewlett Packard HP-UX PA-RISC 11i, 11i v2 (11.23), v3 (11.31) 190 MB 10 MB + 40 MB for logs 1 MB 140 MB 256 MB ~240 MB
      Hewlett Packard HP-UX Itanium 11i v2 (11.23), v3 (11.31) 190 MB 10 MB + 40 MB for logs 1 MB 140 MB 256 MB ~240 MB
      IBM AIX PPC/POWER 5.1, 5.2, 5.3, 6.1 560 MB 10 MB + 40 MB for logs 1 MB 800 MB 256 MB ~610 MB
      Red Hat Enterprise Linux (RHEL)5 x86 & x86-64 AS/ES/WS & Desktop 3.0, 4.x 80 MB 11 MB + 40 MB for logs 1 MB 64 MB 256 MB ~130 MB
      Red Hat Enterprise Linux (RHEL) x86 & x86-64 Server & Desktop 5.x3 80 MB 11 MB + 40 MB for logs 1 MB 64 MB 256 MB ~130 MB
      SUSE Linux Enterprise Servers (SLES)5 x86 & x86-64 9, 10, 11 80 MB 15 MB + 40 MB for logs 1 MB 64 MB 256 MB ~135 MB
      SUSE Novell Linux Desktop x86 & x86-64 9 80 MB 15 MB + 40 MB for logs 1 MB 64 MB 256 MB ~135 MB
      SUSE Linux Enterprise Desktop (SLED) x86 10 & 11 80 MB 22 MB + 40 MB for logs 1 MB 64 MB 256 MB ~140 MB
      SUSE Linux Enterprise Desktop (SLED) x86-64 10 & 11 80 MB 15 MB + 40 MB for logs 1 MB 64 MB 256 MB ~135 MB
      Sun Solaris SPARC 8, 9, 10 240 MB 11 MB + 40 MB for logs 1 MB 160 MB 256 MB ~300 MB
      Sun Solaris x86 9, 10 240 MB 11 MB + 40 MB for logs 1 MB 160 MB 256 MB ~300 MB
      VMware ESX4 & 5 x86 3.0.x, 3.5 80 MB 10 MB + 40 MB for logs 1 MB 64 MB 256 MB ~130 MB


      Note1: Files in /var will grow as new policy is downloaded and data is collected, and so forth. Quest recommends that you allocate sufficient space to the /var filesystem to assure enough space to store package files during software distribution.

      Note2: You can choose /tmp or another directory of your choice for temporary files. Temporary Space is only used when the Agent Installation Wizard installs QMX - Configuration Manager 2007 on the target client machines.

      Note3: The AS, ES and WS variants provided by prior releases of Red Hat Enterprise Linux are not available for version 5. Replacements for all these products are provided with version 5. (see http://www.redhat.com/rhel/ for more information.)

      Note4: QMX - Configuration Manager 2007 supports running inside any VMware virtual machine guest operating system that is one of the QMX - Configuration Manager 2007 supported operating systems. See the QMX - Configuration Manager 2007 Administrator´s Guide for information regarding limitations to running Hardware Inventory in a virtual environment.

      Note5: QMX - Configuration Manager 2007 2.2 no longer supports the following platforms which have reached their End of Life:

      • Apple Mac OS X PPC 10.3

      • Red Hat Enterprise Linux x86 AS/ES 2.1

      • SUSE Linux Enterprise Server (SLES) x86 8

      • SUSE Linux Standard Server x86 8

      • VMware ESX x86 2.5x

  • Patch-level Requirements:

    Before you begin the installation make sure that you have the latest patches for your operating system version. The following is a list of required patch levels:

            AIX 5.1: Maintenance level 4 (5100-04) and 9

            AIX 5.2: Maintenance level 4 (5200-04)

            AIX 5.3: Maintenance level 1 (5300-01)

            HP-UX: Patch PHSS_35379

            HP-UX: Patch PHCO_35732

            Solaris 8: Patch 110934-05, 110380-04, 108993 and 111368-01

            Solaris 9 SPARC: Patch 117480, 113713-04, 112874-37 or greater, and 113319-22-1

            Solaris 9 x86: Patch 114568-24 and 114432

            Solaris 10: Patch 120664

    Quest recommends that you keep each platform up to date with the recommended patch set for that platform.

  • Remote Tools:

    You must have an X Server running in order to launch some X-based tools. A Windows-based X Server enables the UI to show the Unix tools on your Windows desktop. Some choices might be StarNet X-Win32 X Window Server, a platform-independent, network-transparent windowing system that provides a client/server interface between display hardware and the desktop environments. Or, you might use Cygwin/XFree86, an open-source implementation of the X Window system. There is also a WRQ Reflection product. However, Quest cannot provide support for any of these third-party products.

For additional platform support, please contact Sales@Quest.com

 

Back to Top

Global Operations

This product was not tested for international operation. Only U.S. English configurations of this product and U.S. English datasets are supported. Non-ASCII characters and/or non-English configurations have not been tested and this product should not be used in these environments. For specific support information, contact Quest customer support.

 

Back to Top

Getting Started

Contents of the Release Package

The QMX - Configuration Manager 2007 Edition release package contains the following:

Installation Instructions

Installation procedures for the products and packages included in this release are documented in the Install Guide, as found in the \docs directory at the root of the installation media.

 

Back to Top

For More Information

Contacting Quest Software:

Email info@quest.com
Mail Quest Software, Inc.
World Headquarters
5 Polaris Way
Aliso Viejo, CA 92656
USA
Web

http://www.quest.com

Refer to our Web site for regional and international office information.

Contact 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. Visit SupportLink at http://support.quest.com.

From SupportLink, you can do the following:

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: Global Support Guide.


Get the latest product information, find helpful resources, and join a discussion with the QMX - Configuration Manager 2007 Quest team and other community members at: Community Forum.

 

Back to Top

© 2009  Quest Software, Inc.

ALL RIGHTS RESERVED.

 

This document 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
Email: legal@quest.com

Refer to our website for regional and international office information.

 

Trademarks

Quest, Quest Software, the Quest Software logo, Aelita, AppAssure, Benchmark Factory, Big Brother, DataFactory, DeployDirector, ERDisk, Fastlane, Final, Foglight, Funnel Web, I/Watch, Imceda, InLook, IntelliProfile, Internet Weather Report, InTrust, IT Dad, JClass, Jint, JProbe, Knowledge Xpert, LeccoTech, LiteSpeed, LiveReorg, Matrix Insight, Matrix.Net, MIQ, NBSpool, NetBase, Npulse, PerformaSure, PL/Vision, Quest Central, RAPS, SharePlex, Sitraka, SmartAlarm, Speed Change Manager, Speed Coefficient, Spotlight, SQL Firewall, SQL Impact, SQL LiteSpeed, SQL Navigator, SQLab, SQLGuardian, SQLProtector, SQL Watch, Stat, Stat!, StealthCollect, Tag and Follow, Toad, T.O.A.D., Vintela, Virtual DBA, Xaffire, and XRT are trademarks and registered trademarks of Quest Software, Inc in the United States of America and other countries. Other trademarks and registered trademarks used in this guide are property of their respective owners.

 

Third-Party Contributions

This product includes software developed by the following third-parties:

Component License or Acknowledgement
Berkeley DB 4.1.25 BSD 4.4 License Text
Boost 1.33.1 Boost Software License 1.0
Boost 1.34.1 Boost Software License 1.0
libgcc_s 4.1.1 Libgcc_s 4.1.1
Libstdc++ 4.1.1 Libstdc++ license
OpenSSL 0.9.8d OpenSSL
PuTTY .60 MIT 1.0
zlib 1.2.3 zlib 1.2.3

 

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.

 

Back to Top