IBM Tivoli Provisioning Manager Fix Pack 1, Readme

(C) Copyright IBM^(R) Corporation 2006. All rights reserved. May only be used pursuant to a Tivoli^(R) Systems Software License Agreement, an IBM Software License Agreement, or Addendum for Tivoli Products to IBM Customer or License Agreement. No part of this publication may be reproduced, transmitted, transcribed, stored in a retrieval system, or translated into any computer language, in any form or by any means, electronic, mechanical, magnetic, optical, chemical, manual, or otherwise, without prior written permission of IBM Corporation. IBM Corporation grants you limited permission to make hardcopy or other reproductions of any machine-readable documentation for your own use, provided that each such reproduction shall carry the

IBM Corporation copyright notice. No other rights under copyright are granted without prior written permission of IBM Corporation. U.S. Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.

About this fix pack

This readme file contains the latest information about installing Tivoli Provisioning Manager Fix Pack, Version 5.1.0.1.

Important:: The fix pack only applies to a regular installation of Tivoli Provisioning Manager (an installation with WebSphere^(R) Application Server as the application server). A fix pack is not available for a Fast Start installation.

New in Version 5.1.0.1

The following updates are included in Version 5.1.0.1:

Coexistence with Tivoli Configuration Manager

If you are an existing Tivoli Configuration Manager customer you can continue using the Tivoli Management Framework infrastructure while taking advantage of the capabilities of Tivoli Provisioning Manager. This capability is to bring your existing Tivoli Management Framework infrastructure within the management of the Tivoli Provisioning Manager provisioning server. A stepped process is supported so that you can gradually start to work with the Tivoli Provisioning Manager interfaces while maintaining your Tivoli Management Framework environment. When you are ready, you can make a plan to gradually migrate to a full implementation of Tivoli Provisioning Manager.

Support for coexistence was added to Tivoli Provisioning Manager for Software Version 5.1 and is included in Tivoli Provisioning Manager 5.1.0.1 when you apply the fix pack.

Note:: The Fast Start installation does not support coexistence with Tivoli Configuration Manager.

For information about setting up coexistence, refer to the following information:

Tivoli Provisioning Manager for Software Migration and Coexistence Guide in the Tivoli Provisioning Manager for Software information center:http://publib.boulder.ibm.com/infocenter/tivihelp/v17r1/index.jsp
Updates to the documentation in Updates to the Tivoli Provisioning Manager for Software Migration and Coexistence Guide.
Ensure that you check for updated patches on the Tivoli Configuration Manager support Web site at http://www.ibm.com/software/sysmgmt/products/support/IBMTivoliConfigurationManager.html. Installing patches in your Tivoli Management Framework environment is a prerequisite step to setting up the Tivoli Provisioning Manager, Tivoli Configuration Manager coexistence environment.

Upgraded agent manager and common agent

This fix pack includes an update to agent manager and the common agent.

The agent manager is updated during the fix pack installation.
You must upgrade the common agent on depot servers and endpoints after you have installed the fix pack. For more information, see Upgrading the common agent.

Tivoli Provisioning Manager for OS Deployment Embedded Edition

The fix pack includes updates to Rembo Toolkit which is now available as Tivoli Provisioning Manager for OS Deployment Embedded Edition. Updates include:

Tivoli Provisioning Manager for OS Deployment Embedded Edition is globalized
Static IP support for imaging
Support for 32-bit and 64-bit images

You can perform the upgrade after applying the fix pack. For more information, see Upgrading Rembo Toolkit.

Installation on AIX^(R) with a separate DB2^(R) node

You can install Tivoli Provisioning Manager with DB2 on a separate computer. To install in this topology, you must manually install Tivoli Provisioning Manager. For more information, refer to the Tivoli Provisioning Manager Installation Guide for additional topologies on AIX: DB2 on a separate node.

Wake on LAN capability

Wake on LAN provides the ability to start a computer that is currently turned off. You can configure Tivoli Provisioning Manager to send a wake on LAN command to an endpoint. For more information, see "Setting up Wake on LAN" in the information center.

Simple software distribution for Linux^(R) and UNIX^(R)

Simple software product distribution support for Linux and UNIX target computers has been added to the existing Windows^(R) support that was available in Version 5.1.0.1. For more information, see "Simple software product distribution" in the information center.

File distribution

You can use file distribution to copy files in a specified file repository to selected target endpoints without installing them. For more information, see "Distributing files" in the information center.

Device manager federated agent

If you use branch office distribution, a device manager federated agent can be deployed in each branch or subsection of an environment. Endpoints can be configured to poll the device manager federated agent in the branch to ask for jobs and will send results to the same server. The device manager federated agents report status and receive new jobs from the device manager federator on the Tivoli Provisioning Manager server.

Local common agent installation

You can create an image for the common agent and then use the image and response file to install the common agent locally on an endpoint. After the agent is installed, you can use discovery to update Tivoli Provisioning Manager with information about the installed agent. For more information, see "Installing the common agent and subagents using a standalone installation" in the information center.

Client certificate authentication

A self-signed client user certificate can be used to authenticate to Tivoli Provisioning Manager. Using this certificate allows users to skip the default form-based login authentication that normally prompts them for the user ID and password. Client certificate based authentication can only be used if the Tivoli Provisioning Manager was installed using the regular installer and read-only LDAP has been configured. This feature is not supported with the Fast Start installation. For more information, see "Read-Only Lightweight Directory Access Protocol" in the information center.

Activity Plan Editor

The Activity Plan Editor plans enable you to define a group of activities in the Activity Plan Editor, submit the plan to run, and monitor the progress of the plan. Activities are single operations that are performed on a set of targets at specified times. Operations include tasks, software distribution, and inventory operations. Activities contained in a plan can have dependencies associated with them which define circumstances under which the activity is executed. The execution of the operation defined in the activity is performed by the application to which the operation belongs. The group of activities forms the activity plan.

Discovery enhancements

Enhancements to discovery include:

Ability to interface directly to the Change and Configuration Management Database rather than exporting a discovery book and importing it into Tivoli Provisioning Manager.
Ability to discovery more information about WebSphere Application Server and DB2 so that Tivoli Provisioning Manager can provide additional control over these applications. For example, you can use Tivoli Provisioning Manager to start and stop instances or capture an existing installation and deploy another installation with the same configuration.
Enhancements to the information imported from the Change and Configuration Management Database for some hardware resources.
Support for performing SMB discovery using a Windows domain account.

Firewall traversal

Tivoli Provisioning Manager provides a built-in proxy relay collector that you can use if the Tivoli Provisioning Manager servers are separated from endpoints by one or more intermediary networks because of firewall policies or address space concerns. For more information, see "Using a proxy relay collector for communication behind a firewall" in the information center.

Tivoli IT Service Management integration

If you have Tivoli IT Service Management, you can work with Tivoli Provisioning Manager by integrating parts of its user interface into your existing product. For more information, see "Tivoli IT Service Management integration" in the information center.

Client-based remediation Beta for patch management

Client-based remediation uses a "patch policy", and remediation is initiated by the endpoint, instead of Tivoli Provisioning Manager. Client-based remediation is available as a Beta for deployment to Windows endpoints only.

Fixes that were found in Version 5.1

Fix pack V 5.1.0.1 includes fixes addressed in Version 5.1 and customer Authorized Program Analysis Reports (APARs).

For a detailed list of fixes and customer APARs included in this fix pack, refer to the file 5.1.0-TIV-TIO-FP0001.DEFECTS or 5.1.0-TIV-TPM-FP0001.DEFECTS.

To download the defects list:

Go to the IBM Support Web site: http://www.ibm.com/support
In the Support topics list, click Downloads and Drivers.
In the Browse product support section, under Software list, click Tivoli.
In the search box, enter the fix pack number:
- For the Tivoli Intelligent Orchestrator Fix Pack V 5.1.0.1, enter:
  5.1.0-TIV-TIO-FP0001.
