Hello, AD System Discovery is not working, it has stuck on one machine to resolve IP of host.....discover is not running from last three... Below is adsysdis.log Warning.... WARN: Could not get property (domain) for system (0x80005010) SMS_AD_SYSTEM_DISCOVERY_AGENT 13-8-2010 22:12:44 3420 (0x0D5C) GetIPAddr - Host not found resolving FQDN "ABC73613.corp.abc.com". SMS_AD_SYSTEM_DISCOVERY_AGENT 13-8-2010 22:12:44 3420 (0x0D5C) GetIPAddr - Retry with system name "ABC73613"... SMS_AD_SYSTEM_DISCOVERY_AGENT 13-8-2010 22:12:44 3420 (0x0D5C) Above machine is pinging and resolving IP address....properly.. Please share your iputs/answere/comments....

Can you ping the machine from the SCCM server using the FQDN ABC73613.corp.abc.com? If not, can you ping it by its netbios name from the SCCM server?

It's required that the Site Server can resolve the host name of the discovered resources. Check DNS and also common name resultion issues.Kent Agerlund | My blogs: http://blog.coretech.dk/author/kea/ and http://scug.dk/ | Twitter @Agerlund | Linkedin: /kentagerlund

Yes..It is Ping with FQDN also......

The error means E_ADS_COLUMN_NOT_SET The specified column in the directory was not set. Also check the flowchart as well... http://technet.microsoft.com/en-us/library/bb932137.aspxAnoop C Nair - This posting is provided "AS IS" with no warranties or guarantees, and confers no rights. |Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

True....It Ping with hostname, FQDN Name, and resolving...IP address of machine.... Howerver it stucked in same machine...not processing.....

Hello Anoop, How we can set, E_ADS_COLUMN_NOT_SET where this option is?? Please do let me know.....

See, the thread below for more details... http://social.technet.microsoft.com/Forums/en-US/configmgradminconsole/thread/a4fc27d8-542c-45a7-a1e5-4c74e85c7a8b#46a314f4-e6c9-454b-abb6-947c99dbd63b Anoop C Nair - This posting is provided "AS IS" with no warranties or guarantees, and confers no rights. |Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

What you have highlighted looks to me like two completely different issues: 1- WARN: Could not get property (domain) for system (0x80005010) SMS_AD_SYSTEM_DISCOVERY_AGENT 13-8-2010 22:12:44 3420 (0x0D5C) This is, as mentioned in the thread An00p gave the link to, a known bug. However, it has nothing to do with not being able to contact the workstations. It is a warning, not an error. It is something it will get from AD, not from the workstation. We're getting that on our live environment and AD System discovery runs fine regardless. In other words, ignore it. 2-GetIPAddr - Host not found resolving FQDN "ABC73613.corp.abc.com". SMS_AD_SYSTEM_DISCOVERY_AGENT 13-8-2010 22:12:44 3420 (0x0D5C) GetIPAddr - Retry with system name "ABC73613"... SMS_AD_SYSTEM_DISCOVERY_AGENT 13-8-2010 22:12:44 3420 (0x0D5C) This is your real issue and why you can't discover the machine. If it can't resolve the workstation name, it will not generate a DDR for it. With that in mind, let's concentrate on the second issue and ignore the first. In your previous post you said: True....It Ping with hostname, FQDN Name, and resolving...IP address of machine.... Howerver it stucked in same machine...not processing..... What do you mean by that exactly? Here is what I would suggest: manually edit the hosts file of the SCCM server to say ABC73613.corp.abc.com resolves to... whatever it resolves to. Then do another AD System Discovery and see if you still get the same results. Anything on the hosts file will take precedence over DNS, cached DNS, WINS, etc, so it might be the best place to start. When editing the hosts file, ensure that you add an entry for the machine exactly as it appears in the adsysdis.log (as you might have Disjoint Namespaces)

Thanks , it resolves..... Once I have given the LDAP path of above machine, it discovered on console.... However nothing update came on adsysdis.log file.........still showing same machine...... Log file is not updates.......

