0

I used to know how to do this, back when my MCSA/MCSE was still current. For the life of me, I can't recall how though. I know there is a way to rearm the new-user portion of Windows so that, once I get the software and updates all installed, the end user is prompted for a name & password on their first boot.

  • 4
    I guess you're referring to sysprep. – and31415 Jun 28 '14 at 19:42
  • Looks like I am, thanks. It's amazing how fast we lose sysadmin skills, isn't it? I guess my front end stuff would go just as fast if I let it atrophy though. – Imperative Jun 28 '14 at 19:47
  • Now I need to figure out how to execute sysprep on a running install, vs. building an image and pushing it out. – Imperative Jun 28 '14 at 19:48
  • Actually, I'm not sure this is quite what I wanted. I seem to recall there being a way to throw a few registry switches and, bam, the new-user prompt came up on boot. It was especially useful in small offices (non AD) where maintaining a sysprep'd image would be overkill - but attorneys still wanted the DIY new user experience. – Imperative Jun 28 '14 at 19:52
  • 2
    I spend many days a week creating and deploying Windows 7 imagesand using sysprep. I would strongly suggest you don't rely on sysprepping already OOBE'd machines to give to a new user. You will reach a point where it won't work or won't be a viable solution. You should create an image the "official" way and sysprep that with OOBE. Deploy the image and OOBE will go through the new user setup. You should use WAIK and DISM to build your image... You can have an "update" image in WIM format so you don't need to keep deploying and capturing... It is much easier now. – Kinnectus Jun 28 '14 at 23:12

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.