- For the Tivoli Provisioning Manager Fix Pack V 5.1.0.1, enter:
  5.1.0-TIV-TPM-FP0001.
Click Search. The Download Results page is displayed.
On the Download Results page, depending on your search, one of the following links is displayed:
- Tivoli Intelligent Orchestrator Fix Pack 5.1.0-TIV-TIO-FP0001
- Tivoli Provisioning Manager Fix Pack 5.1.0-TIV-TPM-FP0001
Click on the displayed link. The corresponding page is displayed.
For a list of defects that are corrected by this fix pack, click on 5.1.0-TIV-TIO-FP0001-DEFECTS (HTTP) or 5.1.0-TIV-TPM-FP0001-DEFECTS (HTTP).

Product compatibility

Fix Pack V 5.1.0.1 supports all the hardware and software that is supported by Tivoli Provisioning Manager V 5.1.0. The following considerations apply to the fix pack installation:

Fix pack applies to regular installations only: You can only apply the fix pack to a regular installation of Tivoli Provisioning Manager (an installation with WebSphere Application Server as the application server). A fix pack is not available for a Fast Start installation.
Software Package Editor compatibility: When Software Package Editor is updated with Tivoli Provisioning Manager Fix Pack 1, you cannot use these applications to connect with a Tivoli Provisioning Manager 5.1 installation that has not been updated with Fix Pack 1.
Topology: If you have Tivoli Provisioning Manager components distributed in a multi-node installation, the fix pack must be applied to the application server node where Tivoli Provisioning Manager is installed and not on the directory server node.
Coexistence with Tivoli Configuration Manager: The Fast Start installation does not support coexistence with Tivoli Configuration Manager.
Agent manager and common agent version: The agent manager is updated when you install Fix Pack 1. You must also upgrade the common agent on all depot servers after you have applied the fix pack.
Reports: Reports are updated during the fix pack installation, and some reports are deprecated after the fix pack is installed. The reports remain for your reference. You cannot run the reports, but you can view the SQL query for the reports and manually make changes to the SQL query, if required.
Deprecated reports are removed during an upgrade between major releases of Tivoli Provisioning Manager.

Preinstallation checklist

You must install and configure all components of Tivoli Provisioning Manager Version 5.1 before attempting the installation of Fix pack V 5.1.0.1. This includes setting up the database that you plan to use, LDAP, and so on. Thoroughly review the following list of prerequisites for installation before proceeding with the installation:

Identify your current installation situation:

First time Tivoli Provisioning Manager installation
You must install Tivoli Provisioning Manager 5.1 before you install the fix pack.
For a regular installation, refer to the Tivoli Provisioning Manager Installation Guide..
Important:
The Tivoli Provisioning Manager Installation Guide has been updated with a preinstallation checklist to help you to verify all installation requirements as well as recovery information for possible installation errors. The checklist for each operating system is included in the Fix Pack 1 download in the preinstall_checklist subfolder.

Tivoli Provisioning Manager is currently installed
The fix pack can be applied to an existing regular installation of Tivoli Provisioning Manager. After verifying all the prerequisites described in this section, you can install the fix pack. A fix pack is not available for a Fast Start installation.
Log in to the Tivoli Provisioning Manager server as tioadmin.
Verify that the currently installed version of Tivoli Provisioning Manager is operational before you begin the installation of Fix pack 1. The fix pack is compatible with version 5.1.0.0.
To determine the version of Tivoli Provisioning Manager:
1. Go to %TIO_HOME%\config, where TIO_HOME is the Tivoli Provisioning Manager installation directory.
2. Open the file named, build-version.properties.
3. Verify the information in the field, current.version.
Ensure that you can log in to Tivoli Provisioning Manager and run the workflow named no_operation, before installing the fix pack. If the workflow runs successfully, this verifies that the deployment engine in Tivoli Provisioning Manager is working properly.
Cancel all running workflows and clear failed, deleted, and canceled workflows.
Windows
1. Start Tivoli Provisioning Manager. For more information, refer to the section, Administering Tivoli Provisioning Manager in the Installation Guide.
2. Open a command window.
3. Switch to the %TIO_HOME%\tools directory where %TIO_HOME% is the Tivoli Provisioning Manager installation directory.
4. Run the following command:
```
cancel-all-in-progress.cmd
clean-up-deployment-requests.cmd
```
Perform a full backup of your current installation. See Backing up your installation.
Back up any customized automation package files in %TIO_HOME%\drivers. Store the files in a separate location and then delete the copies in %TIO_HOME%\drivers. The fix pack installation automatically migrates automation packages provided with the product. The installation will fail if your customized automation packages remain in the %TIO_HOME%\drivers directory.

Ensure that you have downloaded all the installation files required for the fix pack:

Operating System	Tivoli Provisioning Manager	Agent Manager	Dynamic Content Delivery service
Windows	5.1.0-TIV-TPM-WIN-FP0001.zip	AM_V13_WIN.zip	Dynamic Content Delivery (cds_images.zip) Unzip the file to a temp directory. (win32\setup.exe)
AIX	5.1.0-TIV-TPM-AIX-FP0001.zip	AM_V13_AIX.tar	Dynamic Content Delivery (cds_images.zip) Unzip the file to a temp directory. (aix/setup.bin)
Solaris	5.1.0-TIV-TPM-SOLARIS-FP0001.zip	AM_V13_SUN.tar	Dynamic Content Delivery (cds_images.zip) Unzip the file to a temp directory. (solaris/setup.bin)
Linux	5.1.0-TIV-TPM-LINUX-FP0001.zip	AM_V13_LIN.tar	Dynamic Content Delivery (cds_images.zip) Unzip the file to a temp directory. (linux/setup.bin)
		PPC Linux (AM_V13_LIN_PPC.tar)	Dynamic Content Delivery (cds_images.zip) Unzip the file to a temp directory. (linuxppc/setup.bin)
		Linux on zSeries (AM_V13_LIN_zSeries.tar)	Dynamic Content Delivery (cds_images.zip) Unzip the file to a temp directory. (linuxzSeries/setup.bin)

Create a temporary directory for the fix pack. In these instructions, the directory is called fp_temp. The temporary directory must meet these requirements:
- It exists outside the Tivoli Provisioning Manager installation directory.
- It includes at least 2 GB of free space to contain the fix pack after it is unzipped.
- The Administrator and tioadmin user must have read and write permission to this directory.
Extract the contents of the fix pack download to the temporary directory. After you unpack the file, you can delete the zipped fix pack download to free space in the directory if necessary.
Note:
If you unzip the file from Cygwin, ensure that the files under the fp_temp/installer directory have read and write permissions.
Place the agent manager image file in fp_temp/CAS without extracting the contents.
Place the dynamic content delivery service image file (setup.exe) in fp_temp/CDS.
Verify Tivoli Provisioning Manager is stopped.
Ensure that WebSphere Application Server is stopped too.
Use the serverStatus command to obtain the status of the WebSphere Application Server profile for Tivoli Provisioning Manager. The stopServer command stops the server.
1. Change to the %TIO_HOME%\tioprofile\bin directory, where %TIO_HOME% is the Tivoli Provisioning Manager installation directory.
2. Run the command:
```
stopServer app_server -username was_adminID -password password
```
  app_server
  The name of the application server. The default is server1.
  was_adminID
  The WebSphere Application Server administrator user name. The default is wasadmin
  password
  The WebSphere Application Server administrator password for the specified user name.
Ensure that the Tivoli Provisioning Manager database and directory server are still running. The database and directory server must be running during the fix pack installation process to complete the installation successfully.

Backing up your installation

