BigFix_HeartBeat Issue

Usage and Config Platform
1

Hello everyone!
I am Japanese. Unfortunately I am not good at English.
However, I have some problems with BigFix.
I want help…

Heartbeat has not been made well in either A or B.

【Environment A】
○Server: 9.5.11
○Client1 (Consol)
Windows 10 (1803)
→64bit installed Officescan
○Client2 (Agent)
Windows 10 (1803)
→32bit installed Officescan

【Environment B】
○Server: 9.5.12
○Client1 (Agent, Relay, consol)
Windows 10 (1803)
→CPU:Celeron 64bit installedOfficescan
Client2 (Agent)
Windows 10 (1803)
→64bit

A: I applied FeatureUpdate to Client2.
The application of Feature Update(1809) fails probably due to Officescan, and After that Client2 goes offline.

B: I applied Feature Update(1809) to Client2 using the Relay function of Client1.
After that Client1 goes offline.

However, in the following cases, a report will be output and it will be online.

  1. First time at client restart
  2. “Send Update” is sent from console
  3. Take action and send report by action script

I want to know why this happens.

This is a part of the log.
"
At 14:48:40 +0900-
ActionLogMessage: (action: 218) Action signature verified for Downloads
ItemizedDownloadsAvailable: true (action id 218)
ActionLogMessage: (action: 218) Non-Distributed-Downloads Available
ActionLogMessage: (action: 218) Submitting download request
ActionLogMessage: (action: 218) Download url: 'http: //MANUAL_BES_CACHING_REQUIRED/Win10_1809Oct_Japanese_x32.iso’
At 14:49:03 +0900-
DownloadCRCPing command received
At 14: 52: 46 + 0 900-
Report posted successfully
"
After this, it was offline until 16:00 until it restarted.

Please let me know if you know.

Thankyou

2

If you’re only seeing this behavior during large package installation (like feature upgrade), then it is likely due to most of the client’s resources being used to complete the download. More specifically, after downloading the large ISO, it has to validate the SHA1 of the file, which can take quite a long time (probably more than an hour) at 2% CPU.

Since the agent is still responding to actions and refreshes, then it is working correctly, but too busy to make it through all its content to report a heartbeat. If you want this process to happen faster, then you can increase the WorkIdle/SleepIdle settings ratio to use more CPU, like 5-10%.

3

Steve, thanks for the answer.
In addition there are two questions.

  1. Does the problem of CPU processing power occur continuously?
    → After applying FeatureUpdate to another PC as a relay, it has been offline.

  2. We confirmed with Corp.TrendMicro that FeatureUpdate fails due to the combination of Featurescan for Officescan and 1809.
    It will go offline forever after it fails.

These problems have been constant even after rebooting.

Tell me if you know why.

Thank you