Cannot discover some computers in AD
Hi, We are discovering the computers by AD system discovery. Most of the computers are discovered properly, however, some of them cannot be discovered though they have a dns record. In adsysdis.log the computer names or ip cannot be seen. Boundaries are correct. Where should we look?Systems Engineer
June 29th, 2010 9:24am

hi, check the adsysdis.log file on the site server. If you find any errors, please post them in your reply.Kent Agerlund | http://scug.dk/members/Agerlund/default.aspx | The Danish community for System Center products
Free Windows Admin Tool Kit Click here and download it now
June 29th, 2010 9:35am

Here is a part of the log file. Note that none of the computers that are not being discovered is found in the log, searching for it by name of IP. System DR-DITE-PC5 is accessible. IP address is 192.168.11.121. SMS_AD_SYSTEM_DISCOVERY_AGENT 29/06/2010 10:21:59 AM 6180 (0x1824) System DKARAM-10-124 is accessible. IP address is 192.168.10.124. SMS_AD_SYSTEM_DISCOVERY_AGENT 29/06/2010 10:21:59 AM 6180 (0x1824) System MATALLAH-12-67 is accessible. IP address is 192.168.12.67. SMS_AD_SYSTEM_DISCOVERY_AGENT 29/06/2010 10:21:59 AM 6180 (0x1824) System MRDEMIAN-10-123 is accessible. IP address is 192.168.10.123. SMS_AD_SYSTEM_DISCOVERY_AGENT 29/06/2010 10:21:59 AM 6180 (0x1824) System EJAOUDE-10-121 is accessible. IP address is 192.168.10.121. SMS_AD_SYSTEM_DISCOVERY_AGENT 29/06/2010 10:21:59 AM 6180 (0x1824) System RNOUJEIM-10-122 is accessible. IP address is 192.168.10.122. SMS_AD_SYSTEM_DISCOVERY_AGENT 29/06/2010 10:21:59 AM 6180 (0x1824) System JESFEIR-12-160 is accessible. IP address is 192.168.12.160. SMS_AD_SYSTEM_DISCOVERY_AGENT 29/06/2010 10:21:59 AM 6180 (0x1824) GetIPAddr - Host not found resolving FQDN "Mchehibr-10-129.CreditBank.com.lb". SMS_AD_SYSTEM_DISCOVERY_AGENT 29/06/2010 10:21:59 AM 6180 (0x1824) GetIPAddr - Retry with system name "MCHEHIBR-10-129"... SMS_AD_SYSTEM_DISCOVERY_AGENT 29/06/2010 10:21:59 AM 6180 (0x1824) GetIPAddr - getaddrinfo() for "MCHEHIBR-10-129" failed with error code 11001. SMS_AD_SYSTEM_DISCOVERY_AGENT 29/06/2010 10:22:06 AM 6180 (0x1824) ERROR: Machine MCHEHIBR-10-129 is offline or invalid. SMS_AD_SYSTEM_DISCOVERY_AGENT 29/06/2010 10:22:06 AM 6180 (0x1824) ERROR: CADSource::ProcessSystemInfo: Failed to get IP Address for the system. SMS_AD_SYSTEM_DISCOVERY_AGENT 29/06/2010 10:22:06 AM 6180 (0x1824) ERROR: Failed to generate system information. SMS_AD_SYSTEM_DISCOVERY_AGENT 29/06/2010 10:22:06 AM 6180 (0x1824) System SAOUN-12-122 is accessible. IP address is 192.168.12.122. SMS_AD_SYSTEM_DISCOVERY_AGENT 29/06/2010 10:22:06 AM 6180 (0x1824) System VSALIBA-10-137 is accessible. IP address is 192.168.10.137. SMS_AD_SYSTEM_DISCOVERY_AGENT 29/06/2010 10:22:06 AM 6180 (0x1824) System EAJAOUDE-10-121 is accessible. IP address is 192.168.10.121. SMS_AD_SYSTEM_DISCOVERY_AGENT 29/06/2010 10:22:06 AM 6180 (0x1824) System MCHIBAR-10-129 is accessible. IP address is 192.168.15.90. SMS_AD_SYSTEM_DISCOVERY_AGENT 29/06/2010 10:22:06 AM 6180 (0x1824) System EKOTEIT-10-120 is accessible. IP address is 192.168.12.143. SMS_AD_SYSTEM_DISCOVERY_AGENT 29/06/2010 10:22:06 AM 6180 (0x1824) System ANGELINI-12-66 is accessible. IP address is 192.168.12.66. SMS_AD_SYSTEM_DISCOVERY_AGENT 29/06/2010 10:22:06 AM 6180 (0x1824) DsAddressToSiteNames Failed . Error: 1722 SMS_AD_SYSTEM_DISCOVERY_AGENT 29/06/2010 10:22:16 AM 6180 (0x1824) ERROR: Unable to get AD site name for system ANGELINI-12-66, DS Error=1722. Win32 Error=0 SMS_AD_SYSTEM_DISCOVERY_AGENT 29/06/2010 10:22:16 AM 6180 (0x1824) DDR was written for system 'DISASTER11' - C:\Program Files\Microsoft Configuration Manager\inboxes\auth\ddm.box\adsxixav.DDR at 6/29/2010 10:20:37. SMS_AD_SYSTEM_DISCOVERY_AGENT 29/06/2010 10:22:16 AM 6180 (0x1824) DDR was written for system 'DISASTER1' - C:\Program Files\Microsoft Configuration Manager\inboxes\auth\ddm.box\adsqwnn8.DDR at 6/29/2010 10:20:37. SMS_AD_SYSTEM_DISCOVERY_AGENT 29/06/2010 10:22:16 AM 6180 (0x1824) DDR was written for system 'TRAINEE2' - C:\Program Files\Microsoft Configuration Manager\inboxes\auth\ddm.box\ads5bh01.DDR at 6/29/2010 10:20:37. SMS_AD_SYSTEM_DISCOVERY_AGENT 29/06/2010 10:22:16 AM 6180 (0x1824) DDR was written for system 'DISASTER3' - C:\Program Files\Microsoft Configuration Manager\inboxes\auth\ddm.box\adsk1gr8.DDR at 6/29/2010 10:20:37. SMS_AD_SYSTEM_DISCOVERY_AGENT 29/06/2010 10:22:16 AM 6180 (0x1824) DDR was written for system 'DR-SITE-PC-127' - C:\Program Files\Microsoft Configuration Manager\inboxes\auth\ddm.box\adsbgufp.DDR at 6/29/2010 10:20:37. SMS_AD_SYSTEM_DISCOVERY_AGENT 29/06/2010 10:22:16 AM 6180 (0x1824) DDR was written for system 'MBKARAM-10-204' - C:\Program Files\Microsoft Configuration Manager\inboxes\auth\ddm.box\ads1p8qi.DDR at 6/29/2010 10:20:37. SMS_AD_SYSTEM_DISCOVERY_AGENT 29/06/2010 10:22:16 AM 6180 (0x1824) DDR was written for system 'RCHACOUR-10-214' - C:\Program Files\Microsoft Configuration Manager\inboxes\auth\ddm.box\ads9xb61.DDR at 6/29/2010 10:20:37. SMS_AD_SYSTEM_DISCOVERY_AGENT 29/06/2010 10:22:16 AM 6180 (0x1824)Systems Engineer
June 29th, 2010 11:05am

