IBM Tivoli Software IBM Tivoli Software

[ Bottom of Page | Previous Page | Next Page | Contents ]


Documentation problems and corrections contained in previous fix packs

Planning and Installation Guide

This section contains new and updated information for IBM Tivoli Configuration Manager Planning and Installation Guide:

Defect 56291
In Chapter 5 "IBM Tivoli Configuration Manager Installation and Upgrade", in the "Custom Server Installation" section, at the end of step 10 add the following information:

Ensure that the password you specify does not contain a special character at the end.

Defect 58844
In Chapter "Component Installation Prerequisites", in the "IBM Tivoli Configuration Manager packaging" change the IBM Tivoli Configuration Manager Desktop, Version 4.2.3 description as follows:

This contains the installation image and the InstallShield wizard for a fresh installation or an upgrade of IBM Tivoli Configuration Manager on any workstation that is not a managed node or a Tivoli server.

APAR IZ26569
In Chapter 7. Maintaining and Troubleshooting a Configuration Management Environment add the following new section after the section named "Installation Fails to Start":

Tivoli Web Gateway Installation Fails on AIX

The following error is returned when running setup_aix.bin to install Tivoli Web Gateway on an AIX workstation:

Command failed for db_vendor_name -tvf
/usr/TivTwg_II/db/config/work/db/db_vendor_name/sql/create_db.sql

This might be due to an incorrect umask setting on the target workstation. Tivoli Web Gateway requires umask to be set to 022. To solve this problem, check the umask setting and correct if necessary.

License Management Extension

This section contains new and updated information for IBM Tivoli Configuration Manager License Management Extension:

APAR IY87620
In Chapter 2. Planning the license management extension topology in section "Prerequisites for new components" add after the text:

The following Configuration Manager components are prerequisites for the Configuration Manager Extension for License Manager component:

the following paragraph:

If a managed node is created to hold the Tivoli License Manager data handler the following products are needed:

APAR IY87630
In Chapter 5. Deploying and configuring agents in section "Deploying agents using Configuration Manager software package blocks" add at the end of the current step 5:

Copy the agt_install.pl script to the Tivoli server to import the software package blocks.

the following information:

Note:
Ensure that all software package blocks are stored under the same directory, otherwise the agt_install.pl script will not work.

User's Guide for Deployment Services

This section contains new and updated information for IBM Tivoli Configuration Manager User's Guide for Deployment Services:

Defect 56271
In Chapter 2 "Performing Activity Planner Operations", in the "Launching the Activity Planner GUIs" section, add to the third bullet of the procedure the following information:

To use the Activity Plan Editor and the Activity Plan Monitor GUIs from the Tivoli desktop, the user password can contain all the special characters from ASCII 32 to ASCII 127. The only special character that cannot be used is "double quotes".

Defect 58571
In Chapter 4 "Troubleshooting" add after the last section the following information:

If you are using a Sybase database in your Tivoli environment and the manual configuration of the environment is performed before installing the Activity Planner component, then the same configuration should be repeated after the Activity Planner installation because the settings of the LD_LIBRARY_PATH environment variable are overwritten by the Activity Planner installation.

Defect 58569
In Chapter 24 "Troubleshooting" add after the last section the following information:

If you are using a Sybase database in your Tivoli environment and the manual configuration of the environment is performed before installing the Directory Query component, then the same configuration should be repeated after the Directory Query installation because the settings of the LD_LIBRARY_PATH environment variable are overwritten by the Directory Query installation.

APAR IZ10192
In Chapter 4 "Troubleshooting", in the "Specific Problems and Workarounds" section, at the end of the section add the following information:

JCF paths for the APMCLASSPATH environment variable are wrong

If you migrate from older releases to Tivoli Configuration Manager 4.2.3 release, the odadmin environment variable APMCLASSPATH wrongly points to the following paths:

even if you have migrated to the correct Tivoli Management Framework level.

Manually correct the paths by modifying them as follows:

Note:
On AIX platforms, do not use the VI editor to modify these paths.
Defect 60053
In Chapter 13. Administering the Web Interface in section "Publishing and Unpublishing Web Objects" subsection "wweb" add the following information to the current {-i all | -i interp } description:

The possible values are:

Reference Manual for Software Distribution

This section contains new and updated information for IBM Tivoli Configuration Manager Reference Manual for Software Distribution:

APAR IY97515
In Chapter 1 "Editing the Software Package Definition File" in section "execute_user_program" in subsection called "Format of the execute_user_program Stanza" add before the paragraph:

The corequisite_file stanza comprises two different sets of attributes, the add_file set and add_directory set.

the following information:

When you create a package that contains:

and install it in transactional, the two corequisite files (coreq_install and coreq_commit) are downloaded on the target. During the package installation, the coreq_install file is used and then deleted. During the package commit, the coreq_commit file is used but it is not deleted, because it might be used in the remove operation if performed in transactional mode.

APAR IY98382
In Chapter 1 "Editing the Software Package Definition File" modify the table contained in section "Attributes in the File System Stanzas" as follows:

in the table row for "name" under the column "required" replace "yes" with "no".

User's Guide for Inventory

This section contains new and updated information for IBM Tivoli Configuration Manager User's Guide for Inventory:

APAR IY76046
In Chapter 3. Working with Inventory profiles, section "Software patch scan options for PC", add at the end of the section the following paragraph:

For more details on these files, refer to the IBM Tivoli Configuration Manager Patch Management Guide.

WSUS Automated Patch Management Solution
If you installed the WSUS Patch Automation solution, replace the mssecure.cab, mbsacli.exe, and ApprovedItems.txt files with the following files everywhere:
Table 82. WSUS patch management files
SUS Files WSUS Files
mssecure.cab wsusscan.cab
mbsacli.exe WindowsUpdateAgent20-x86.exe
ApprovedItems.txt ApprovedChanges.txt
APAR IY81403
The "temporary tables" feature does not apply on Sybase and Informix®, because these 2 RDBMS vendor do not clean up the contents of a temporary table after the commit; only after releasing the session to the database. So, you will see some messages like:
Sybase Server Error: Msgno 3621 Level 10 State 0 Command has
been aborted due to "unique constraint violation" errors 
caused by attempts to insertrows already present in the database.
This error can cause a decrease in performance.
APAR IY92834
In Appendix B "Commands", in the "wtransfer" section, add to the command description the following information:

