We are attempting to migrate the BigFix client from our old root server to a new root server using the “Switch BES Client Action Site Masthead - BES >= 9.0” and “Switch BES Client Action Site Masthead (Windows)” task. However, the migration is not completing successfully. We have noticed that the keystorage folder contains only two files.
OLD Root server version= 10.0.8
New Root server Version= 11.0.3
Could you please assist us in resolving this issue?
Looks like the migration didn’t go as planned. If you’re seeing only two files in the keystorage folder, it means the BigFix Client didn’t complete the registration process.
To make sure your BES Client migration goes smoothly, keep these key points in mind:
Check Network Connectivity
Make sure the new BigFix master server or relay servers are reachable from the client’s new location or subnet.
Run telnet or other network tests to confirm connectivity.
Double-check with your network team to ensure that all required firewall rules and ports are properly configured.
Preserve Critical Client Settings
Take note of any important settings, like failover relay configurations, that the client will need after the migration.
Ensure the client is set up correctly so it can immediately connect to the new environment after switching the masthead.
Handle Client Reset During Masthead Switch
When the masthead switches, the client resets completely, meaning all previous settings are wiped.
To prevent issues, preconfigure the necessary settings using a batch job or script to reapply them after the migration.
Thanks for your inputs. We have already verified the suggested points both before and after the migration, and all prerequisites are in place. However, we are still facing the same issue.
Your client registration is still not completing, indicating a clear issue with client-relay communication. I recommend engaging your network or firewall team to monitor for any potential blockages while reinitiating the client registration process. Alternatively, you may consider opening a case with the HCL support team for further assistance.