PENDING adsysdis.log shows The agent does not need to run now

[David S.]

Our Active Directory System Discovery hasn't worked in over a year. Looking at the adsysdis.log I see that it's reporting "The agent does not need to run now, therefore exit."

Any insight as to what to check would be appreciated.

Thanks,

Anonymized and truncated log:
** Service Thread is starting **
Connecting to site server's (\\***.***.***) registry
Inbox source is local on ***.***.***
Component setting of ACTIVE was specified in the site control file.
Removing redundant containers and validating them...
!!!!Valid Search Scope Name: LDAP://DC=***,DC=*** Search Path: LDAP://DC=***,DC=*** IsValidPath: TRUE
!!!!Valid Search Scope Name: LDAP://DC=***,DC=***,DC=int Search Path: LDAP://DC=***,DC=***,DC=*** IsValidPath: TRUE
Current time is Mon Aug 12 09:15:01 2024 (local time).
Last Run time is Mon Jun 26 07:55:01 2023 (local time).
The agent does not need to run now, therefore exit.
*** Shutting Down ************************

 

[Prajwal Desai]

Do you see any errors or error codes that might help here with troubleshooting?

 

[David S.]

The adsysdis.log has no errors. I haven't noticed any other errors either. Not sure what other logs to check for errors.

We only recently discovered this issue when we noticed that devices were showing outdated Last Logon dates. Which led us to the adsysdis.log and the realization that it hasn't run since last June.

 

[Prajwal Desai]

Do you see the same lines in the adsysdis.log if you manually trigger the system discovery method. We need to determine whether the discovery method can run and if yes, then why is it not running as per the schedule.

 

[David S.]

Yes, selecting Run Full Discovery Now results in the exact same log entries.

 

[Prajwal Desai]

Yes, selecting Run Full Discovery Now results in the exact same log entries.

See if this helps - https://forums.prajwaldesai.com/threads/sccm-ad-system-discovery-not-running.5130/

 

[David S.]

Site status is showing all green. Rebooting and re-running the discovery resulted in the same entries in adsysdis.log. Unsurprising as we reboot all our servers monthly for patching so it has reboot multiple times since it stopped actually running.