Quest® Management Xtensions - Configuration Manager 2007 Edition

Version 2.1

Release Notes

February 2009

 


Contents

Welcome to Quest® Management Xtensions - Configuration Manager 2007 Edition

New in this Release

Resolved Issues and Enhancements

Known Issues

Third-Party Known Issues

System Requirements

Global Operations

Contents of Release Package

For More Information

 


Welcome to Quest® Management Xtensions - 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.

 


New in This Release

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

  1. Windows 2008 Server Support

    QMX 2.1 supports Windows 2008 Server operating systems.

  2. VMware ESX 3.5 Support

    QMX 2.0 supported VMware ESX 3.5 but had not created the following collection and query:

  3. AIX 6.1 Support

    QMX 2.1 now supports AIX 6.1 and has created this new collection and query:

    The following collections and queries were updated for this release:

    For AIX 6.1 to show up in these collections and queries, you must delete the old collections and queries and install the new ones.

    Note: Upgrading the MMC extensions, does not automatically install collections or queries for any new client Agents supported by QMX - Configuration Manager 2007, nor does it update existing collections or queries. However, reinstalling a query or collection overwrites any modifications that you might have made.

  4. CentOS Support

    QMX 2.1 now supports CentOS 4 and 5 and provides all the necessary collections and queries in this release.

  5. Using Scripts to Collect Hardware Inventory

    QMX 2.1 now allows you to use scripts to collect hardware inventory information. QMX executes all scripts that reside in the noidmof directory with a script extension (.sh, .py, .pl) and marked as executable. The output (if the script is successful) is used exactly the same as a noid mof file.

  6. Maintenance Windows

    Maintenance Windows is a new feature which allows you to define a service window in which to perform software distributions and software updates. The window uses an estimated time (defined in the SW Distribution wizard) to complete the entire installation of the software distribution or update. You define maintenance windows by collection with an effective start date, start and end times, and a set recurrence pattern.

    To take advantage of this new feature, you must edit packages and advertisements that existed before upgrading to version 2.1. (See "Upgrade Packages and Advertisements After an Upgrade" in Chapter 9 of the Installation guide for more information.

    Note: Software Distribution expects to run mandatory assignments within defined Maintenance Windows. If you have not defined any maintenance windows, no distribution assignments will run unless you explicitly set them to ignore maintenance windows.

  7. Native Mode

    Native Mode is a new security site mode that was added to System Center Configuration Manager 2007 which provides a more reliable infrastructure.

    Note: See "Installing the MP Proxy" in Chapter 7 of the Installation guide for more information.

  8. New clienttool Options

    Quest has provided new clienttool options to help you perform Agent Configuration, Maintenance Window, and Native Mode tasks.

  9. Please refer to Chapter 9 in the Administrator's Guide for information about these new clienttool options.

 


Resolved Issues and Enhancements

The following is a list of issues addressed and implemented in this release of Quest® Management Xtensions - Configuration Manager 2007 Edition.

  1. Fixed high CPU usage issue during some inventory scans

    Hardware Inventory was taking much longer than usual or CPU usage could be high for an extended period of time (hours). Hardware Inventory and File Collection could enter an infinite recursion while following bad symlinks.

  2. Fixed File Collection Details Reporting on Mac OS X

    No File Collection Details were displaying in the Resource Explorer on Mac OS after Software Inventory because File Collection Details requires privileges.

  3. Fixed Inventory For Microsoft Office Applications on Mac OS X

    Microsoft Office Applications (such as Word, Excel, PowerPoint, and so forth) were not showing up in the Add/Remove Programs node within the System Center Configuration Manager 2007 Resource Explorer after Hardware Inventory scans on Mac OS X 10.4 and 10.5 systems.

  4. Scheduler improvements

    When a task was scheduled to start at a specific time, the actual execution time could vary by several minutes. The QMXcm 2.1 release fixed the scheduler so that there is no lag time when executing scheduled tasks. Other improvements to the scheduler include:

  5. VAS 3.5 Support

    QMXcm 2.1 installs the latest release, VAS 3.5, which supports:

  6. Revised and expanded "Troubleshooting" Chapter in the Install Guide

    Chapter 10 in the Installation Guide has been expanded to include more information about log files, configuration files, and changing logging behavior.

 


Known Issues

The following is a list of issues known to exist at the time of Quest® Management Xtensions - Configuration Manager 2007 Edition 2.1 release.

 

Client

CR#14830 clienttool Metering Usage Report Option is not correctly reporting the software metering usage. The clienttool --run-software-metering-usage-report is not calculating all software metering usage data.
Workaround: Use the SCCM Reports. The Software Metering reports show that the data for all running processes is sent to SMS.
CR#15884 QMX Agent Terminates. The QMX Agent may terminate improperly if shutting down while a long operation is in progress.
CR#16082 Multiple sites publishing certificates to Active Directory confuse the client. If there are multiple SCCM sites publishing certificates into the same Active Directory domain, the client can (and will occasionally) pick the wrong certificates and distrust the Management Point it is supposed to use.
Workarounds:
1. Install the MP Proxy on the Management Point. The client will ignore any stored mixed-mode certificates and start communicating with the MP Proxy.
2. Unjoin the client from Active Directory, run clienttool --reset-stored-site-info, and clienttool --run-policy-update. The client will continue to function unless it is rejoined and a certificate maintenance cycle is performed.
CR#16099 Cannot switch client from one MP Proxy to another. If you have a client pointed at an MP Proxy and want to point it at a different MP Proxy, you must use the clienttool --reset-client-id option when switching:
For example:
# /opt/quest/qmxcm/bin/clienttool --reset-stored-site-info --reset-client-id --set-mp mpproxy1.mixed.qmxdev
This will cause a new SMSID to be generated.

Hardware Inventory

CR#14832 Hardware Inventory on some ESX 3.5 computers is not properly reporting some information. Hardware Inventory is not properly reporting the Model #, Serial # and Manufacturer data on ESX 3.5.

Installation

CR#14716 Install and Upgrade will fail if the client machine does not have enough free disk space. You must increase the size of /tmp (or /opt on AIX) to 3 times the size of the installation package. You can decrease the size of the directory after the installation.

Software Metering

CR#13702 Software Metering rule names cannot have space in them. Except on a Mac OS X, all other platforms do not permit spaces in Software Metering rule names.

 


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.0 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

 


System Requirements

  • System Center Configuration Manager 2007 Requirements:

  • QMX Reqirements

    • Management Point

      • System Center Configuration Manager 2007 SP1, R2

      • Windows Server 2003, Windows Server 2003 R2, and Windows Server 2008

      • IIS 6 and 7

    • Configuration Manager Console Requirements

      • Windows XP, Windows Server 2003, Windows Server 2003 R2, and Windows Server 2008

      • System Center Configuration Manager 2007 is Installed and fully functional.

      • 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 PPC Server & Desktop 10.3, 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 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 2.0 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) x86 AS/ES 2.1 80 MB 11 MB + 40 MB for logs 1 MB 64 MB 256 MB ~130 MB
      Red Hat Enterprise Linux (RHEL) x86 & x86-64 AS/ES/WS & Desktop 3.0, 4.0 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.03 80 MB 11 MB + 40 MB for logs 1 MB 64 MB 256 MB ~130 MB
      SUSE Linux Enterprise Server (SLES) x86 8 80 MB 22 MB + 40 MB for logs 1 MB 64 MB 256 MB ~140 MB
      SUSE Linux Enterprise Servers (SLES) x86 & x86-64 9, 10 80 MB 15 MB + 40 MB for logs 1 MB 64 MB 256 MB ~135 MB
      SUSE Linux Standard Server x86 8.0 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 80 MB 22 MB + 40 MB for logs 1 MB 64 MB 256 MB ~140 MB
      SUSE Linux Enterprise Desktop (SLED) x86-64 10 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 x86 2.5.x, 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 2.1 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.

  • 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

 


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.

 


