(imported topic written by Quynhnd91)
I have deployed some security hotfix successful but after 3 hours I have still seen them on Add/Remove Program on BES Client (I begin deploy for BES Client .
Normal after 5 minutes status of these security hotfixs on BES Consolve display “Complete-Cache on BES Server” I can see them on Add/Remove Program (Last time I have tested))
How do I know these security hotfixs deployed successful?
How do I solve this problem?
Thanks
I am from Misoft in VietNam
(imported comment written by BenKus)
Hi Quynhnd,
In your BES Console, look on the “Actions” tab and double-click on the action you took. Look at the “Computers” tab below to see the action result for each computer to figure out what happened.
Ben
(imported comment written by Quynhnd91)
Thanks Ben,
I have checked as you have been guide. The result is and 0% fixed
All BES Client were no fixed. Security hotfixs are only downloaded to BES Server.
I was attached capture screen on BES Console for a action
I look forward to your support.
Thanks.
(imported comment written by BenKus)
I recommend looking at:
http://support.bigfix.com/cgi-bin/kbdirect.pl?id=173
And if that doesn’t help, you should probably open a support case because something might not be working as expected.
Ben
(imported comment written by Quynhnd91)
Thanks Ben,
I have checked this solution.
I will try again continue.
What are more reasons?
(imported comment written by BenKus)
Quynhnd,
I suggest you start up a support case because it sounds like your BES Server or BES Relays or BES Clients are not properly configured or not working properly.
Ben
(imported comment written by Quynhnd91)
Hi Ben,
After I have been send refresh to BES Client and view log as below:
Can you explain
FAILED to Synchronize
error below?
Thanks!
At 08:54:22 +0700 -
Report posted successfully.
At 09:09:11 +0700 -
Report posted successfully.
At 09:15:12 +0700 -
Client shutdown (Service manager stop request)
At 09:15:13 +0700 -
Starting client version 6.0.7.8
At 09:15:16 +0700 -
RegisterOnce: Attempting to register with ‘http://127.0.0.1:52311/cgi-bin/bfenterprise/clientregister.exe?RequestType=RegisterMe60&ClientVersion=6.0.7.8&Body=1178681125&SequenceNumber=13&MinRelayVersion=6.0.0.0’
Registered
At 09:15:17 +0700 - actionsite (http://172.16.18.204:52311/cgi-bin/bfgather.exe/actionsite)
Successful Synchronization with FixSite (version 4) - ‘http://127.0.0.1:52311/cgi-bin/bfenterprise/BESGatherMirror.exe?url=http://172.16.18.204:52311/cgi-bin/bfgather.exe/actionsite’
At 09:15:17 +0700 - BES Asset Discovery (http://sync.bigfix.com/cgi-bin/bfgather/assetdiscovery)
Successful Synchronization with FixSite (version 15) - ‘http://127.0.0.1:52311/cgi-bin/bfenterprise/BESGatherMirror.exe?url=http://sync.bigfix.com/cgi-bin/bfgather/assetdiscovery’
At 09:15:17 +0700 - BES Inventory and License (http://sync.bigfix.com/cgi-bin/bfgather/besinventory)
Successful Synchronization with FixSite (version 35) - ‘http://127.0.0.1:52311/cgi-bin/bfenterprise/BESGatherMirror.exe?url=http://sync.bigfix.com/cgi-bin/bfgather/besinventory’
At 09:15:18 +0700 - BES Support (http://sync.bigfix.com/cgi-bin/bfgather/bessupport)
Successful Synchronization with FixSite (version 364) - ‘http://127.0.0.1:52311/cgi-bin/bfenterprise/BESGatherMirror.exe?url=http://sync.bigfix.com/cgi-bin/bfgather/bessupport’
At 09:15:18 +0700 - BigFix AntiPest (powered by PestPatrol) (http://sync.bigfix.com/cgi-bin/bfgather/antipest)
Successful Synchronization with FixSite (version 191) - ‘http://127.0.0.1:52311/cgi-bin/bfenterprise/BESGatherMirror.exe?url=http://sync.bigfix.com/cgi-bin/bfgather/antipest’
At 09:15:18 +0700 - Client Manager for Anti-Virus (http://sync.bigfix.com/cgi-bin/bfgather/avclient)
Successful Synchronization with FixSite (version 921) - ‘http://127.0.0.1:52311/cgi-bin/bfenterprise/BESGatherMirror.exe?url=http://sync.bigfix.com/cgi-bin/bfgather/avclient’
At 09:15:18 +0700 - Client Manager for Spyware Tools (http://sync.bigfix.com/cgi-bin/bfgather/spywareclient)
Successful Synchronization with FixSite (version 106) - ‘http://127.0.0.1:52311/cgi-bin/bfenterprise/BESGatherMirror.exe?url=http://sync.bigfix.com/cgi-bin/bfgather/spywareclient’
At 09:15:18 +0700 - Enterprise Security (http://sync.bigfix.com/cgi-bin/bfgather/bessecurity)
Successful Synchronization with FixSite (version 864) - ‘http://127.0.0.1:52311/cgi-bin/bfenterprise/BESGatherMirror.exe?url=http://sync.bigfix.com/cgi-bin/bfgather/bessecurity’
At 09:15:18 +0700 - Patches for RedHat Enterprise Linux (http://sync.bigfix.com/cgi-bin/bfgather/rhelpatches)
Successful Synchronization with FixSite (version 190) - ‘http://127.0.0.1:52311/cgi-bin/bfenterprise/BESGatherMirror.exe?url=http://sync.bigfix.com/cgi-bin/bfgather/rhelpatches’
At 09:15:18 +0700 - Patches for Solaris (http://sync.bigfix.com/cgi-bin/bfgather/solarispatches)
Successful Synchronization with FixSite (version 486) - ‘http://127.0.0.1:52311/cgi-bin/bfenterprise/BESGatherMirror.exe?url=http://sync.bigfix.com/cgi-bin/bfgather/solarispatches’
At 09:15:18 +0700 - SANS Top Vulnerabilities to Windows Systems (http://sync.bigfix.com/cgi-bin/bfgather/sanswindows)
Successful Synchronization with FixSite (version 45) - ‘http://127.0.0.1:52311/cgi-bin/bfenterprise/BESGatherMirror.exe?url=http://sync.bigfix.com/cgi-bin/bfgather/sanswindows’
At 09:15:18 +0700 - Security Policy Manager (http://sync.bigfix.com/cgi-bin/bfgather/securitypolicymanager)
Successful Synchronization with FixSite (version 37) - ‘http://127.0.0.1:52311/cgi-bin/bfenterprise/BESGatherMirror.exe?url=http://sync.bigfix.com/cgi-bin/bfgather/securitypolicymanager’
At 09:15:18 +0700 - Updates for Windows Applications (http://sync.bigfix.com/cgi-bin/bfgather/updateswindowsapps)
Successful Synchronization with FixSite (version 63) - ‘http://127.0.0.1:52311/cgi-bin/bfenterprise/BESGatherMirror.exe?url=http://sync.bigfix.com/cgi-bin/bfgather/updateswindowsapps’
At 09:15:29 +0700 -
Report posted successfully.
At 09:29:01 +0700 -
DownloadPing command received
At 09:32:19 +0700 -
Report posted successfully.
At 09:36:01 +0700 -
DownloadPing command received
At 09:46:54 +0700 -
Report posted successfully.
At 10:01:32 +0700 -
Report posted successfully.
At 10:16:01 +0700 -
Report posted successfully.
At 10:27:03 +0700 -
ForceRefresh command received
ForceRefresh: Version difference, gathering action site
At 10:27:04 +0700 - actionsite (http://172.16.18.204:52311/cgi-bin/bfgather.exe/actionsite)
FAILED to Synchronize - General transport failure. - ‘http://127.0.0.1:52311/cgi-bin/bfenterprise/BESGatherMirror.exe?url=http://172.16.18.204:52311/cgi-bin/bfgather.exe/actionsite&Time=11May10:27:04&rand=7b24fa78’ http failure code 404
At 10:27:07 +0700 -
Report posted successfully.
At 10:28:04 +0700 - actionsite (http://172.16.18.204:52311/cgi-bin/bfgather.exe/actionsite)
FAILED to Synchronize - General transport failure. - ‘http://127.0.0.1:52311/cgi-bin/bfenterprise/BESGatherMirror.exe?url=http://172.16.18.204:52311/cgi-bin/bfgather.exe/actionsite&Time=11May10:28:04&rand=4945716e’ http failure code 404
At 10:29:42 +0700 -
Report posted successfully.
At 10:32:12 +0700 -
Report posted successfully.
At 10:33:21 +0700 - actionsite (http://172.16.18.204:52311/cgi-bin/bfgather.exe/actionsite)
FAILED to Synchronize - General transport failure. - ‘http://127.0.0.1:52311/cgi-bin/bfenterprise/BESGatherMirror.exe?url=http://172.16.18.204:52311/cgi-bin/bfgather.exe/actionsite&Time=11May10:33:21&rand=44f47b4e’ http failure code 404
(imported comment written by BenKus)
The failed to synchronize for the actionsite is the reason your agents are not getting the new action… It could be for multiple reasons… you might try to run the BES Diagnostics tool on your BES Server to try to spot the issue (it is in your start menu).
Something to try is to restart the root server service and send another action… If you are using a proxy, pay close attention to the “Exclude” section of the proxy instructions at http://support.bigfix.com/cgi-bin/kbdirect.pl?id=105
But I suggest that you start a support case because I can’t really troubleshoot it well here.
Ben
(imported comment written by Quynhnd91)
Thanks Ben,
I have added the BES server IP address and hostname at the exception list (proxy configuration on IE browse)
Now BES Clients are deployed.
Thank you very much for your help.