Quest® Management Xtensions for SMS
Version 1.6
Release Notes
December 2007
Welcome to Quest® Management Xtensions for SMS
Resolved Issues and Enhancements
QMX for SMS is comprised of a Unix, Linux, or Mac OS X Client (the Client) which is installed on the managed hosts and extensions to the SMS Administrator Console.
The Client is designed to work and act like the SMS Advanced 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 SMS 2003 Administrator 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 SMS reports, and so forth.
New Features in Quest® Management Xtensions for SMS 1.6
New Platform and Environment Support
HP-UX 11.23 (Itanium)
HP-UX 11.31 (PA-RISC and Itanium)
Mac OS X 10.5
Solaris 9 (x86)
Solaris 10 (x86)
Solaris 10 (x86_64)
The following is a list of issues addressed and enhancements implemented in Quest® Management Xtensions for SMS 1.6.
| CR#29254 | After the Client was installed on HP-UX and Solaris systems, if you joined the
Client to Active Directory, you saw the "No valid licenses found, entering HOST
mode" warnings output to the console from vasclnt every hour.
These warnings pertained to missing VAS licenses. This is an issue with VAS
and was fixed in VAS 3.2.x release now being installed with QMX for SMS 1.6. |
| CR#31063 | When uninstalling the Client, the install script reported an error:
/var/tmp/rpm-tmp.2478: line 10: /opt/quest/qmxsms/sbin/qmxsmsd_init:
No such file or directory error reading information on service quest-qmxsmsd:
No such file or directory.
You can safely ignore this error; this does not cause any problems after the uninstall is complete. |
| CR#35971 | Client Installation Wizard now recognizes Mac OS X clients joined to Active Directory using the Directory Access utility from Mac OS. |
| CR#37585 | Removed the QMX for SMS installation process dependency on the SUNWslpu package on Solaris Clients. The SUNWslpu package is typically installed by Solaris by default and since QMX for SMS does not require the SUNWslpu package in order to run properly, Quest removed the installation process dependency. |
| CR#35967 | QMX for SMS now reports more concise and consistent Operating System Version information of Linux Clients during Hardware Inventory. The Description field was modified to be clearer using the following template: OS name; Distribution version; (architecture). |
| CR#25065 | SunOS SPARC Solaris 10 hardware inventory reported incorrect installation date of OS. |
| CR#25227 | In some Sun boxes the Hardware Inventory was not reporting the name of the processor when Solaris 9 is installed. |
| CR#42211 | Performance improvement and reduced CPU resources for Metering on Solaris 8. |
| CR#33224 | To upgrade your system you must upgrade the Clients first. Then,
once that is complete, upgrade the MMC Extensions. However, during the interim between
upgrading the Clients and upgrading the MMC Extensions, Hardware and Software
Inventory will work, but Software Distribution, Remote Tools, and Policy Spy
will not be available for the upgraded QMX for SMS Clients from the
SMS Administrator's Console with the older version of QMX for SMS MMC Extension.
Workaround: Use a phased approach to upgrading your systems. Upgrade all of your Clients for a particular site server completely, then upgrade the Clients for the next site server, and so on. Also, to continue managing the Clients with the older version of QMX for SMS, create collections based on the version number. Or, you can install the new MMC Extensions on a separate Administrator's console to manage the new clients. |
New Features in the Previous Release of Quest® Management Xtensions for SMS--version 1.5
New Platform and environment support
Asianux 2.0
Red Hat Enterprise Linux 5 Server and Desktop (32-bit, x86-64bit)
SMS 2003 Service Pack 3
Solaris Zones
VMware ESX Server 2.5.3 and 3.0.1 support (QMX agent can reside on ESX Server or Clients that run as Guest)
Native 64-bit support (previously, emulation-only):
Red Hat Enterprise Linux 4, and 5
SLES 9, 10
Platforms no longer supported (end of life):
Red Hat Linux 7.3, 8, 9 i386
SUSE Linux (Professional) 8.2, 9.0, 9.1, 9.2, 9.3, 10 i386
Enhanced Security Features
Management Point Verification. The QMX for SMS Client verifies a Management Point as a valid or "trusted" Management Point using the signature from the Trusted Root Key (TRK). Management points can be obtained directly from the management points or from Active Directory. It ignores all management points with certificates that are not verified by using the TRK.
Benefit: This prevents client tasks from being "spoofed" by an invalid management point.
Policy Signature Verification: The QMX for SMS Client verifies the signature of the SMS policy before it accepts it.
Benefit: This ensures valid policies.
Client Inventory Encryption (optional) As requested by SMS policy, the QMX for SMS Client signs inventories using the client's private key. The QMX for SMS Client encrypts Discovery Data Record (DDR) and hardware inventory information for all management points "hiding" behind a single IP address or DNS name before posting them to SMS. User only sees information about encrypted inventories in debug logs.
Benefit: This prevents the possibility of the server accepting "spoofed" inventories.
Minimize root processes to prevent unauthorized privilege escalation
Uses separate process that only receives commands from QMX for SMS when root is required
Runs from a pre-configured list of commands
Software Package Verification The QMX for SMS Client verifies the signatures of packages received in Software Distribution. The QMX for SMS Client validates the software package before installing them by performing a hash check.
Benefit: This ensures Software files and policies have not been altered in transit.
Unauthorized Privilege Escalation is limited by running all possible processes as a non-privileged user. To prevent privilege escalation attacks, the usage of root has been minimized. The QMX for SMS Client runs as a non-privileged user; it only runs certain commands as root. There is a limited list of processes it runs, files it looks at to get inventory data, etc. as root. It has to request that the Privilege Monitor carry out privileged operations on its behalf.
QMX for SMS Integration with Active Directory: QMX for SMS can securely obtain lists of management points and their certificates from Active Directory. This requires the use of Vintela Authentication Service (VAS) to be installed and joined to the Active Directory domain. Thus, the QMX for SMS Client Installation Wizard performs the join during the installation.
QMX for SMS Client certificate maintenance cycle performance: The clienttool has a new -run-certificate-maintenance option that forces the certificate maintenance cycle. This function updates the list of trusted Management Point certificates.
QMX for SMS only sends the discovery items requested by policy. QMX for SMS discovery follows the SMS policy of providing only the classes and properties that are requested. The clienttool option, -run-discovery, sends a Discovery Data Record (DDR) report and posts only the discovery-related inventory that is found in the policy.
Management Point Extension (MPE) Removal
To minimize configuration and support concerns, the Client communication now occurs directly with SMS Management Point instead of by means of the QMX for SMS Management Point Extension.
When upgrading to QMX for SMS 1.5, you can remove the Management Point Extension manually by means of Add/Remove Programs or by using the SMS Distribute Software Wizard.
Note: DO NOT remove the QMX for SMS Management Point Extensions until after the upgrade of all the QMX for SMS Client machines is complete and you know you have a successful installation!
UI and Wizard Improvements
Client Installation Wizard
Installation Auto-Run. When you insert the CD, the Management Console Extensions Setup Wizard starts automatically.
Pre-Installation Verification Tool. The MMC Extensions Installation wizard includes a Pre-Installation Verification tool to ensure your SMS system is properly configured. It checks that the management point is installed and functioning.
Significant enhancements to the UI, including integrating Active Directory domain joins, the SSH Scan utility, and adding "su" to access root privileges.
Separated Permissions screens for SSH Access permissions and root privileges permissions
Can now use "su" to access root privileges
QMX for SMS can now automatically join your Unix, Linux, or Max OS X systems to Active Directory domain by means of Vintela Authentication Services (VAS)
Discovery options for Client Installation are less ambiguous. The various methods of identifying systems on which to install the Client have been added as menu items. You can identify systems manually, by importing a text file listing hostnames and IP addresses of the systems, by searching for VAS-enabled systems in a list of Active Directory containers, by scanning IP address ranges for open SSH ports, or by specifying SMS 2003 Collections.
New Discovery Methods are:
The "Manually" method allows you to enter a specific Hostname or IP Address
The "By Network Discovery" method enables the wizard to select target systems by scanning a range of IP addresses for open SSH ports
You can now view the details of the installation, drilling to the individual Hostname Details
Auto Install Queries and Collections. You can add Quest default queries and collections for the Unix, Linux, or Mac OS X operating systems you need, from within the MMC Console snap-in
Software Distribution Wizard
Software Dist of Packages Without Files. You can use the General Unix Software Distribution method to create and distribute patches and scripts, as well as packages that do not contain files. (File-less Packages.)
Benefit: You can send only a command line to a collection of computers.
You can now distribute IBM RPMs with the Software Distribution Wizard. (Refer to the "AIX Toolbox for Linux Applications" for details on how to use RPM files on AIX.)
A new Agree to the license option has been added to the Mac OS X software Distribution dialog to allow you to automatically respond "Y" (yes) to the license agreement. This will allow you to distribute software without requiring the end user to agree to the license before it installs the package.
The Program Properties dialog has been simplified by merging all Operating System tabs into a single QMX for SMS tab.
Integration with Universal Management Instrumentation (UMI) replaces/updates OpenWEBM
Binary compatibility with Quest Management Xtensions for MOM 2.0 and QMX for OM when they release. The OpenWBEM backend was replaced with UMI. The QMX for SMS Client now shares the same OpenWBEM CIMOM as the QMX for MOM Agent.
Benefit: This will enable both products to share functionality and reduce the overall footprint required to have both QMX for SMS and QMX for MOM on the same client.
Note: QMX for SMS 1.6 is NOT compatible with QMX for MOM 1.1.
Integration with Vintela Authentication Services (VAS)
VAS Distribution and Join. If your clients do not already have a licensed version of Vintela Authentication Services (or VAS) installed on them, the Client Installation Wizard automatically installs a VAS Client. However, without purchasing and installing the license for VAS, QMX for SMS only enables the VAS features that are directly relevant to Active Directory domain joins for Unix, Linux, or Mac OS X systems and some additional security benefits. To enable the full feature set of VAS, you must purchase and install a license.
Uninstall VAS. QMX for SMS has no dependency on VAS. QMX for SMS functions properly if VAS is uninstalled and VAS functions property if QMX for SMS if uninstalled. You can uninstall VAS by advertising a command using the Software Distribution Wizard. Or, you can do it manually. However, if you want to join your domain to Active Directory you must have VAS installed on your QMX for SMS Client. Because running QMX for SMS without VAS-provided services makes your environment less secure, Quest does not recommend removing VAS altogether.
VAS Upgrades. The QMX for SMS Client allows you to upgrade VAS by advertising a command using the Software Distribution Wizard.
Mac OS X 10.4 Support of VAS. VAS 3.2 will enable QMX for SMS to use Active Directory for discovery of Mac OS X 10.4 systems and for joining Mac OS X 10.4 systems to Active Directory. Mac OS software inventories have been improved.
The QMX for SMS Client Installation Wizard performs the join during the installation. Integrated VAS functionality in Client Install Wizard allows Unix, Linux, or Mac OS X systems to be joined into AD as part of client install.
The following is a list of issues known to exist at the time of the Quest® Management Xtensions for SMS 1.6 release.
| 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 |
| CR#43124 | Asianux is recognized as a Red Hat 4 Linux; there are no query or collections for Asianux. |
| SMS Issue | Issues in Client after the SMS 2003 SP2 and SMS 2003 SP3 deployment:
During the upgrade of SMS, there is a temporary period of time when the client gets no response from SMS. The following message displays a few minutes after the SMS Service Pack 2 (or SMS Service Pack 3) deployment: (This condition corrects itself after the SMS upgrade is completed.
If you check the the SP2 Upgrade Checklist in the SMS 2003 SP2 documentation, you will find a section called Determining that SMS Setup has Completed. That section establishes that you need to wait at least 30 minutes before you start using SMS again, this is because many SMS inside components are being updated and this is a long process that also affects the communication between the Client and SMS; that communication is reestablished as soon the SMS environment has completed the SP2 setup. |
| 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. |
| SMS Issue | Orphaned Inventory. In some cases where SP1 has been installed it may take as much as 4
hours for SMS to recognize and process "orphaned" inventory. Orphan
systems are systems which have been reported to Hardware or Software Inventory,
but are not "official" computer objects in SMS yet. You can see an "orphaned"
Unix object in a collection, but not in the Resource Explorer's Hardware or Software Inventory.
Depending on the order in which policy is received from the Management Point, the Client's Hardware or Software Inventory may precede Data Discovery Record (DDR) going into SMS. That is, before the Client reports itself into SMS as a valid client and creates a computer object in SMS. This results in a new QMX for SMS system becoming an "orphan" from SMS's point of view. The hardware inventory group will be empty in the Resource Explorer. If you don't want to wait for the normal cycle, you can force inventory from the command line of the Client using the clienttool --run-hardware-inventory or the
clienttool --run-software-inventory command. |
| CR#25193 | In Hardware Inventory, the category Add/Remove Programs: Install Date and Publisher Data are not reported for Mac OS X. |
| CR#25347 | Resource Explorer does not show Install Date for Sun patches in Hardware. |
| CR#25350 | Network providers are not reporting the same number of instances. |
| CR#25524 | Resource Explorer does not collect information about Keyboard and Pointing Devices in RHEL2.1 when X11 is not installed on the system. |
| CR#25911 | Resource Explorer does not report the CPU Clock Speed on HP-UX. |
| CR#26014 | Resource Explorer does not report CD-ROM for HP-UX. |
| CR#30440 | Resource Explorer lists real SCSI Disk adapters on Mac OS X, as well as some "rogue" devices. |
| CR#31845 | Missing Hardware History Properties. At times blank lines appear in the Hardware History node in the Resource Explorer. This is a known issue in SMS. Please refer to the Microsoft Knowledge base article at: http://support.microsoft.com/kb/322476 for a work around. |
| CR#47055 | Resource Explorer does not show Services for non-global zones.
Services are reported to SMS, but Resource Explorer does not contain them.
Workaround: You can run Software Meteing to gather the information. |
| CR#24596 | Quest Management Xtensions for MOM (QMX for MOM) Compatibility: QMX for SMS 1.6 is only compatible with QMX for MOM 2.0 and newer. |
| 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 for SMS 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.)
|
| CR#31990 | When you delete QMX for SMS 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#32076 | After installing the QMX for SMS Client on AIX 5.1, the client cannot update policy.
This is because the AIX patch level is not up to date. (Quest recommends Patch level 9.)
Workaround: Connect to host and restart qmxsmsd and owcimomd
daemons by command: /opt/quest/qmxsms/sbin/qmxsmsd_init restart. After this
use clienttool with the --run-policy-update
and --run-software-distribution options. |
| CR#32478 | When you install QMX for SMS 1.6 on ESX 2.5.3 and join to the
Active Directory domain, sudo will fail. This is not a QMX for SMS bug;
ESX prevents this from working. (This happens when VAS is installed and joined to
Active Directory, whether QMX for SMS is installed or not.)
Workaround: use su instead. |
| 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. |
| CR#46567 | When you install the QMX for SMS 1.6 Client with Client Installation Wizard on Mac OS X 10.5
or HP-UX 11.31 system and check "Join Unix clients to the Active Directory" option,
the join will fail because the version of VAS shipping with QMX for SMS 1.6 (VAS 3.2)
does not support HP-UX 11.31 and Mac OS X 10.5 platforms. You will receive a warning message in the installation log.
QMX for SMS 1.6 will successfully install on the platforms that are unsupported by VAS 3.2, but the
computers won't be joined to Active Directory.
Note: VAS 3.3.1 will release in late January. At that time you will be able to download VAS 3.3.1 and distribute the bits to your QMX clients via Software Distribution. |
| CR#28590 | No 'busy' cursor displays when installing collections and queries. When you add new collections using the QMX for SMS Collections Installation wizard, there is no progress indication. Be patient for a few seconds. When the installation completes, the QMX for SMS Collections Installation dialog closes. |
| CR#24339 | Putty ssh shell requires X option: %PUTTY% -ssh -X -l %USERNAME% %HOSTNAME%.
The problem is when you start putty ssh shell from Non-Windows Remote tools, it checks the existence
of X Server and displays a warning that says, "No X Server Detected" if an X Server
has not been started. In fact, it does not need an X Server (because it is not an X application),
so if you ignore this warning and click "Yes", the ssh shell will start successfully.
|
| CR#31882 | Remote Tool X-window opens in another terminal session. When UserA launches Remote tools, the window with this tool appears on the desktop of UserB, who is logged on the same machine with Remote desktop. Note: This happens only if UserB launched X Server earlier than UserA. |
| CR#22733 | RPM packages do not install if RPM is located in sub-directory of the installation source. |
| CR#24959 | Child packages remain available after disabling parent packages |
| CR#33030 | Client hangs when you distribute a command line containing the
clienttool command. The problem is that the Client
cannot do two things at once, so during the Software Distribution process
it cannot run clienttool. You have to schedule it to
execute clienttool after the software distribution is completed. |
| SMS Issue | Software Distribution may fail if the distribution point is installed
on Windows Server 2003 R2 due to the new security schema of
IIS version 6.0. Please verify that every Distribution Point has
the following configuration:
For more information about the new IIS ver 6.0 security schema check the IIS 6.0 Operations Guide in the following site: Microsoft Windows Server 2003 TechCenter |
| 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. |
| CR#25372 | File Collection fails for all subdirectories of /mnt/ when
File Collection rule is set with the path of /mnt. |
| CR#27978 | If two files have the same name and the same size, but the name differs in case,
clienttool --run-software-inventory indicates that both files were collected,
but the Resource Explorer only shows the first file in the list in
Software | File Details. For example, File, file, and FILE are sorted as
file, File, FILE. Only "file" will be listed in the Resource Explorer.
Note: if size differs, all files are displayed. |
| CR#46593 | Upgrade from 1.2.2 version destroys CCM_HistoricalMeteredData. Upgrading from 1.5 to 1.6 works fine. |
Upgrading Quest Management Xtensions for SMS
When upgrading QMX for SMS to the latest product release, you must
install the QMX for SMS Client (the Client) on each Non-Windows resource you want to manage with SMS and
you must install the QMX for SMS Microsoft Management Console Extension (which includes the
Snap-In, Wizards, and Remote Tools) on every machine that runs the
SMS Administrator's console.
To upgrade the Client, you can manually install the Client or use the Client Installation Wizard:
To upgrade the Client manually, enter either of these commands:
./install_qmx_client.sh -u OR ./upgrade_qmx_client.sh
To upgrade the Client using the QMX for SMS Software Distribution Wizard, distribute the upgrade_qmxsms_client.sh script using the General Unix software distribution method.
Please see Chapter 8, Upgrading QMX for SMS, in the Installation Guide for screen shots and step-by-step instructions.
Installation of QMX for SMS 1.6 will delete the previous version and install the upgrade.
Whether you upgrade the Client manually or using the Wizard, you must re-install the All Unix Systems Query and Collection so that your new Clients will be included (see Installing the Queries and Collection in Chapter 4 of the Installation Guide. For example, you must re-install the "All Red Hat Linux Systems" query and collection to retain the Red Hat Linux clients in the associated collection.
To upgrade the Management Console Extensions:
Insert the installation CD into the CD-ROM drive of the target machine.
The Management Console Extensions Setup Wizard starts automatically and leads you through the process.
Please see Chapter 8, Upgrading QMX for SMS, in the Installation Guide for screen shots and step-by-step instructions.
For additional platform support, please contact Sales@Quest.com
|
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.
The Quest® Management Xtensions for SMS release package contains the following:
aix-power contains the QMX for SMS Client Installation packages for the AIX operating system.
autorun folder contains the files required for the autorun feature.
diagnostics contains the qmx_hardware_information.sh script used for collecting hardware information
docs contains the product user guides and the VASTOOL MAN PAGE .html file.
hpux-ia64 contains the QMX for SMS Client Installation packages for the HP-UX operating system on the Itanium platform.
hpux-parisc contains the QMX for SMS Client Installation packages for the HP-UX operating system.
linux-rh2.1-x86 contains the QMX for SMS Client Installation packages for the Linux operating system.
linux-rh3-x86 contains the QMX for SMS Client Installation packages for the Linux operating system.
linux-rh3-x86_64 contains the QMX for SMS Client Installation packages for the Linux operating system.
osx-ppc contains the QMX for SMS Client Installation packages for the Max OS X operating system.
osx-x86 contains the QMX for SMS Client Installation packages for the Max OS X operating system.
sunos-sparc contains the QMX for SMS Client Installation packages for the Sun Solaris operating system.
sunos-x86 contains the QMX for SMS Client Installation packages for the Sun Solaris operating system on Intel platform.
umi contains the umi packages.
win32 .msi files for the QMX for SMS Windows components.
autorun.exe launches Autorun when the disk is inserted.
autorun.inf
install_qmx_client.sh script.
QMX_1.6_ReleaseNotes.htm for this release of QMX for SMS.
setup.exe
upgrade_qmx_client.sh script.
NOTE: For step-by-step installation instructions,
see the Installation Guide located on the installation CD in the
docs | pdf folder.
Step 1: Install the QMX for SMS Microsoft Management Console Extensions on every machine that runs the SMS Administrator's console: Insert the installation CD into the CD-ROM drive of the target machine and click the Install tab.
Step 2: Install the Queries and Collections on the Central Site Server.
If you opt to install the Queries and Collections, be sure you are logged into Windows as a user with permission to create queries and collections in SMS 2003. We recommend that you run it from the top-level site server.
Collections are automatically propagated down from higher to lower level sites; queries are not. Thus, you can install the collections once on your top-level site server and they propagate throughout your hierarchy. In contrast, you must install the queries individually on any site server where you want them to be available.
Right click Queries and choose All Tasks | QMX for SMS Queries Installation Tool.
Right click Collections and choose All Tasks | QMX for SMS Collections Installation Tool.
Step 3: Install the License: From the Administrator Console, right-click the Tools group to open the shortcut menu. Choose All Tasks | License Manager to open the License Manager dialog.
Note: When you purchase QMX for SMS you will receive an email that contains one License file. Licenses for QMX for SMS are tracked using hardware inventory and compared to the license file for each SMS Central Site. QMX for SMS provides reminder alerts when each Central Site's license total differs from the number of systems identified by means of Hardware Inventory.
Import the license file for each SMS Central Site server you have using the License Manager accessed via the Tools node.
Step 4: Install the Client onto your non-Windows hosts: From the Administrator Console, right-click the parent Collections group, a specific collection name, or the Tools group to open the shortcut menu. Choose All Tasks | Client Installation Wizard to start the Client Installation Wizard.
You can install QMX for SMS Clients manually, as well. See the Install Guide for instructions.
Note: The order in which you install these components is important. Quest recommends that you install the Windows components before you install the Client so that when the client does its auto-discovery the hardware and software inventory will show up immediately.
Before you start the installation, it is recommended that you close all the previously open applications.
Note: Before installing QMX for SMS into Solaris 10 zones, please read the General Zone Guidelines in the QMX for SMS Installation Guide.
| info@quest.com | |
| Quest Software, Inc. World Headquarters 5 Polaris Way Aliso Viejo, CA 92656 USA |
|
| Web |
Refer to our Web site for regional and international office information.
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: http://support.quest.com/pdfs/Global Support Guide.pdf.
Get the latest product information, find helpful resources, and join a discussion with the QMX for SMS Quest team and other community members. Join the QMX for SMS community at: http://vintela.inside.quest.com/category.jspa?categoryID=34
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.
© 2007; Quest Software, Inc. ALL RIGHTS RESERVED.
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.
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 |
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.