Thursday, June 10, 2010

SCCM | Discover Another Trusted Domain

Here's the scenario. SCCM site server is located in DomainA.com and willing to discover DomainB.com, which is a trusted domain. Before we begin to configure the discovery methods, please make sure that the SCCM site server's account got the read permission in DomainB.com.

First, you need to configure the Discovery Methods which located under site settings.

Right click Active Directory System Group Discovery, select Properties.

Click on new, the yellow star.

Choose Custom LDAP or GC query, then key in your domain. For example, DomainB.com, LDAP://DC=DOMAINB,DC=COM

Click OK after you have done with the settings.

Then click on the Polling Schedule, tick the Run discovery as soon as possible, following by OK.

You have completed configure Active Directory System Group Discovery, repeat the same things on Active Directory System Discovery.

After you finished configured Active Directory System Discovery, you can update the collection membership  and refresh All Systems Collections. The computers on another domain should have listed out.
By at
Labels: , ,

10 comments:

  1. AnonymousApril 28, 2015 at 10:42 AM

    Hi Hau
    Hope you are doing well...

    I have the similar scenario.....need your help !!!!
    Unable to install the Clients to the Machines in Domain B (Second Domain in the forest)
    It seems to just copy the Files.
    Install the client only partially, Config Manager Applet is there in Control Panel.

    No Software Center installed and Machine Status ( Client = No ) in SCCM Console.

    Something stops the process in between.

    Please check the Log below :
    ————————————————

    Execute query exec [sp_IsMPAvailable] N’PO1′ SMS_CLIENT_CONFIG_MANAGER 27/04/2015 2:20:45 PM 16460 (0x404C)
    —> Trying the ‘best-shot’ account which worked for previous CCRs (index = 0x1) SMS_CLIENT_CONFIG_MANAGER 27/04/2015 2:20:45 PM 16460 (0x404C)
    —> Attempting to connect to administrative share ‘\\TestClient\admin$’ using account ‘Domain\admintest’ SMS_CLIENT_CONFIG_MANAGER 27/04/2015 2:20:45 PM 16460 (0x404C)
    —> The ‘best-shot’ account has now succeeded 12 times and failed 0 times. SMS_CLIENT_CONFIG_MANAGER 27/04/2015 2:20:45 PM 16460 (0x404C)
    —> Connected to administrative share on machine TestClient using account ‘Domain\admintest’ SMS_CLIENT_CONFIG_MANAGER 27/04/2015 2:20:45 PM 16460 (0x404C)
    —> Attempting to make IPC connection to share <\\TestClient\IPC$> SMS_CLIENT_CONFIG_MANAGER 27/04/2015 2:20:45 PM 16460 (0x404C)
    —> Searching for SMSClientInstall.* under ‘\\TestClient\admin$\’ SMS_CLIENT_CONFIG_MANAGER 27/04/2015 2:20:45 PM 16460 (0x404C)
    —> System OS version string “6.1.7601” converted to 6.10 SMS_CLIENT_CONFIG_MANAGER 27/04/2015 2:20:45 PM 16460 (0x404C)
    —> Unable to connect to WMI (root\ccm) on remote machine “TestClient”, error = 0x8004100e. SMS_CLIENT_CONFIG_MANAGER 27/04/2015 2:20:45 PM 16460 (0x404C)
    —> Creating \ VerifyingCopying exsistance of destination directory \\TestClient\admin$\ccmsetup. SMS_CLIENT_CONFIG_MANAGER 27/04/2015 2:20:45 PM 16460 (0x404C)
    —> Copying client files to \\TestClient\admin$\ccmsetup. SMS_CLIENT_CONFIG_MANAGER 27/04/2015 2:20:45 PM 16460 (0x404C)
    —> Copying file “C:\Program Files\Microsoft Configuration Manager\bin\I386\MobileClient.tcf” to “MobileClient.tcf” SMS_CLIENT_CONFIG_MANAGER 27/04/2015 2:20:45 PM 16460 (0x404C)
    —> Copying file “C:\Program Files\Microsoft Configuration Manager\bin\I386\ccmsetup.exe” to “ccmsetup.exe” SMS_CLIENT_CONFIG_MANAGER 27/04/2015 2:20:46 PM 16460 (0x404C)
    —> Created service “ccmsetup” on machine “TestClient”. SMS_CLIENT_CONFIG_MANAGER 27/04/2015 2:20:46 PM 16460 (0x404C)
    —> Started service “ccmsetup” on machine “TestClient”. SMS_CLIENT_CONFIG_MANAGER 27/04/2015 2:20:46 PM 16460 (0x404C)
    —> Deleting SMS Client Install Lock File ‘\\TestClient\admin$\SMSClientInstall.PO1′ SMS_CLIENT_CONFIG_MANAGER 27/04/2015 2:20:46 PM 16460 (0x404C)
    Execute query exec [sp_CP_SetLastErrorCode] 2097152814, 0 SMS_CLIENT_CONFIG_MANAGER 27/04/2015 2:20:46 PM 16460 (0x404C)
    —> Completed request “2097152814”, machine name “TestClient”. SMS_CLIENT_CONFIG_MANAGER 27/04/2015 2:20:46 PM 16460 (0x404C)
    Deleted request “2097152814”, machine name “TestClient” SMS_CLIENT_CONFIG_MANAGER 27/04/2015 2:20:46 PM 16460 (0x404C)
    ____________________________

    ~Thanks


    ReplyDelete
    Replies
    1. HauApril 29, 2015 at 6:42 PM

      check the locationservices.log and clientlocation.log in the client under c:\windows\ccm\logs

      I'm suspecting it couldn't contact the management point.

      Did you check any SCCM record publish in the SystemManagement container in Domain B?

      Delete
  2. YH TanMay 22, 2015 at 11:36 PM

    Hi Hau. i have exactly the same scenario. My SCCM is in domainA and i want to discover the computers in domainB. I installed the client manually on domainB from the log in can locate the MP in domainA. everything looks fine but i cant see the computer reporting back to the SCCM Console? By the way i didnt see the records published in domainB. do i need to create myself? Thanks

    ReplyDelete
    Replies
    1. HauMay 25, 2015 at 4:20 PM

      Are you using SCCM 2012 or SCCM 2007?

      In SCCM 2012, you can configure Active Directory Forest under Hierarchy Configuration to publish the SCCM record.

      Delete
    2. YH TanMay 25, 2015 at 7:56 PM

      Hi Hau. currently using SCCM 2012 R2 in DomainA. Previously running SCCM 2007 in DomainB i can still see the old records there, but not the records from SCCM 2012.

      Is it a must to configure the Active Directory Forest in order for computers in DomainA to report back to SCCM 2012 in DomainA?

      Thanks.

      Delete
    3. YH TanMay 26, 2015 at 12:07 AM

      By the way, i configured Company.com under the Active Directory Forest, so it should include DomainA.company.com and DomainB.company.com right?i also granted the computer acct to the System Management container of DomainB.

      Delete
    4. HauMay 26, 2015 at 2:55 PM

      For publishing purpose, you might want to add DomainB as well

      Delete
    5. YH TanMay 27, 2015 at 10:23 PM

      Do you mean to add the domainB under Active Directory Forest? So it will become company.com and DomainB.company.com

      Delete
  3. HauMay 26, 2015 at 2:54 PM

    This comment has been removed by the author.

    ReplyDelete
  4. UnknownJuly 8, 2015 at 9:28 PM

    Hi

    Thank you for your great job.. I am New in SCCM .

    What is the requirements needed to manage clients in another domain ?

    Thanks in advance

    Basem

    ReplyDelete

Subscribe to: Post Comments (Atom)