Important:: The fix pack installation makes changes to the database, directory server, and files in the Tivoli Provisioning Manager installation directory. Since the fix pack affects multiple product components, ensure that you perform create a backup image of the entire Tivoli Provisioning Manager computer using your standard backup tools and processes. If the directory server is on a separate computer, also ensure that you back up the directory server data on that computer as described in Backing up directory server data.

If you want to recover your current Version 5.1.0.0 installation, or if you encounter an error during installation, You can use this backup to restore your current installation without the fix pack.

Before backing up or restoring the installation

Before you begin back up of the database, ensure that all running workflows are stopped, and then stop Tivoli Provisioning Manager.

Ensure that Tivoli Provisioning Manager is running.
Stop all running workflows.
1. Change to the %TIO_HOME%\tools directory.
2. From the command prompt, run the following commands:
```
cancel-all-in-progress.cmd
clean-up-deployment-requests.cmd
```
Stop Tivoli Provisioning Manager.
Stop all running applications on the Tivoli Provisioning Manager computer.

Backing up directory server data

Tivoli Provisioning Manager uses data on the directory server for authentication and authorization services. In Tivoli Provisioning Manager Version 5.1.0.0, all roles and user information are stored on the directory server. If your directory server is on a separate computer, ensure that you back up your Tivoli Provisioning Manager data on the directory server. If you need to restore your Tivoli Provisioning Manager Version 5.1.0.0 installation, the backed up directory server data can also be restored on the directory server.

Backing up on Tivoli Directory Server data

You can use tools provided with Tivoli Directory Server to back up your directory server data for Tivoli Provisioning Manager.

On the computer where Tivoli Directory Server is installed, stop Tivoli Directory Server. Run the following command:
```
ibmdirctl -D cn=root -w password stop
```
where password is the password for the root DN and hostname is the host name of the directory server computer.
To verify that Tivoli Directory Server is stopped, run the following command:
```
ibmdirctl -D cn=root -w password status
```
Change to the tds_installdir/sbin, where tds_installdir is the directory where Tivoli Directory Server is installed.

Run the following command to backup the directory server:

idsdbback -k path

where path is the full path where you want to store the backup. For example:

idsdbback -k d:\backup

A message similar to the following example is displayed.

You have chosen to perform the following actions:
 
GLPDBB029I The database and configuration files for directory server instance 
'tioadmin' will be backed up to 'd:\backup'.
 
Do you want to....
 (1) Continue with the above actions, or
 (2) Exit without making any changes:

Type 1 to confirm the backup.
Start Tivoli Directory Server. The directory server must be running to run the fix pack installer.

Backing up Microsoft Active Directory data

There are several ways to back up and restore data in Microsoft^(R) Active Directory. If you have an existing process and tools, you should follow your business processes for backing up and restoring the data.

This documentation describes two approaches:

Use the Windows backup utility. This method is simpler, but it backs up and restores the system state of the entire directory server.
Use the ldifde utility. You can back up and restore directory server data specific to Tivoli Provisioning Manager, but it requires more manual configuration steps.

Backing up with the Windows backup utility

To back up directory server data with the Windows backup utility:

Click Start > Programs > Accessories > System Tools > Backup. The Backup or Restore Wizard is displayed.
On the Welcome panel, Next.
On the Backup or Restore panel, click Backup files and settings and click Next.
On the What to Back Up panel, click Let me choose what to back up and click Next.
On the Items to Back Up panel, expand My Computer in the left pane, and then select the System State check box. Click Next.
On the Backup Type, Destination, and Name panel, specify the name of the backup file and the directory where you want to store it. Click Next.
A summary of your selections is displayed. Click Finish.

The backup file with the specified name is saved.

Backing up with the ldifde utility

To back up directory server data with the ldifde utility:

Identify the OU in the directory server that you want to back up. The default OU that is created for Tivoli Provisioning Manager is called TIO.
Run the following command to export the data to a backup file.
```
ldifde -m -f path -d root_DN
```
path
The full path and file name for the backup data.
root_DN
The OU and distinguished name (DN) for the directory server.

For example:
```
ldifde -m -f d:\backup\exportedTIO.ldif -d "ou=TIO,dc=tpmad,dc=example,dc=com"
```
A file with the specified name is created.
Open the backup data file in a text editor.

Passwords are not exported, so you must update user accounts so that empty password fields can be imported when you restore the data.

In the backup data file, search for each user object using the search term objectClass: user. The following example shows a user:

changetype: add
accountExpires: 9223372036854775807
cn: tioappadmin
codePage: 0
countryCode: 0
displayName: tioappadmin
distinguishedName: CN=tioappadmin,OU=TIO,DC=tpmAD,DC=example,DC=com
givenName: tioappadmin
homePhone: (000)111-2223
instanceType: 4
mail: user@company
mobile: (000)111-2223
name: tioappadmin
objectCategory: 
 CN=Person,CN=Schema,CN=Configuration,DC=tpmAD,DC=example,DC=com
objectClass: top
objectClass: person
objectClass: organizationalPerson
objectClass: user
sAMAccountName: tioappadmin
sn: tioappadmin
streetAddress: 123 Example Drive
telephoneNumber: (000)111-2223
userAccountControl: 66048
userPrincipalName: tioappadmin@company
uSNChanged: 54356
uSNCreated: 54354
whenChanged: 20061206184647.0Z
whenCreated: 20061206184647.0Z

For each user object, change the value of userAccountControl from 66048 to 66080. The following example shows the change in bold.

changetype: add
accountExpires: 9223372036854775807
cn: tioappadmin
codePage: 0
countryCode: 0
displayName: tioappadmin
distinguishedName: CN=tioappadmin,OU=TIO,DC=tpmAD,DC=torolab,DC=ibm,DC=com
givenName: tioappadmin
homePhone: (000)111-2223
instanceType: 4
mail: user@company
mobile: (000)111-2223
name: tioappadmin
objectCategory: 
 CN=Person,CN=Schema,CN=Configuration,DC=tpmAD,DC=torolab,DC=ibm,DC=com
objectClass: top
objectClass: person
objectClass: organizationalPerson
objectClass: user
sAMAccountName: tioappadmin
sn: tioappadmin
streetAddress: 123 Example Drive
telephoneNumber: (000)111-2223
userAccountControl: 66080
userPrincipalName: tioappadmin@company
uSNChanged: 54356
uSNCreated: 54354
whenChanged: 20061206184647.0Z
whenCreated: 20061206184647.0Z

Save your changes to the file.

Restoring Tivoli Directory Server data

If you need to restore your backed up directory server data, you can use tools provided with Tivoli Directory Server to perform the task.

Stop Tivoli Directory Server. Run the following command:
```
ibmdirctl -D cn=root -w password stop
```
where password is the password for the root DN and hostname is the host name of the directory server computer.
To verify that Tivoli Directory Server is stopped, run the following command:
```
ibmdirctl -D cn=root -w password status
```
Change to the tds_installdir/sbin, where tds_installdir is the directory where Tivoli Directory Server is installed.

Run the following command to restore the directory server data:

idsdbrestore -k path

where path is the full path where the backup data is stored.

idsdbrestore -k d:\backup

A message similar to the following example is displayed.

You have chosen to perform the following actions:
 
GLPDBR026I The database and configuration files for directory server instance
'tioadmin' will be restored from files in directory 'd:\backup'. 
Note: The data in the currently configured database will be overwritten and will be 
lost. The schema files and directory key stash file currently configured will be 
overwritten. Unless the -r option was specified the configuration file and 
configuration key stash file will also be overwritten.
 
Do you want to....
 (1) Continue with the above actions, or
 (2) Exit without making any changes:

Type 1 to confirm that you want to restore the data.

Restoring Microsoft Active Directory

The following procedures describes how to restore Microsoft Active Directory data that was backed up using one of the methods described in Backing up Microsoft Active Directory data.

Restoring with the Windows backup utility

To restore data with the Windows backup utility:

