![]() |
![]() |
[ Bottom of Page | Previous Page | Next Page | Contents ]
This section contains new information for the following manuals of the IBM(R) Tivoli(R) Configuration Manager, Version 4.2.1 library.
The following new information applies to the IBM Tivoli Configuration Manager: User's Guide for Software Distribution.
In Chapter 15 "Troubleshooting", in the section "Hints and Tips", add the following text at the end of the list:
Cloning software packages from the Tivoli desktop
When cloning software packages from one profile manager to another using the drag-and-drop function, the cloned software package might not work correctly.
To clone a software package from one profile manager to another, perform the following steps:
You can also move a software package from one profile manager to another, by performing one of the following procedures:
In Chapter 15 "Troubleshooting", in the section "Troubleshooting the Software Package Editor GUI", add the following bullet after the first bullet:
To use the Software Package Editor on Windows XP systems, you must be a member of the Administrators or Power Users group.
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", section "Attributes in Windows Registry Object Stanzas", Table 14 "SPD file attributes for Windows registry objects", add the following note to the explanation of the add attribute:
In Chapter 3 "Using Commands", add the text below to the following commands:
In Chapter 1 "Editing the Software Package Definition File", in the section "Software Package Name and Version", 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", 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 Deployment Services.
In Chapter 13 "Administering the Web Interface", in the section "Monitoring the Results of Operations", add the following text before the table:
The software packages distributed using Software Distribution are tracked in the Inventory database by the endpoint label, while the software packages distributed using the Web Interface are tracked by the workstation hostname. This can lead to a misalignment of information in the Inventory database if you install an endpoint on the Web Interface client workstation and distribute software packages to this workstation using Software Distribution.
To avoid this problem, you should install the endpoint with the same name as the workstation hostname or, if the endpoint is already installed, change its name to match the workstation hostname.
In the "Troubleshooting" section in the same chapter, add the following entry after the last entry in the Administrator on the Tivoli server section:
Information concerning software packages installed on a Web Interface client is inconsistent when an endpoint is installed on the same workstation.
The software packages distributed using Software Distribution are tracked in the Inventory database by the endpoint label, while the software packages distributed using the Web Interface are tracked by the workstation hostname. This can lead to a misalignment of information in the Inventory database if you install an endpoint on the Web Interface client workstation and distribute software packages to this workstation using Software Distribution.
To avoid this problem, you should install the endpoint with the same name as the workstation hostname or, if the endpoint is already installed, change its name to match the workstation hostname.
In Chapter 2 "Performing Activity Planner Operations", in the 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 4 "Troubleshooting", section "Specific problems and workarounds", add the following text:
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.
In Chapter 3 "Using the Command Line" in Table 2 "Sub-elements that define the activity plan", in the row targets_computation the following information should be added:
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 ACT_STATUS_TGT. If the target exists, the OID in the table is the current OID, otherwise it is ----.
In Chapter 3 "Using the Command Line" in Table 3 "Sub-elements that define frequency information", in the row targets_resolution the following information should be added:
If the targets resolution (targets_computation=a) is at activity execution, the targets are evaluated when the activity starts.
The following new information applies to the IBM Tivoli Configuration Manager: User's Guide for Inventory.
In Appendix B, update the usage of the wepscan command as follows:
wepscan [-d {1 | 2 | 3}] [-s[-l]] [-t mc_upcall_timeout]
and add the following parameter to the parameters for command wepscan:
The following information changes apply to the IBM Tivoli Configuration Manager: Release Notes(R).
In Chapter 3 "Software limitations, problems, and workarounds" in the section "Software Problems and Workarounds" in the subsection "Web Gateway" the following problem description and workaround should be added after defect 28358:
APAR IY64238: Repeated attempts to install the IBM Tivoli Configuration Manager Web Gateway on Windows 2000 Advanced Server dual processor workstations might cause the installation process to stop abruptly.
Workaround: Install the IBM Tivoli Configuration Manager Web Gateway component using an alternate installation method, such as the software package block or silent installation methods. For more information on these methods, refer to IBM Tivoli Configuration Manager Planning and Installation Guide.
In Chapter 3 "Software limitations, problems, and workarounds" in the section "Software Problems and Workarounds" in the subsection "Change Manager" the following problem description and workaround should be added:
If you are using the 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: You should change the collate to SQL_Latin1_General_CP1_CI_AS and the primary language of the user owning the Change Manager tables should be set to English.
[ Top of Page | Previous Page | Next Page | Contents ]