[Stagiair]

Hello,

Hope someone can help me out.
I've been working for weeks on figuring out WDS, Sysprep, answerfile and all other terms.
I succeeded in my testenvironment and now i am deploying images on the companynetwork.
But i get stuck.. at the first computer where i want to install my image with his answerfile (unattend.xml).
Everything is going okay and works but when it finishes with installing and the moment for me is there to log in, it goes wrong.

When i try to log in on the domain it says "The trust relationship between this workstation and the primary domain failed.".
While the domain has been configured on the computer (on the loginscreen you see the domain like: DOMAIN: domain.local).
If i want to log in with the localaccount it says: "Account has been disabled" :S

Did everything as they say here: http://technet.micro...c730845(v=ws.10).aspx at the table under (Secure join) and even tried another computer, but the same problem.

What now?
I have tried everything, serious. The deadline is tomorrow.
Please help!


Unattend: http://pastebin.com/....php?i=xtpCHcXe

This post has been edited by Stagiair: 25 October 2012 - 01:53 AM

[Stagiair]

I could do it with a script, searched an searched but there is not a single script that works to me.

This post has been edited by Stagiair: 25 October 2012 - 07:07 AM

[Tripredacus]

This XML file you posted puts the system into Audit Mode. You should be doing a domain join in OOBE instead.

Also I see you are adding the Administrator account, this account already exists.

[WinOutreach4]

The very last line in this TechNet article says that if you use sysprep /audit to boot to audit mode, the computer will be removed from the domain. The Specialize pass runs during first boot (that's where domain join happens), so you are joining the domain, but then leaving it again when audit mode starts. So Tripredacus is correct and you should remove this part from your unattend file.

Hope this helps,

David

Windows Outreach Team - IT Pro

[Stagiair]

Thanks guys, worked out well!
But my logoncommands don't run!
These are the commands that should run:

 <FirstLogonCommands>
                <SynchronousCommand wcm:action="add">
                    <CommandLine>cscript //b c:\\windows\\system32\\slmgr.vbs /ipk serial-x-x-x</CommandLine>
                    <Order>1</Order>
                    <RequiresUserInput>false</RequiresUserInput>
                </SynchronousCommand>
                <SynchronousCommand wcm:action="add">
                    <CommandLine>cscript //b c:\\windows\\system32\\slmgr.vbs /ipk serial-x-x-x</CommandLine>
                    <Order>2</Order>
                    <RequiresUserInput>false</RequiresUserInput>
                </SynchronousCommand>
                <SynchronousCommand wcm:action="add">
                    <CommandLine>cscript //b c:\\windows\\system32\\slmgr.vbs /ipk serial-x-x-x</CommandLine>
                    <Order>3</Order>
                    <RequiresUserInput>false</RequiresUserInput>
                </SynchronousCommand>
                <SynchronousCommand wcm:action="add">
                    <CommandLine>cscript //b c:\\windows\\system32\\slmgr.vbs /ato serial-x-x-x</CommandLine>
                    <Order>4</Order>
                    <RequiresUserInput>false</RequiresUserInput>
                </SynchronousCommand>
                <SynchronousCommand wcm:action="add">
                    <CommandLine>cscript //b c:\\windows\\system32\\slmgr.vbs /dlv all</CommandLine>
                    <Order>5</Order>
                    <RequiresUserInput>false</RequiresUserInput>
                </SynchronousCommand>
            </FirstLogonCommands>

I have autologon enabled, so they should run when the account is logged in though?
Those are commands to activate Windows 7 and Office btw.
Under OobeSystem and under the component: Microsoft Windows Shell.
So it should work?

Thanks!

This post has been edited by Stagiair: 26 October 2012 - 02:36 AM

[Stagiair]

Nevermind.
Everything works now except the computer problem.
You can't prompt for a computername and join the domain unattended.
There is something wrong with the order.

Only do the joindomain part and put the computername tags just this way:
<ComputerName>*<ComputerName>

You will get a random machinename and you can add to your logoncommands a script to rename your pc.
It's a bug we have to deal with!
Searched many days for this but this is the only solution.

[WinOutreach4]

Great! Glad to hear that you got it working. As for the computer name while joining the domain, have you looked into Prestaging the computers in Active Directory? WDS will pull the computer name from AD if you have the machine pre-staged.


David

Windows Outreach Team - IT Pro