The wtransfer command uses TAR software to compress the files to be transferred from one managed node to another. Some HP-UX platforms do not allow long file names, the size limit depends on the specific HP-UX version. So if the TAR software on the source workstation allows long file names, and the TAR software on an HP-UX target workstation does not, the files are not transferred. This problem can be solved only if a patch for the specific HP-UX version is available.

APAR IY96075
In Appendix E "Installing and uninstalling Common Inventory Technology (CIT)", in the "Installing Common Inventory Technology (CIT)" section, add the following information at the end of the current section:

Another way to change the CIT installation directory is to overwrite the default CIT_DestinationDirectory variable by editing the CIT_Preinstall.spb software package. The modified CIT_Preinstall.spb should then be distributed against all the gateway bundle directories replacing the old software package.

After installing any Tivoli Configuration Manager fix pack or interim fix and before performing any Tivoli Configuration Manager activity on the endpoints of your environment, perform the following steps:

  1. Make a backup copy of the old CIT_Preinstall.spb software package before replacing it with the new one.
  2. Import the software package using the CIT_import.pl command. This command creates a profile manager called Inventory_CIT_PM and adds to the profile manager the following software packages:
    CIT. 2.6.0
    CIT_Preinstall.CIT
    Note:
    The CIT version 2.6.0 might vary depending on which fix pack or interim fix you have installed.
  3. Open the Inventory_CIT_PM profile manager and right-click CIT_Preinstall.CIT.
  4. Select Convert -> Unbuild.
  5. Specify a path where to unbuild the software package, then select Convert & Close.
  6. Open CIT_Preinstall.CIT using the software package editor and select edit -> variable list editor. The default value for CIT_DestinationDirectory is:
    $(Destination_$(os_family))$(FileSeparator)
    tivoli$(FileSeparator)cit

    Modify this value for example into
    $(Destination_$(os_family))$(FileSeparator)
    ..$(FileSeparator)mydir

    The new CIT installation directory is C:\Program Files\..\my_cit_dir on Windows workstations, or /opt/../my_cit_dir path on UNIX.
  7. Save the modified variable value.
  8. Right-click again CIT_Preinstall.CIT.
  9. Select Convert.
  10. Specify the old name and path of the software package, select the overwrite check box, then select Convert & Close. The default path used by the new CIT_preinstall.spb software package has been updated.
  11. Replace the CIT_preinstall.spb software package on all the gateway bundle directories of your environment. All the following software packages must be replaced with the new .spb file:
    lcf_bundle.41100\lib\aix4-r1\inv\CIT\SPB\CIT_Preinstall.spb
    lcf_bundle.41100\lib\hpux10\inv\CIT\SPB\CIT_Preinstall.spb
    lcf_bundle.41100\lib\linux-ix86\inv\CIT\SPB\CIT_Preinstall.spb
    lcf_bundle.41100\lib\linux-ppc\inv\CIT\SPB\CIT_Preinstall.spb
    lcf_bundle.41100\lib\linux-s390\inv\CIT\SPB\CIT_Preinstall.spb
    lcf_bundle.41100\lib\solaris2\inv\CIT\SPB\CIT_Preinstall.spb
    lcf_bundle.41100\lib\solaris2-ix86\inv\CIT\SPB\CIT_Preinstall.spb
    lcf_bundle.41100\lib\w32-ix86\inv\CIT\SPB\CIT_Preinstall.spb
Note:
It is recommended to test the new variable on some endpoints, before deploying it to the entire environment.
Feature 205561
In Appendix B "Commands" in section "wsetinvpchw" add to the list of the -a components the following new component:
Lpar
Lists the number of processors allocated on each logical partition.
Feature 205561
In Appendix B "Commands" in section "wgetinvpchw" add at the end of the command output the following row:
Lpar:YES
Feature 205561
In Appendix E "Installing and uninstalling Common Inventory Technology (CIT)" after the "Managing the Inventory bundle dependency set" section, add the following new sections:

Scanning virtual environments

Inventory uses the CIT capability to collect LPAR information in a VMware environment.

VMware versions supported by CIT are shown in the table below:

Table 83. Versions of VMware supported by CIT
VMWare versions tested on CIT
ESX Server 2.5.3
ESX Server 3.0
ESX Server 3.01
ESX Server 3.02
ESX Server 3.5

Standard Inventory functions are not impacted whether the scans are performed on guest or host operating systems. However, due to a limitation of the data export function in the virtualization software, hardware and software discovery operations performed on guest operating systems might report incorrect data.

CIT provides an enabler to export correct data to the guest systems so that CIT instances installed on each operating system partition can discover and return correct data.

The CIT enabler stores the correct hardware information on the guest operating systems. In this way when a hardware Inventory scan starts on a guest operating system, the correct hardware configuration data is retrieved and stored in the Inventory RDBMS. You can query the data by running the LOGICAL_PARTITION_QUERY and the LOGICAL_PARTITIONED_SYSTEMS_QUERY

Starting the enabler

The CIT enabler is installed on the physical workstation which hosts the guest operating systems. The CIT enabler does not require an installation process. To use the CIT enabler, copy the files listed below from the /cit_enabler folder on the IBM Tivoli Configuration Manager, Version 4.2.3 Fix Pack 9 CD 1 to the workstation which hosts the guest operating systems:

Table 84. Enabler executable files
Virtual software Supported OS Files
VMware Microsoft Windows
  • cpuid.exe
  • retrieve.pl
  • wenvmw.exe
Linux
  • cpuid
  • dispatcher
  • retrieve.pl
  • wenvmw.sh

You must install VMware VmPerl Scripting API before starting the enabler for the first time.

To start the enabler, launch the executable file from a shell or command prompt. You can optionally specify the -v option to generate a log file named env_out.txt, which is created in the same directory where the executable file is located.

Notes:
  1. The guest workstations must be active when the enabler is started.
  2. Any guest workstations not active when the enabler is running, are not detected.
  3. If you run the enabler after the configuration changes are applied to the guest workstation, the updated data is returned by the hardware scan.
  4. The information retrieved by the enabler is deleted after a reboot.

Enabler return codes

The following is a list of the return codes returned by the enabler. Return codes help you identify the result of the command.

A return code of 0 indicates that the command completed successfully:

OK: CIT ENABLER return code = 0

while a nonzero return code indicates that an error occurred. The following example shows the case in which the user does not have enough privileges, when running the CIT enabler executable:

OK: CIT ENABLER return code = 11
ERROR: dispatcher return code = 11"

