Michael Posted May 15, 2012 Posted May 15, 2012 Well typically it takes a good 5 minutes or so depending on the hardware. You should see a black background with white writing at the bottom. If it's booting straight into Windows, then I would say MySysprep has not run correctly.
satn Posted May 15, 2012 Posted May 15, 2012 in fact i have a lot of composents's installation before booting into windows. I think mysysprep is working i see a logo mysysprep during windows's operations's installation and windows is into domain at the end installations but i have as computeur's name "administrator1" .
Michael Posted May 15, 2012 Posted May 15, 2012 It sounds like MySysprep is running correctly, but please check the following: - On your answer file specify the FQDN and not the NETBIOS name - If you check Device Manager (logging on locally), are drivers installed for your network adapter (LAN)?
satn Posted May 16, 2012 Posted May 16, 2012 hello my answer file is with FQDN name and drivers are installed. can you give me an other exemple for unattended.xml to see if problems are into my file thanks
burgemaster Posted December 6, 2012 Posted December 6, 2012 (edited) 3. Open up Notepad and paste the code below. Save the file as Sysprep.cmd in C:\Windows\System32\Sysprep\ Code: @echo off mysysprep /oobe /generalize /unattend:c:\windows\system32\sysprep\unattend.xml When running the sysprep.cmd anyone is getting "“mysysprep is not recognized as an internal or external command” as I was with 64bit win7 sp1... You need to add the following to "path" in "Environmental variables" ;C:\Windows\System32\Sysprep Edited December 6, 2012 by burgemaster
Arthur Posted December 6, 2012 Posted December 6, 2012 You need to add the following to "path" in "Environmental variables" I think this should also work... mysysprep /oobe /generalize /unattend:%SystemRoot%\[color="#FF0000"]SysNative[/color]\SysPrep\unattend.xml 32-bit applications can access the native system directory by substituting %windir%\Sysnative for %windir%\System32. WOW64 recognizes Sysnative as a special alias used to indicate that the file system should not redirect the access. This mechanism is flexible and easy to use, therefore, it is the recommended mechanism to bypass file system redirection. Note that 64-bit applications cannot use the Sysnative alias as it is a virtual directory not a real one. (Source)
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