IBM Support

How do I migrate clients to a new server that uses a different masthead? Called a "masthead switch"

Technote (troubleshooting)


Problem(Abstract)

You will need to distribute the masthead for the new server to the clients currently using the old server. This is often referred to as performing a "masthead switch".

Resolving the problem

You will need to distribute the masthead for the new server to the clients currently using the old server. Due to the complexity and risks of migrating clients to a new server, it is strongly recommended that a IBM Support Technician help in planning the migration process.

Note: We will call the old deployment 'Deployment A' and the new deployment 'Deployment B'. We will assume both deployments are already installed and functional.

It is very important that you STOP or REMOVE all TEM Relays from Deployment A before you begin the migration process. Due to this requirement, you should ensure that TEM is not being actively used for any major software/patch deployments while the migration is ongoing.

Using a Web URL:

  • The new masthead.afxm file for the new deployment needs to be web accessible to the clients that are being migrated, you have a few options for doing this when taking the switch masthead action:
    • If the new TEM server or any of the new TEM relays in the new deployment (Deployment B) are reachable by the clients you are migrating, you simply need to point the clients to pick up the new masthead from one of the new relays or the new server. The new masthead is accessible on these new parents at: http://{NEW PARENT}:52311/masthead/masthead.afxm
    • Take the first action on Task # 460 - "Switch BES Client Action Site Masthead- BES >= 7" in the BES Support site, edit the action script, and change the URL in the action script to the URL from a host of 127.0.0.1 to the address of one of the new parent relays or server.


    • If none of the new deployment's TEM servers or relays are reachable by the old clients, you can host the masthead.afxm file in the wwwrootbes directory of the server or the relays of the old deployment (Deployment B). The new masthead.afxm file would then be accessible at the following URL: http://{OLD PARENT}:52311/cgi-bin/wwwrootbes/masthead.afxm
    • Export the masthead file from the TEM Administration tool on the new deployment TEM server. Bring the file over and place the file in either \BES Server\wwwrootbes (if hosting on the old server), or \BES Relay\wwwrootbes (if hosting on an old relay).
    • Take the first action on Task # 460 - "Switch BES Client Action Site Masthead- BES >= 7" in the BES Support site, edit the action script, and change the URL in the action script to the URL from a host of 127.0.0.1 to the address of one of the new parent relays or server:
      http://{OLD PARENT}:52311/cgi-bin/wwwrootbes/masthead.afxm

Using a Network Share:
  • The masthead.afxm file can also be hosted on a network share.
    Export the masthead file from the TEM Administration tool on the new deployment TEM server. Place the file on the network share location you would like to host it at.

    Take the second action on Task # 460 - "Switch BES Client Action Site Masthead- BES >= 7" in the BES Support site and in the dialog replace \\server_name\share_name\masthead.afxm with the network share location you are hosting your masthead file at:


Notes:
  • Take the switch masthead action from the old TEM deployment (Deployment A), this tell clients to download the new masthead and restart.
  • It is Highly recommended to initially target this action only at a small test group of computers. When you are satisfied that the clients have switched successfully to the new deployment (Deployment B), then you should gradually target this Task to more clients in production.
  • Eventually, you should create a policy action from this task targeting at all computers.
  • After you create the policy action, you should leave the old TEM (Deployment A) server running for at least a week. This will give clients that have not checked in recently a chance to get the new masthead. There is no harm in leaving the server running for a long period to pick up any stragglers.
  • When you are satisfied that almost all clients have transitioned to Deployment B, you will want to recreate your relay structure in Deployment B.
  • Make sure to run the BES Remove utility to completely remove all traces of the TEM Relay installation on any machines that were formerly relays in Deployment A.
  • After running the BES Remove utility, you can use the normal TEM Relay installation tasks in BES Support to install Relays for Deployment B.

Related information

How to Migrate Primary IBM Tivoli Endpoint Manager and

Historical Number

373

Document information

More support for: IBM BigFix family

Software version: All Versions

Operating system(s): Platform Independent

Reference #: 1506046

Modified date: 15 September 2014


Translate this page: