![]() |
![]() |
[ Bottom of Page | Previous Page | Next Page | Contents ]
This section contains new and updated information for IBM(R) Tivoli(R) Configuration Planning and Installation Guide:
cd C:\Program Files\Tivoli\Policy Director\sbin pdjrtecfg -action \ config -host hostname -java_home drive:%WAS_HOME%\java\jre -host /<access_manager_server_name>and replace the command to be run on the Web Gateway server to create the SSL configuration file and keystores with the following example:
java com.tivoli.mts.SvrSslCfg userName Password pdmgrdHostname \ pdacldHostname pdmgrdPort pdacldPort configuration_file \ keystore_file create
where:
In Chapter 1. Overview of Configuration Management, 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.
For more details on these files, refer to the IBM Tivoli Configuration Manager 4.2.3 Patch Management Guide.
This section contains new and updated information for IBM Tivoli Configuration User's Guide for Inventory:
For more details on these files, refer to the IBM Tivoli Configuration Manager 4.2.3 Patch Management Guide.
As software scan options for PC and UNIX, ensure you select Run the scan to perform a scan on the endpoint, and Send the results to the configuration repository to create the DAT file on the endpoint. If the upload of the results is needed, you can run the wepscan -s command.
wloadiso [-d { 1 | 2 | 3 }] -f filename | -l listfilename
and replace the description of the -f DAT file option with the following two options:Step 4:
On the endpoint, locate the zip file (for example w32-ix86.zip) in the $LCFROOT/inv/ISOLATED/common/ directory, and manually copy the file from this directory to the directory on the disconnected system that you created in step 3.
Step 9:
On the disconnected system unzip the zip file, from the directory that you created in Step 3, and run:
wepscan -i -n DAT_file_name
where:
export LD_LIBRARY_PATH=.:$LD_LIBRARY_PATH
Step 11:
Run the wloadiso command from the $LCFROOT/inv/ISOLATED/depot directory on the endpoint to send the scan data to the configuration repository. Before running the wloadiso -f file.dat command, set up the lcf environment to access the shared libraries needed by the command. See wepscan for the procedure on how to set the environment.
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_nameand add the following entries at the end of the Options list:
wgetinvpcsw [-b] [-c] [-f] [-h] [-r] [-s] [-x] [-m] [-d] profile_nameand add the following entry at the end of the Options list:
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_nameand add the following entry at the end of the Options list:
wgetinvunixsw [-b] [-c] [-f] [-p] [-s] [-x] [-d] profile_nameand add the following entry at the end of the Options list:
SUS Files | WSUS Files |
---|---|
mssecure.cab | wsusscan.cab |
mbsacli.exe | WindowsUpdateAgent20-x86.exe |
ApprovedItems.txt | ApprovedChanges.txt |
APM login failure on Linux(TM)
If Activity Planner fails and the following message is displayed
AMN0121E Activity Planner initialization failed. Check whether the Activity Planner user has been created correctly and/or the user and password maintained by Activity Planner are syncronized with the corresponding values of the operating system.
and the oservlog contains reports similar to the following:
2005/09/19 10:50:58 -01: PAM: pam_acct_mgmt failed=User account has expired (13) 2005/09/19 10:50:58 -01: @verify_password: Invalid username or password 2005/09/19 10:50:58 -01: @rconnect: Login failed for tivapm from host 100007fGo to /etc/pam.d and edit the oserv file
#%PAM-1.0 # Created by etc-tivoli.cfg for DS/Win and JCF login on systems with Pluggable # Authentication Modules (PAM). Install will not overwrite this file if it # exists. See the PAM doc for your platform for details on modifying this file. auth required /lib/security/pam_unix.soAdd the following line:
account required /lib/security/pam_unix.so
At the end of the "Option" section add the following option description:
wresgw discover [-v] [-C resource_gateway_type] endpoint...Change the endpoint description in the Options list as follows:
For the wresgw ls command, lists all known resource gateway types on the endpoint that you specify.
For the wresgw update command, indicates the endpoint for which the object ID or endpoint label is being updated. This option is mandatory.
The APM_RPC_MAX_THREADS environment variable has been added to the APM_core process. This variable sets the maximum number of concurrent remote procedure call threads handled by the dispatcher. The default value is 250.
This section contains new and updated information for IBM Tivoli Configuration Reference Manual for Software Distribution:
logoff stanza
To perform a logoff operation on Windows endpoints, use the logoff stanza, the format of which is as follows:
logoff force = y/n (default = n) force_if_locked = y/n (default = n) during_install = y/n (default = n) during_commit = y/n (default = n) during_undo = y/n (default = n) during_remove = y/n (default = n) end
Attribute | Comments | |||
---|---|---|---|---|
Values | Required | Default | Stanza | |
force | The logoff operation is forced also if any applications are currently active on the workstation. | |||
String expression | No | n | logoff | |
force_if_locked | The logoff operation is forced if the workstation is locked. | |||
String expression | No | n | logoff | |
during_install | The logoff operation is performed during the during_install phase. | |||
String expression | No | n | logoff | |
during_commit | The logoff operation is performed during the during_commit phase. | |||
String expression | No | n | logoff | |
during_undo | The logoff operation is performed during the during_undo phase. | |||
String expression | No | n | logoff | |
during_remove | The logoff operation is performed during the during_remove phase. | |||
String expression | No | n | logoff |
SPD File Example: logoff
The following section shows an example of a software package definition file containing a logoff stanza:
'TIVOLI Software Package v4.2.3 - SPDF' package ## ## Package attributes ## logoff force = y force_if_locked = n during_install = n during_commit = y during_undo = n during_remove = n end end
The length of the string that defines the name and version of a software package can vary depending on how you distribute it:
This section contains new and updated information for IBM Tivoli Configuration User's Guide for Software Distribution:
However, do not use depots for extremely large distributions.
Error while generating a software package using Autopack
During the creation of the first Autopack snapshot, some system resources might be included in the snapshot. This might cause a failure when Autopack generates the software package. If the creation of the software package fails with one or both of the following error messages:
DISSP6018E Failed to build file_name
DISSE0282E Error compressing the file file_name in the
Software Package Block.
generate the software package again excluding the files listed in the error messages, as explained in "Creating the first snapshot" in Chapter 8.
Key | Description |
---|---|
resinit_one_reboot | Defines the endpoint behavior in processing software packages. If you change the default value resinit_one_reboot=y and set it to resinit_one_reboot=n, the packages are processed one by one, and if a package requires a reboot, the endpoint is rebooted immediately. |
Using the Save option of the Software Package Editor
Software Package Editor is unable to save a software package on an AIX(R) endpoint that has Software Package Editor Version 4.2.3 and fix pack 1 installed. No error message is displayed. The workaround is to select a file between those displayed in the panel. Then the Save option works properly. This problem is a known issue of JRE 1.3.1.If you install the Patch Management fix pack component, see the updated version of the Patch Management Guide to see the new patch management tables and views.
This section contains new and updated information for IBM Tivoli Configuration Patch Management Guide:
The activity plan fails on targets deleted from the Tivoli database
Deleting endpoints from the Tivoli database does not delete those endpoints from the configuration repository. This might cause the activity plan to fail on the deleted endpoints because targets for the workflow are defined based on the information in the configuration repository.
To prevent this problem, after deleting the endpoints using the wdelep command, run the winvrmnode command to remove hardware and software scan information from the configuration repository. For more information on these commands refer to Tivoli Management Framework: Reference Manual and IBM Tivoli Configuration Manager: User's Guide for Inventory.
SUS server synchronization problem
Cause:If you work with the SUS server, during the SUS server synchronization on the Microsoft web site, the following error message INVCC0264E No files to transfer is displayed.
Solution: To avoid the problem you can perform one of the following tasks:
Cause: ITCM 4.2.3 plus interim fix 0001. If you set delete_plans=yes in the patch management configuration and run the workflow when there are no entries in the APM database, the following error message is logged in the execution log of the workflow: ERROR: Command >wlstpln< failed.
Solution: The process completed successfully. Ignore the error message.
This section contains new and updated information for IBM Tivoli Configuration Manager Messages and Codes:
Defect 55666
The command you are using requires integration with Inventory.
The operation failed.
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
See message.
The install operation failed.
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.
This section contains new information for the Software Package Editor online help:
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:
For more information on defining conditions, see the Conditions help panel.
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.
[ Top of Page | Previous Page | Next Page | Contents ]