profit10 Posted June 19, 2014 Posted June 19, 2014 I have created a Windows 7 image and used WDS to deploy it. I have a couple issues with my unattend file. en-GB en-GB en-GB en-GB activates local admin 1 net user administrator /active:yes true XXXXX-XXXXX-XXXXX-XXXXX-XXXXX xxxxx xxxxx false en-GB en-GB en-GB en-GB cscript.exe c:\windows\system32\sysprep\join.vbs join domain 3 false 1 cscript.exe c:\windows\system32\slmgr.vbs /ato activate windows false 2 c:\wireless.cmd set wireless settings false true false Work xxxxx true xxxxx true Local administrator administrator administrators administrator xxxxx xxxxx false GMT Standard Time It should prompt for a computer name and then on first log on it should activate windows, join domain and copy the wireless settings before restarting. It joined the domain itself, didn't prompt for a name and called itself 'administrator3' Then on first log on it activates and adds the wireless correctly. Can anyone see why this is happening? Any help would be much appreciated. Thanks.
DMcCoy Posted June 19, 2014 Posted June 19, 2014 Which unattend is this, the WDS client phase, or the image phase? It seems to be a mix of both. You can't use WDS on it's own to prompt for a name then join, it happens in the wrong phase and breaks the trust relationship. You need to script it in the image run commands or use name and approve in WDS instead.
profit10 Posted June 19, 2014 Author Posted June 19, 2014 I have used this same file with an image about a year ago and it worked fine. What I do is: Install windows and all programs etc Stick Unattend.xml in the sysprep folder and run sysprep gui Sysprep does it's thing and restarts where I boot into WDS and capture the image.
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now