Quest® Management Xtensions - Configuration Manager 2007 Edition
Version 2.0
Release Notes
April 2008
Welcome to Quest® Management Xtensions - Configuration Manager 2007 Edition
Quest® Management Xtensions - Configuration Manager 2007 Edition (QMX - Configuration Manager 2007) is comprised of a Unix, Linux, or Mac OS X Agent which is installed on the managed hosts 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 Features since the release of Quest® Management Xtensions for SMS 1.6:
Usability and Look and Feel
New name - Quest Management Xtensions - Configuration Manager 2007 Edition (QMX - Configuration Manager 2007).
Resizable Wizard pages.
Content of the page is "sticky" unless you must re-enter new data.
Tool tips added to Wizard pages.
You can minimize the Wizard pages onto the Task bar so you can pause to perform other tasks, then return.
Checks for errors before you click Next.
Integration with menus on Action Pane.
Agent Push Install Wizard
You can run multiple instances of the push installer without blocking the use of the Console.
Collections and Queries
More comprehensive set of pre-defined Collections and Queries are available for each potential software distribution target (set of binary compatible machines).
Filtering functionality to help you refine the list.
Software Distribution Wizard
More intuitive page sequence.
Allows you to install multiple packages in a program.
You can take advantage of the built-in dependency ordering that RPMs provide when several RPM files are installed together.
Fails to reinstall any version of a package already installed.
Generates a script, overcoming the 255 command line character limit.
Requires "write" permission to the package source directory to create the script.
1.6 functionality not available in 2.0, includes:
Remote Tools Manager
Policy Spy
License Manager reminder alerts when each Central Site's license total differs from the number of systems identified by means of Hardware Inventory
QMX-specific Program Properties tab (See Known Issue: CR #14032).
These features are under consideration for future releases.
Note: Existing VMX/QMX for SMS licenses will not be accepted by the new version; upgraded licenses are available at no cost.
The following is a list of issues known to exist at the time of Quest® Management Xtensions - Configuration Manager 2007 Edition 2.0 release.
| CR#25193 | In Hardware Inventory, under Add/Remove Programs, The install date is not available for Mac OS X, and publisher information is only available for those packages that provide it. |
| 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#47055 | Resource Explorer does not show Services for non-global zones.
Services are reported to System Center Configuration Manager, but Resource Explorer does not contain them.
Workaround: You can run Software Metering to gather the information. |
| CR#14046 | HW Inventory incorrectly reported on ESX 3.5. The number of CPUs is not being properly reported under VMWare ESX 3.5 |
| CR#13843 | Push Installer throws an exception if User Account Control (UAC) is Cancelled on VISTA. The push installer causes an unknown exception if you start it with a non-administrator user on VISTA with UAC turned on, then cancel the User Account Control dialog box. This is because we do not have a digital certificate for the push installer. The push installer is the only executable in our console extensions that is not digitally signed. |
| CR#13846 | SSO push install fails on VISTA. Single sign on does not work for a non-administrator account. |
| CR#13849 | A non-admin user can not install QMX -- Configuration Manager 2007 on VISTA. When you run the installer (either the msi directly or through the autorun) on VISTA with a user that does not have administrator rights, you get a message that says, "An unidentified program wants access to your computer." This is because the msi is not digitally signed. |
| 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#13702 | Cannot meter programs with spaces. Configuration Manager 2007 will not meter software
applications with spaces in their names; Software Metering Rule names cannot have spaces in them.
Note: This issue was fixed for Mac OS X but not on any other platform as of the 2.0 release. |
| CR#46593 | Upgrade from 1.2.2 version loses metering data collected since the last time the
metering report was generated.
Workaround: run clienttool --run-software-metering-usage-report
before upgrading. Note: Upgrading from 1.5 to 1.6 works fine. |
The following is a list of third-party issues known to exist at the time of QMX - Configuration Manager 2007 2.0 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 or higher. |
| 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. |
| 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. |
| 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. |
| 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 |
There are four stages to upgrading to Quest® Management Xtensions - Configuration Manager 2007 Edition:
Stage 1: Upgrade the VMX or QMX for SMS Client to the new QMX - Configuration Manager Agent. (See Upgrading the Client)
Stage 2: Upgrade Microsoft System Management Server (SMS) to Microsoft System Center Configuration Manager 2007.
Stage 3: Upgrade the Quest Microsoft Management Console (MMC) extensions, which include the property pages and remote administration tools that enable you to manage non-Windows systems from the Configuration Manager Console. (See Upgrading the Console Extensions)
Stage 4: If you are upgrading from VMX for SMS 1.2.x or earlier, you must also uninstall the old Management Point Extension. There are step-by-step instructions for this in the "Upgrade" chapter of the Installation Guide. However, it is important NOT to remove the MPE until you are confident your upgrade was successful.
Important Upgrade Considerations:
Before you begin, please take note of the following:
The order in which you perform these steps is important:
You must upgrade the VMX or QMX for SMS Client to the QMX - Configuration Manager 2007 Agent before you upgrade SMS to Microsoft System Center Configuration Manager 2007.
Note: Quest recommends that you use a phased approach to upgrading your systems. Upgrade all of your VMX/QMX Clients for a particular site server completely, then upgrade them for the next site server, and so on.
After upgrading SMS to System Center Configuration Manager 2007, you must upgrade the Microsoft Management Console (MMC) extensions because the old QMX for SMS Administrator Console extensions for the Software Distribution Wizard, Remote Tools, and so froth, will not work with the new System Center Configuration Manager console. (See Upgrading the Console Extensions)
Suggestions for System Management During the Interim:
During the interim between upgrading the Client and upgrading the MMC extensions, do not create new Software Distributions for the upgraded Agent from the older MMC extensions. (Hardware and Software Inventory will work.)
To manage the new Agents with the older version of the MMC extensions, create collections based on the Agent version number. Or, you can install the new MMC console extensions on a separate console to manage the new Agents during the transition period.
After you upgrade the QMX - Configuration Manager 2007 Agent:
You must re-install your non-Windows collections and queries. (See Step 2 for how to install Collections and Queries.) The collections and queries that you created with VMX or QMX for SMS will not work with QMX - Configuration Manager 2007. QMX - Configuration Manager 2007 provides new collections and queries that are much more refined and useful for managing non-Windows resources.
For your convenience, the upgrade process creates symbolic
links for the legacy product naming conventions so that any configuration files or init scripts
that you have created for previous releases of QMX for SMS that depend on the "VMX" or
"Vintela" names are still accessible. For example, /opt/vintela/vmx
will link to /opt/quest/qmxcm unless /opt/vintela/vmx could not be
removed due to extra files. Originally this product was named Vintela Management Extensions (VMX). It is necessary
for the code base to retain some references to "VMX" or "Vintela" for
upgrade and compatibility purposes.
When you receive an upgrade for your VMX or QMX for SMS product, you can either upgrade the VMX/QMX for SMS Client manually or use the QMX for SMS Software Distribution Wizard.
Note: If you have Vintela Management Extensions (VMX) version 1.1 or older, you must first upgrade to QMX for SMS version 1.2, 1.5, or 1.6. You can not directly upgrade the 1.1 VMX Client to the 2.0 QMX - Configuration Manager 2007 Agent. It is safe to upgrade the 1.2, 1.5, or 1.6 Clients to the 2.0 QMX - Configuration Manager 2007 Agent provided that the version of the console extensions with which you are performing a distributed upgrade is not newer than the client's version.
When upgrading by means of the Software Distribution Wizard, please note:
Make sure to use the same version of the console extensions that is running on the client when you create the upgrade package. For example, if you have a client with VMX 1.2 installed, use the Admin Console with VMX 1.2 installed.
Make sure you have plenty of space for the
temporary install files! 800 MB is required in /var/opt/quest/qmxcm for AIX. Other platforms do not
require as much space; it depends on the size of the install files.
To upgrade the QMX for SMS Client Using the Wizard
In the SMS Administrator Console, navigate to and right-click the collection you wish to upgrade.
Choose All Tasks | QMX for SMS Software Distribution Wizard to start the Software Distribution Wizard.
The wizard steps you through the process of identifying the package, source files, and so forth.
When the wizard displays the Select Method dialog, choose General Unix.
Browse to select the upgrade_client.sh script file.
Note: Do not use quotes in this command line.
Proceed through the rest of the Software Distribution Wizard screens to create an Advertisement and set the date and time when you want to assign the program.
After you create the Advertisement, SMS 2003 publishes the upgrade and all the clients in the collection will install the upgrade after the next policy update.
To upgrade the QMX for SMS Client manually
Insert the installation CD into the CDROM drive of the target machine.
Note: You can install from the network file system if you do not have a physical CD by mounting the image or copying the files to your network mount. However it is important that you maintain the directory structure. (See Step 4 for details about the correct directory structure.)
Open a terminal.
Change to the root user, if necessary.
Navigate to the CD directory.
Your system may vary. You might need to mount the CD in order to navigate to it.
Change to the cdrom directory and enter:
./install_client.sh -u
Note: When upgrading, it is not necessary to enter the SITE_CODE and the MP_ADDRESS values in the command if the site code or the management point values have not changed since the last the QMX for SMS Client was installed. The upgrade script will use the existing site code and management point values if you do not supply them. The system reconfigures the new QMX - Configuration Manager 2007 Agent using the previous settings for the SMS Site Code and Management Point, unless they were invalid. For example, the Site Code must be in all capital letters. If it is not, it will ask you to reenter it with all capitals.
Because QMX - Configuration Manager 2007 2.0 has been designed to take advantage of the new user interface and productivity features of Microsoft's System Center Configuration Manager 2007, you can not automatically upgrade the Windows components from any previous release of VMX or QMX for SMS to QMX - Configuration Manager 2007 2.0.
While both QMX for SMS and QMX - Configuration Manager 2007 can coexist, the old Microsoft Management Console extensions are incompatible with the new Configuration Manager Console.
To install the new Microsoft Management Console (MMC) extensions, follow the procedures for a new installation. (See Step 1 for how to use the Quest Configuration Manager Console Extensions Setup Wizard.)
Note: After you upgrade the MMC extensions, you must enable anonymous connections in the Distribution Point configuration for Software Distribution to work properly. (See explanation in System Center Configuration Manager 2007 Requirements)
Note1: Files in Note2: You can choose 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.0 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.
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 - Configuration Manager 2007 Edition release package contains the following:
aix-power contains the QMX - Configuration Manager 2007 Agent Installation packages for the AIX operating system.
autorun folder contains the files required for the autorun feature.
diagnostics contains the hardware_information.sh script used for
collecting hardware inventory information at the command line. This is a Support tool
used to validate the actual configuration the operating system reports when queried.
docs contains the product Administrator's Guide, Installation Guide, and vastool.html
(the VASTOOL MAN PAGE).
hpux-ia64 contains the QMX - Configuration Manager 2007 Agent Installation packages for the HP-UX operating system on the Itanium platform.
hpux-parisc contains the QMX - Configuration Manager 2007 Agent Installation packages for the HP-UX operating system on the PA-RISC platform.
linux-rh2.1-x86 contains the QMX - Configuration Manager 2007 Agent Installation packages for the Red Hat 2.1 x86 operating system.
linux-rh3-x86 contains the QMX - Configuration Manager 2007 Agent Installation packages for the Red Hat 3 x86 and higher operating system.
linux-rh3-x86_64 contains the QMX - Configuration Manager 2007 Agent Installation packages for the Red Hat 3 x86_64 and higher operating system.
osx-ppc contains the QMX - Configuration Manager 2007 Agent Installation packages for the Max OS X operating system on the PPC platform.
osx-x86 contains the QMX - Configuration Manager 2007 Agent Installation packages for the Max OS X operating system on the Intel platform.
sunos-sparc contains the QMX - Configuration Manager 2007 Agent Installation packages for the Sun Solaris operating system on the SPARC platform.
sunos-x86 contains the QMX - Configuration Manager 2007 Agent Installation packages for the Sun Solaris operating system on the Intel platform.
umi contains the umi packages.
win32 .msi files for the QMX - Configuration Manager 2007 Windows components.
autorun.exe launches Autorun when the disk is inserted.
autorun.inf
install_client.sh script. The Agent Installation Script.
QMXcm2.0_ReleaseNotes.htm for this release of QMX - Configuration Manager 2007.
upgrade_client.sh script.
Please note the following before you begin the installation process:
For step-by-step installation instructions, refer to the Installation Guide located on the
installation CD in the docs folder.
Before you start the installation, it is recommended that you close all the previously open applications.
Before installing QMX - Configuration Manager 2007 into Solaris 10 zones, please read the General Zone Guidelines in the QMX - Configuration Manager 2007 Installation Guide.
Step 1: Install the Quest Configuration Manager Console extensions on all servers and workstations that run the Configuration Manager Console.
Insert the installation CD into the CD-ROM drive of the target machine to open the autorun dialog.
Click the Install tab on the autorun dialog.
Click the Quest Management Xtensions for ConfigMgr Installer link.
The Configuration Manager Console Extensions Setup Wizard starts automatically to lead you through the following dialogs:
"Welcome" dialog
License File
Destination Folder
Ready to Install
"Finish" dialog.
Close the autorun dialog and open the Configuration Manager Console.
Step 2: Install the Collections and Queries on the Central Site Server.
If you opt to install the Collections and Queries, be sure you are logged into Windows as a user with permission to create collections and queries in System Center Configuration Manager 2007. 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.
From the Configuration Manager console, navigate to System Center Configuration Manager | Site Database | Computer Management.
Right click Collections and choose Install Non-Windows Collections.
Follow the instructions on the screen to complete the installation.
In similar manner to install queries, right click Queries and choose Install Non-Windows Queries.
Step 3: Install the License.
Import the license file for each Central Site server you have using the License Manager.
From the Configuration Manager Console, right-click the Tools group to open the shortcut menu.
Choose QMX for ConfigMgr License Manager to open the License Manager dialog.
Note: When you purchase QMX - Configuration Manager 2007 you will receive an email that contains one License file. QMX - Configuration Manager 2007 manages its own licenses. The License Manager imports the license file, validates the data, and enters it into the Site Control File.
Step 4: Install the QMX - Configuration Manager 2007 Agent onto your non-Windows client machines:
Optional: If you plan to copy the installation files from the product distribution CD so that you can run the installation from your hard drive, it is important that you are careful to maintain the directory structure. You can copy only the platform-specific files that you need to a convenient location on your system; that is, you can prepare a directory containing only the install script and the directories for your operating system platform. However, the installation script is expecting to find certain files in specific locations.
The install_client.sh script is at the root of the product distribution CD.
Under that are folders for the individual operating systems. You must also copy
umi folder and the individual operating system folders under umi, as well as the
bin folder and the individual operating system folders under bin.
From the root, copy
install_client.sh script file.
platform-specific folder. For example, the osx-x86 folder.
umi folder.
From the umi folder, copy
install_umi.sh script file.
platform-specific folder. For example, the osx-x86 folder.
bin folder.
From the umi/bin folder, copy
platform-specific folder. For example, the osx-x86 folder.
Execute the install_client.sh script.
Enter the System Center Configuration Manager Site Code and Management Point when the installer prompts you for them.
| 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 - 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.
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.
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 |
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.