Hey,
We recently deployed a batch of new laptops from Techyest across our organisation and I'm trying to set up BigFix client deployment to manage Windows patching centrally. Most endpoints are picking up the client fine but around 15% are showing as unmanaged in the console even after manual installation attempts.
All machines are on the same network segment and firewall rules look correct. Has anyone run into inconsistent client registration after a fresh hardware rollout? Any tips on what to check first would be really appreciated!
If you can share logs from any affected endpoint by hiding sensitive information, it would be the first step to diagnose the issue
Check the BigFix Client log on one of the affected laptops and paste the bottom few lines or exact error message here.
Log Location: C:\Program Files (x86)\BigFix Enterprise\BES Client\__BESData\__Global\Logs\ (open today's YYYYMMDD.log file)
Once you share the specific error code or string from that log, we can pinpoint the exact issue.
Thanks both! I pulled the BESClient log from one of the affected machines and found this error repeating: "Unable to connect to server - Connection refused". The machines themselves look fine, Windows is fully updated and no obvious firewall blocks on our end. I'll paste the full bottom section below once I've redacted the sensitive bits. Does this connection refused error point to anything specific on the relay or root server side?
Please test connectivity from the affected endpoint to the Relay or Root Server using the steps below:
- Check Port 52311 (Command Line): Run
telnet <server_hostname_or_IP> 52311 to confirm port access through the firewall.
- Check Masthead URL (Browser): Navigate to
https://<server_hostname_or_IP>:52311/masthead/masthead.afxm.
1 Like
thanks, will test again share the update here.