Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I'm pushing out a new Win7 image to several machines using WDS, unattend.xml, and oobeunattend.xml.

Naturally you have to create the local user in the OOBE experience but it isn't something I want to keep there.

I added this to my OOBE.xml but it isn't working, its even after my domain joining component:

<settings pass="auditUser">
- <component name="Microsoft-Windows-Deployment" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="" xmlns:xsi="">
 - <RunSynchronous>
   - <RunSynchronousCommand wcm:action="add">
      - <Credentials>
        <Description>Removes original test user</Description> 
        <Path>net user temp /del</Path> 
share|improve this question
up vote 1 down vote accepted

Woohoo I got it!

In my answer file, instead of doing a script (which was running in the Specialize component anyway, and the user was created in oobeSystem) in specialize, I added Windows-Shell-Setup --> FirstLogonCommands and put the command there. Worked perfectly! Thanks!

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.