As you move to Windows 7, you might be tempted to separate users and workstations based on the fact that they are migrated already or still run a previous OS.

As you map this in your environment you sometimes will end up with a separate main OU for users / computers and Sub-OUs that are exactly similar to your previous implemenation:

Note that when you do this Sccm will not scan the sub-folders.

see http://support.microsoft.com/kb/983514/en-us

Extract: <

Consider the following scenario:

  • You enable the Active Directory System Discovery method or the
    Active Directory User Discovery method on a System Center Configuration
    Manager 2007 Service Pack 2 (SP2) site server.
  • You add the paths of some organizational unit (OU) to the Active Directory
    containers list. The Recursive search option is
    enabled.
  • Some OUs that are in the container list and some related child OUs share the
    same common name (CN).

In this scenario, some of these OUs that share
the same CN are not discovered when the Active Directory System Discovery
method or the Active Directory User Discovery method runs.

For
example, the following OUs are added to the Active Directory containers list.

  • OU1
  • TestOU1
  • OU2

The “OU1” OU has the following child OUs:

  • TestOU1
  • TestOU4
  • TestOU5

The “OU2” OU has the following child OUs:

  • TestOU1
  • TestOU6

In this example, the “TestOU1” OU occurs three times.
However, only one “TestOU1” OU is discovered when the Active Directory System
Discovery method or the Active Directory User Discovery method runs.

>

One way to effectively check you don’t have the problem is to open the Ad*dis.log files and look for entries starting with !!!!Valid AD container

Compare that to what you have configured in your Discovery Methods. It should match. If it does not, apply the hotfix and you will see that it solves the problem and missing entries will appear at next discovery.

Advertisements