kurthv
asked on
SCCM error in SMS_AS_SYSTEM_DISCOVERY_AGENT - no DDR generated
In our SCCM installation we are getting the following error in the SMS_AD_SYSTEM_DISCOVERY_AG ENT logs:
"SMS Active Directory System Discovery Agent reported errors for 34 objects. DDR's were generated for 0 objects that had errors while reading non-critical properties. DDR's were not generated for 34 objects that had errors while reading critical properties."
In fact we are missing quite a few PCs in the ALL SYSTEMS collection so we think this is related to this error. Can anyone please advise how to investigate and solve this? Is it possible to get these 34 objects listed where the error occured?
Many thanks!
"SMS Active Directory System Discovery Agent reported errors for 34 objects. DDR's were generated for 0 objects that had errors while reading non-critical properties. DDR's were not generated for 34 objects that had errors while reading critical properties."
In fact we are missing quite a few PCs in the ALL SYSTEMS collection so we think this is related to this error. Can anyone please advise how to investigate and solve this? Is it possible to get these 34 objects listed where the error occured?
Many thanks!
computer account*
ASKER
Yes, I just doublechecked, the Full control is set as described in the article.
Take a look at adsysdis.log under %systemroot%\SMS\logs. Post any errors from that log here.
ASKER
I cannot find this log, the path does not exist. I will ask our admin who installed all this, maybe he knows...
Or do a search for the file. It could be on a different drive or in a different folder.
ASKER
Yes, I did a search but it was not found. There is a folder "Program files\SMS_CCM\Logs" but the file adsysdis.log is not in there... :-(
I think SMS_CCM is the SMS client folder, there should be just a "SMS" folder somewhere...
ASKER
Ok, we found the log after all... ;-)
Here is an extract:
GetIPAddr - Host not found resolving FQDN "testxp1.TEST.local". $$<SMS_AD_SYSTEM_DISCOVERY _AGENT><Fr i Feb 06 12:30:05.009 2009 W. Europe Standard Time><thread=64376 (0xFB78)>
GetIPAddr - Retry with system name "TESTXP1"... $$<SMS_AD_SYSTEM_DISCOVERY _AGENT><Fr i Feb 06 12:30:05.009 2009 W. Europe Standard Time><thread=64376 (0xFB78)>
GetIPAddr - getaddrinfo() for "TESTXP1" failed with error code 11001. $$<SMS_AD_SYSTEM_DISCOVERY _AGENT><Fr i Feb 06 12:30:07.561 2009 W. Europe Standard Time><thread=64376 (0xFB78)>
ERROR: Machine TESTXP1 is offline or invalid.~ $$<SMS_AD_SYSTEM_DISCOVERY _AGENT><Fr i Feb 06 12:30:07.564 2009 W. Europe Standard Time><thread=64376 (0xFB78)>
ERROR: CADSource::ProcessSystemIn fo: Failed to get IP Address for the system.~ $$<SMS_AD_SYSTEM_DISCOVERY _AGENT><Fr i Feb 06 12:30:07.564 2009 W. Europe Standard Time><thread=64376 (0xFB78)>
ERROR: Failed to generate system information.~
I think we are having problems with DNS, we are looking into this at the moment, but the admins for those machines are 9 hours behind our time, so we need to wait for answers...
Here is an extract:
GetIPAddr - Host not found resolving FQDN "testxp1.TEST.local". $$<SMS_AD_SYSTEM_DISCOVERY
GetIPAddr - Retry with system name "TESTXP1"... $$<SMS_AD_SYSTEM_DISCOVERY
GetIPAddr - getaddrinfo() for "TESTXP1" failed with error code 11001. $$<SMS_AD_SYSTEM_DISCOVERY
ERROR: Machine TESTXP1 is offline or invalid.~ $$<SMS_AD_SYSTEM_DISCOVERY
ERROR: CADSource::ProcessSystemIn
ERROR: Failed to generate system information.~
I think we are having problems with DNS, we are looking into this at the moment, but the admins for those machines are 9 hours behind our time, so we need to wait for answers...
ASKER
No more comments on this?
We found out that those missing PCs need to have a different DNS name in the computer account for them to turn up in SCCM. But, this would mean we would need to edit each computer account. They are using a different DNS server and are not willing to change it for various reasons. If we change the DNS name to their DNS then it works (but we are still not able to install the client, but that's probably another issue...).
Any ideas how we can solve this without changing all the DNS names in the computer accounts?
We found out that those missing PCs need to have a different DNS name in the computer account for them to turn up in SCCM. But, this would mean we would need to edit each computer account. They are using a different DNS server and are not willing to change it for various reasons. If we change the DNS name to their DNS then it works (but we are still not able to install the client, but that's probably another issue...).
Any ideas how we can solve this without changing all the DNS names in the computer accounts?
You might want to post a cross "pointer" question into the Active Directory group to this question for more AD expertise. I tried to change the DNS name on a test computer account here in ADUC and was unsuccessful, so I have no idea what you mean by changing the DNS name of the computer accounts unless you mean the DNS record.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
http://techgurulive.com/20