Contents of the Release Package

The Quest® Management Xtensions - Configuration Manager 2007 Edition release package contains the following:

 


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: http://support.quest.com/pdfs/Global Support Guide.pdf.


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: http://vintela.inside.quest.com/category.jspa?categoryID=34

 


© 2008  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 Agreement
Berkeley DB 4.1.25 Copyright 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. All advertising materials mentioning features or use of this software must display the following acknowledgement: This product includes software developed by the University of California, Berkeley and its contributors. Neither the name of the University nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission. THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. The Institute of Electrical and Electronics Engineers and the American National Standards Committee X3, on Information Processing Systems have given us permission to reprint portions of their documentation. In the following statement, the phrase ``this text'' refers to portions of the system documentation. Portions of this text are reprinted and reproduced in electronic form in the second BSD Networking Software Release, from IEEE Std 1003.1-1988, IEEE Standard Portable Operating System Interface for Computer Environments (POSIX), copyright C 1988 by the Institute of Electrical and Electronics Engineers, Inc. In the event of any discrepancy between these versions and the original IEEE Standard, the original IEEE Standard is the referee document. In the following statement, the phrase ``This material'' refers to portions of the system documentation. This material is reproduced with permission from American National Standards Committee X3, on Information Processing Systems. Computer and Business Equipment Manufacturers Association (CBEMA), 311 First St., NW, Suite 500, Washington, DC 20001-2178. The developmental work of Programming Language C was completed by the X3J11 Technical Committee. The views and conclusions contained in the software and documentation are those of the authors and should not be interpreted as representing official policies, either expressed or implied, of the Regents of the University of California. NOTE: The copyright of UC Berkeley's Berkeley Software Distribution ("BSD") source has been updated. The copyright addendum may be found at ftp://ftp.cs.berkeley.edu/pub/4bsd/README.Impt.License.Change and is included below. July 22, 1999 To All Licensees, Distributors of Any Version of BSD: As you know, certain of the Berkeley Software Distribution ("BSD") source code files require that further distributions of products containing all or portions of the software, acknowledge within their advertising materials that such products contain software developed by UC Berkeley and its contributors. Specifically, the provision reads: " * 3. All advertising materials mentioning features or use of this software * must display the following acknowledgement: * This product includes software developed by the University of * California, Berkeley and its contributors." Effective immediately, licensees and distributors are no longer required to include the acknowledgement within advertising materials. Accordingly, the foregoing paragraph of those BSD Unix files containing it is hereby deleted in its entirety. William Hoskins Director, Office of Technology Licensing University of California, Berkeley
Boost 1.33.1
Boost 1.34.1
compress-Zlib 1.41
HPUX-Pstat 1.01
HTML-Parser 3.54
HTML-Tagset 3.10
libgcc_s 3.2.3
libgcc_s 3.3.2
libgcc_s 3.3.3
libgcc_s 3.4.5
libgcc_s 4.1.1
Libstdc++ 3.2.3
Libstdc++ 3.3.2
Libstdc++ 3.3.3
Libstdc++ 3.4.5
Libstdc++ 4.1.1
libwww-perl 5.805
Microsoft HTML Help Workshop and Documentation 1.4
OpenSSL 0.9.8d This is a copy of the current LICENSE file inside the CVS repository. LICENSE ISSUES ============== The OpenSSL toolkit stays under a dual license, i.e. both the conditions of the OpenSSL License and the original SSLeay license apply to the toolkit. See below for the actual license texts. Actually both licenses are BSD-style Open Source licenses. In case of any license issues related to OpenSSL please contact openssl-core@openssl.org. OpenSSL License --------------- /* ==================================================================== * Copyright (c) 1998-2007 The OpenSSL Project. All rights reserved. * * Redistribution and use in source and binary forms, with or without * modification, are permitted provided that the following conditions * are met: * * 1. Redistributions of source code must retain the above copyright * notice, this list of conditions and the following disclaimer. * * 2. Redistributions in binary form must reproduce the above copyright * notice, this list of conditions and the following disclaimer in * the documentation and/or other materials provided with the * distribution. * * 3. All advertising materials mentioning features or use of this * software must display the following acknowledgment: * "This product includes software developed by the OpenSSL Project * for use in the OpenSSL Toolkit. (http://www.openssl.org/)" * * 4. The names "OpenSSL Toolkit" and "OpenSSL Project" must not be used to * endorse or promote products derived from this software without * prior written permission. For written permission, please contact * openssl-core@openssl.org. * * 5. Products derived from this software may not be called "OpenSSL" * nor may "OpenSSL" appear in their names without prior written * permission of the OpenSSL Project. * * 6. Redistributions of any form whatsoever must retain the following * acknowledgment: * "This product includes software developed by the OpenSSL Project * for use in the OpenSSL Toolkit (http://www.openssl.org/)" * * THIS SOFTWARE IS PROVIDED BY THE OpenSSL PROJECT ``AS IS'' AND ANY * EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE * IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR * PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE OpenSSL PROJECT OR * ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, * SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT * NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; * LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) * HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, * STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) * ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED * OF THE POSSIBILITY OF SUCH DAMAGE. * ==================================================================== * * This product includes cryptographic software written by Eric Young * (eay@cryptsoft.com). This product includes software written by Tim * Hudson (tjh@cryptsoft.com). * */ Original SSLeay License ----------------------- /* Copyright (C) 1995-1998 Eric Young (eay@cryptsoft.com) * All rights reserved. * * This package is an SSL implementation written * by Eric Young (eay@cryptsoft.com). * The implementation was written so as to conform with Netscapes SSL. * * This library is free for commercial and non-commercial use as long as * the following conditions are aheared to. The following conditions * apply to all code found in this distribution, be it the RC4, RSA, * lhash, DES, etc., code; not just the SSL code. The SSL documentation * included with this distribution is covered by the same copyright terms * except that the holder is Tim Hudson (tjh@cryptsoft.com). * * Copyright remains Eric Young's, and as such any Copyright notices in * the code are not to be removed. * If this package is used in a product, Eric Young should be given attribution * as the author of the parts of the library used. * This can be in the form of a textual message at program startup or * in documentation (online or textual) provided with the package. * * Redistribution and use in source and binary forms, with or without * modification, are permitted provided that the following conditions * are met: * 1. Redistributions of source code must retain the copyright * notice, this list of conditions and the following disclaimer. * 2. Redistributions in binary form must reproduce the above copyright * notice, this list of conditions and the following disclaimer in the * documentation and/or other materials provided with the distribution. * 3. All advertising materials mentioning features or use of this software * must display the following acknowledgement: * "This product includes cryptographic software written by * Eric Young (eay@cryptsoft.com)" * The word 'cryptographic' can be left out if the rouines from the library * being used are not cryptographic related :-). * 4. If you include any Windows specific code (or a derivative thereof) from * the apps directory (application code) you must include an acknowledgement: * "This product includes software written by Tim Hudson (tjh@cryptsoft.com)" * * THIS SOFTWARE IS PROVIDED BY ERIC YOUNG ``AS IS'' AND * ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE * IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE * ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE * FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL * DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS * OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) * HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT * LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY * OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF * SUCH DAMAGE. * * The licence and distribution terms for any publically available version or * derivative of this code cannot be changed. i.e. this code cannot simply be * copied and put under another distribution licence * [including the GNU Public Licence.]
Perl 5.8.8
PuTTY .60 Requirements:
The copyright notice and permissions paragraph in the license text must be included in all copies of the software:

PuTTY is copyright 1997-2007 Simon Tatham.
Portions copyright Robert de Bath, Joris van Rantwijk, Delian Delchev, Andreas Schultz, Jeroen Massar, Wez Furlong, Nicolas Barry, Justin Bradford, Ben Harris, Malcolm Smith, Ahmad Khalifa, Markus Kuhn, and CORE SDI S.A.
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL SIMON TATHAM BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
SNMP_Session 1.08
URI 1.35
XML-Parser 2.34
zlib 1.2.3 zlib.h -- interface of the 'zlib' general purpose compression library version 1.2.3, July 18th, 2005 Copyright (C) 1995-2005 Jean-loup Gailly and Mark Adler This software is provided 'as-is', without any express or implied warranty. In no event will the authors be held liable for any damages arising from the use of this software. Permission is granted to anyone to use this software for any purpose, including commercial applications, and to alter it and redistribute it freely, subject to the following restrictions: 1. The origin of this software must not be misrepresented; you must not claim that you wrote the original software. If you use this software in a product, an acknowledgment in the product documentation would be appreciated but is not required. 2. Altered source versions must be plainly marked as such, and must not be misrepresented as being the original software. 3. This notice may not be removed or altered from any source distribution. Jean-loup Gailly jloup@gzip.org Mark Adler madler@alumni.caltech.edu

 

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.