| Pristine Manager |
There is a deployment service
called the Pristine Manager. It is used for the initial installation of
computers or the reinstallation of existing computers. Deployment
Administrators now have an ITCM integrated tool to manage the different
images used for the initial installation or the reinstallation of existing
computers. All management information is stored in the Configuration
Repository. |
| Default Customizations |
It is possible to customize the
distribution parameters as well as operational mode of an existing
SoftwarePackage or a SoftwarePackage to be built. |
| Dynamic variables |
It is possible to change values
during the SoftwarePackage execution on the target. |
| Change Manager |
The long awaited sequencing feature has
been implemented. You can sequence tasks by associating priorities to
each configuration element. |
| Scanning of Microsoft
Hot Fixes and Patches |
A new Automation Server can be used to
apply patches. The scanner engine has been updated
to pick up those Windows Updates directly from native registry keys and WMI.
By using Tivoli queries, you can now list Hotfixes. |
| Integration with Tivoli
Provisioning Manager |
Workflows delivered by Tivoli
Provisioning Manager can now be used by ITCM 4.2.3. These workflows can use
the sophisticated capabilities of ITCM 4.2.3 to provide a highly capable
Configuration Management process. |
| Activity Planner |
Periodic Status Notification can be
provided to Deployment Administrators. |
| Framework 4.1.1 |
There is a feature for Tivoli Gateways to
periodically test the "health" of their assigned Endpoints. In case a
problem is found, it can be fixed automatically or the Framework
Administrator can be notified. |
| MDist2 tables |
Software Deployment will only start if
ITCM has connectivity to the MDist2 tables located in the Configuration
Repository. In the older version 4.2, if the connectivity was not available
then the Deployment Administrator did have very limited control over the
distribution of SoftwarePackages. |