To restore the directory server data, you must reboot the computer in safe mode with the domain controller in Directory Services Restore Mode.
1. Reboot the computer, and press F8 during the reboot.
2. Select Directory Services Restore Mode (Windows domain controllers only) and continue the reboot in safe mode.
Click Start > Programs > Accessories > System Tools > Backup. The Backup or Restore Wizard is displayed.
On the Welcome panel, Next.
On the Backup or Restore panel, click Restore files and settings and click Next.
On the What to Restore panel, expand File in the left pane, and then expand the appropriate backup. Select the System State check box, and then click Next.
A summary of your selections is displayed. Click Finish.
Restart the computer for the changes to take effect.

Restoring with the ldifde utility

To restore directory server data with the ldifde utility:

Remove existing data in the organizational unit (OU) for Tivoli Provisioning Manager. The default OU is TIO.
1. Click Start > Programs > Control Panel > Administrative Tools > Active Directory Users and Computers.
2. Select the domain. For example, dc=tpmad,dc=example,dc=com.
3. Select the OU, and then delete it.
Run the command to restore the data.
```
ldifde -i -f filename
```
where filename is the full path and file name of the file with the backed up directory server data.
Reset the password of each user.
1. Click Start > Programs > Control Panel > Administrative Tools > Active Directory Users and Computers.
2. Select the domain. For example, dc=tpmad,dc=example,dc=com.
3. Select the TIO OU.
4. Select the name of a user and click Reset Password.
5. Specify a new password.
6. Repeat the above substeps for each user.

Troubleshooting Microsoft Active Directory data backup

Problems restoring with the Windows backup utility

If the following error is displayed when you try to restore data with the Windows backup utility, the computer is not running in Directory Services Restore Mode. See step 1 of Restoring with the Windows backup utility for more information.

The system state cannot be restored while the Active Directory service is running.
You must first re-boot and select the advanced startup option "Directory Services Restore Mode"
 before restoring the system state on this computer.

Problems restoring with the ldifde utility

If the following error is displayed when you try to restore data with the ldifde utility, the data that you exported for the backup file contains system specific information. The -m option must be included in the backup command to perform the restore operation successfully.

Add error on line 2: Unwilling To Perform 
The server side error is "The modification was not permitted for security reasons."
 0 entries modified successfully

If the following error is displayed when you try to restore data with the ldifde utility, verify that you have changed the user account settings for all user objects in the backup file as described in step 4 of Backing up with the ldifde utility.

Loading entries.. 
Add error on line 3: Unwilling To Perform 
The server side error is "Unable to update the password. The value provided for the 
new password does not meet the length, complexity, or history requirement of the domain."

Installing the fix pack

Ensure that you meet all the requirements as described in Preinstallation checklist.
Ensure that the directory server and database are running, and that Tivoli Provisioning Manager and WebSphere Application Server are stopped.
Log in to the Tivoli Provisioning Manager computer as tioadmin
Open a command within Windows (either locally or using remote desktop) but not remotely using SSH.
Change to the fp_temp directory.
Run the appropriate command:
Note:
Installation options are case-sensitive.
To perform the full fix pack installation, run the upgrade script with the application server and database passwords.
```
winUpgrade.bat -WASadmin was_adminID -WASadminPWD was_admin_pwd -DBRuntimePWD runtime_pwd -DBAdminPWD admin_pwd
```
was_adminID
The WebSphere Application Server administrator ID. The default is wasadmin.
was_admin_pwd
The WebSphere Application Server administrator password. The default is wasadmin.
runtime_pwd
Specify the database user password that was used to install Tivoli Provisioning Manager.
admin_pwd
Specify the database instance owner password that was used to install Tivoli Provisioning Manager.

Updating depot servers and endpoints

This section describes important updates to apply to depot servers and endpoints after installing Fix Pack 1.

Upgrading the common agent

You must upgrade the common agent on all depot servers and endpoints after installing Fix Pack 1. The instructions in this section are an update to the information center topic "Upgrading the common agent".

To upgrade the common agent, you must uninstall existing installed agents and then install the new common agent.

Important:

As you perform the upgrade, ensure that you select the correct software when you uninstall the old common agent and then install the new common agent.

Version 5.1.0.0: Tivoli Common Agent Stack for TPM V5.1
Version 5.1.0.1: Tivoli Common Agent Stack

Upgrading the common agent on depot servers

If you are using depot servers, upgrade the depot servers before you upgrade endpoints.

Verify that a service access point other than the Common Agent service access point (SAP) exists on each depot server. This service access point must support the Device.ExecuteCommand command.
Remove the common agent from depot servers. You can use the Uninstall Software Products page or use the uninstaller in the home directory where the common agent was installed. The common agent for Tivoli Provisioning Manager Version 5.1.0.0 is Tivoli Common Agent Stack for TPM V5.1.
Uninstall each depot server:
1. Click Inventory > Infrastructure Management > Depots.
2. Next to the depot server, click Delete.
Add each depot server that you removed.
1. Click Inventory > Infrastructure Management > Depots.
2. Click Edit > Add Depot.
3. Specify the appropriate options and then click Save. If you were using the depot services agent before you removed the depot, ensure the Install the depot agent services option is selected.

Upgrading the common agent on endpoints

After you have upgraded depot servers, upgrade the common agent on endpoints.

Verify that a service access point other than the Common Agent service access point (SAP) exists on each endpoint. This service access point must support the Device.ExecuteCommand command.
Uninstall the existing common agent. You can use the Uninstall Software Products page or use the uninstaller in the home directory where the common agent was installed. The common agent for Tivoli Provisioning Manager Version 5.1.0.0 is TCA-1.3.0.26.
Install the new common agent. The following steps describe how to install the default common agent from the Web interface:
Note:
The default common agent does not include the client-based remediation subagent. To install the common agent with client-based remediation subagent, you must use the Install Software Stacks page and select the TCA with Client Based Remediation Stack as the software stack to install.

To install the default common agent:
1. In the navigation pane, click Software Management > Install > Common Agent.
2. Follow the instructions on the Install Common Agent page:
  1. Type a relevant name for the common agent installation task.
  2. Select the common agent software stack for the task. The new common agent stack is called Tivoli Common Agent Stack.
  3. Select the Show computers missing any selected software box to filter the target computers based on missing software.
  4. Select one or more target computers for the task.
  5. If required, select the Credentials check box and specify the credentials for creating a Remote Execution and Access (RXA) service access point on each target computer. If no default service access points (SSH or RXA) exist on the target computers, you can specify here the credentials for an RXA service access point that will be created on each target computer.
  6. Schedule the task to run immediately or at a specified time.
  7. Configure the notification settings for the task.
  8. Save as favorite task, if needed.
  9. Click Submit.

Upgrading Rembo Toolkit

The new version of the Rembo Toolkit is now available as Tivoli Provisioning Manager for OS Deployment Embedded Edition. These instructions will help you upgrade your Rembo Toolkit to the latest version. All of your existing operating system images are preserved during this upgrade.

The instructions will help you upgrade your existing Rembo Toolkit to Tivoli Provisioning Manager for OS Deployment Embedded Edition if the following are true:

You were using an existing Tivoli Provisioning Manager 5.1 installation before applying fix pack.
You have one or more Rembo Toolkit 4.0 boot servers installed using Tivoli Provisioning Manager and you have images that were captured with the Rembo server.
Note:
When you installed Fix Pack 1, the rembo.tcdriver automation package was installed and the data for all of the Rembo data model objects were automatically migrated.

To upgrade your Rembo Toolkit to Tivoli Provisioning Manager for OS Deployment Embedded Edition:

Navigate to Inventory > Manage Inventory > Computers and find the computer that has the Rembo Toolkit installed.
Click on the computer name.
Click the Software tab.
Next to Rembo Toolkit 4.0, Actions > Upgrade.

The Rembo Toolkit is updated. The software installation now appears as TPM for OS Deployment EE.