We are discovering the computers by AD system discovery Are those computer accounts disabled? How is discovery set up (scope? Domain? OU)?
Free Windows Admin Tool Kit Click here and download it now
June 29th, 2010 11:22am

No the computers are enabled and working. The discovery is set up by OUs.Systems Engineer
June 29th, 2010 11:29am

Hi, can you ping the computers. the error in the log file is the same error I have seen when we couldn't ping the computer from the site server. It's the site server that must be able to resolve the host name of the client.Kent Agerlund | http://scug.dk/members/Agerlund/default.aspx | The Danish community for System Center products
Free Windows Admin Tool Kit Click here and download it now
June 29th, 2010 11:36am

yes we can ping the computer's host name from the site server.Systems Engineer
June 29th, 2010 12:19pm

No the computers are enabled and working. The discovery is set up by OUs. Just to double check: are those computers in one of those OUs?
Free Windows Admin Tool Kit Click here and download it now
June 29th, 2010 12:42pm

Does the site servers computer account have read access to the OU where the computers are located? John Marcum | http://myitforum.com/cs2/blogs/jmarcum |
June 29th, 2010 3:01pm

My apology. After choosing "Local domain" as the container to discover from, the computers appeared. We double checked the OUs and there was a mistake. We added the OU and everything works fine now. Thank you for your time.Systems Engineer
Free Windows Admin Tool Kit Click here and download it now
June 29th, 2010 3:25pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics