Client not reporting to the bigfix server

[Moinul]

Can anyone please help, Recently we have upgraded our Bigfix server from 2012 to 2019, we have imported all the fillets and installed the new client to all the devices, the issue is the devices are stopped to report to bigfix server after a certain time, I checked all BESClient is up and running in services, any idea what is the fix for it please. It works if we send manual refresh to all the devices. After send the manual refresh it start to report but stopped again after certain time. Your help is much appreciated

[JasonWalker]

It is not clear to me what you are saying.

If you upgraded your BigFix Server from Windows 2012 to Windows Server 2019, you should not have to import fixlets or install new clients.

Did you upgrade your server, or are you trying to migrate to a new server?

Is the new server using the same Masthead as the original BigFix deployment, or are you trying to migrate clients to a new masthead?

[Moinul]

We have migrated to the new Bigfix server, old server had 2012 server OS with Bigfix 9.5 and the new one with server 2019 OS with Bigfix 11 with new masthead file, that is the reason we had to export all the fillets from old bigfix server to the new BigFix server.

[itsmpro92]

Post deleted by author

[DerrickD]

Sounds like you didn’t upgrade, you created a whole new BigFix environment.

You’ll want to review documentation on moving a client to a new BigFix server.

If they are still connected to your older environment, then you can reuse and augment as needed the switch masthead tasks.

If not, the short answer is you’ll want to at minimum delete KeyStorage, __BESData, swap out the masthead, but you’ll probably also need to reset/reconfigure some client configs as well. You’ll have to touch every client.

[Aram]

@Moinul

It works if we send manual refresh to all the devices. After send the manual refresh it start to report but stopped again after certain time. Your help is much appreciated

If the question is about Clients already registered and reporting into your new BigFix Server, it sounds like you may need to troubleshoot Client responsiveness. Jason has a good topic on this:

Tip: Troubleshooting Client Reponsiveness

I hope to make a thread here or Wiki post to cover some steps to diagnose one of the most common reported issues, “My clients are not reporting”. This can be complex to diagnose, because there can be several causes related to each customer’s specific configuration. Nothing here is meant to supplant advice from BigFix Support or BigFix Services, but my hope is this can be a handy reference for first steps at diagnosing common issues. The settings discussed in this post can be found at https://…

If my guess is correct, I’d suggest reviewing the following section from the topic above: “If the client is posting reports, but much less frequently than expected; is receiving GatherHashMV messages, but is slow to execute or report back Analysis results, there may be long-running evaluations”

Regardless, I’d suggest opening a Support case to help troubleshoot further.