Updating operating system attributes

An existing Tivoli Provisioning Manager computer that has been upgraded with the fix pack to Version 5.1.0.1, might have an updated architecture bus parameter for the operating system software configuration template. The default is value is 32-bit.

Note:: A capture image task will fail if the architecture bus parameter is empty or incorrect.

If the upgraded computer is a 64-bit computer, run the Windows Configuration Discovery again to populate the correct parameter value.

Navigate to Inventory > Manage Discovery > Discovery Configurations.
Next to the Windows Configuration Discovery, click the Actions icon, and then click Run.
Specify a unique name for this discovery task.
Display the target computer list By Computer and select the computer that you will use to capture the image.
Specify if you want the task to run immediately or schedule for a later time.
Click Submit.

The Windows Configuration Discovery will discover the attributes of the computer.

To verify that the correct architecture bus parameter value was populated, perform the following steps:

Click Inventory > Manage Inventory > Computers and select the computer.
Click the Software tab.
Click the Windows software installation.
On the Software Installation page, expand Configuration Templates.
Verify that the parameter ArchitectureBus is in the configuration template and has a value of either 32-bit or 64-bit. The parameter and a valid value are required for image capture to work successfully.

Migrating customized automation packages

After you have installed the fix pack, you must reinstall automation packages that you have created or customized. If you have made changes to data model objects that are imported by an automation package since installing it in Version 5.1.0.0, you can create migration workflows to automate the required changes to the data model objects.

To update an automation package:

Create the migration workflows that will perform the data model changes. In the workflows, include the data model queries to make the required changes for your automation package. The workflows must not require any input parameters to run.
Create an <update> section in the file TC-INF/tc-driver.xml for your automation package. The following example shows a section for an update to an automation package at the Tivoli Provisioning Manager Version 5.1.0.0 level.
```
<update version="5.1.0.1">
   <item name="workflow/Migrate/RemoveOldObjects_MigrateDCM_5_1_0_1.wkf" action="update-workflow" />
   <item name="workflow/Migrate/InsertNewObjects_MigrateDCM_5_1_0_1.wkf" action="update-workflow" />
</update>
```
- In the <update> element, specify the Tivoli Provisioning Manager version for this update. For migration workflow that update the automation package for Fix Pack 1, use the value 5.1.0.1.
- Create an <item> element for each migration workflow for the specified version.
  - Consider using a naming convention for your migration workflows. The example uses MigrateDCM_5_1_0_1 at the end of the migration workflow file names.
  - Consider storing the migration workflows in a separate directory. For example, workflows/Migrate.
  - The value for the action attribute is always update-workflow.
Save your changes to tc-driver.xml and repackage the automation package.
Install the updated automation package. The migration workflows are registered with Tivoli Provisioning Manager. They are added to a master update workflow called __master_tcdriver_udpate_. This workflow runs when the deployment engine starts.
Restart Tivoli Provisioning Manager so that the deployment engine is restarted.

When the deployment engine starts, it runs the workflow __master_tcdriver_udpate_ and runs the migration workflows that are registered. During this migration process, the deployment engine does accept any other deployment requests. When the migration process is complete, the deployment engine starts to process deployment requests in the queue.

If the migration process fails, the deployment engine stops. Check the workflow execution log for the deployment request for the __master_tcdriver_udpate_ workflow and correct any errors in the migration workflow that failed. To view workflow execution logs from the Web interface:

Click Automation > Workflow Status.
Search for the __master_tcdriver_udpate_ workflow.
Click the workflow execution ID for the __master_tcdriver_udpate_ workflow in the search results. The log for the workflow execution is displayed.

Recovering from installation errors

The following main steps occur during installation of the fix pack:

Installation of fix pack files.
Post-installation configuration such as migration of directory server data and migration of automation packages.
Upgrade of the agent manager.
Upgrade of the dynamic content delivery service.

The fix pack uninstaller can revert the changes made in step 1, but it cannot revert any of the changes made after that step. An uninstaller is not available for the other steps. If an installation error occurs during any of these steps, it therefore recommended that you restore your backup of Tivoli Provisioning Manager before you applied the fix pack, and then try the fix pack installation again.

To recover from an installation error:

Record any error messages that you received and address the errors.
Check the log files for information about the error and possible recovery actions.
Fix pack installer
%TIO_HOME%\logs\update
Data migration
%TIO_LOGS%\fixpack
The agent manager
The logs subdirectory of the agent manager installation directory. The default agent manager installation directory is:
```
C:\Program Files\IBM\AgentManager
```
The dynamic content delivery service
The default location for the dynamic content delivery service logs is:
```
C:\Program Files\IBM\tivoli\common\ctgde\logs
```
Check Known problems and workarounds for possible installation errors and recovery actions.
Restore the system image that you created for the Tivoli Provisioning Manager computer in Backing up your installation using your standard backup tools and processes.
If your directory server is on a separate computer, ensure that you also restore your backed up directory server data as described in Backing up directory server data.
Try to apply the fix pack again.

For information about the fix pack installer, see Uninstallation information.

Updates to the documentation

The information center is updated for Tivoli Provisioning Manager Version 5.1.0.1. You can view the updated Tivoli Provisioning Manager information center on ibm.com, or you can download the latest version of the product information after installing the product.

To update your local information center to the most current level, follow the instructions below.

Go to Information updates page in the information center.
Follow the instructions on the page.

The following subsections highlight additional important changes to the documentation.

Updated installation documentation

The Tivoli Provisioning Manager Installation Guide has been updated with a preinstallation checklist to help you to verify all installation requirements as well as recovery information for possible installation errors.

The checklist for each operating system is included in the Fix Pack 1 download in the preinstall_checklist subfolder.
You can view the complete updated installation guides in the latest information center.

Updates to the Tivoli Provisioning Manager for Software Migration and Coexistence Guide

In Chapter 2, "Creating a coexistence environment", the section "Step 2: Installing patches on the IBM Tivoli Management Framework environment" describes installation of fixes, including the Software Distribution Server fix. Before applying the Software Distribution Server fix, ensure that you have stopped the Tivoli Provisioning Manager server.

Common agent installation

Standalone installation using an image

If you are using an image to perform a standalone installation, note the following updates apply to the information center topic "Installing the common agent and subagents using a standalone installation". This information does not apply to an installation of the common agent from the Web interface.

Installing the common agent without client-based remediation

Note:: For Tivoli Provisioning Manager Version 5.1.0.1, client-based remediation is available as a Beta for deployment to Windows endpoints only.

When you create an image of the common agent, the image contains all subagents by default. If you do not want to use client-based remediation you must remove the subagent from the image before you use install it on an endpoint.

To remove the subagent for client-based remediation from the image, delete the following files from the subagents subfolder of the image.

com.ibm.tivoli.tpm.compliance.remediation.subagent.jar
com.ibm.tivoli.tpm.compliance.remediation.commons.jar

Using a truststore file

If you are distributing a truststore file with installation of the common agent, you must update the scripts install.bat (for Windows endpoints) and install.sh (for UNIX or Linux endpoints) to copy the truststore file to the correct location on endpoints. Perform the following steps:

Verify settings in the response file caInstall.rsp.
- Leave the default location of the truststore on the endpoint. The default is agent_install_dir/trust.
- The following settings are configured:
```
CASInstall.TruststoreType="copy"
CASInstall.TrustStoreLocation="cert"
```
Add the following commands at the beginning of the scripts. If are not installing the common agent in the default location, replace c:\program files\tivoli\ep\cert and /opt/tivoli/ep/cert with the correct full path.
install.bat
```
mkdir "c:\program files\tivoli\ep\cert"
copy d:\windows\cert\agentTrust.jks "c:\program files\tivoli\ep\cert"
 
```
install.sh
```
mkdir -p /opt/tivoli/ep/cert
cp /media/cdrom/linux86/cert/agentTrust.jks /opt/tivoli/ep/cert
```

