Still stumped? For other log files to check, go to the section on Advanced debugging later in this document. NetJoinDomain attempt failed 0x2: check your OU specification NetJoinDomain attempt failed: 0x89a � check your domain join credentials Search for DJoin.exe to see a log of the domain join operations:ĭsGetDCName failed: 0x54b � check your fully qualified domain name You want the log file that's in C:Windows\Panther\UnattendGC. Note: Be sure you are not looking at the setupact log in C:Windows\Panther. Check this log file for errors:Ĭ:\Windows\Panther\ UnattendGC\setupact.log The following log file details the progress of the mini-setup process, including a summary line for each domain attempt. Check the Setupact log on the desktop for errors Keep in mind that while you will look at logs on the desktop to identify your problem, you will update the unattend file in your OS layer or in an application layer to correct it so that newly created desktops will successfully join your domain.
#Powershell join domain specific ou how to#
If your desktop is not joining the domain correctly, here are some common issues and how to solve them. With the unattend builder you can specify all of the settings required to join the desktop to the domain during creation. We recommend that you use the Unidesk unattend builder tool to create your unattend file. When a Windows 7 desktop is created in Unidesk it runs through the Microsoft Windows mini-setup process which uses a file called unattend.xml to configure a variety of desktop settings.