Search results for query: *

UPDATE: I think we had a build problem, i let the client build the image from my build guide, but when i tried to sysprep manually, it comes back with the same machine name! i think its a bad sysprep causing all this hearburn, imaging a rebuild now, will see very soon.

Oh, and yes, i can join PC manually to domain using the credentials.

VictorySabre, thnx for the reply! Actually it's kinda weird, a conflict of some kind going on. the log file says its joined the domain, then it joins it to the workgroup! In the sysprep file, the identification section is blank. In my scenario i setup a reference PC, added the driver path...

UPDATE: I tried the password in quotes deal and still no luck. After the OSD pushes the OS to the managed client, it goes into the mini-setup and seems to hang a long time at the join domain screen before continuing on. The process completes but get only the local logon - no domain logon...

I also have had this problem on the lasst 2 projects i have been on. Here is what i know: First: check this MS KB out: http://support.microsoft.com/Default.aspx?kbid=910200 RESOLUTION To resolve this issue, do not put the "JoinWorkgroup" entry or the "JoinDomain" entry in the...