Disk space footprint on AIX

In the information center, the requirements for installing the common agent state that 150 MB of space is required in the installation location, /usr or /opt.

Most of the common agent installation files and the subagents are installed in the /usr directory. The Common Inventory Technology (CIT) subagent is installed in /opt and requires approximately 30 MB of disk space.

Changing access rights

In the information center topic "Requirements for common agent installation", the following statement appears:

Microsoft Active Directory overwrites some required default user privileges when it is installed on Windows 2003. You must modify the access rights for the user used to install the common agent so that the required privileges are assigned to the user account.

A similar statement appears in the Chapter 3 of the Tivoli Provisioning Manager Installation Guide for Windows under the section "Changing user privileges".

Microsoft Active Directory overwrites some required default user privileges when it is installed on Windows 2003. You must modify the access rights for tioadmin so that the required privileges are assigned to the user account.

This statement applies to all installations of Tivoli Provisioning Manager on a Windows computer. Ensure that you follow the documented instructions for updating the access rights.

Client-based remediation setup

Note:: For Tivoli Provisioning Manager Version 5.1.0.1, client-based remediation is available as a Beta for deployment to Windows endpoints only.

If the Tivoli Provisioning Manager server is running on Linux or UNIX or does not have Internet access, you can use a Windows gateway computer to act as a proxy for communication with the Windows Server Update Services.

Set up a Windows computer as your gateway.
1. The computer must be defined in the Tivoli Provisioning Manager data model.
2. Cygwin 1.5.10 or higher must be installed. Packages for SSH and Wget must be installed.
3. SSH credentials must be configured for the computer.
Define the computer as the gateway in Tivoli Provisioning Manager.
1. In the navigation pane, click System Management > Global Settings.
2. Click the Variables tab.
3. Find the variable wsus-download-sever-name.
4. Set the value of the variable to the name of the gateway server (the value of the Name field).
If the operating system for the gateway computer is not defined in the data model, add a software resource for it.
1. Navigate to Inventory > Manage Inventory > Computers.
2. Find the gateway computer and click its name in the search results.
3. Click the Software tab.
4. Click Edit > Add Software Installation.
5. In the Name field, type the name of the operating system.
6. In the Software Definition list, select the software definition that matches the operating system on the gateway computer.
7. Specify any other required options and then click Save.
Add a variable to the gateway computer to identify it as the proxy server:
1. In the navigation pane, search for the computer using the Find field and click its name in the search results.
2. Click the Variables tab.
3. Add the variable wsus-proxy-server-enabled and set the value to true. This variable determines if download through the proxy is required or not. Since we are running all operations (cab file download, cab file extraction, etc) on a remote Windows computer, all relevant info has to be attached to this computer.
4. Add the variable wsus-download-proxy-server-ip and specify the proxy server IP.
5. The remote Windows system server must have an HTTP SAP with WUA context that will hold all relevant information on proxy server, such as the proxy port, proxy user name, and proxy password.

Disk space required for downloading patches

The information center topic "Downloading the Microsoft updates" describes how to download Microsoft patches in advance before performing patch installation. If you decide to perform this optional procedure, ensure that you have allocated enough disk space for the patches on the provisioning server.

For each locale that you download, allocate a minimum of 4 GB of free disk space. As more patches are discovered by Microsoft, more disk space will be required.

Default administrator for Web interface

For a regular installation, the users tioappadmin and tioadmin are created. The tioappadmin user is the default administrator user in the Web interface and has all permissions for all objects in the data model.

If you are performing a Fast Start installation, only the tioadmin user is created. The tioadmin user is not assigned to an access group by default, so you must assign the permissions to the user. To assign all permissions for all objects in the data model:

Log on to the Web interface with the user tioadmin.
Click System Management > Manage Users.
Click the tioadmin user.
Select Edit > Assign Access Permissions.
Under Available Access Groups, select sample:all-objects
Under Available Permissions, select sample:all-permissions
Click Save.

Uninstallation information

This section describe how to uninstall files installed by the fix pack installer. This process only reverts files installed by the fix pack installer. It does not revert migrated data or upgraded core components.

If you only need to revert the changes made by the fix pack installer, use the information in this section.
If the fix pack installation performed any additional steps after running the fix pack installer, the only way to revert all changes is to restore your backup of the Tivoli Provisioning Manager installation before you applied the fix pack. See Recovering from installation errors for more information.

Before you begin

Before you uninstall the fix pack:

Ensure that the database server and the directory server are both running.
Stop the Tivoli Provisioning Manager server. For detailed instructions on how to start and stop the servers in different environments, refer to the installation guide that is supplied with the product.
Ensure that the WebSphere Application Server is stopped.

Uninstalling the fix pack

To uninstall Fix Pack V 5.1.0.1 on Windows using the silent uninstaller:

From a command prompt, log in to the Tivoli Provisioning Manager server as Administrator
On the Tivoli Provisioning Manager server, ensure that both the JAVA_HOME and WAS_HOME environment variables are set.
Note:
The WAS_HOME variable is the location of the WebSphere Application Server and the JAVA_HOME variable is set to WAS_HOME\java
Change the directory to fp_temp\installer where fp_temp is the directory in which you unzipped the fix pack ZIP file.

From fp_temp\installer, run the following command, from a Windows Command prompt, to launch the uninstallation using the silent mode:

updateSilent.bat -fixpack [ -install | -uninstall | -list ] todinstallDir [ fixpackID ] [ installFixpackDir ]

For example, to uninstall the fix pack on Windows systems:

updateSilent.bat -fixpack -uninstall "C:\Program Files\IBM\tivoli\tpm" tpm51_fp1_win_Enterprise "C:\Program Files\IBM\temp\installer"

The system completes the installation. A successful installation gives an error level of 0. Review the log files located in %TIO_HOME%\logs\update directory for any errors.

Redeploying the expanded archive files

After you have completed the uninstallation procedure, you must redeploy the EAR (expanded archive) files on the WebSphere Application Server.

To redeploy the EAR files:

Log in to the Tivoli Provisioning Manager server as user tioadmin.
Start the WebSphere Application Server.
Run the command given below from a Cygwin command prompt:
```
$TIO_HOME/tools/was_deploy.sh"  username password server base_DN
```
For example:
```
"$TIO_HOME/tools/was_deploy.sh"  wasadmin wasadmin server1 "dc=mycompany,dc=com"
```
Note:
Replace the variables in the command with the correct values:
- was_user with your WebSphere Application Server user name
- was_pwd with your WebSphere Application Server password
- server with the Application server name
- base_DN with the Base Distinguished Name of the Application server. The correct value for base_DN can be obtained from the XML tag <root> in $TIO_HOME/config/user-factory.xml.
Stop the WebSphere Application Server.

Known problems and workarounds

This section describes known limitations in this release of Tivoli Provisioning Manager V 5.1.0. Where applicable and known, suggested workarounds are identified.

Workarounds for installation problems

This section provides workarounds to problems that you might encounter during the installation of the Fix pack.

Unable to start Tivoli Provisioning Manager

Description

When starting Tivoli Provisioning Manager V 5.1.0 from the Windows Services menu, the following error occurs:

Could not Start the IBM Tivoli Intelligent Orchestrator service on Local Computer
Error 1069: The service did not start due to a logon failure

Workaround

The tioadmin user must have Log On As Service privileges. To grant the privilege:

Login as tioadmin.
Go to Start > Programs > Administrative tools.
Start Local Security Policy Management console.
In that console go to: Local Policies >User Rights Assignment.
Add tioadmin user to the Log on as service property.

Post-installation script fails

Description

When you try to rerun the fix pack installation winUpgrade.bat or the post-installation script postinstall.bat, an error message is displayed.

Error about the eclipse directory

