UnsecureJoin
Applies To: Windows 7, Windows 8, Windows 8.1, Windows Server 2008, Windows Server 2008 R2, Windows Server 2012, Windows Server 2012 R2, Windows Vista
UnsecureJoin specifies whether to add the computer to the domain without requiring a unique password. UnsecureJoin is performed, by using a null session with a pre-existing account. This means there is no authentication to the domain controller when configuring the machine account; it is done anonymously. The account must have a well-known password or a specified value for MachinePassword. The well-known password is the first 14 characters of the computer name in lower case. For more information, see MachinePassword. If the well-known password is used, then the password is changed to a strong password by Netlogon after the join completes.
Values
true |
Adds the computer to the domain without requiring that Domain, Username, and Password are specified in the Credentials section for authentication to the domain during the domain join process. |
false |
Requires that a valid Domain, Username, and Password are specified in the Credentials section for authentication to the domain during the domain join process. This is the default value. |
Note
Domain, Username, and Password must not be specified in the Credentials section if UnsecureJoin is set to true.
Valid Passes
specialize
Parent Hierarchy
Microsoft-Windows-UnattendedJoin | Identification | UnsecureJoin
Applies To
For the list of the supported Windows editions and architectures that this component supports, see Microsoft-Windows-UnattendedJoin.
XML Example
The following XML output shows the computer added to the domain without the requirement of a unique password.
<UnsecureJoin>true</UnsecureJoin>