active directory discovery
I see that sometimes. I don't ever worry about it. As long as you know the site server has read access to all of your OU's you should be ok. It could be the computer account is in AD but doesnt' resolve to an IP.John Marcum | http://myitforum.com/cs2/blogs/jmarcum/|
June 27th, 2012 2:05pm
heello,
when im trying to discover machines by active directory discovery i see this error:
SMS Active Directory System Discovery Agent reported errors for 272 objects. DDR's were generated for 0 objects that had errors while reading non-critical properties. DDR's were not generated
for 272 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 discovered 213 but the others i dont see it
any idea?
thanks
Free Windows Admin Tool Kit Click here and download it now
June 27th, 2012 2:07pm
I see that sometimes. I don't ever worry about it. As long as you know the site server has read access to all of your OU's you should be ok. It could be the computer account is in AD but doesnt' resolve to an IP.John Marcum | http://myitforum.com/cs2/blogs/jmarcum/|
June 27th, 2012 2:25pm
Have you reviewed adsysdis.log for specific systems that you expect to be discovered but have not been?Jason | http://blog.configmgrftw.com | Twitter @JasonSandys
Free Windows Admin Tool Kit Click here and download it now
June 28th, 2012 4:27am
Have you reviewed adsysdis.log for specific systems that you expect to be discovered but have not been?Jason | http://blog.configmgrftw.com | Twitter @JasonSandys
June 28th, 2012 4:47am
Many of this kind of issues are caused by missing DNS records. Please check DNS server and see if the records for the lost computers are present.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.
Free Windows Admin Tool Kit Click here and download it now
June 28th, 2012 5:37am
Many of this kind of issues are caused by missing DNS records. Please check DNS server and see if the records for the lost computers are present.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.
June 28th, 2012 5:57am
the computers that dont bring me are because they dont resolve an IP address.
thanks!!
So if do discovery by network discovery will be the same?
because network discovery only bring me the objects that have an IP?
thanks againnn
Free Windows Admin Tool Kit Click here and download it now
July 1st, 2012 5:48am
Yuck on the network discovery -- it will discover "everything" including printers, switches, and other devices that are no manageable by ConfigMgr.
Is you intention to manage these systems that are not being discovered? If so, using a startup script to install the client agent on them may be a better path to follow as this does not rely on discovery.Jason | http://blog.configmgrftw.com | Twitter @JasonSandys
July 1st, 2012 5:51am