A complete list of all nonzero return codes is provided in the table below:

Table 85. Enabler return codes
Return value Code Description
RETRIEVE_NODECAPACITY_ERROR 1 Cannot collect host system processor number.
RETRIEVE_NODEID_ERROR 2 Cannot collect host system serial number.
RETRIEVE_VMCAPACITY_ERROR 3 Cannot collect number of processors assigned to virtual machines.
RETRIEVE_VMID_ERROR 4 Cannot collect virtual machines IDs.
SET_GUESTINFO_ERROR 5 Cannot transfer information from host system to guest systems.
GET_VMLIST_ERROR 6 Cannot retrieve list of registered virtual machines.
CONNECT_VM_ERROR 7 Cannot establish connection with virtual machines.
NO_PRIVILEGES 11 User does not have enough privileges when running the CIT enabler executable.
GENERIC_ERROR -1 A generic error has occurred. For more information, enter the command again with the -v option. The resulting information is logged into the env_out.txt file.
VMWARENOTFOUND_ERROR 100 VMware Server not found on host system.
VMWARENOTSUPPORTED_ERROR 105 VMware Server version not supported.
VMPERL_NOT_FOUND 120 VmPerl Scripting API not found or incorrectly configured.
Defect 205492
In Appendix E "Installing and uninstalling Common Inventory Technology (CIT)" in section "Installing Common Inventory Technology (CIT)" replace the current step 5 of the procedure with the following information:

On the Inventory server, run the following command:

winstsp -f -ty @CIT. 2.6.0 @Endpoint:ep1
wcommtsp -f @CIT. 2.6.0 @Endpoint:ep1 

where:

ep1
Is the name of the endpoint.
Defect 205493
In Appendix E "Installing and uninstalling Common Inventory Technology (CIT) in section "Installing Common Inventory Technology (CIT)" replace the current step 2 of the procedure with the following information:

On the Inventory server, run the following command:

$BINDIR/../generic/inv/SCRIPTS/CIT_import.pl -d CD_ROM/CIT_SPB

where

CD_ROM/CIT_SPB
Specifies the path where the CIT_Preinstall.spb and CIT.spb software packages are located on the IBM Tivoli Configuration Manager, Version 4.2.3 Fix Pack 9 CD 1.

You can also copy the software packages to a local folder and run the command locally.

Defect 203233
In Appendix F "Troubleshooting" add the following new section called Common Inventory Technology scanners:

If you experience issues related to Inventory hardware and software scans, for example the scan fails or does not collect all the expected information, it is necessary to use a troubleshooting procedure specific for the Common Inventory Technology component.

Collect the configuration files that Tivoli Configuration Manager writes and passes to the Common Inventory Technology scanners as input parameters, and the command line syntax that Tivoli Configuration Manager uses when invoking the Common Inventory Technology scanners. Depending on the different customizations of the InventoryConfig profile and the platform on which the scan runs, the above-mentioned commands and configuration files are:

Table 86. Commands and configuration files on Windows platforms
Windows
Type of scan Command Configuration file
Hardware scan
C:\Program Files\tivoli\cit
\bin\wscanhw -c C:\win_ep_name\
\inv\SCAN\config.xml -o
C:\win_ep_name\\inv\SCAN\
tivhscan.mif-m
config.xml

Scan for installed products

using signature matching

C:\Program Files\tivoli\cit
\bin\wscansw -i C:\win_ep_name\
\inv\SCAN\wscansw.xml -o
C:\win_ep_name\\inv\SCAN\
swscan.xml -c C:\win_ep_name\
\inv\SCAN\config.xml -e
C:\win_ep_name\\inv\SCAN\
warning.out
wscansw.xml, config.xml
Scan files for basic information
C:\Program Files\tivoli\cit
\bin\wscanfs -c C:\win_ep_name\
\inv\SCAN\config.xml -o 
C:\win_ep_name\
\inv\SCAN\tivfscan.mif -m
config.xml
Scan files for header information
C:\Program Files\tivoli\cit\
bin\wscanfs -c C:\win_ep_name\
\inv\SCAN\config3.xml -o
 C:\win_ep_name\\inv\SCAN\
tivwscan.mif -m
config3.xml
Scan registry for product information
C:\Program Files\tivoli\cit\
bin\wscanvpd -c C:\win_ep_name\
\inv\SCAN\config.xml -o
 C:\win_ep_name\\inv\SCAN\
tivrscan.mif -m
config.xml
Table 87. Commands and configuration files on UNIX platforms
UNIX
Type of scan Command Configuration file
Hardware scan
/opt/tivoli/cit/bin/wscanhw -c
 /tivoli/unix_ep_name/
/inv/SCAN/config.xml -o 
/tivoli/unix_ep_name
//inv/SCAN/
tivhscan.mif -m
config.xml

Scan for installed products

using signature matching

/opt/tivoli/cit/bin/wscansw -i
 /tivoli/unix_ep_name/
/inv/SCAN/wscansw.xml -o 
/tivoli/unix_ep_name/
/inv/SCAN/swscan.xml -c 
/tivoli/unix_ep_name//inv/
SCAN/config.xml -e /tivoli/
unix_ep_name//inv/SCAN/
warning.out
wscansw.xml, config.xml
Scan files for basic information
/opt/tivoli/cit/bin/wscanfs
 -c /tivoli/unix_ep_name//
inv/SCAN/config.xml -o 
/tivoli/unix_ep_name/
/inv/SCAN/tivfscan.mif -m
config.xml
Scan registry for product information
/opt/tivoli/cit/bin/wscanvpd
 -c /tivoli/unix_ep_name//inv/
SCAN/config.xml -o /tivoli/
unix_ep_name//inv/SCAN/
tivrscan.mif -m
config.xml

The Common Inventory Technology scanners might return error codes. Return codes help you identify the result of the command: a return code of 0 indicates that the command completed successfully, while a nonzero return code indicates that an error occurred. A list of all nonzero return codes is given in Table 88:

Table 88. Return codes
Return value Code Description
WSRC_WRONG_PARMS 1 One or more CLI options are incorrect.
WSRC_INPUT_FILE_PARSE_ERROR 2 An error occurred while parsing the configuration file.
WSRC_SIGNATURE_FILE_PARSE_ERROR 3 An error occurred while parsing the signature file.
WSRC_OUTPUT_FILE_ERROR 4 An error occurred while writing the output file.
WSRC_INPUT_FILE_ERROR 5 An error occurred while reading the input file.
WSRC_MISSING_SIGNATURE_FILE 6 No signature file was specified and no default signature file is available.
WSRC_VALUE_OUT_OF_BOUND 7 One of the values you specified exceeds the assigned limits.
WSRC_INTERNAL_ERROR 8 An internal error has occurred.
WSRC_TIMEOUT_ELAPSED 9 The specified timeout has expired.
WSRC_UPGRADE_IN_PROGRESS 10 CIT is being upgraded and commands are momentarily not responding.
WSRC_FILE_READ_ONLY 11 The output file is read only.
WSRC_INIFILE_NOT_FOUND 12 The cit.ini file was not found.
WSRC_CITFILE_NOT_FOUND 13 The CIT configuration file was not found.
WSRC_CCLOGFILE_NOT_FOUND 14 The CitTrace.properties file was not found.
WSRC_KEY_NOT_FOUND 15 The value you specified is incorrect.
WSRC_VALUE_NOT_VALID 16 The specified value is not valid.
WSRC_KEY_CANNOT_CHANGE 17 The specified key cannot be modified.
WSRC_FILE_CANNOT_OPEN 18 Cannot open the specified file.
WSRC_FILE_CANNOT_RENAME 19 Cannot rename the specified file.
WSRC_FILE_CANNOT_DELETE 20 Cannot delete the specified file.
WSRC_CITFILE_NOT_VALID 21 The cit.ini file is corrupt.
WSRC_CIT_TRACEFILE_NOT_VALID 22 The trace file is corrupt.
WSRC_INVALID_AGE 24 The age you specified is incorrect.
WSRC_INVALID_TIMEOUT 25 The timeout you specified is incorrect.
WSRC_INVALID_ATTRIBUTE 26 The attribute you specified is incorrect.
WSRC_INVALID_OUTPUT_FORMAT 27 The output format you specified is not supported.
WSRC_CANNOT_LOAD_PROVIDER 28 The required .dll or shared library file is not available.
WSRC_QUERY_TIMED_OUT 29 The query has reached the timeout.
WSRC_QUERY_FAILED 30 The query has failed.
WSRC_PROCESS_INTERRUPTED 31 The process was interrupted.
WSRC_NO_CONFIG_NAME 32 No configuration file was specified.
WSRC_NO_CONFIG_OPTION 33 No configuration option was specified.
WSRC_NO_OUTPUT_NAME 34 No output file was specified.
WSRC_NO_PARMS 35 No parameters were specified.
WSRC_EMPTY_CONFIG_ELEMENT 36 The configuration file contains an empty element.
WSRC_FAILURE 37 An internal error has occurred.
WSRC_NO_SORT_FIELD_NAME 38 You specified the sort option in the command without specifying a sort criterion.
WSRC_INVALID_SORT_FIELD_NAME 39 The sort criterion you specified is incorrect.
WSRC_WARNING_FILE_ERROR 40 An error has occurred while attempting to create the warning file during a software scan.
WSRC_UNABLE_TO_INITALIZE 41 The process initialization failed.
WSRC_MISSING_XSS_SCHEMA_FILE 42 Cannot find the signature catalog schema.
WSRC_UNABLE_INSTALL_DRIVER 45 Cannot install the CITMDRV_IA64.SYS, CITMDRV_AMD64.SYS, CITMDRV.SYS drivers.
WSRC_UNABLE_LOAD_CITMEMDLL 46 Cannot load the CITMEM.DLL library.
WSRC_UNABLE_LOAD_SYMBOL_
IN_CITMEM
47 Cannot load the symbols in the CITMEM.DLL library.
WSRC_UNABLE_READ_CITMEMDLL 48 Cannot read the CITMEM.DLL library.
WSRC_FILE_ACCESS_DENIED 49 The user does not have sufficient rights to access the file.
WSRC_NOT_AUTHORIZED 50 The user does not have sufficient rights to perform the operation.
WSRC_FILE_NOT_FOUND 51 The specified file or directory does not exist.
Defect 204521
In Appendix F "Troubleshooting" add the following new section called Common Inventory Technology installations:

The default installation of Common Inventory Technology is performed on the endpoints using the Tivoli Configuration Manager Software Distribution disconnected command line.