ERROR: Need to clean up C:\Program Files\IBM\tivoli\tpm\eclipse before running post-install, exiting.

Resolution

To fix the error about the eclipse directory, remove the %TIO_HOME%\eclipse directory before you run the fix pack installation or post-installation script again.

Tivoli Provisioning Manager is not processing deployment requests

Description

After starting Tivoli Provisioning Manager for the first time, deployment requests for workflows remain in the Create state and do not run.

Explanation

The first time that you start Tivoli Provisioning Manager after the applying Fix Pack 1, the deployment engine runs a workflow to migrate automation packages provided with the product to the Fix Pack 1 level. During this migration process, the deployment engine does accept any other deployment requests.

When the migration process is complete, the deployment engine starts to process deployment requests in the queue.

If the migration process fails, the deployment engine will not start. You must restore your Tivoli Provisioning Manager and try to apply the fix pack again.

Running Windows Update Agent discovery scans for patch management and client-based remediation

Description

If your Tivoli Provisioning Manager

environment is configured to run both of the following types of Windows Update Agent discovery scans:

Discovery scans that originate from the Tivoli Provisioning Manager for server-based patch management.
Discovery scans that originate from endpoints for client-based remediation.

Ensure that you schedule these discovery scans so that the scan periods do not overlap. If both discovery scans are running at the same time, the discovery scans might fail.

Assigning a static IP to a Windows 2000 computer

Description

To assign a static IP address to a Windows 2000 computer, the network interfaces of the target computer must be physically connected and network-enabled. Interfaces that are not enabled on the network will not be fully configured.

This limitation is caused by a known issue with Windows 2000. For more information, refer to article KB815322 on the Microsoft Web site.

Discovery of network interfaces on Sunfire 4200 AMD Opteron

Description

When you run Rembo Hardware discovery on a Sunfire 4200 AMD Opteron computer with multiple network interfaces, more than one network interface is has the Netboot Enabled option selected for network booting, but only one network interface is physically connected. The cpu.family attribute is also identified as Intel.

Resolution

You can manually fix the information that was incorrectly discovered.

Navigate to Inventory > Manage Inventory > Computers and find the Sunfire 4200 AMD Opteron computer.
Disable network booting for one of the network interfaces:
1. Expand Network Resources and find the network interface.
2. In the row with the network interface, click Actions > Properties.
3. Clear the Netboot Enabled check box, and then click Save.
Correct the type of CPU identified by the discovery:
1. Expand Hardware Resources.
2. Find the cpu.family property and change its value to AMD.

Cannot retrieve the list of packages in Software Package Editor

If you receive the following error when you try to retrieve a list of packages in Software Package Editor, here is some additional information about the error and how to diagnose it.

DISSP6047E An error occurred while retrieving the list of packages. See the log for details.

Explanation: An error occurs when you try to retrieve the list of packages by selecting Open > Open from repository. This problem is caused by communication problems, and the operation is not performed.

Verify the following conditions:

The connection to Tivoli Provisioning Manager by checking the hostname, the port, and the URL definition on in the Preferences page of the Eclipse-based Software Package Editor.
The presence of a firewall.
Tivoli Provisioning Manager is up and running.

For additional details, see the workflow log in the Tivoli Provisioning Manager Web Interface, and the swdisGUI.tr1 and swdisGUI.tr2 trace files. If you are using the Eclipse-based Software Package Editor, you can find these trace files in the Eclipse installation directory. If you are using the Web Start Software Package Editor, you can find these trace files in the Web Start cache memory directory.

Excluded targets appear when submitting an activity plan

Description

When you exclude targets from an activity plan at the plan level using a target file, the excluded targets are displayed when you submit the plan. This behavior is a limitation of the user interface and does not affect the way that the activity plan is processed.

Registration of device manager endpoints

Description

Registration of device manager endpoints causes an OutOfMemory error. The error appears in the WebSphere Application Server log file %TIO_HOME%\tioprofile\logs\server1\SystemOut.log.

Workaround

Reduce the maximum number of open connections and change the heap size.

Log on to the WebSphere Application Server administration console at:
```
https://hostname:9043/ibm/console/logon.jsp
```
Change the number of open connections.
1. Click Servers > Application servers > server_name > Ports.
2. Click View associated transports for the appropriate port.
3. Change the Maximum open connections setting to 2500.
Change the maximum heap size:
1. Click Servers > Application servers > server_name > Process Definition > Java Virtual Machine.
2. Change the Maximum Heap Size setting to 1024 MB.

Manually backing up the installation

If you do not have the ability to create a complete image of your Tivoli Provisioning Manager computer, follow the information in this section to back up your database and save the current Tivoli Provisioning Manager and core component installation directories.

Note:: A full Tivoli Provisioning Manager image is the supported backup method.

Backing up a DB2 database

To back up the database:

Ensure that you followed the steps in Before backing up or restoring the installation.
Open the file %TIO_HOME%\config\dcm.xml to verify the database name and user name. The name element contains an alias for the database name, and the username element contains the user name. This information is specified Tivoli Provisioning Manager installation.
Log on as Administrator.
Open a DB2 command window.
Run the following command to check for other running applications:
```
db2 list applications
```
If the command lists other applications, run the following command to disconnect them:
```
db2 force applications all
```
If you are not connected to the database, use the db2 connect command to connect to the database.
Back up the database with the following command:
```
db2 backup db db_name user user_name using password to location
```
db_name
The name of the database.
user_name
The user name of the user performing the backup.
password
The password used to authenticate the user name.
location
The location that the database backup will be stored.
- The full path of the location is required. The specified directory must already exist.
- The instance owner user must have write permissions to the specified path.
- Consider saving the backup in a location that is accessible from the Tivoli Provisioning Manager computer so that you do not need to transfer the backup to a second location when you are performing backup and restore operations.
If you did not select a target directory that is accessible to the Tivoli Provisioning Manager computer, transfer the backup to an accessible location.

A backup has been created and can be used to restore the Tivoli Provisioning Manager database when it is required.

Restoring a DB2 database

To restore the database:

Ensure that you followed the steps in Before backing up or restoring the installation.
Open the file %TIO_HOME%\config\dcm.xml to verify the database name and user name. The name element contains an alias for the database name, and the username element contains the user name. This information is specified Tivoli Provisioning Manager installation.
Log on as Administrator.
Open a DB2 command window.
Run the following command to check for other running applications:
```
db2 list applications
```
If the command lists other applications, run the following command to disconnect them:
```
db2 force applications all
```
End the DB2 session with the command db2 terminate.
Delete and uncatalog the existing database with the following command
```
db2 drop db db_name
```
where db_name is the name of the database.
Restore the backed up database with the following command:
```
db2 restore db db_name user user_name using password from location
```
db_name
The name of the database.
user_name
The user name of the user restoring the database.
password
The password used to authenticate the user name.
location
The location where the backup is stored. The full path of the location is required.

The Tivoli Provisioning Manager database has been restored. The database backup remains in place so that you can restore the database whenever it is required.

Backing up the directory server

Follow the instructions in Backing up directory server data.

Backing up Tivoli Provisioning Manager and core component files

Back up the following directories before you apply the fix pack so that you can recover the files at a later time or if you encounter errors during installation.

Tivoli Provisioning Manager installation directory

This directory contains Tivoli Provisioning Manager and files for dynamic content delivery service. The default location is:

C:\Program Files\ibm\tivoli\tpm

Note:: If you installed the dynamic content delivery service in a different directory, ensure that you back up that directory.

Agent Manager installation directory

The default location is:

C:\Program Files\IBM\AgentManager

Manually installing the fix pack

This section describes the manual installation of the Tivoli Provisioning Manager fix pack.

Note:: Only regular installation of the fix pack with winUpgrade.bat is officially supported.

To install Fix Pack V 5.1.0.1 using the silent mode:

