Bize Ulaşın / Contact Us

Using MDT DB to get location specific Domain Joining parameters in SCCM OSD

If you have multiple domains as me and want to automate domain joining task by sensing locations automatically in SCCM OSD, you can use MDT DB to do it easily. You can also do this by adding more actions with different queries to your TS or customizing your coustomsettings.ini. But I prefer using MDT DB as changes there doesn’t need to be refresh as packages, GUI makes it easier to manage and more foolproof, etc.

All you need to do is modifying location details on your MDT DB and call these variables in your SCCM TS.

So first edit your location details in MDT Workbench, you’ll need to edit four values here as shown below.

07-01-2013 13-27-03

DomainAdmin :
The name of the account used to join the domain. Example : OSDAdmin
DomainAdminDomain : The domain of the account used to join the domain. Example: Domain1
DomainAdminPassword : The password of the account used to join the domain.
JoinDomain : The name of the domain in which the computer should be placed. Example: Domain1.local
MachineObjectOU : The OU in which the computer account should be created (if it does not already exist)., Exaple: OU=NewComps,DC=Domain1,DC=Local

Then you’ll need to modify your “Apply Network Settings” action in your TS to use values in MDT DB. It is very as MDT Workbench displays these as it is. So all you need to do adding % to the start and the end of the variable as below.

Domain : %JoinDomain%
DomainOU : %MachineObjectOU%
Account : %DomainAdmin%
Password : %DomainAdminPassword%

 07-01-2013 13-25-08

All done, now you can test it.

Please note that you’ll need a working SCCM and MDT integration to use this method first.

2 comments on “Using MDT DB to get location specific Domain Joining parameters in SCCM OSD

  1. on August 19, 2018
    JEan-SEbastien Frenette says:

    I’m trying to do that with SCCM 1806 and Windows 10 1709 and it doesn’T work. I have put my exactly as stated, the step run fine but the computer isn’t joined to domain. No error in smsts.log. I don’t get what I’m missing

    • on October 16, 2018
      Osman Shener says:

      You can check MDT/BDD logs located on the client computer, it will show you the properties and their values pulled from MDT DB. Are you sure your client gets other settings from the DB?

Leave a Reply

Your email address will not be published. Required fields are marked *

Kontrol / Control * Time limit is exhausted. Please reload CAPTCHA.

This site uses Akismet to reduce spam. Learn how your comment data is processed.