We are having an issue with clients after upgrades that were migrated to a new bigfix instance.
We are migrating to a new instance of bigfix (new license, new FQDN of the masthead). We will soon no longer control the domain that the FQDN used so we are migrating.
We are using the fixlet Switch BES Client Action Site Masthead - BES >= 9.0 to migrate to the new server and that is working great. The fixlet runs on the old device, it starts communicating with the new environment and stops communicating with the old environment.
The issue happens when upgrading the client from 10.0.7 to 10.0.8(new server is 10.0.8) During the upgrade some clients seem to revert back to the old masthead and try communicating with the old server again.
This does not happen on all servers, only on about 20% so far
I think the problem is happening in this line of the client upgrade log where it seems to find an old masthead(from the last client upgrade) in temp
InstallShield 8:50:06: Invoking script function FindMastheadFile
MSI (s) (54!F0) [08:50:06:579]: PROPERTY CHANGE: Modifying MASTHEADFILE property. Its current value is ‘’. Its new value: ‘C:\Windows\TEMP\ActionSite.afxm’.
MSI (s) (54!F0) [08:50:06:595]: PROPERTY CHANGE: Adding MASTHEADFILEDESTLOCATION property. Its value is ‘c:\Program Files (x86)\BigFix Enterprise\BES Client\ActionSite.afxm’.
1: INSTALLATION INFO: Successfully copied c:\Program Files (x86)\BigFix Enterprise\BES Client\ActionSite.afxm to C:\Windows\TEMP\ActionSite.afxm
I checked temp on the devices that failed and that file is the old masthead file. Should the temp ActionSite.afxm file be deleted for the upgrade or am I missing any steps in the migration to ensure that this does not happen?