Ensure that you meet all the requirements as described in Preinstallation checklist.
On the Tivoli Provisioning Manager server, ensure that both the JAVA_HOME and WAS_HOME environment variables are set.
WAS_HOME variable
```
echo %WAS_HOME%
```
The WAS_HOME variable is the location of the WebSphere Application Server and the output would be similar to this:
```
C:\IBM\WebSphere\AppServer
```
JAVA_HOME variable
```
echo %JAVA_HOME%
```
The output would be similar to this:
```
C:\IBM\WebSphere\AppServer\java
```
Log in to the Tivoli Provisioning Manager server as tioadmin.
Change directory to fp_temp directory.

Run the following command:

updateSilent.bat -fixpack [ -install | -uninstall | -list ] todinstallDir [ fixpackID ] [ installFixpackDir ]

The system completes the installation. A successful installation gives an error level of 0. Review the log files located in %TIO_HOME%\logs\update directory for any errors.

Data migration and post-installation steps

Complete the following instructions after you install the fix pack.

Back up the database from your fix pack installation using the backup utility that is provided with the database.
Log on as tioadmin.
Ensure that the database server and the directory server are running.
Stop the Tivoli Provisioning Manager server.
Ensure that the WebSphere Application Server is stopped when the Tivoli Provisioning Manager server is stopped.
Open a DOS command prompt.
Change the directory to fp_temp\installer\utils.
Run the following command:
```
postinstall.bat was_user was_pwd server "base_DN"
```
- was_user with your WebSphere Application Server user name
- was_pwd with your WebSphere Application Server password
- server with the Application server name. The default is server1.
- base_DN with the Base Distinguished Name of the Application server
  Note:
  The correct value for base_DN can be obtained from the XML tag <root> in %TIO_HOME%\config\user-factory.xml.
For example:
```
postinstall.bat wasadmin wasadmin server1 "dc=mycompany,dc=com"
```
The log files for the post-installation script can be found in the directory: %TIO_LOGS%\fixpack.
Note:
- Restart the system if you get an error similar to this and then reset the ulimit size after restarting the system.
```
Too many open files
```
- If the post-installation script fails, perform the following steps:
  1. Remove the %TIO_HOME%\eclipse directory.
  2. Run the post-installation script again.
From a command window, run the command
```
%TIO_HOME%\tools\setupCmdLine.cmd
```
.
Update the Tivoli common agent services:
1. Change to the fp_temp\CAS directory.
2. Extract the contents of the agent manager image.
3. Run the following command:
```
start /B /WAIT "" setupwin32.exe -is:javahome "%JAVA_HOME%" -silent -W CASInstall.InstallType="upgrade" -W CASInstall.DBRuntimePassword="runtime_pwd" -W CASInstall.DBAdminPassword="admin_pwd" -W CASInstall.StartAfterReboot="False" -W CASInstall.StartAfterInstall="False"
```
  runtime_pwd
  Specify the database user password that was used to install Tivoli Provisioning Manager.
  admin_pwd
  Specify the database instance owner password that was used to install Tivoli Provisioning Manager.
Copy setup.exe from fp_temp\CDS to cds_installdir\scripts.
Change to the cds_installdir\scripts directory, where cds_installdir is the dynamic content delivery service installation directory.

Run the following command:

start /B /WAIT "" setup.exe -silent -is:log %TEMP%\cds_upgrade.txt -V LICENSE_ACCEPT_BUTTON="true" -V CDS_DB_PASSWORD="runtime_pwd"

runtime_pwd: Specify the database user password that was used to install Tivoli Provisioning Manager.

Stop WebSphere Application Server with the following command:
1. Change to the %TIO_HOME%\tioprofile\bin directory, where %TIO_HOME% is the Tivoli Provisioning Manager installation directory.
2. Run the command:
```
stopServer app_server -username was_adminID -password password
```
  app_server
  The name of the application server. The default is server1.
  was_adminID
  The WebSphere Application Server administrator user name. The default is wasadmin
  password
  The WebSphere Application Server administrator password for the specified user name.
Stop and restart Tivoli Provisioning Manager.

Contacting customer support

If you have any questions about this fix pack, call the IBM Support Center for your country. For example, in the USA call 1-800-IBM-SERV. For specific contact numbers for all countries, refer to the following Web site:

http://techsupport.services.ibm.com/guides/contacts.html

If you find a problem or have a suggestion about the Automation Package Development Environment features or the documentation in general, contact IBM through the Tivoli Provisioning Manager and Intelligent Orchestrator Automation Package Development Environment forum. The forum is a technical discussion focussed on installing, configuring and using the Automation Package Development Environment (APDE) for writing workflows and creating automation packages for the Tivoli Provisioning Manager products.

To access the forum:

Go to the Web site,http://www-128.ibm.com/developerworks/forums/tivoli_forums.jsp
Click on the Tivoli Provisioning Manager and Intelligent Orchestrator Automation Package Development Environment link on the Web site.

Notices and trademarks

The following section includes important information about this document and its use.

Notices

This information was developed for products and services offered in the U.S.A.

IBM may not offer the products, services, or features discussed in this document in other countries. Consult your local IBM representative for information on the products and services currently available in your area. Any reference to an IBM product, program, or service is not intended to state or imply that only that IBM product, program, or service may be used. Any functionally equivalent product, program, or service that does not infringe any IBM intellectual property right may be used instead. However, it is the user's responsibility to evaluate and verify the operation of any non-IBM product, program, or service.

IBM may have patents or pending patent applications covering subject matter described in this document. The furnishing of this document does not grant you any license to these patents. You can send license inquiries, in writing, to:
IBM Director of Licensing
IBM Corporation
North Castle Drive
Armonk, NY 10504-1785
U.S.A.

For license inquiries regarding double-byte (DBCS) information, contact the IBM Intellectual Property Department in your country or send inquiries, in writing, to:
IBM World Trade Asia Corporation
Licensing
2-31 Roppongi 3-chome, Minato-ku
Tokyo 106, Japan

The following paragraph does not apply to the United Kingdom or any other country where such provisions are inconsistent with local law:

INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.

Some states do not allow disclaimer of express or implied warranties in certain transactions, therefore, this statement may not apply to you.

This information could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein; these changes will be incorporated in new editions of the publication. IBM may make improvements and/or changes in the product(s) and/or the program(s) described in this publication at any time without notice.

Any references in this information to non-IBM Web sites are provided for convenience only and do not in any manner serve as an endorsement of those Web sites. The materials at those Web sites are not part of the materials for this IBM product and use of those Web sites is at your own risk.

IBM may use or distribute any of the information you supply in any way it believes appropriate without incurring any obligation to you.

Licensees of this program who wish to have information about it for the purpose of enabling: (i) the exchange of information between independently created programs and other programs (including this one) and (ii) the mutual use of the information which has been exchanged, should contact:
IBM Canada Ltd.
Office of the Lab Director
8200 Warden Avenue
Markham, Ontario
L6G 1C7
Canada

Such information may be available, subject to appropriate terms and conditions, including in some cases, payment of a fee.

The licensed program described in this document and all licensed material available for it are provided by IBM under terms of the IBM Customer Agreement, IBM International Program License Agreement or any equivalent agreement between us.

Trademarks

The following terms are trademarks or registered trademarks of International Business Machines Corporation in the United States or other countries or both:

IBM
Tivoli
The Tivoli logo
WebSphere
AIX
DB2

Linux is a trademark of Linus Torvalds in the United States, other countries, or both.

UNIX is a trademark of The Open Group in the United States, other countries, or both.

Java^(TM) and all Java-based trademarks and logos are trademarks of Sun Microsystems, Inc. in the United States, other countries, or both.

Microsoft and Windows are trademarks or registered trademarks of Microsoft Corporation in the United States, other countries, or both.

Other company, product and service names may be trademarks or service marks of others.