How to troubleshoot sysprep issues when joining a domain

Author: NetworkAdminKB.com
Created: 2010-12-06
Modified: 2010-12-06

Issue:

You encounter one or more issues while joining a computer to the domain using sysprep.

 

The sysprep Setuperr.log may report errors similar to the following

2010-11-30 14:16:51, Error   [DJOIN.EXE] Unattended Join: NetJoinDomain failed error code is [2202]

2010-11-30 14:16:51, Error   [DJOIN.EXE] Unattended Join: Unable to join; gdwError = 0x89a

 

2010-11-30 12:36:41, Error   [DJOIN.EXE] Unattended Join: NetJoinDomain failed error code is [1355]

2010-11-30 12:36:41, Error   [DJOIN.EXE] Unattended Join: Unable to join; gdwerror = 0x54b

 

2010-11-30 10:46:53, Error   [DJOIN.EXE] Unattended Join: NetJoinDomain failed error code is [1326]

2010-11-30 10:36:53, Error   [DJOIN.EXE] Unattended Join: Unable to join; gdwerror = 0x52e

 

 

 

Cause

Typically the causes are either network, permissions, or username and password errors.

 

Error 1326: Logon failure: unknown user name or bad password.

Typically this error signifies a bad username or password mis-match.

 

Error 1355: The specified domain either does not exist or could not be contacted.

Typically this error signifies network, DNS, or WINS issues.

 

Error 2202: You specified an invalid user name or group name.

Typically this error signifies an invalid (incorrect format) username is being used.  This can happen if you use a third party utility that creates the unattended.xml file used by sysprep.

 

Solution:

Review the following sysprep log files

 

1)      Location: C:\Windows\Panther\UnattendedGC

a.       Setupact.log

b.      Setuperr.log

2)      Location: C:\Windows\Debug

a.       Netsetup.log

 

The netsetup.log file will provide the most valuable information for issues when joining the domain.  Look for the NetpDoDomainJoin section that pertains to the domain join.  In the following example the account name is not specified correctly.

 

The log file below is a demonstration of caused the 2202 error in my case.

 

11/30/2010 14:09:48:654 NetpDoDomainJoin

11/30/2010 14:09:48:654 NetpMachineValidToJoin: SERVER01

11/30/2010 14:09:48:654         OS Version: 6.1

11/30/2010 14:09:48:654         Build number: 7600 (7600.win7_rtm.090713-1255)

11/30/2010 14:09:48:701         SKU: Windows Server 2008 R2 Enterprise

11/30/2010 14:09:48:701 NetpDomainJoinLicensingCheck: ulLicenseValue=1, Status: 0x0

11/30/2010 14:09:48:701 NetpGetLsaPrimaryDomain: status: 0x0

11/30/2010 14:09:48:701 NetpMachineValidToJoin: status: 0x0

11/30/2010 14:09:48:701 NetpJoinDomain

11/30/2010 14:09:48:701         Machine: SERVER01

11/30/2010 14:09:48:701         Domain: domain.com\dc1.domain.com

11/30/2010 14:09:48:701         MachineAccountOU: (NULL)

11/30/2010 14:09:48:701         Account: domain.com\domain1\addwks

11/30/2010 14:09:48:701         Options: 0x23

11/30/2010 14:09:48:701 NetpLoadParameters: loading registry parameters...

11/30/2010 14:09:48:701 NetpLoadParameters: DNSNameResolutionRequired not found, defaulting to '1' 0x2

11/30/2010 14:09:48:701 NetpLoadParameters: DomainCompatibilityMode not found, defaulting to '0' 0x2

11/30/2010 14:09:48:701 NetpLoadParameters: status: 0x2

11/30/2010 14:09:48:701 NetpValidateName: checking to see if 'domain.com' is valid as type 3 name

11/30/2010 14:09:48:810 NetpCheckDomainNameIsValid [ Exists ] for 'domain.com' returned 0x0

11/30/2010 14:09:48:810 NetpValidateName: name 'domain.com' is valid for type 3

11/30/2010 14:09:48:810 NetUseAdd to \\dc1.domain.com\IPC$ returned 87

11/30/2010 14:09:48:810 NetUseAdd bad parameter is 5

11/30/2010 14:09:48:810 NetpJoinDomain: status of connecting to dc '\\dc1.domain.com': 0x89a

11/30/2010 14:09:48:810 NetpJoinDomainOnDs: Function exits with status of: 0x89a

11/30/2010 14:09:48:810 NetpDoDomainJoin: status: 0x89a

Article ID: 245, Created On: 9/18/2011, Modified: 9/18/2011