This section contains a cumulative list of enhancements introduced in the
previous fix packs, interim fixes, and the current fix pack.
(1) No operating system patches are supported, only
patches related to software applications.
- Targets resolved by APM Executer and no longer by APM Handler -
Feature 59552
-
To fully use this enhancement, activity plans must be submitted with
target resolution at plan submission and not at activity execution.
To enable this feature, add the following entry to the apm.ini file:
resolve_targets_in_executer=yes
in the [ENGINE_TUNING] section of the
file.
Enabling this feature, the Activity Planner Handler can now handle
other activity plan actions, while the targets are being resolved by the Activity
Planner Executer.
- WSUS 3.0 support - Feature 59432
-
Prerequisites for using WSUS version 3.0 are the following:
- Install the "Microsoft SQL Server Native Client" from the Microsoft Web
site.
- Install the "Microsoft SQL Server 2005 Command Line Query Utility"
from the Microsoft Web site.
- Set the two wseccfg command parameters as
follows:
- wsus_db_host=\\.\pipe\MSSQL$MICROSOFT##SSEE\sql\query
- wsus_version=3
With this feature the WSUS_info_retriever.sh script has been modified to accept the -v3 new parameter.
- Windows 2008 endpoint support for Patch Management
- Endpoints having Windows 2008 installed are now supported among the
targets managed by the Patch Management solution. On these targets, no operating
system patches are supported, only patches related to software applications.
The support for operating system patches is deferred until an operating system
patch is provided for testing purposes.
- Windows 2008 and AIX 6.1 support
- The endpoint support has now been extended to endpoints having the following
Windows platforms installed:
- Windows Server 2008 Standard (ix86 only)
- Windows Server 2008 Enterprise (ix86 only)
and to endpoints having the AIX platform version 6.1 installed.
This
extended support is for endpoints only. Web Interface and GUI functions are
not supported on these platforms, because Java version 1.3.1 is not supported.
Install the Windows 2008 and AIX 6.1 endpoint using the endpoint setup
released with the following patch:
4.1.1-LCF-0051.
- TCM 7.1 Discovery Library Adapter (DLA) support
- This Discovery Library Adapter (DLA) collects data from Tivoli Configuration
Manager 4.2.3 and creates Discovery Library books containing information about
the resource instances and their relationships known to the system. The Discovery
Library books can be imported into CCMDB or into a data store for which a
Discovery Library Reader exists.
This DLA package is located on the Tivoli
Configuration Manager Version 4.2.3 Fix Pack 6 CD 1 under the /dla directory.
For more details about the DLA package, refer to
the Readme contained in the zip file named TCM_DLA.zip stored on the Tivoli Configuration Manager Version 4.2.3
Fix Pack 6 CD 1 under the /dla directory.
- Discovery Library Integration Framework Plug-in for Tivoli
Configuration Manager
- The Discovery Library Integration Framework provides a set of reusable
software components which work together to perform discoveries of Configuration
Items (CIs) that are to be maintained by CCMDB. The plug-in for Tivoli Configuration
Manager is responsible for discovering the CIs specific to the Tivoli Configuration
Manager product.
This plug-in is located on the Tivoli Configuration
Manager Version 4.2.3 Fix Pack 6 CD 1 under the /dii directory.
For more details about the plug-in, refer
to the User's Guide contained in the zip file
named TDI_CCMDB_TCM_plugin1.2.zip. The file
name for the User's Guide is TDI_CCMDB_TCM_plugin_UserGuide.pdf.
- Add scripts as arguments in sp_val_operation for data moving
operations - Feature 59700
-
Add the pre- and post-scripts to the arguments that
the data moving operation passes to the sp_val_operation validation policy script. For more details about the sp_val_operation validation policy, refer to the IBM Tivoli Configuration Manager: Reference Manual for Software Distribution. With this feature the arguments that the data moving operation passes
to the sp_val_operation validation policy script are
the following:
For the Delete operation:
$1 --> DataMovingRequests.1
$2 --> delete
$3 --> <target_path>
$4 --> <file>
$5 --> SCRIPT_LIST
<stdin> --> <target endpoint list>
For the Send operation:
$1 --> DataMovingRequests.1
$2 --> send
$3 --> <source_path>
$4 --> <target_path>
$5 --> <file>
$6 --> <source_host>
$7 --> SCRIPT_LIST
<stdin> --> <target endpoint list>
For the Retrieve operation:
$1 --> DataMovingRequests.1
$2 --> retrieve
$3 --> <source_path>
$4 --> <target_path>
$5 --> <file>
$6 --> <source_host>
$7 --> SCRIPT_LIST
<stdin> --> <target endpoint list>
For the Endpoint to Endpoint operation:
$1 --> DataMovingRequests.1
$2 --> retrieveE2E
$3 --> <source_path>
$4 --> <target_path>
$5 --> <file>
$6 --> <source_endpoint>
$7 --> SCRIPT_LIST
<stdin> --> <target endpoint list>
where: SCRIPT_LIST is a single argument which contains the following four lines:
spre:<spre_script>
spost:<spost_script>
tpre:<tpre_script>
tpost:<tpost_script>
separated by the \r character.
On UNIX platforms, a direct "echo" of the entire SCRIPT_LIST causes the following
behavior: every line is written above the previous one, because \r represents
the carriage return. For this reason you can only see the last line of the
script.
You must create a validation script to extract the four lines
contained in the SCRIPT_LIST argument. For example, for a Retrieve operation on Solaris platforms, a simple way to do this is as
follows:
echo $7 | awk -F"^M" '{print $1"\n"$2"\n"$3"\n"$4}' | while read a
do
<use $a variable that contains a single line>
done
where:
- ^M
- Does not represent the characters ^ and M. It represents the sequence of the ctrl-v and ctrl-m key combinations.
Another example of how to create the validation script is the
following:
echo $7 | awk '{n=split($0, v, "\r"); print v[1]"\n"v[2]"\n"v[3]"\n"v[4]}'
| while read a
do
<use $a variable that contains a single line>
done
- Ignore option extended to targets not scanned - Feature
59702
- The ignore option for the remove operation has
been extended to targets which have not been scanned and do not have an entry
in the COMPUTER table. If a remove operation is performed on mixed targets
(some have an entry in the COMPUTER table while others do not) by the Activity
Planner using the ignore option (-I), the targets that do not have an entry in the COMPUTER table are skipped,
and the remove operation proceeds with the targets that have been scanned.
In the software package log file, the following error message is displayed
for the targets that do not have an entry in the COMPUTER table:
DISSE0072E List of targets on which the requested operation cannot be
submitted:
endpoint_name DISSE0407E Failed cm_status check.
You must take remediation actions on these targets by either running
a scan on them, or by sending a dummy software package before performing a
remove operation on them. If the remove operation is performed by the Activity
Planner, a target on which the validation fails shows the "success" state.
If you want a validation failure to be considered as a failure, also by the
Activity Planner, you must set the FailOnValidationFailure option using the Activity Planner, in addition to the ignore option. In case of mixed targets, scanned and not scanned, the DISSE0329E error message keeps displaying if you do not use the ignore option. The text of the error message has been changed
as follows:
DISSE0329E Mixed targets (with an entry in COMPUTER table and without
an entry) are not allowed in the remove operation if the force option
is not set. Use the ignore option to skip the not scanned targets or
submit two different requests or perform a scan for all targets.
Also,
the text of the DISSE0330E error message has been changed 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.
to indicate the possibility
of using the ignore option to skip the non-installed
targets, if you disable the remove_not_installed option
by running the following command:
wswdcfg -s disable_remove_not_installed=y
Using this setting, you do not receive the DISSE0330E error
message in case of mixed targets, installed and not installed.
The following enhancements were introduced in the previous fix pack and
interim fixes:
- Cancel as preferred final status for a plan - Feature
56137
- Before submitting a plan, you can define its final status to Cancel
if any of the plan activities have been cancelled and the others are successful,
either by selecting Set Cancel as preferred final status in the General page of the Plan Submission Parameters notebook or by specifying -Dis_cancel_preferred=y in the wsubpln command.
- Emergency patch management - Feature 56053
- The Configuration Manager Patch Management solution identifies the set
of patches to be deployed to each endpoint on the basis of a preventive endpoint
inventory scan. This scan might cause critical delay in the patch installation.
When the Administrator responsible for approval determines that an update,
released in an important Microsoft(R) security bulletin, needs to
be implemented immediately, he can use the emergency patch management feature
to defer the preventive inventory scan and install the update as soon as possible.
For more information on this feature, see IBM(R) Tivoli Configuration
Manager Patch Management Guide.
- Patch Management deployment paradigm - Feature 56053
- This feature extends Software Distribution capabilities to the Patch
Management solution, enabling the Patch Management component to retrieve the
software package to be installed from a depot or a file server, rather than
the source host. Use this feature in environments with communication problems,
when retrieving a software package from a source host might take time. For
more information on this feature, see IBM Tivoli Configuration
Manager Patch Management Guide.
- Enable Move Data to retrieve AS/400 spool file - Feature 56336
- With this feature the Data Moving Service in an OS/400(R) environment
has been extended. You can now move OS/400 spool files from an OS/400 system to
a Windows or UNIX target. Target systems can be endpoints or managed
nodes. To differentiate the spooled files from the OS/400 native files,
when running the wspmvdata command, specify the path
name using the following format:
Job Number/Job User/Job Name/Spooled File Number
Ensure that Job Number is not preceded by a slash.
As
an example see the following command:
wspmvdata -c -s @swd400 -t @intermesoli -P
sp:028421/qtivoli/qlcfd/1 -P tp:/targetdir qprint
Where:
- swd400
- Is the OS/400 host name.
- intermesoli
- Is the receiver host name, either a managed node or an endpoint.
- sp:028421/qtivoli/qlcfd/1
- Identifies the spool file on the OS/400 system. If you omit the spooled file
number (1 in this example), and more than one spool file exists for the same
job, the last created spooled file is retrieved.
- /targetdir
- Is the destination path on the target system.
- qprint
- Is the spooled file name to be retrieved. Do not use wildcards for spooled
file names.
When performing a retrieve operation of an OS/400 spooled file, a new file is created
under the specified destination directory using the following naming convention:
JobNumber.JobUser.JobName.SpooledFileNumber.SpooledFileName
In the example
described above this file is /targetdir/028421.qtivoli.qlcfd.1.qprint.
Notes:
- Notice the usage of the codepage translation option ( c) in the example described above. Using this argument results in the OS/400 spooled file being translated from EBCDIC to ASCII codepage, before
it is written to the UNIX or Windows destination location.
- If the target system is a managed node, a subdirectory with the name of
the origin host is created inside the destination directory on the target
system. The naming convention for the subdirectory is as follows:
endpointname_distributionID_timestamp
For more details on the wspmvdata command,
refer to the IBM Tivoli Configuration Manager: Reference Manual for Software Distribution.
- Enabling proxy support for the SUS Patch Management solution
- You can use a proxy server to access the Microsoft Web site, or your local HTTP
server where the mssecure.cab file has been downloaded.
You can customize
the HTTP proxy server name (if enabled) and the related user ID and password
(if required by the proxy settings). Proxy parameters are defined at installation
time in the tpm_update.req file, as described in the readme of the interim
fix. This feature guarantees a higher security when accessing the Internet
or your local network.
- Avoiding concurrent logins during critical distributions -
Feature 54613
- On Windows operating systems, you can use the concurrent
login feature to prevent the end user from logging in to the workstation and
performing a shutdown while a distribution is taking place. This feature guarantees
that critical distributions are not interrupted. You can also define a maximum
number of logins that can be performed during a distribution. In this case,
the distribution is paused and restarts after the user logs off. For more
information, see Implementing the concurrent login feature.
- Performing the logoff operation on Windows endpoints -
Feature 55186
- You can perform the logoff operation on Windows endpoints. A new action has been
added to the software package definition file. You can define the logoff operation
in the following phases:
- during_install
- during_remove
- during_commit
- during_undo
For more information on this feature, see Documentation notes.
- Displaying the .jar files version - Feature 55204
- You can display the version of APM .jar files, if the version is indicated
in the .jar file. You can start the command on Tivoli servers and managed nodes after having
set the Tivoli environment, as described below:
- On UNIX operating systems:
- . ./wjarversion.sh jarfile
- On Windows operating systems:
- wjarversion.bat jarfile
where:
- jarfile
- Is the name of the .jar file for which you want to display the version.
The following are the .jar files supported for this feature:
- apm.jar
- apm_utils.jar
- swd_plugin.jar
- tl_plugin.jar
The files required for implementing this feature are located in the /JarVersion
folder in IBM Tivoli Configuration Manager, Fix Pack 4.2.3-TCM-FP01.
- Displaying the patch level for the Activity Plan Editor and
Activity Plan Monitor - Feature 55205
- You can display the patch level installed for the Activity Plan Editor
and Activity Plan Monitor by selecting the About menu
item in the Help menu.
- Completing workflows separately - Feature 55260
- You can decide whether patch management workflows are completed in one
or in two steps. This feature guarantees a higher flexibility in the workflow
process. For more information on this feature, see Documentation notes.
- Performing patch management using WSUS - Feature 55317
- You can perform patch management using WSUS to implement the approval
mechanism of patches and to download up-to-date patches from the Microsoft Web
site. For more details on this new automated patch management solution, see
the updated version of the IBM Tivoli Patch Management Guide.
- Maintaining the access attributes of already existing files
and directories - Feature 55359
- You can maintain the access attributes of already existing files and
directories on UNIX. To enable this feature, select the Maintain existing value check box in the Add File System Objects Properties
- Advanced window, UNIX Attr. tab of Software Package
Editor or set preserve_unix to y in the add_directory
or add_file stanzas of the SPD file.
- A 32 bit scanner, mrmbios.exe, substitutes the 16
bit scanner - Feature 180357
- With this feature the Windows 64-bit platforms support has been
extended. The old 16-bit mrmbios.exe file has been now replaced
by a 32-bit file having the same name, and using new device drivers. The new mrmbios.exe file allows you to scan, in addition to the old platforms,
new platforms such as AMD 64 and Itanium 64.
- Running a program before the reboot of a commit - Feature
55409
- You can run a program before the reboot of a commit by setting the following
variables in swdis.var:
- __COMMIT_REBOOT_FORCED__
- Specifies YES to force a reboot when a commit is run with -cr or -co parameters.
- __BEFORE_REBOOT_PROG_PATH__
- Specifies the path of the program to be run on the endpoints. If this
variable is empty no program is run.
- __BEFORE_REBOOT_PROG_ARGS__
- Specifies arguments passed to the program. Separate arguments with a
blank space.
- __BEFORE_REBOOT_PROG_TIMEOUT__
- Specifies the time, expressed in seconds, to wait for the completion
of the program. Default is 60.
To enable this feature, you must set at least __COMMIT_REBOOT_FORCED__ to YES and define the program path in __BEFORE_REBOOT_PROG_PATH__.
- Managing software packages - Feature 55487
- You can set the use_real_capabilities key to true with
the wswdmgr command to not distribute a software package
on targets belonging to policy regions where the administrator, submitting
the distribution, does not have the required roles. The default is false.
- Working with the Software Distribution Endpoint Notification
dialog - Feature 55522
- The Software Distribution Endpoint Notification dialog that pops up
on the screen of the endpoint when a software package is submitted for distribution
is changed. In the title bar the Close button (X) no longer appears. The Cancel
push button is replaced by the Reset push button that resets the changed
values in this dialog with the default values for this operation. To close
the dialog you must click OK.
- Tivoli Configuration Manager license management extension
- You can use the Configuration Manager license management extension to
provide license management facilities. For details see IBM Tivoli Configuration Manager: License Management Extension.
- Patch Management extension
- The solution manages Microsoft patches, service packs, and
update rollups for the following operating systems and applications:
- Windows 2000 Professional SP(TM) 3 or later
- Windows 2000 Server SP 3 or later
- Windows 2000 Advanced Server SP 3 or later
- Windows XP Professional
- Windows XP Home Edition
- Windows 2003 Server Standard Edition
- Windows 2003 Server Enterprise Edition
- Windows 2003 Server Web Edition
- Internet Explorer 5.01 or later
- Media Player 6.4 or later
- Exchange 2000 Server
- Exchange Server 2003
- Microsoft Office 2000
- Microsoft Office XP
- Microsoft Office 2003
For details, see IBM Tivoli Configuration Manager Patch Management
Guide.
- Active Directory integration
- IBM Tivoli Configuration Manager provides the capability of merging Active
Directory and endpoint information into a relational database. See Tivoli Monitoring: Active Directory Agent for more information.
- Solaris x86 support
- Tivoli Configuration Manager is supported on Tivoli Management Framework 4.1.1 endpoints
running Solaris 8, 9, 10 for x86 architecture, in particular Solaris 10 for
AMD Opteron processor.
- Search facilities for saved activity plans
- A dynamic search has been added to group saved plans.
- Activity plan group creation, submission, and tracking
- This feature introduces a tool that manages groups of activity plans
as a single entity. A script is used to create the group of activity plans
and assign a name to the group. A further script is then scheduled as a repeating
job to first submit the group of plans and then produce HTML format reports
of its progress by querying the APM and MDIST2 databases. See Implementing the activity plan group management feature for
instructions about using this tool.
- Immediate start for unique targets in conditioned activities
- With this feature you can add a new submission parameter to the Activity
Planner. When submitting a plan, it is now possible to enable the Activity
Planner server to evaluate all the conditioned activities of a plan, as soon
as the plan is submitted. In this way if a conditioned activity has a target,
which is not contained in a conditioning activity, the operation for that
target starts immediately. One limitation is that a plan with at least one
activity, having the option target computation at activity execution set, cannot be submitted if this feature is enabled.
To enable this
feature from the Activity Planner command line, run the wsubpln command in the following way:
wsubpln -r plan_name -Dpre_eval_conditions=true
To enable this feature
from the Activity Planner GUI, the Pre-evaluate conditions
at plan submission check box has been added to the Plan Submission Parameters panel.
To enable this feature from the
Change Manager command line, specify the -e option when
running the wsyncrmod command, or select the Pre evaluate conditions at plan submission check box which has been added
to the Select activity plan name panel.
- Signature management improvement
- To allow a more accurate software scan, Inventory has been modified
to use complex signatures and a new catalog including not only files, but
registry keys, mixed and extended signatures. See IBM Tivoli Configuration
Manager: User's Guide for Inventory
- Improved locale information management
- With this feature the Inventory scan distinguishes language specific
operating system information for Windows operating systems. The mixed language
environment is supported. See IBM Tivoli Configuration Manager: User's Guide
for Inventory.
- Correlation of software recognition data
- Enhancement of the Inventory signature scan to retrieve the path for
file signatures and store them in the database. This enhancement enables the
scan to identify and differentiate between multiple instances of a signature
on the same endpoint. See IBM Tivoli Configuration Manager: User's Guide
for Inventory.
- Windows service information
- Information on the services present on a Windows workstation is added to the set
of information that Inventory can collect. See IBM Tivoli Configuration
Manager: User's Guide for Inventory.
- Dynamic logical partitioning (LPAR) information on processor
allocated on partitions
- In environments that have logical partitions, Inventory can collect
LPAR information. The operating systems on which LPAR information can be discovered
are the following:
- AIX(R), version 5.3 on P5
- Red Hat Enterprise Linux(R) Advanced Server, version 4.0 on PowerPC(R) iSeries(TM)
- SuSE Linux Enterprise Server, version 9 on PowerPC iSeries
- HP-UX, version 11.11 on HP9000
- Sun Solaris Operating Environment, version 10 on Sun SPARC
- Stop on failure check box
- With this feature you can soften the check performed by Change Manager
on each ex-requisite dependency, related to a Software Distribution element,
to avoid a failure in the synchronization process, if the condition is not
met on one of the target machines. Using this feature you can control the
Change Manager behavior when evaluating the dependency. The Stop on failure check box has been added to Change Manager to activate
the feature.
To enable this feature, perform one of the following actions:
- Right-click the Dependencies pane of the Software Distribution element panel. Select the Software
Distribution Ex-requisite dependency type from the Add menu. By default, the Stop on failure check
box is selected and active, to maintain compatibility with the previous fix
pack level.
- Select Software Distribution element from the Add menu. The Software Distribution element panel is displayed. Click the Distribution Options button to display the Distribution Options panel.
By default, the Stop on failure check box is greyed
out. It becomes active after adding a Software Distribution ex-requisite dependency
to the Software Distribution element specified.
- From the Edit menu, select Create
Reference Model. The Properties panel is displayed.
By default, the Stop on failure check box is greyed
out. It becomes active after adding a Software Distribution element, which
contains a Software Distribution ex-requisite dependency.
- Enabling Tivoli Configuration Manager - Tivoli Provisioning
Manager coexistence
- A new resource, ReportManager, has been included in Software Distribution
product. It is needed to enable the Tivoli Configuration Manager - Tivoli
Provisioning Manager coexistence. ReportManager is used to provide the reports
to Tivoli Provisioning Manager when distributions are initiated by Tivoli
Provisioning Manager itself. To enable the integration, the $BINDIR/TME/ReportManager/rep_DB_Vendor.sql script must be executed to update the inventory
database. Supported database vendors are DB2 and Oracle.
- Send a Tivoli notice managing lcf script package attributes
- For Software Distribution a Tivoli notice is sent each time a value
related to the following package attributes is enabled during the import operation,
or changed when re-importing or using the wsetspgs command. The change
can be performed using both SPEditor or command line interfaces. The notice
is not sent if the value remains the same.
This is the list of the existing
attributes for which the notice is activated with the current feature:
- lcf_before_prog_path
- lcf_before_prog_args
- lcf_before_prog_timeout
- lcf_after_prog_path
- lcf_after_prog_args
- lcf_after_prog_timeout
For Inventory a tivoli notice is sent to the inventory notice
group, when the (after and/or before) script content for unix (and/or pc)
of an InventoryConfig profile changes. For Inventory four different messages
have been added: one for every script content that changes. The message is
related to one of the following four scripts:
- the before script for pc
- the after script for pc
- the before script for unix
- the after scripts for unix
- Customize the source host for Data Moving endpoint to endpoint
- With this feature the source host for Data Moving endpoint to endpoint
send and delete operations is not necessarily the Tivoli server anymore. With
this feature the source host can be customized. A default value can be set
using the following command:
wswdcfg -s datamoving_source_host=ManagedNode name
- Nokia s60 support
- With this feature, the Nokia device support has been extended. IBM Tivoli
Configuration Manager now supports Nokia s60 devices. The entire set of functions
already supplied for the Nokia 9500 and Nokia 9300 devices is supported. Moreover
some new functions are supported only for Nokia s60 devices. This means:
- The ability of defining the device using TRM
- The ability of creating and managing software packages capable of performing
device provisioning, device management, application distribution, and notification
actions
- The ability of managing all the supported configuration options when performing
device management operations
- The ability of performing the following actions:
- TARM config
- wipe
- reboot
- process listing
- process stop
- generic
- The ability of performing hardware, software, and configuration scanning
of the Nokia s60 device.
- Virtual resource scan - Feature MR0508067421
- With this feature, it is possible to report the virtual SCSI devices
assigned to a logical partition, only for AIX platforms. When running an Inventory
hardware scan to discover storage devices on a logical partition of an AIX
workstation, the virtual SCSI devices are now reported in the STORAGE_DEV_QUERY,
which displays the new storage device type called "Virtual Disc".
The operating systems for which this information can be discovered are the
following:
- IBM AIX 5.2 (32-bit and 64-bit)
- IBM AIX 5.3 (32-bit and 64-bit)
- Multi core support - Feature MR0826056352
- With this feature, it is possible to report the correct number of physical
processors, logical processors assigned to each core, and the cores on the
physical processor in the inventory tables, views, and queries. A multi-core
processor is one that combines two or more independent processors into a single
package. The operating systems for which this information can be discovered
by the Common Inventory Technology are the following:
- AIX
- IBM AIX 5.2 (32-bit and 64-bit)
- IBM AIX 5.3 (32-bit and 64-bit)
- HP-UX
- HP-UX 11i PA-RISC
- HP-UX 11i for Itanium
- Linux
- Red Hat Enterprise Linux 3.0 (U1) AS/ES/WS for i386
- Red Hat Enterprise Linux 4.0 AS/ES/WS for i386
- Red Hat Enterprise Linux 4.0 x86_64 AS/ES/WS
- Red Hat Enterprise Linux 3.0 (U2) (AS) PPC for iSeries and pSeries 64-bit
(AS)
- Red Hat Enterprise Linux v4.0 PPC for iSeries and pSeries 34-bit (AS)
- Red Hat Enterprise Linux 3.0 (U1) s390/s390x for S/390 and zSeries (AS)
- Red Hat Enterprise Linux 4.0 s390/s390x for S/390 and zSeries (AS)
- SuSE Linux Enterprise Server 8 (SP2a) for i386
- SuSE Linux Enterprise Server 9 for i386
- SuSE Linux Enterprise Server 9 for x86_64
- SuSE Linux Enterprise Server 8 (SP3) PPC for iSeries and pSeries 64-bit
- SuSE Linux Enterprise Server 9 PPC for iSeries and pSeries 64-bit
- SuSE Linux Enterprise Server 8 s390/s390x for S/390 and zSeries
- SuSE Linux Enterprise Server 9 s390/s390x for S/390 and zSeries
- SuSE Linux Enterprise Server 10 for i386
- SuSE Linux Enterprise Server 10 for x86_64
- SuSE Linux Enterprise Server 10 s390/s390x for S/390 and zSeries
- SuSE Linux Enterprise Server 10 PPC for iSeries and pSeries 64-bit
- Sun Solaris
- Sun Solaris 8 SPARC (32-bit and 64-bit)
- Sun Solaris 9 SPARC (32-bit and 64-bit)
- Sun Solaris 10 SPARC (32-bit and 64-bit)
- Sun Solaris 10 x86
- Windows
- Windows 2000 Professional/Server/Advanced Server (SP3)
- Windows XP Professional (32-bit)
- Windows 2003 Server (Standard and Enterprise Editions)
- Windows 2003 x64 (Standard and Enterprise Editions)
- Windows Vista (Desktop)
- Patch automation for target filtering - Feature MR0404064528
- With this feature, you can define filters for grouping endpoints and
deploy the security patches to these groups of endpoints. It is now possible
to define filters based on the information already available in the Inventory
database, and also to create groups of endpoints using the new wsecgrp command.
For more details on this command, see the IBM Tivoli Configuration Manager:
Patch Management Guide.
- New Microsoft catalog and WUA support
- You can perform patch management also using the new Microsoft .cab file
and its associated WUA. For details see the IBM Tivoli Configuration
Manager: Patch Management Guide.
- New options supported by the wsubpln command - Features
MR0503066815 and MR0414062811
- The wsubpln command now supports the following new options:
- submit_plans
- If this option is enabled, an automatic plan submission occurs immediately
after the plan creation.
- skip_plans_creation
- If this option is enabled, the plan is created at the end of the workflow.
For more details on this command, see the IBM Tivoli Configuration
Manager: Patch Management Guide.
- Tivoli Provisioning Manager for Operating System Deployment
integration - Feature 58233
- This fix pack provides the integration with the product Tivoli Provisioning
Manager for Operating System Deployment Version 5.1 through the new component Tivoli Provisioning Manager for Operating System Deployment integration Version
4.2.3. Only English version is currently available, the localized versions
will be available in the next fix pack. This integration replaces the old "Image
Management Services Integration, Version 4.2.3" released with fix pack
2, that needs to be uninstalled before installing the Tivoli Provisioning
Manager for Operating System Deployment integration. For more details,
refer to the IBM Tivoli Configuration Manager: User's Guide for Operating
System Deployment Solution.
- Windows Vista support
- The endpoint support has now been extended to endpoints having the Windows
Vista platform installed. As prerequisite, you must install the following
Framework patch on the Windows Vista endpoints of your environment:
4.1.1-LCF-0042
The Web Interface component is not supported on Windows
Vista endpoints.
- Configure the Ignore option results in APM - Feature 58122
- A new check box has been added to customize the behavior of the Activity
Planner Monitor for those targets failing the CM_STATUS validity check for
a software distribution (SWD) activity when the "Ignore" option is set. This
new check box will be enabled only when the "Ignore" check box is set. When
the check box is set, all targets on which the validation fails will be marked
as 'failed'. If this check box is not checked (default) the old behavior will
be in effect: targets for which the validation failed will be marked as successful.
- Add "defer" as possible default_action - Feature IY92880
- When a software distribution is performed specifying some options in
the User Notification Settings panel, not only "accept" and "reject" can be
selected as default action, but also "defer". The default action is
the action that is run after the specified timeout if no changes are performed
on the User Notification Settings panel.
- Nokia 9300i devices support
- With this feature, the Nokia device support has been extended. IBM Tivoli
Configuration Manager now supports Nokia 9300i devices. For these new devices,
the same set of functionalities of the Nokia 9300 devices is supported.
- Tivoli Provisioning Manager for Operating System Deployment
internationalized
- With this feature, the Tivoli Provisioning Manager for Operating System
Deployment product has been internationalized. To enable this feature, install
SWD_L10N under the /images path and the Tivoli_APM_GUI_L10N_Fix.v4.2.3.FP04.spb
software package block under the /packages path.
- Collect real and virtual network adapters - Feature
205563
- The network adapter table needs to differentiate between real and virtual
adapters. A new table ALL_NET_ADAPTER (H_ALL_NET_ADAPTER) having ADAPTER_ID
and COMPUTER_SYS_ID as fields was created. New views (ALL_NET_CARD_VIEW,H_ALL_NET_CARD_VIEW)
and new queries (ALL_NET_CARD_QUERY, H_ALL_NET_CARD_QUERY) were also created.
- VMware host serial number - Feature 205720
- Scanning a Windows VMware guest workstation, Inventory reports the serial
number of the VMware host in the SERIAL NUMBER column of the LPAR view.
- Collect LPAR information in a VMware environment - Feature
205561
- Inventory now uses the Common Inventory Technology (CIT) capability
to collect LPAR information in a VMware environment. 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
enabler is provided to bypass current limitations of some virtualization software
and should not be seen as a standard part of the Inventory offering.