Hi,
When you right-click a client in the console and look for the properties, do you see the AD informationn?
Maybe this post help you:
http://www.deploymenttech.com/index.php?option=com_content&view=article&id=241:creating-ou-based-collections&catid=34:blog&Itemid=1
What does adsysgrp.log says ? Check if the computers are already discovered by AD system discovery to get the OU details into DB bcz ad system group discovery will not discover does not discover new resources; it adds group information to previously discovered resources.
Can you try updating the collection membership and see if that gets ?
Do you see any warnings/errors messges under SMS_System_group discovery_agent ?
More info about AD system Group Discovery http://technet.microsoft.com/en-us/library/bb694071.aspx
Are you trying with qeury similar to below :
select SMS_R_SYSTEM.ResourceID,SMS_R_SYSTEM.ResourceType,SMS_R_SYSTEM.Name,SMS_R_SYSTEM.SMSUniqueIdentifier,
SMS_R_SYSTEM.ResourceDomainORWorkgroup,SMS_R_SYSTEM.Client from SMS_R_System
where SMS_R_System.SystemOUName ="ESKONR.COM/COMPUTERS"
If all above doesnt help ,take a look this thread might help you http://social.technet.microsoft.com/Forums/en-US/configmgrgeneral/thread/886b77db-796c-4813-9231-f8f495fc036
yes the systems are already discovered within SCCM but there is no OU properties within the system properties. i have updated the collection membership many times with no result and there are no warnings/errors in the system status/site status. i have tried manually inputting the sql querry and used the wizard but nothing shows up in the new collection.
would extending the AD schema after installing SCCM cause this problem?
I would either force discovery to run as soon as possible or run back through the logs. I have seen where it took several passes to grab all the OUs. It took 2 days to pull them all in.
did you check adsysgrp.log ? it should have some info what has been discovered .
Hi,
You may refer to the following steps to check:
1. Confirmed that the AD System Discovery and AD System Group Discovery methods were enabled.
2. Next make sure the specific OU is listed under Active Directory containers. If it is not, add it by clicking the New Active Directory Container icon (yellow star). Select Custom LDAP or GC query, then click the Browse button and browse to the OU.
Alternatively, you can just choose the root of your domain, and use enable the Recursive Search option checkbox.
Regards,
Sabrina
here is an excerpt from the latest adsysgrp.log i dont see any errors.
** Service Thread is starting **~ $$<SMS_AD_SYSTEM_GROUP_DISCOVERY_AGENT><Thu Apr 07 09:15:00.772 2011 Pacific Daylight Time><thread=2688 (0xA80)>
INFO: Component setting of ACTIVE was specified in the site control file.~ $$<SMS_AD_SYSTEM_GROUP_DISCOVERY_AGENT><Thu Apr 07 09:15:01.786 2011 Pacific Daylight Time><thread=2688 (0xA80)>
INFO: Removing redundant containers and validating them...~ $$<SMS_AD_SYSTEM_GROUP_DISCOVERY_AGENT><Thu Apr 07 09:15:01.786 2011 Pacific Daylight Time><thread=2688 (0xA80)>
The Run Count value in the site control file is 16.~ $$<SMS_AD_SYSTEM_GROUP_DISCOVERY_AGENT><Thu Apr 07 09:15:01.786 2011 Pacific Daylight Time><thread=2688 (0xA80)>
The Schedule token value in the site control file is 000120000010A000.~ $$<SMS_AD_SYSTEM_GROUP_DISCOVERY_AGENT><Thu Apr 07 09:15:01.786 2011 Pacific Daylight Time><thread=2688 (0xA80)>
Incremental synchronization is enabled.~ $$<SMS_AD_SYSTEM_GROUP_DISCOVERY_AGENT><Thu Apr 07 09:15:01.786 2011 Pacific Daylight Time><thread=2688 (0xA80)>
The Full Synchronization Schedule token value in the site control file is 0001170000500008.~ $$<SMS_AD_SYSTEM_GROUP_DISCOVERY_AGENT><Thu Apr 07 09:15:01.786 2011 Pacific Daylight Time><thread=2688 (0xA80)>
Optional attributes count = 0 $$<SMS_AD_SYSTEM_GROUP_DISCOVERY_AGENT><Thu Apr 07 09:15:01.786 2011 Pacific Daylight Time><thread=2688 (0xA80)>
!!!!Valid AD container 0: LDAP://DC=DOMAIN,DC=CC~ $$<SMS_AD_SYSTEM_GROUP_DISCOVERY_AGENT><Thu Apr 07 09:15:01.786 2011 Pacific Daylight Time><thread=2688 (0xA80)>
~Current time is 4/7/2011 9:15:01 AM Pacific Daylight Time $$<SMS_AD_SYSTEM_GROUP_DISCOVERY_AGENT><Thu Apr 07 09:15:01.802 2011 Pacific Daylight Time><thread=2688 (0xA80)>
~Last Run time is 4/7/2011 9:10:01 AM Pacific Daylight Time $$<SMS_AD_SYSTEM_GROUP_DISCOVERY_AGENT><Thu Apr 07 09:15:01.802 2011 Pacific Daylight Time><thread=2688 (0xA80)>
~Next Run time is 4/7/2011 9:15:00 AM Pacific Daylight Time $$<SMS_AD_SYSTEM_GROUP_DISCOVERY_AGENT><Thu Apr 07 09:15:01.802 2011 Pacific Daylight Time><thread=2688 (0xA80)>
It is time to run on the schedule.~ $$<SMS_AD_SYSTEM_GROUP_DISCOVERY_AGENT><Thu Apr 07 09:15:01.802 2011 Pacific Daylight Time><thread=2688 (0xA80)>
Starting the data discovery.~ $$<SMS_AD_SYSTEM_GROUP_DISCOVERY_AGENT><Thu Apr 07 09:15:01.802 2011 Pacific Daylight Time><thread=2688 (0xA80)>
INFO: Number of Assigned Systems found = 0.~ $$<SMS_AD_SYSTEM_GROUP_DISCOVERY_AGENT><Thu Apr 07 09:15:01.802 2011 Pacific Daylight Time><thread=2688 (0xA80)>
INFO: There are no assigned systems to this site or its child secondary sites. Ending Discovery... $$<SMS_AD_SYSTEM_GROUP_DISCOVERY_AGENT><Thu Apr 07 09:15:01.802 2011 Pacific Daylight Time><thread=2688 (0xA80)>
*** Shutting Down ************************~ $$<SMS_AD_SYSTEM_GROUP_DISCOVERY_AGENT><Thu Apr 07 09:15:01.802 2011 Pacific Daylight Time><thread=2688 (0xA80)>
Hi Sabrina,
1. both AD system Discovery and AD system Group Discovery are turned on with recursive set to yes and group set to included
2. i have added both the root domain and the ou in question to the AD system group discovery and AD system discovery.
i dont see any errors in the adsysgrp.log.
Yes, I know this is an old post, but Im trying to clean them up.
Did you solve this problem, if so what was the solution?
Since no one has answer this post, I recommend opening a support case with CSS as they can work with you to solve this problem.
This topic is archived. No further replies will be accepted.
Other recent topics