Use the following troubleshooting procedure when installing Common Inventory Technology on Tivoli Configuration Manager workstations:

  1. Enable the Software Distribution disconnected CLI traces by opening on the endpoint the Software Distribution swdis.ini file, which can be found under the %WINDIR% directory on Windows and the /etc/Tivoli directory on UNIX, and set the trace_level value to 5 in the MOBILE section of the file. A sample MOBILE section of the swdis.ini file follows:
    [#MOBILE]
    product_dir=C:\swdis
    working_dir=C:\swdis\work
    backup_dir=C:\swdis\backup
    profile_dir=C:\swdis\work\profiles
    trace_level=0
    trace_size=1000000
    send_timeout=300
    autopack_dir=C:\swdis\autopack
    staging_dir=swdis\service
    user_file_variables=C:\swdis\swdis.var
    import_libraries=spd,libecimp
  2. Distribute an Inventory profile by running the wdistinv command using the inv_ep_debug option, so that when the Inventory scan runs on the endpoint, a log file called INVxxxxx.LOG (where xxxxx is the scan_id) is created under the inv/SCAN directory.
  3. Collect under the inv/SCAN directory the file INVxxxxx.LOG, and under the product directory specified in the MOBILE section mentioned in step 2 the trace files *.trc, and under the working directory the epsp.cat file. Collect the cit.ini file, which can be found under the %WINDIR% directory on Windows or the /etc/Tivoli directory on UNIX.
APAR IY96992
In Appendix E "Troubleshooting" section "Common Inventory Technology traces" modify the following information:

The current path under "On Windows systems" should be replaced with:

C:/Program Files/ibm/tivoli/common/CIT/logs/traceCIT.log

The current path under "On UNIX systems" should be replaced with:

/usr/ibm/tivoli/common/CIT/logs/traceCIT.log
APAR IY99115
In Appendix B "Commands" section "winvmigrate" subsection "examples" replace:
winvmigrate -c C:\temp\ITLM22ForIBM_SoftwareCatalog_2006-06-30.xml
with:
winvmigrate -c C:\temp\IBM_SoftwareCatalog.xml
APAR IY99115
In Chapter 5 "Collecting custom information with Inventory" section "Using signatures" replace the current instructions at the end of the section with the following instructions:
APAR IY99115
In Chapter 5 "Collecting custom information with Inventory" section "Using signatures" add at the end of the section the following new information:

From the following FTP Web site

ftp://ftp.software.ibm.com/software/tivoli_support/misc/CandO/TivoliCatalog/

you can download the following catalog files:

Note:
The files that can be used by Tivoli Configuration Manager are:
  • ITLM22_SoftwareCatalog_YYYY-MM-DD.xml
  • YYMMDDSWSIGS.INI
The other files are for Tivoli License Manager only.

Since June 2007 the new naming convention of these files is the following:

Note:
The files that can be used by Tivoli Configuration Manager are:
  • itlcm22-allProducts-fullSwCat-YYYYMMDD.xml
  • inventory-allProducts-fullSwCat-YYYYMMDD.ini
The other files are for Tivoli License Manager only.
APAR IZ13447
In Appendix B "Commands" in section "winvmgr" add the following command parameter when describing the -c option:

PM_WSUS_enabled=y | n

Specifies if you want to use the Microsoft WSUS Server for the Automated Patch Management solution provided by Tivoli Configuration Manager.

Defect 59750
In Appendix E "Installing and uninstalling Common Inventory Technology (CIT)" in section "Installing Common Inventory Technology (CIT)" replace the current step 5 of the procedure with the following information:

On the Inventory server, run the following command:

winstsp -f -ty @CIT. 2.6.0 @Endpoint:ep1
wcommtsp -f @CIT. 2.6.0 @Endpoint:ep1 

where:

ep1
Is the name of the endpoint.
Note:
This installation method is not supported on OS/400 systems.

Database Schema Reference

This section contains new and updated information for IBM Tivoli Configuration Manager Database Schema Reference:

Defect 202144
In Chapter 3 "Configuration repository views", in the "Inventory views" section, at the end of the MATCH_SWARE_VIEW description add the following note:

The extended signatures are not displayed by the MATCH_SWARE_VIEW, while they are displayed by the INST_SWARE_VIEW.

APAR IY95425
In Chapter 5 "Configuration repository tables", in the "Inventory tables" section, at the end of the FILE_DESC table description add the following note:

The following columns:

FILE_COMMENTS
FILE_INTERNAL_NAME
FILE_PRODUCT_NAME
FILE_COMPANY_NAME
FILE_LEG_COPYRIGHT
FILE_PROD_VERSION
FILE_DESCRIPTION
FILE_LEG_TRADEMARK
FILE_PRIVATE_BUILD
FILE_VERSION
FILE_ORIG_FILENAME
FILE_SPECIAL_BUILD  

are populated only by data coming from scans run against pervasive devices.

Feature 205561
In Chapter 3 "Configuration repository views" in section "LPAR_VIEW" check all the Windows NT/2000 columns of the table and add the following note after the table:
Note:
For these operating systems, on a VMware environment, you must run the CIT enabler on the host server after starting the guest workstation and before running the scan.
Feature 205561
In Chapter 3 "Configuration repository views" in section "LOGICAL_PARTITIONS_VIEW" check all the Windows NT/2000 columns of the table and add the following note after the table:
Note:
For these operating systems, on a VMware environment, you must run the CIT enabler on the host server after starting the guest workstation and before running the scan.
Feature 205561
In Chapter 3 "Configuration repository views" in section "LPAR_SYSTEMS_VIEW" check all the Windows NT/2000 columns of the table and add the following note after the table:
Note:
For these operating systems, on a VMware environment, you must run the CIT enabler on the host server after starting the guest workstation and before running the scan.
Feature 205563
In Chapter 5 "Configuration repository tables" section "Inventory tables" add the following new subsection:

ALL_NET_ADAPTER

Describes the physical and virtual network adapter installed on a system. One record exists for each network adapter for each system scanned.

Populated by an inventory hardware scan.

The columns in this table are as follows:

COMPUTER_SYS_ID (primary key)

ADAPTER_ID (primary key)

PERM_MAC_ADDR

CURRENT_ADDR

ADAPTER_TYPE

ADAPTER_MODEL

MANUFACTURER

INST_DATE

RECORD_TIME

Feature 205563
In Chapter 4 "Queries" section "Inventory queries" add the following new subsection:

ALL_NET_CARD_QUERY

Returns information about network cards on target systems.

Runs against the view ALL_NET_CARD_VIEW.

The columns in this query are as follows:

TME_OBJECT_LABEL

TME_OBJECT_ID

COMPUTER_SYS_ID

ADAPTER_ID

PERM_MAC_ADDR

CURRENT_ADDR

ADAPTER_TYPE

ADAPTER_MODEL

MANUFACTURER

INST_DATE

RECORD_TIME

Feature 205563
In Chapter 4 "Queries" section "Historical inventory queries" add H_ALL_NET_CARD_QUERY to the existing list.
Feature 205563
In Chapter 3 "Configuration repository views" in section "Inventory views" add the following new subsection:

ALL_NET_CARD_VIEW

Displays information about physical and virtual network cards on target systems.

Based on the COMPUTER and ALL_NET_ADAPTER tables.

The columns in this view are as follows:

Column Name Description AIX HP-UX Linux (S/390) Linux (PC) NetWare OS/2 OS/400 Solaris Windows 98 Windows NT/2000
W Reported only on systems with WMI.
TME_OBJECT_LABEL The object label for the system. X X X X X X X X
TME_OBJECT_ID The object ID for the system. X X X X X X X X
COMPUTER_SYS_ID The computer system ID. X X X X X X X X
ADAPTER_ID The unique ID of the adapter. X X X X X X X X
PERM_MAC_ADDR The permanent media access control (MAC) address for the system. X X X X X X
CURRENT_ADDR The current network address for the system. X X X X X X
ADAPTER_TYPE The network adapter installed on the system. X X X X X X
ADAPTER_MODEL The model of the network adapter installed on the system. X X X X X X X
MANUFACTURER The manufacturer of the network adapter installed on the system. X X X X
INST_DATE The date that the network card was installed on the system. X W
RECORD_TIME The time that the data was updated at the database. X X X X X X X X
Feature 205563
In Chapter 3 "Configuration repository views" in section "Historical inventory views" add H_ALL_NET_CARD_VIEW to the existing list.
APAR IY97995, IY97996
In Chapter 3 "Configuration repository views" in section "Inventory views" before the subsection called "ASP_VIEW" add the following new note:
Note:
Some views, created by the .sql scripts, such as CAT_SIG_V and CHECK_SIG are not described in this manual because they are used for product internal tasks only, and do not apply to an external user.
APAR IY97094
In Chapter 5 "Configuration repository tables" at the end of the "SIGNATURE" section add the following note:
Note:
The possible values for the IBM_SOURCE key are:
CUSTOM
A signature you created.
IBM
A signature loaded from the IBM signature catalog.
SWD
A signature created by the Tivoli Configuration Manager Software Distribution.
APAR IY97190
In Chapter 3 "Configuration repository views" section "COMPUTER_VIEW" insert a row in the existing table having as column name OS_KERNEL_MODE, as description "The operating system kernel mode (32-bit or 64-bit)" and check all operating systems except for OS/2, NetWare, OS/400 and Linux (pc).
APAR IY97190
In Chapter 4 "Queries" section "COMPUTER_QUERY" add OS_KERNEL_MODE to the existing list.
APAR IY97190
In Chapter 5 "Configuration repository tables" section "COMPUTER" add OS_KERNEL_MODE to the existing list.
APAR IZ11361
In Chapter 3 "Configuration repository views", in the "PROCESSOR_VIEW" section, add the following row to the current table:
Column Name
IS_ENABLED
Description
The enablement of the processor. Possible values are:
Y
The processor is enabled.
N
The processor is not enabled.
H
(Windows platforms only) The hyperthreading feature is enabled.
and check all operating systems listed in the table.
APAR IZ14763
In Chapter 5 "Configuration repository tables", before the "INST_PARTITION" section, add the following table:

INST_PARTITION_MB

Describes a disk partition on a drive on the system. One record exists for each partition for each system scanned.

Populated by an inventory hardware scan.

The columns in this table are as follows:

COMPUTER_SYS_ID (primary key)

FS_ACCESS_POINT (primary key)

DEV_NAME

PARTITION_TYPE

MEDIA_TYPE

PHYSICAL_SIZE_MB (1)

FS_TYPE

FS_MOUNT_POINT

FS_TOTAL_SIZE_MB (1)

FS_FREE_SIZE_MB (1)

RECORD_TIME

Note:
(1) The size values of these columns are specified in megabytes.
APAR IZ14763
In Chapter 3 "Configuration repository views", before the "PARTITION_VIEW" section, add the following view:

PARTITION_MB_VIEW

Displays information about disk partitions on target systems.

Based on the COMPUTER and INST_PARTITION_MB tables.

The columns in this view are as follows:

Column Name Description AIX HP-UX Linux (S/390) Linux (PC) NetWare OS/2 OS/400 Solaris Windows 98 Windows NT/2000
TME_OBJECT_LABEL The object label for the system. X X X X X X X X X
TME_OBJECT_ID The object ID for the system. X X X X X X X X X
COMPUTER_SYS_ID The computer system ID. X X X X X X X X X
FS_ACCESS_POINT The location where the partition is mounted. X X X X X X X X X
DEV_NAME The device name. X X X X X X X X X
PARTITION_TYPE The type of partition on the drive. X X X X X X X X X
MEDIA_TYPE The media type that contains the partition. X X X X X X X X X
PHYSICAL_SIZE_MB The size of the drive that contains the partition in MB. X X X X X X X X X
FS_TYPE The file system type. X X X X X X X X X
FS_MOUNT_POINT The point where the partition attaches to the operating system. X X X X X X X X X
FS_TOTAL_SIZE_MB The size of the partition in MB. X X X X X X X X X
FS_FREE_SIZE_MB The amount of free space on the partition in MB. X X X X X X X X X
RECORD_TIME The time that the data was updated at the database. X X X X X X X X X
APAR IZ14763
In Chapter 4 "Queries", before the "PARTITION_QUERY" section, add the following query:

PARTITION_MB_QUERY

Returns information about disk partitions on target systems.

Runs against the view PARTITION_MB_VIEW.

The columns in this query are as follows:

TME_OBJECT_LABEL

TME_OBJECT_ID

COMPUTER_SYS_ID

FS_ACCESS_POINT

DEV_NAME

PARTITION_TYPE

MEDIA_TYPE

PHYSICAL_SIZE_MB

FS_TYPE

FS_MOUNT_POINT

FS_TOTAL_SIZE_MB

FS_FREE_SIZE_MB

RECORD_TIME

Feature 221408
In Chapter 5. Configuration repository tables in section "LPAR" add the following columns to the current table:
Feature 221408
In Chapter 3. Configuration repository views in section "LPAR_VIEW" add the following rows to the current view:
Column Name Description AIX HP-UX Linux (S/390) Linux (PC) NetWare OS/2 OS/400 Solaris Windows 98 Windows NT/2000

PHYS_SHAREDPC

The physical shared pool capacity. X

PHYS_SHAREDPC_CORES

The physical shared pool capacity in cores. X

LPAR_ONLINE_VP_COUNT

The number of online virtual processors in the partition. X

LPAR_IS_SHARED_TYPE

If the partition runs on a shared pool of processors, then the value of the field is Y. Otherwise the partition is dedicated and the field value is N. X

LPAR_IS_CAPPED

If partition is of a shared type and is marked as capped, then the field gets the value Y. In other cases it is N or empty as in the case of dedicated partition. X

LPAR_ENTITLEMENT

The current entitlement of the partition, such as the number of processing units that the partition is guaranteed to get if it needs them. X

LPAR_MIN_VP_COUNT

The minimum virtual processor setting for the partition. X

LPAR_MAX_VP_COUNT

The maximum virtual processor setting for the partition. X

LPAR_MIN_CAPACITY

The minimum capacity for the partition. X

LPAR_MAX_CAPACITY

The maximum capacity for the partition. X

LPAR_IDLE_CP_WEIGHT

The idle capacity weight setting for the partition, such as the priority of the partition when idle CPU resources are distributed among partitions. X

SMT_IS_ENABLED

The SMT (Simultaneous Multithreading) status in the partition. If SMT is enabled the field is Y; if SMT is disabled it is N. X

NODE_ACT_PROC_COUNT

The number of physical CPUs that are licensed and active in the system. For IBM partitioned systems, it is the total of dedicated processors and shared processors. X
APAR IZ29297
In Chapter 4. Queries in section "LOGICAL_PARTITIONS_QUERY" add the following columns to the current query:
APAR IZ29297
In Chapter 3. Configuration repository views in section "LOGICAL_PARTITIONS_VIEW" add the following rows to the current view:
Column Name Description AIX HP-UX Linux (S/390) Linux (PC) NetWare OS/2 OS/400 Solaris Windows 98 Windows NT/2000
LPARCAP_IN_CORES The number of processor cores assigned to the partition. X X X1 X 1X
NODECAP_IN_CORES The number of processor cores in the system (node). X X X1 X 1X
SHAREDPC_IN_CORES Total number of processor cores available in the shared pool. X X1 X 1X
Note:
1 For these operating systems, on a VMware environment, it is required to run the CIT enabler on the host server after starting the guest workstation and before running the scan.
APAR IZ45160
In Chapter 4. Queries in section "PARTITION_MB_QUERY" add the following note to the column named FS_FREE_SIZE_MB:
Note:
The value of this column for Windows platforms might report a value bigger than the total disk size, because it is the value returned by the Microsoft WMI layer.
APAR IZ45160
In Chapter 4. Queries in section "PARTITION_QUERY" add the following note to the column named FS_FREE_SIZE_KB:
Note:
The value of this column for Windows platforms might report a value bigger than the total disk size, because it is the value returned by the Microsoft WMI layer.
APAR IZ45160
In Chapter 5. Configuration repository tables in section "INST_PARTITION_MB" add the following note to the column named FS_FREE_SIZE_MB:
Note:
The value of this column for Windows platforms might report a value bigger than the total disk size, because it is the value returned by the Microsoft WMI layer.
APAR IZ45160
In Chapter 5. Configuration repository tables in section in section "INST_PARTITION" add the following note to the column named FS_FREE_SIZE_KB:
Note:
The value of this column for Windows platforms might report a value bigger than the total disk size, because it is the value returned by the Microsoft WMI layer.

Patch Management Guide

This section contains new and updated information for IBM Tivoli Configuration Manager Patch Management Guide:

In Chapter 2 "Installing the automated patch management solution", in the "Upgrading the Patch Management Automation Server driver" section, replace step 6 with the following text:

In Chapter 7 "Troubleshooting", at the end of the "Other common problems" section, add the "Wrong code set" sub-section:

Cause: If you are defining a name for a group, a patch, or any other object, containing a character code set that is not defined in the Tivoli environment, the character is not displayed correctly in the name.

Solution: Set the TIS_CODESET variable to the appropriate code set as follows:

  1. Copy the Tivoli environment settings to a temporary file:
    odadmin environ get >env.out
  2. Add the following line to the temporary file:
    TIS_CODESET = TIS_CODESET
    where TIS_CODESET is the new value of the code set.
  3. Import the new TIS_CODESET setting value in the Tivoli environment:
    odadmin environ set < env.out
  4. Stop and start the Tivoli server:
    reexec oserv all

APAR IY98107
In Chapter 1 "Introduction" in section "Planning your environment" modify the table called "Patch tools" as follows:

At the end of the wsusscn2.cab description add the following note:

Note:
The wsusscn2.cab file is renamed as wsuscan.cab during the download process. After updating the catalog with the new wsusscn2.cab file, verify if the date of the wsuscan.cab file matches the size and date of the new wsusscn2.cab file.
Defect 59014
In Chapter 3 "Configuration and administrative tasks" in section "Configuring automated patch management settings" add the following information:

At the end of the Add tioadmin login description add the following note:

Note:
Ensure that the tioadmin user is allowed to write to the following product directories:
  • product_dir
  • provider_patch_dir
  • provider_spb_dir
This is valid only if these directories are local.
Defect 59003
In Chapter 1 "Introduction" in section "Operating systems and applications managed with this solution" replace the current bullet: with the following information:

APAR IZ01645
In Chapter 7 "Troubleshooting" in section "Common problems and troubleshooting scenarios" add at the end of the subsection called "Other common problems" the following information:

Windows Update Agent (WUA) does not work properly

For the Microsoft Windows Update Agent (WUA) to work properly, ensure that the following Windows services are enabled and set to Automatic:

In addition, for the WUA to receive necessary updates from other Microsoft products, ensure that Windows Installer 3.1 is installed.

Defect 59751
In Chapter 6 "Automated patch management command line" in section "wsecgensp" add the following information to the "Options" subsection:

-H 9
Specifies whether software packages are generated using the installer for Windows 2008 and Windows Vista. If this option is not specified or if you enter a value different from 9, the packages are created using the default installer.
and add to the current usage of the command the following information:
[-H 9]
APAR IZ13447
In Chapter 3 "Configuration and administrative tasks" in section "Configuring automated patch management settings" add the following information at the end of the section:

winvmgr command

Specify if you want to use the Microsoft WSUS Server for your patch management operations by running the following Inventory command:

winvmgr -c PM_WSUS_enabled=y
Defect 59810
In Chapter 1 "Introduction" in section "Operating systems and applications managed with this solution" add to the current list the following bullets: and add after the bulleted list the following note:
Note:
No operating system patches are supported for Windows Server 2008, only patches related to software applications.

User's Guide for Operating System Deployment Solution

This section contains new and updated information for IBM Tivoli Configuration Manager User's Guide for Operating System Deployment Solution:

In Chapter 1 "Overview", in the "Components of an operating system imaging solution" section, replace the note under the IBM Tivoli Provisioning Manager for Operating System Deployment server at Spoke level description with the following:
Note:
The IBM Tivoli Provisioning Manager for Operating System Deployment server at Spoke level must be a managed node and endpoint. The config.csv file contains a line for the IBM Tivoli Provisioning Manager for Operating System Deployment server at Spoke level. The "Description" field of this line must contain a name equal to the label of the endpoint installed on the IBM Tivoli Provisioning Manager for Operating System Deployment server at Spoke level.
In Chapter 2 "Planning and installing your environment", at the end of the "Configuring the Rembo.ini file" section, add the following information:

After you customized the rembo.ini file, you must stop and start the Activity Planner engine by running the following commands from the Tivoli server bash shell:

wstopapm
wstartapm
In Chapter 2 "Planning and installing your environment", in the "Installation requirements for Tivoli Provisioning Manager for Operating System Deployment" section, after the "Server system requirements information", add the following information:

Operating System Requirements:

The Tivoli Provisioning Manager for Operating System Deployment servers must be installed on Windows platforms only.

In Chapter 2 "Planning and installing your environment", in the "How to set up Tivoli Provisioning Manager for Operating System Deployment" section, change the text as follows:
In Chapter 2 "Planning and installing your environment", in the "Requirements for the installation" section, replace the link in step 1 with the following:

http://www.microsoft.com/downloads/details.aspx?familyid= 0CAA294C-29D9-4449-81D5-4B69B97DF7AE&displaylang=en

In Chapter 4, "Generating differential Tivoli Provisioning Manager for Operating System Deployment files", in the "Step 1: Generating the Differential RAD activity plan:" sub-section, modify step 3 as follows:

Enter a RAD file name that does not include special characters. This is because the Update Slaves activity passes the file name to a Tivoli bash script and the Tivoli bash does not support special characters.

In Chapter 4 "Implementing the operating system imaging solution", in the "Backing up user settings" section, replace the first two bullets under step 3 with the following:
In Chapter 4 "Implementing the operating system imaging solution", in the "Refreshing a workstation" section, replace the first two bullets under step 3 with the following:
In Chapter 4 "Implementing the operating system imaging solution", in the "Refreshing a workstation" section, replace the first two bullets under step 3 with the following:

Guide for Microsoft Active Directory Integration

This section contains new and updated information for IBM Tivoli Configuration Manager Guide for Microsoft Active Directory Integration:

APAR IY93326
In Chapter 6. Query Directory for Microsoft Active Directory command line in sections named "wadquerydc", "wadquerycfg", and "wadqueryrep", add the following information to the "Authorization" subsection:

Domain administrator

For issuing the logon_user option of the command.

Tivoli Integration Pack for NetView User's Guide

This section contains new and updated information for IBM Tivoli Integration Pack for NetView User's Guide:

APAR IY92481
In Chapter 3, in the "Configuring Tivoli Discovery" section, add the following sentence at the end of the existing note:

The NetView database and the Tivoli Report are updated only with those resources having the transport protocol set to AF_INET.

Messages and Codes

This section contains new and updated information for IBM Tivoli Configuration Manager Messages and Codes:

Defect 55666

CMYSE0265E
You cannot create the software package because the SWD-Inventory integration is currently disabled.
Explanation:

The command you are using requires integration with Inventory.

System action:

The operation failed.

Operator response:

If inventory integration is required, use the wswdmgr software distribution command and the wsetinvswd Inventory command to enable integration. See: IBM® Tivoli® Configuration Manager: Reference Manual for Software Distribution, SC23-4712 and IBM Tivoli Configuration Manager: User's Guide for Inventory, SC23-4713 for more information.

Defect 55824

DISSE0624E
An error occurred contacting the managed node `managed node'. Make sure the managed node is defined as a gateway or stand-alone repeater and is working properly.
Explanation:

See message.

System action:

The install operation failed.

Operator response:

Ensure you defined the source host as a Tivoli gateway or a repeater. Check that the Tivoli gateway or the repeater is running. See the wrpt or wgateway commands in the Tivoli Management Framework: Reference Manual, GC32-0806.

Defect 59754/59755
The message text for the DISSE0330E error message has been modified as follows:
DISSE0330E Remove operation for targets having a different package state
in the Inventory database is not allowed if the force option is not set. 
You can use the ignore option to skip the not installed targets if you 
disable the remove_not_installed by running 
wswdcfg -s disable_remove_not_installed=y.
The current explanation for the CMW0007E error message has been modified as follows:
One of the steps you performed during the silent installation 
has failed.
The current operator response for the CMW0007E error message has been modified as follows:
See the upper sections of this log file to determine 
the nature of the error. 
Correct the error and try the operation again.

Release Notes

This section contains new and updated information for IBM Tivoli Configuration Manager Release Notes:

APAR IY81403
In the section "Supported Databases" the following paragraph should be added at the end of the section:

The "temporary tables" feature does not apply to Sybase and Informix, because these two RDBMS databases do not clean up the contents of a temporary table after the commit operation, but only after releasing the session to the database. You can therefore receive the following error message, which might cause a performance decrease:

Sybase Server Error: Msgno 3621 Level 10 State 0
Command has been aborted.
APAR IY90442
In Chapter 2 "Installation and Upgrade Notes", in the "Supported operating systems" section, the table "Supported operating systems by administrative interfaces and endpoint" should be modified as follows:

APAR IZ01088
In Chapter 3 "Software limitations, problems, and workarounds", in section "Automated Patch Management" add the following limitation:

The Windows Server Update Services (WSUS) server version 3.0 is not supported. Use the WSUS server version 2.1.

Software Package Editor online help

This section contains new information for the Software Package Editor online help:

Feature 55186
The following is the help panel for the Logoff Properties dialog box:

Use this dialog box to specify whether you want a logoff operation to be performed on Windows endpoints and to define the settings for the logoff operation. You can select one or more of the following options:

Logoff during install
The logoff operation is performed during the during_install phase.
Logoff during undo
The logoff operation is performed during the during_undo phase.
Logoff during remove
The logoff operation is performed during the during_remove phase.
Logoff during commit
The logoff operation is performed during the during_commit phase.
Force
The logoff operation is forced also if any applications are currently active on the workstation.
Force if locked
The logoff operation is forced if the workstation is locked.

For more information on defining conditions, see the Conditions help panel.

Defect 55461
The Maintain existing value check box has been added to the Add Directory Properties and Add File Properties dialogs. The following is the help panel for this check box:

Select this check box to maintain the file or directory access attributes and the ownership if the file or directory already exists on the target. If the file or directory does not exist, the check box selection has no effect, and the default value (Use system value check box), or the ones that you selected, are assumed.

Man page missing updates

This section provides information about commands that have been added or changed but for which new man pages are not available.

Software distribution

The changes to these commands are documented in the IBM Tivoli Configuration Manager: Reference Manual for Software Distribution.

Activity Planner

The changes to this command are documented in the IBM Tivoli Configuration Manager: User’ Guide for Deployment Services.

Inventory
wcollect wepscan winvdeps winvmgr winvmigrate winvpackage winvsig wloadiso wsetinvpchw wsetinvswd wsetinvunixhw

The changes to these commands are documented in the IBM Tivoli Configuration Manager: User's Guide for Inventory.

License Manager Extension
The License Manager Extension changes the winvsig command and introduces the following new commands:

The new and changed commands are documented in Configuration Manager: License Manager Extension

Microsoft® Active Directory Integration
Microsoft Active Directory Integration introduces the following new commands:


[ Top of Page | Previous Page | Next Page | Contents ]