![]() |
![]() |
[ Bottom of Page | Previous Page | Next Page | Contents ]
This section contains new information and documentation corrections contained in this fix pack.
This section contains new information for the following manuals of the IBM(R) Tivoli(R) Configuration Manager, Version 4.2.2 library.
The following new information applies to the IBM Tivoli Configuration Manager: User's Guide for Software Distribution.
In chapter 15 "Troubleshooting", section "Troubleshooting the Software Package Editor GUI", add the following entry after the first entry:
Starting the Software Package Editor. To use the Software Package Editor on Windows XP systems, you must be a member of the Administrators or Power Users group.
In Chapter 15 "Troubleshooting", section "Hints and Tips", add the following text at the end of the list:
To clone a software package from one profile manager to another, perform the following steps:
The following new information applies to the IBM Tivoli Configuration Manager: User's Guide for Deployment Services.
max_error_info_sizekeyword in the DEFAULT section of the apm.ini file and enlarge the ERROR_INFO column in the ACT_STATUS_TGT table to the same value defined for the
max_error_info_sizekeyword. The maximum size for this column depends on the database you are using.
The following new information applies to the IBM Tivoli Configuration Manager: Planning and Installation Guide.
Ensure that you install the same level of code on the endpoints that is installed on the Tivoli server. If an interim fix or fix pack is installed on the Tivoli server, the same interim fix or fix pack must be installed on the endpoint.
The following new information applies to the IBM Tivoli Configuration Manager: Reference Manual for Software Distribution.
In Chapter 1 "Editing the Software Package Definition File", table 14 "SPD file attributes for Windows registry objects", add the following note to the explanation of the add attribute:
In Chapter 1. Editing the Software Package Definition File, Software Package Name and Version section, add the following sentence at the end of the first list:
The length of the string that defines the name and version of a software package can vary depending on how you distribute the software package:
In Chapter 3, Using Commands, add the text below to the following commands:
In Chapter 3 "Using Commands", section Disconnected Target Commands" modify the usage of the wdlssp command as follows:
wdlssp
wdlssp -B.
and add the following description in the Options section:
The following new information applies to the IBM Tivoli Configuration Manager: User's Guide for Inventory.
This section contains problems and corrections for the following manuals of the IBM Tivoli Configuration Manager, Version 4.2.2 library:
The following information changes apply to the IBM Tivoli Configuration Manager: 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:
The following information changes apply to the IBM Tivoli Configuration Manager: 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 "Subelements 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 IBM Tivoli Configuration Manager: Messages and Codes.
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, open the Desktop directory on cd 3 of the IBM Tivoli Configuration Manager Desktop CD (cd3\desktop), then run setup.exe. 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 IBM Tivoli Configuration Manager: 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, add the following sentence at the end of the hidden description:
If you set this option in an InventoryConfig profile, its value overrides the hidden keyword value.
The following information changes apply to the IBM Tivoli Configuration Manager: Release Notes(R).
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.
[ Top of Page | Previous Page | Next Page | Contents ]