/build/static/layout/Breadcrumb_cap_w.png

Systems Management Question


Unable to reach Agent-managed devices and Most of the desktops are failed

11/03/2017 1713 views
Hi,

1. I could see the error Offline -  "unable to reach Agent-Managed device" on my devices which are in Patch Schedule. Even though, devices are online and able to ping the devices with the latest Agent 7.2 is running and its keeps updating the inventory, Can anyone help me where exactly im going wrong and to fix this issue. SavVPb.png

2. Second issue, most of the devices goes in Failed on status. Please refer the screenshots and appreciate your help. Thank youovyAUI.png
3 Comments   [ + ] Show comments

Comments

  • Are your devices with the agen5 installed able to resolve the server name via dns? 7.x relies on the agent being deployed via server name rather than IP address, this would prevent the agent from communicating effectively during the patching lifecycle
  • Make sure those machines are able to ping the K1 box using it's FQDN.

    Do a telnet test to port 443 against that FQDN.

    Are all your devices showing as Offline or just some of them?

    If you go to Settings › Support › Diagnostic Utilities

    Pick Services, see if you see any services in failed status
  • Sorry for the delayed reply, Thank you for the updates, unable to check these test/settings as i'm not having devices access and sitting remote in location. If i can get the troubleshooting steps to resolve this issue would be much appreciated, Thanks

Be the first to answer this question

Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login

Share

 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