Performing post-migration updates to rules and policies

If you are upgrading BMC Server Automation using the various component installers, you must run the postmigration file to update BLPackages that refer to old Group Policy Object (GPO) assets.

This topic contains the following sections:

• • Before you begin
  • To execute the postmigration file
  • Where to go from here

Before you begin

Perform upgrade and post-migration activities in the following order. This order of steps ensures that all the Application Server steps are completed first, and that the need for a specific BMC Server Automation Console (RCP client) restart does not interfere with the postmigration script. For more information, see Upgrading-using-individual-component-installers.

1. Before upgrading the BMC Server Automation Application Server, run the configurator utility.
2. Upgrade the Application Server and then stop the Application Server.
3. Execute the postmigration file as described in this topic.
4. Stop the RSCD Agent, and then upgrade the BMC Server Automation Console.
5. Ensure that the RSCD Agent is restarted after you upgrade the BMC Server Automation Console.

To execute the postmigration file

Warning: Prior to running the postmigration file, review the following Knowledge Article from BMC Customer Support to avoid running out of disk space on the Application Server:  When upgrading BMC Server Automation to 8.5.1 Patch 4, 8.6, or 8.7, the postmigration utility fails with "No space left on device" (Knowledge Article ID: KA421781 ) 

1. Navigate to the postmigration file found within the BMC Server Automation installation directory:

   (Windows):  <installDirectory>\NSH\bin\postmigration
   (Linux or UNIX): <installDirectory>/NSH/bin/postmigration

    

2. Run the postmigration file.
    Progress messages regarding the relevant component templates are displayed on-screen and are also written to the postmigration.log file stored in the same location as the postmigration file.

Where to go from here