Troubleshooting Sysprep Domain Join Issues

Nov 5, 2013 14:19 · 195 words · 1 minute read

I’ve spent the morning trying to figure out why a SYSPREP’d instance was not joining the domain.

Turns out that in the folder C:\Windows\Panther\UnattendGC there is an extremely useful log files called setupact.log.

This log provides a verbose breakdown what happens during the sysprep process for the machine in question.

To access the log you will need to launch notepad under Administrator context.

Once you open the log, search for the DJOIN string. From there you’ll see all sorts of juicy details about the domain joining sequence.

Once you find the error codes, google them and you’ll be up and running in no time.

A couple of example codes and their translation…

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

Typically this error signifies a bad username or password.

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.