We have problems with Active Directory Discovery. The problem is that it seems that ConfigMgr is not making any WINS requests for the computernames it finds. I can ping the NetBIOS names from the SCCM server without any issues, so the server itself has no problem with WINS resolution. Here is what an entry in adsysdis.log looks like: INFO: discovered object with ADsPath = 'LDAP://dc.whatever.se/CN=DNN287,OU=k204,OU=vlan,OU=employees,OU=computers,OU=resources,OU=lnu,DC=whatever,DC=se' SMS_AD_SYSTEM_DISCOVERY_AGENT 2010-06-11 08:40:08 20484 (0x5004) WARN: Could not get property (domain) for system (0x80005010) SMS_AD_SYSTEM_DISCOVERY_AGENT 2010-06-11 08:40:08 20484 (0x5004) ERROR: GetIPAddr - getaddrinfo() for 'DNN287.whatever.se' failed with error code 11004. SMS_AD_SYSTEM_DISCOVERY_AGENT 2010-06-11 08:40:10 20484 (0x5004) ERROR: Machine DNN287 is offline or invalid. SMS_AD_SYSTEM_DISCOVERY_AGENT 2010-06-11 08:40:10 20484 (0x5004) As you can see, it just tries to add "whatever.se" to the name. But the problem is that the clients is registered in DNS with different dns suffixes depending on the building it is located in, and we have 10-15 different suffixes. For example: the computername above (DNN287) is registred in DNS as DNN287.one.whatevertwo.se. Our DNS is BIND and not a Microsoft DNS... Our clients is in the same AD domain as the SCCM server... As a reference I found this thread: http://social.technet.microsoft.com/Forums/en-US/configmgrsetup/thread/75e6cfd9-dc72-4225-b88b-0390a15ad77b Which is the exact same problem. Our old SCCM 2007 R2, but on a Server 2003 worked with WINS resolution, but now, when we are using Server 2008, it stopped working. The resolution mentioned in the thread seems to work only with a Microsoft DNS...

Make sure the dns suffix (for the clients) is added to the Advanced TCP/IP settings on the site server. Make sure the the system DNN287 is active in Active Directory and not disabled. If it is disabled then the error above is true in that is cannot and will report a discovery record for it as it is disabled. Are you able to ping this system by Netbios name or by FQDN and by its IP Address? Is DNS Configured to utilize WINS? Is that functioning correctly? David Baur

So, I've run into a very similar issue at my current client (although we have a good work-around available). Via a few insider's, this is the result of a known bug that rears its ugly head in Server 2088 R2 only because of a TCP/IP stack redesign. There are no plans at this point to fix the bug for ConfigMgr though. If you cannot find another way to work-around the issue, please contact CSS.Jason | http://myitforum.com/cs2/blogs/jsandys | http://blogs.catapultsystems.com/jsandys/default.aspx | Twitter @JasonSandys

Not sure if you saw this (or maybe your call to css prompted it) but Microsoft did release a hotfix a few weeks ago for this issue: http://support.microsoft.com/default.aspx?scid=kb;en-us;2345551&sd=rss&spid=12769.Jason | http://myitforum.com/cs2/blogs/jsandys | http://blogs.catapultsystems.com/jsandys/default.aspx | Twitter @JasonSandys