![]() |
![]() |
[ Bottom of Page | Previous Page | Next Page | Contents ]
This section contains problems and corrections for the following manuals of the IBM(R) Tivoli(R) Configuration Manager, Version 4.2.2 library, contained in previous fix packs:
The following information changes apply to the User's Guide for Software Distribution.
In Chapter 15, section "Troubleshooting the Software Package Editor GUI", add the following bullet after the first bullet:
In Chapter 15, "Troubleshooting", section "Software Distribution Log", add the following note to the "Distributive" section:
In Chapter 11 "Configuring a Network Topology", section "Scenario 3: Distributing from a Source Host through Repeater Depots", remove the following sentence:
However, do not use depots for extremely large distributions.
In Chapter 6 "Embedding Native Objects into a Software Package", section "Using Dialogs to Embed or Edit an HP-UX Package", replace the bullet number four with the following text:
In the HP-UX Source Depot path text box, type the absolute path of the HP-UX package. In the HP-UX Source Depot File Name specify the file name of the HP-UX software depot, if the images to be installed are stored in a single file.
In Chapter 9 "Preparing a Software Package for Distribution", section "Change Management Operations", subsection "Overwriting Default Variables" replace the second paragraph with the following text:
When you subsequently remove a software package, you can define or override only those variables that were not resolved when the package was installed or those variables that are left unresolved for future remove operations, even though they were resolved during the package installation. If these variables are not overwritten after the package installation, they maintain the values used during the installation.
The following information changes apply to the Reference Manual for Software Distribution.
The description of the execute_user_program stanza does not include an explanation of the behavior if the timeout is set to 0. If execute_user_program.timeout is equal to 0 and the user program is the last action in the software package, the timeout value set for the gateway repeater is used.
In Chapter 3 "Using Commands", section "Server Commands", add the text below to the initial description of each of the following commands:
This command specifies whether the distribution fails on endpoints that cannot be reached for any reason. Supported values are true and false. The default value is false.
The following information changes apply to the User's Guide for Deployment Services.
In Chapter 2, section "Selecting Targets for an Activity", add the following text to the first item in the bulleted list in step 4:
A list of target names. Select this type if you define the targets using the $(TARGET_LIST) variable.
In Chapter 1, section "Before You Start", modify the sentence:
In Chapter 2 "Using the Command Line", Table 5 "Sub-elements that define the activity plan", targets_computation row, add the following information:
If targets are defined at plan level and targets resolution is specified at plan submission, targets are calculated when the plan is submitted and inserted in the ACT_STATUS_TGT table. If the target exists, the OID in the table is the current OID, otherwise it is ----.
The following information changes apply to the Planning and Installation Guide.
In Chapter 7, "Desktop Installation", section "Desktop Installation", replace the paragraph:
The Desktop installation program installs Tivoli Desktop for Windows and the IBM Tivoli Configuration Manager administrative interfaces. This installation can be used on the following Windows operating systems only:
with the following two paragraphs:
The Desktop installation program installs Tivoli Desktop for Windows and the IBM Tivoli Configuration Manager administrative interfaces. This installation can be used on supported Windows operating systems only.
To install Tivoli Desktop for Windows on Windows Server 2003, perform the following steps:
When the Tivoli Desktop installation is complete, you can install components that are provided as SPBs (located in the directory cd3\SPB), using Software Distribution (see the section Components Installed using Software Package Blocks for more information).
In Chapter 4, section "Upgrading Database Scripts", sub-section "Upgrading From IBM Tivoli Configuration Manager Version 4.2" replace the paragraph that describes how to upgrade to Software Distribution 4.2.2 with the following text:
The Software Distribution upgrade from 4.2 to 4.2.2 does not require any upgrade script for the database repository.
In Chapter 6, Table 25 "Web Gateway Component Prerequisites", first row of the "Web Gateway database" table, change:
IBM DB2(R)
into:
IBM DB2 Server
In Chapter 1, section "IBM Tivoli Configuration Manager Components and Services", add the following information to the Software Distribution component description:
You must install the Software Distribution component on the Tivoli server before you can install either the Software Distribution or Software Distribution Gateway component on any managed node in the local Tivoli region.
In Chapter 1, at the end of section "IBM Tivoli Configuration Manager Components and Services", delete the following paragraph:
You must install these components on the Tivoli server before you can install them on a managed node or before you can install the associated gateway component on a gateway. For example, you must install the Software Distribution component on the Tivoli server before you can install either the Software Distribution or Software Distribution Gateway component on any managed node in the local Tivoli region.
The following information changes apply to the User's Guide for Inventory.
In Appendix B, add the following sentence for commands wdistinv and winvmgr, at the end of the wake_on_lan description:
If you set this option in an InventoryConfig profile, its value overrides the wake_on_lan keyword value.
In Appendix B, add the following sentence for commands wdistinv and winvmgr, at the end of the hidden description:
If you set this option in an InventoryConfig profile, its value overrides the hidden keyword value.
In Chapter 3 "Working with Inventory profiles", section "Software scan configuration options", paragraph "Directories" add the following note at the end of the paragraph:
If you installed the WSUS Patch Automation solution, in Appendix B "Commands", replace the current usage of the wsetinvpcsw command with the following usage:
wsetinvpcsw [-b {SCAN | UPDATE | BOTH | NO}] [-c {QUICK | FULL | MD5 | NONE}] [-f {Y | N}] [-h {SCAN | UPDATE | BOTH | NO}] [-r {SCAN | UPDATE | BOTH | NO}] [-s {SCAN | UPDATE | BOTH | NO}] [-x {Y | N}] [-m {Y | N}] [-d {Y | N} [-n file_ name]] profile_name
and add the following entries at the end of the Options list:
In Appendix B "Commands", replace the current usage of the wgetinvpcsw command with the following usage:
wgetinvpcsw [-b] [-c] [-f] [-h] [-r] [-s] [-x] [-m] [-d] profile_name
and add the following entry at the end of the Options list:
In Appendix B "Commands", replace the current usage of the wsetinvunixsw command with the following usage:
wsetinvunixsw [-b {SCAN | UPDATE | BOTH | NO}] [-c {QUICK | FULL | MD5 | NONE}] [-f {Y | N}] [-p {SCAN | UPDATE | BOTH | NO}] [-s {SCAN | UPDATE | BOTH | NO}] [-x {Y | N}] [-d {Y | N}] profile_name
and add the following entry at the end of the Options list:
In Appendix B "Commands", replace the current usage of the wgetinvunixsw command with the following usage:
wgetinvunixsw [-b] [-c] [-f] [-p] [-s] [-x] [-d] profile_name
and add the following entry at the end of the Options list:
The following information changes apply to the Database Schema Reference.
In Chapter 5 "Configuration repository tables", section "Activity Planner tables", subsection "ACT_PARAMETER" add the following note at the end of the section:
The following information changes apply to the Release Notes.
In Chapter 3, section "Software Problems and Workarounds", sub-section "Change Manager", add the following problem description and workaround:
If you are using Change Manager based on Microsoft(R) SQL Server and the primary language is not set to English, you might have some problems with the date format (for example month is taken instead of day).
Workaround: Change the collate to SQL_Latin1_General_CP1_CI_AS and the primary language of the user owning the Change Manager tables to English.
In Chapter 3, section "Software Problems and Workarounds", sub-section "Software Package Editor", add the following problem description and workaround:
Software Package Editor GUI does not start on a Terminal Server Windows 2003.
Workaround: Open Software Package Editor using the Tivoli desktop.
This section describes the following options for obtaining support for IBM products:
If you have a problem with your IBM software, you want it resolved quickly. Begin by searching the available knowledge bases to determine whether the resolution to your problem is already documented.
[ Top of Page | Previous Page | Next Page | Contents ]