Smooth Transition of BigFix Clients to a New Instance with New Relays

Content Authoring
1

Hello Team,

We currently have a BigFix setup with three relays and approximately 3,000 endpoints. Now, we are planning to migrate all the clients to a new BigFix instance that has three new relays.

Could you please guide me on the best approach to achieve this transition smoothly? Specifically, I’m looking for insights on:

  1. Steps to configure the new instance and relays to accept the clients.
  2. Efficiently updating client configurations to point them to the new relays without causing disruptions.
  3. Handling potential challenges during the migration process.

If there are any tools, scripts, or recommendations for minimizing downtime and ensuring a seamless migration, I would greatly appreciate it.

2

During the phased migration, you can consider and implement the following points to ensure a smooth transition:

Use the Switch Masthead Fixlet and Modify It Accordingly:

A. Run Port Checks Against All New Relays:

  • Integrate a port-checking mechanism within the Fixlet using a tool like PortQry.exe.
  • The script should test connectivity to all new relay servers on the required port (e.g., port 52311 or your specific port).

B. Check Port Check Logs for Client Connectivity:

  • After running the port checks, analyze the logs to determine if the client can connect to any of the new relays.
  • Proceed with the migration only if the client successfully connects to at least one new relay.

C. Create Batch File for Masthead Switch and Client Reset:

  • The batch file should handle the masthead switch and resets the BESClient.
  • This batch file is responsible for performing the necessary actions after the masthead switch, including below:
    • Replacing the Masthead File:
    • Resetting the BESClient:
      • Deletes client data folders and specific registry keys to reset the client’s state.
      • Applies key client settings related to the new infrastructure, such as relay configurations and reporting intervals.
    • Updating the FailoverRelayList:
      • Configures the client with a complete list of relay addresses (combination of IP & Hostname to avoid DNS issues), combining both new and old relays to ensure connectivity (if by any chance you want to roll back the client).
    • Restarting the BESClient Service:
1 Like