mikeyd

I'm considering looking into MDT (LTI). Thanks for your reply. Regards, Mike

Leaving out computername did the job. Unfortunately UnattendJoin runs in the specialize part of the setup before OOBE so the the computer is joined to the domain with a random WIN-yyyyyyy computername - But I can solve this by joining the computer to the domain using a powershell script later in the setup process. Thanks for your help. Regards, Mike

I'm deploying Windows 7 enterprise thru WDS (running on Windows Server 2008 R2). Deployment is working fine except that I want to set the computername manually during install instead of prestaging the computer in AD or having a randomly generated computername. I was thinking of creating a script that asks for the computername sometime during install and then modifies the unattend xml file automatically. My setup is a school environment with computers being moved and re-installed (renamed) constantly. So I added Microsoft-Windows-Deployment_neutral, RunSynchronous, RunSynchronousCommand, cmd.exe to the specialize section of the unattended xml file to test if I could edit c:\windows\panther\unattend.xml and set the computername before Microsoft-Windows-UnattendedJoin_neutral was executed. However the runsynchronous command is run just after the computer being joined to the domain - Pressing Shift-F10 and editing unattend.xml earlier in the specialize process works fine. My second thought was to add Microsoft-Windows-Deployment_neutral, RunSynchronous, RunSynchronousCommand, cmd.exe to WindowsPE and edit x:\sources\wdsunattend\wdsimageunattend.xml. However I'm unable to run cmd.exe in the WinPE environment. Pressing Shift-F10 works but in this case wdsimageunattend.xml is not copied until just before the system reboots (so I'm unable to test if editing the file works). Any suggestions on how to make this work? Regards, Mike