piglovesrat15 Posted December 21, 2010 Share Posted December 21, 2010 I have created a Sysprep.xml file that successfully run (C:\windows\system32\sysprep\sysprep /generalize /oobe /shutdown /unattend:c:\sysprep.xml) and apply the image for Windows 7x64 Enterprise. I enabled the local administrator account in the Sysprep.xml.My question, is there a way to tell Sysprep not to create a new user account after applying the image to a new computer and instead pop up a command prompt with "net user" command to change the built-in local administrator's password? I've done that with Windows XP Sysprep.Thank you. Link to comment Share on other sites More sharing options...
Tripredacus Posted December 21, 2010 Share Posted December 21, 2010 Why not just leave the Administrator account disabled and create a new user account in the Administrators group? If you use the built-in Administrator account, you run the risk of bricking the OS if the account gets corrupted. Link to comment Share on other sites More sharing options...
piglovesrat15 Posted December 23, 2010 Author Share Posted December 23, 2010 Thanks for your reply. But leave the built-in admin account enabled is one of the requirements from the manager. Link to comment Share on other sites More sharing options...
Tripredacus Posted December 23, 2010 Share Posted December 23, 2010 It needs to create a user account. You can just have it create an account, and put your CMD into the FirstLogon Commands. The problem is that once you change the password on the Administrator account, you will still log in with the created account. You could also run a script that adds the Auto Logon keys into the registry for the Administrator account, so on a reboot that is the account that logs on instead of the new one. There is no harm to have another account on the machine to use in case of emergency, or by your technical staff. Link to comment Share on other sites More sharing options...
IcemanND Posted December 27, 2010 Share Posted December 27, 2010 If the machines are joined to a domain add a domain user or group to the local administrators group will solve the problem also. Link to comment Share on other sites More sharing options...
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