How to stop sysprep'd system image deployment from prompting local-user creation
I have uploaded a sysprep'd windows 7x64 image to our K2000 that contains a couple programs and customizations. the image includes an admin account (NOT the admin account that is supplied by win 7 and automatically disabled) This is the ONLY account that we want on the image when the deployment is finished. prior to the post-installation tasks, however, I am prompted to create an account, password, etc. how do I bypass this? I have read about unattend.xml files but have no idea where to start.
-I am using the system image deployment, NOT a scripted installation
-I am deploying Windows 7 Enterprise x64
-My KBE is based on ADK, not WAIK but seems to be working well
-I am currently using the sysprep GUI found in C:/Windows/System32/Sysprep
-I am using Sysprep OOBE/generalize
everything else works like a charm, I just need to bypass this OOBE user creation one way or another
0 Comments
[ + ] Show comments
Answers (3)
Answer Summary:
Please log in to answer
Posted by:
getElementById
8 years ago
Use the Sysprep Creator. It has an option to "copy profile of the user running sysprep" (see attached)
Here are some useful links
Imaging Best Practices
https://support.software.dell.com/k2000-systems-deployment-appliance/kb/121734
Sysprep Creator ITNinja Post (also accessible from your K2000 under Tools)
http://www.itninja.com/blog/view/sysprep-creator-wizard
Posted by:
auzi95
8 years ago
Top Answer
I actually figured it out. I can write out an explanation if anyone is interested
Comments:
-
yes please, that would be helpful - jeffery.steward 8 years ago
-
I used Windows System Image Manager, which is included in WAIK to create an answer file. This explanation was especially useful:
http://theitbros.com/sysprep-a-windows-7-machine-%E2%80%93-start-to-finish/
I was using a VM so i was able to take snapshots and roll back to a pre-sysprep state. this saved me from having to start from a raw image as suggested in that link.
I also set autologin to occur once since the post installation tasks don't seem to start until after the first login. - auzi95 8 years ago
Posted by:
SMal.tmcc
8 years ago
down and dirty method is to create the second user in your answer file then delete it as post task
net user kprepper /delete
Comments:
-
I had considered that, but the whole idea was to keep it as tidy as possible. Creating the answer file was a learning experience anyway - auzi95 8 years ago