Active Directory System Discovery not working due to DNS, can I force it to use NetBIOS?
Hopefully this is the correct forum for this question.
I have a new SCCM (SP2 not R2) install and I am trying to get the list of computers in the Directory so that I may push the client to all my systems. Right now Only 24 systems show up in my All Systems group. I have 900 or so computers in the domain so this
is a little odd.
The Error i get in the Status detail is :
SMS Active Directory System Discovery Agent reported errors for 992 objects. DDR's were generated for 0 objects that had errors while reading non-critical properties. DDR's were not generated for 992 objects that had errors while reading critical properties.
Possible cause: The SMS Service might not have access to some properties of this object. The container specified might not have the properties available.
Solution: Please verify the Active Directory schema for properties that are not replicated or locked. Refer to the discovery logs for more information.
I look in the adsysdis.log file and I see:
INFO: discovered object with ADsPath = 'LDAP://dc.A.B.edu/CN=MACHINE1,CN=Computers,DC=A,DC=B,DC=edu'~
WARN: Could not get property (domain) for system (0x80005010)~ $$<SMS_AD_SYSTEM_DISCOVERY_AGENT><Wed Jul 14 11:33:56.538 2010 Eastern Daylight Time><thread=4872 (0x1308)>
ERROR: GetIPAddr - getaddrinfo() for 'MACHINE1.A.B.edu' failed with error code 11004.
ERROR: Machine MACHINE1 is offline or invalid.~
WARN: CADSource::ProcessSystemInfo: Failed to get IP Address for the system.~ $$<SMS_AD_SYSTEM_DISCOVERY_AGENT>
I am in an academic setting and unfortunately do not have control over our campus-wide DNS server. Also the full machine name is different from it's name in DNS. so in the above the machine has a netbois name of machine1, a full machine name of machine1.A.B.edu,
but a DNS name of 1-2.dhcp.B.edu
Can I force SCCM to lookup machine info using the NetBIOS name?
July 14th, 2010 7:01pm
What OS is your site server?
I have recently uncovered a known bug concerning discovery and disjoint dns namespace that happens when ConfigMgr is installed on 2008 R2; essentially, the DNS suffix search order is not honored.
I don't know of any good work-arounds though and calling CSS is probably the best path for you to take.Jason | http://myitforum.com/cs2/blogs/jsandys | http://blogs.catapultsystems.com/jsandys/default.aspx | Twitter @JasonSandys
Free Windows Admin Tool Kit Click here and download it now
July 14th, 2010 7:30pm
Interesting, the site server is 2008 R2. Good to know.
July 14th, 2010 9:54pm
There is no correlation between machine name and dns entry.
Sorry but you lost me. Is it possible to open a command prompt on the SCCM server and enter ping machinename and get a reply by resolving machinename to an IP in DNS? If not then AD System Discovery will not work. You will have to use another discovery method.
John Marcum | http://myitforum.com/cs2/blogs/jmarcum |
Free Windows Admin Tool Kit Click here and download it now
July 14th, 2010 10:06pm