Then right click on an OU containing your computers and select Delegate Control. Delegating domain join permissions ^Ĭreate a custom security group named something like: Allowed to Join Computers to the Domain. A new copy is retrieved every time a computer is imaged.
You do not need to update your DeploymentShare when editing just the CustomSettings.ini. Save your customsettings.ini and open up Active Directory Users and Computer. In our environment, we use a special account that is delegated permissions to create/delete computer accounts. The CustomSettings.ini file is stored in clear text and can easily be found. DomainAdminPassword=The DomainAdmin user’s passwordĮven though the properties above say “DomainAdmin” and “DomainAdminPassword”, please do not actually use your Domain Administrator for this process.DomainAdminDomain= Your Domain Name – EX: Test.Local.DomainAdmin=A User that Can Join Machines to the Domain.JoinDomain=Your Domain Name – EX: Test.Local.
Specifically, you will need to set the following: The necessary settings needed for a MDT domain join can be configured in your CustomSettings.ini file. If it doesn’t succeed, it will attempt another domain join with the Recover From Domain task.Ī blank Unattend.XML opened in Window SIM MDT domain join settings ^ In essence, the actual join domain process occurs in the Install phase and requires a handful of administratively assigned settings to succeed. The Lite Touch wizard will set the same task sequence variables in either case, and the "Recover from domain" step will notice that the unattend.xml didn't do the join. using the "Recover from Domain" step, you would need to remove the join entries from the unattend.xml associated with your task sequence. By default, the domain join happens as part of the OS installation - the unattend.xml specifies to join the domain.
0 kommentar(er)
