We have 2 BF Inventory servers and want to use just one. We do not want to migrate any data just the agents from 1 BF server to the 2nd.
Can we just migrate the agents (using http://www-01.ibm.com/support/docview.wss?uid=swg21506046) ?
We can set up the scan on the new BF Inventory server but do the agents need to be reset before or after migration to clear any data in the dirs on the BF Agent?
The masthead switch should work for you but I suggest trying it on a few clients before doing all of them.
As long as you have dynamic-targetted actions in the BigFix deployment (so that the migrated agents execute the catalog updates, scans, and uploads in the target deployment) the masthead switch should be all that you need.
Currently running the following:
Server 1 Red Hat 6.x
ILMT version: 9.2.14.0-20181211-2317
Bigfix Server Version: 9.5.5.193 with schema: 9.44, DB Version: DB2 v10.5.0.8 8
Server 2 Red Hat 7.x
ILMT version: 9.2.15.0-20190401-1727
Bigfix Server Version: 9.5.11.191 with schema: 9.96, DB Version: DB2 v10.5.0.10 10
I need to migrate the clients from Server 1 to Server 2. Do I need to remove or upgrade the BigFix clients or can I just copy over the new masthead file from the new server to the clients?
What is the best process for migrating clients from one server to another?
Since Server 2 appears to be the target environment, copy Server 2’s actionsite.afxm or masthead.afxm file to the /var/opt/BESServer/wwwrootbes/Uploads folder on Server 2. For convenience, this file should be named masthead.afxm.
From the Server 1 BigFix Console, take action on the Task 1516: Switch BES Client Masthead - BES >= 9.0, found in the BES Support Site.
In the Take Action dialog box, choose the appropriate target clients. Then open the Action Script tab, and modify the URL in line 1 of the Action Script to point to Server 2. (something like: http://server2:52311/Uploads/masthead.afxm ).
After the computers show up in the new environment, you can upgrade the BigFix Clients to 9.5.11.191.
What are the differences to this migration strategy if we’re moving from a Windows server based BigFix 9.2.9 to a Windows server based BigFix 10.
Ideally we’d like to migrate the agents first as they are and then upgrade them once on the new BigFix 10 server.
Mixed agent OS’s to migrate: RedHat, CentOS, Win Server and Solaris.
The same strategy will work for Windows to Windows migrations. Find the wwwrootbes/Uploads folder on the BigFix v10 root server, and copy the new v10 actionsite.axfm as masthead.afxm into this location.
After that, you can do the Masthead Switch in the v9 environment as above, taking care to modify the URL in the actionscript to point to the v10 server, and then upgrade your endpoints to v10 after they appear in the v10 Console.
Note that the Masthead Switch action will never finish in the v9 console.
Thanks.
That has worked for the non-firewalled agents.
What would be the strategy to migrate a relay, and it’s connected agents, that are firewalled.
i.e the agents can only talk to that Relay and the Relay then has a firewalled route through to the master. How do I preserve the connectivity from those agents to the Relay?