[ Bottom of Page | Previous Page | Next Page | Contents ]
You could consider the following approach:
- Create a V2.1 environment, with a new administration server, runtime servers, and runtime server databases separate
from those of V1.1.1.
- Fully configure this environment but do not start any servers.
- Prepare a schedule for redeploying the agents to use the new runtime servers, using
one or more of the V2.1 agent redeployment methods:
- Web deployment
- The installagent command
- Using the software distribution component of Tivoli Configuration Manager
- On UNIX nodes in RSH/SSH networks
- Windows logon script
- OS/400 agent deployment from connected Windows node
See the chapter on agent deployment in IBM Tivoli License Manager: Planning, Installation, and Configuration, version 2.1.
- Stop the V1.1.1 servers.
- Migrate the administration server database on to a new computer that the V2.1 administration server
is configured to use.
- Start the V2.1 servers.
- Redeploy the agents.
- Uninstall the V1.1.1 servers and databases.
[ Top of Page | Previous Page | Next Page | Contents ]