DebugJoin
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
DebugJoin specifies a trigger to run the debugging routine if setup encounters an error code. This setting enables you to debug Windows Setup failures. Additionally, if a specific error code is used with DebugJoinOnlyOnThisError, DebugJoin will apply only for failures with the specified error code. For more information, see DebugJoinOnlyOnThisError.
Important
This is an advanced setting designed to be used by product development and Microsoft Product Support Services. Leave this setting unmodified when you configure the unattended answer file.
If DebugJoin is specified, a trace file is generated during the domain join process (%WINDIR%\Panther\UnattendGC\UnattendedJoinDCLocator.etl). This trace file can be useful for diagnosing network connectivity issues during setup that might prevent domain join from succeeding.
Values
true |
Triggers a debugging routine if the domain join operation fails for any reason. If the computer has a kernel debugger attached, it immediately breaks into the debugger after the failed domain join operation. This setting is primarily designed for internal debugging. |
false |
Adds the computer to the domain without performing debugging tasks. This is the default value if |
This string type does not support empty elements. Do not create an empty value for this setting.
Valid Passes
specialize
Parent Hierarchy
Microsoft-Windows-UnattendedJoin | Identification | DebugJoin
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 how to set debug joins.
<DebugJoin>true</DebugJoin>