I have a Bigfix deployment where some of my relays are reporting an actionsite version much higher than it should be. This is probably due to the fact that we had to reinstall our Bigfix server. We also reinstalled the relays and clients, but some may have old settings somehow.
The “normal” actionsite version is 165. Some relays are reporting an actionsite version of 383. Is it correct to assume that these relays will not be getting actions until the actionsite version “catches up”? Is there an easy way to fix this? I have 20 relays showing an actionsite version of 383.
The relays are supposed to be smart enough to realize that if you have gone back in time far enough, then they need to reset themselves to the new sequence number… but in this case, it seems like this isn’t working. You can check with support and they can try to diagnose… or you can BES Remove and reinstall the relay and that will wipe away all its history of the previous actionsite sequence numbers.
Unfortunately, just doing a uninstall and reinstall from the BES console of the relay agent does not work. In most cases, the client will not even process the action, but in the cases where it did, when the relay was reinstalled the actionsite was still 383.
I’ve been able to fix it by doing this:
Uninstall the Relay agent.
Uninstall the BES client.
Delete all the leftover files from the Bigfix directory.
Yes. The BES Remove tool will make that easier by collapsing steps 1-3 into 1 step…
Note that if you stop the relay service, the agent should get its instructions from the server (I am pretty sure about this, but you should try it) and so you might be able to simply stop the relays for a bit and then you can get control of the agent on the relay…
Oh, I didn’t realize that you meant a utility called “BES Remove”. I’ve found and downloaded it and am running it on the affected machines via psexec, then BES client deploy to reinstall the client, and the bes task to install the relay agent again.
PS. Running besremove.exe /silent /all doesn’t remove some of the BES Client files. Running it twice removes everything. Strange, but not a huge deal.
