Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

The second Search paths may not discovered when you enable any Active Directory discovery method that runs on a System Center Configuration Manager 2007 SP2 site server


View products that this article applies to.

Symptoms

Consider the following scenario:
  • You enable one of the following Active Directory discovery method on a System Center Configuration Manager 2007 Service Pack 2 (SP2) site server:
  • Active Directory System Discovery
    Active Directory User Discovery

    Acitve Directory System Group Discovery

    Active Directory Security Group Discovery
  • You add a search path to the Active Directory OUslist.
  • You add a second search path to the Active Directory OUslist. This search path contains the string of the first search path you just added.
In this scenario, the second search path is not discovered when one of aboe Active Directory Discovery method process runs.

For example, you create two Organizational Units (OUs) under an OU which is named “Organization Computers”, and then you name the OUs "abc" and "abcd." You add a search path of domain\Organization Computers\abc for the first OU, and then you add a search path of domain\Organization Computers\abcd for the second OU. In this scenario, the second OU is not discovered when the Active Directory System Discovery process or the Active Directory User Discovery process runs.

↑ Back to the top


Resolution

Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing the problem described in this article. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site: Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Prerequisites

To apply this hotfix, you must have System Center Configuration Manager 2007 SP2 installed on the computer.

Installation instructions

Note The following hotfix package can be installed on a System Center Configuration Manager 2007 SP2 site server that is running an x86-based version of an operating system or an x64-based version of an operating system:
SCCM2007-SP2-KB978757-X86-ENU.msi

Restart requirement

You do not have to restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace a previously released hotfix.

File information

The English (United States) version of this hotfix installs files that have the attributes that are listed in the following tables. The dates and the times for these files are listed in Coordinated Universal Time (UTC). The dates and the times for these files on your local computer are displayed in your local time together with your current daylight saving time (DST) bias. Additionally, the dates and the times may change when you perform certain operations on the files.
System Center Configuration Manager 2007 file information notes
File nameFile versionFile sizeDateTimePlatform
Adsgdis.dll4.0.6487.211439,78401-Feb-201010:05x86
Adsource.dll4.0.6487.2114126,82401-Feb-201010:05x86
Adsysdis.dll4.0.6487.211442,34401-Feb-201010:05x86
Adsysgrp.dll4.0.6487.211439,78401-Feb-201010:05x86
Adusrdis.dll4.0.6487.211439,78401-Feb-201010:05x86

↑ Back to the top


Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

↑ Back to the top


More Information

To add a search path for Active Directory System Discovery or Active Directory User Discovery, follow these steps:
  1. Open the Configuration Manager Console window.
  2. Locate the following item:
    Site Database\Site Management\<site name>\Site Settings\Discovery Methods
  3. Double-click the Active Directory System Discovery or the Active Directory User Discovery item in the right-side panel to open its Properties dialog box.
  4. On the General tab, click to select the Enable Active Directory System Discovery or the Enable Active Directory User Discovery check box if it is not selected.
  5. Add a new container to the Active Directory containers list.
For more information about how to configure the Active Directory System Discovery method, visit the following Microsoft website:

For more information about how to configure the Active Directory User Discovery method, visit the following Microsoft website:

For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
824684 Description of the standard terminology that is used to describe Microsoft software updates

↑ Back to the top


Keywords: kbexpertiseinter, kbautohotfix, kbfix, kbsurveynew, kbqfe, kbhotfixserver, kb

↑ Back to the top

Article Info
Article ID : 978757
Revision : 1
Created on : 1/7/2017
Published on : 10/28/2011
Exists online : False
Views : 235