Thanks , it resolves..... Once I have given the LDAP path of above machine, it discovered on console.... However nothing update came on adsysdis.log file.........still showing same machine...... Log file is not updates....... What was resolved? How was it resolved?

run the AD discovery cycle and monitor the log file.//Eswar Koneti @ www.eskonr.com

Hello It resolves IP address, when I had given LDAP Path of above machine(ABC73613.corp.abc.com ), it discovered in console. Also, gave LDAP path othe problematic machine, it does not discovered Log file not updtaes: Means adsysdis.log is not updates as it stuck in below lines..couple of days..not showing today's date on log file. WARN: Could not get property (domain) for system (0x80005010) SMS_AD_SYSTEM_DISCOVERY_AGENT 13-8-2010 22:12:44 3420 (0x0D5C) GetIPAddr - Host not found resolving FQDN "ABC73613.corp.abc.com". SMS_AD_SYSTEM_DISCOVERY_AGENT 13-8-2010 22:12:44 3420 (0x0D5C) GetIPAddr - Retry with system name "ABC73613"... SMS_AD_SYSTEM_DISCOVERY_AGENT 13-8-2010 22:12:44 3420 (0x0D5C)

As said, nothing is coming in log file, it stuck on below lines...after that no progress... WARN: Could not get property (domain) for system (0x80005010) SMS_AD_SYSTEM_DISCOVERY_AGENT 13-8-2010 22:12:44 3420 (0x0D5C) GetIPAddr - Host not found resolving FQDN "ABC73613.corp.abc.com". SMS_AD_SYSTEM_DISCOVERY_AGENT 13-8-2010 22:12:44 3420 (0x0D5C) GetIPAddr - Retry with system name "ABC73613"... SMS_AD_SYSTEM_DISCOVERY_AGENT 13-8-2010 22:12:44 3420 (0x0D5C)

Have you checked to see if the log is corurpted and rendering incorrectly in trace?

Hello Marshal.... It seems , corrupreted, but how I can check it has corrupted......in Crash dump it is showing very old logs... Please do let me know..

Be honest with you, looking at these ConfigMgr logs in Notepad makes them look a little crazy :-) I only know one person that can make sense of them "on the fly" and he knows who he is ;-) Best thing to do, is rename the log file so you have a copy, then rerun the discovery method to generate a new log ... open in trace, see if you get any further. I'm sure I've heard of this happening before, a few years ago. Might be worth searching these very forums if you're stuck.

Thanks Marshall.... Yes...new Log generaed and it saying that ..... and adsysdis.log given below error for this machine... ERROR: System ABC77765 is a unsupported operating system, unsupported version, or malformed AD entry. Reported system type is: (). what is unsuppoter operating sysytem? Malformed AD entry..? I have rejoined the machine to domain, still getting same error Could be problem here..any tweak..pls do let me know.......... I am looking log files on trace32...not on notepad :) N

check out this thread for the problenm on unsupported operating system with some interesting things http://social.technet.microsoft.com/Forums/en/configmgrgeneral/thread/a6be8c13-334d-4a93-9141-d55d6e5bf441 //Eswar Koneti @ www.eskonr.com

Already wnt throght...not much help...... as only on error: is getting i. not a warning...probabaly due this machine is not coming on console.... ERROR: System ABC77765 is a unsupported operating system, unsupported version, or malformed AD entry. Reported system type is: (). what is unsuppoter operating sysytem? Malformed AD entry..? I have rejoined the machine to domain, still getting same error

Hello - Try to delete the system account and recreate the same? Wait for AD replication to complete the process. Then try running discovery. Also, you can compare the attributes of other system account with ABC77765 using ADSIedit. Anoop C Nair - This posting is provided "AS IS" with no warranties or guarantees, and confers no rights. |Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

If it's just getting stuck on that one system, and you cannot recreate it easily, then set the permissions on that computer account object in A/D, so that the site servers computer account is denied access to it. A/D Discovery should continue about its business of scanning the LDAP path you specified. Not a solution really, more a work-around.