REPO CONTENT MENU Audit/Sysprep/Generalize Setupcomplete/Firstlogon Silent Install Scripting Examples Useful Helpers ************************************************************************* 1. Audit/Sysprep/Generalize Some General hints: https://technet.microsoft.com/en-us/library/cc722413(v=ws.10).aspx And a reminder: Sysprep/Generalize consumes one rearm, so on Win 7 Systems with a limitted rearm count it might need to restore the count after 3-5 Sysprep cycles. In Win 8 onwards a new rearm functionality was introduced with a count of 1000 rearms (the lack of any Initial Grace Phase makes it almost obsolete). Win 7/8/8.1: When prompted to enter a username and password, press Ctrl+Shift+F3 Win 10: In opposite to the predecessors the entry point moved to the first Settings screen, where you're asked to chose 'Quick Settings' or configure manually. Procedure stays the same. The system will reboot and login automatically to the build in Admin account. Best is to close the Sysprep Window via 'X' to avoid any unwanted actions at this point. Now install any Windows Updates and deployment wide programs (such as Microsoft Office, Adobe Flash Player, Java, printer drivers etc). You can restart if required because you will automatically be logged back into this temporary built-in administrator account. You will be stuck in this audit mode until sysprep is run later in the process. Windows 8.1: For some weird reason this system doesn't allow updating via the normal GUI. You can use the Powershell WU CMDlet from the Little Helpers part or something like WUMT (you can find info here at MDL). NOTE: I can recommend doing this in VM with snapshot capability as the process might fail and then leaves you unable to log into the account, so you need to start over again. Any modifications you make to this user profile will be automatically copied to the local system default user profile. So this is the time to adjust your start menu, desktop wallpaper and icons, and general profile modifications as these settings will apply to all newly created users on the system. NOTE: Windows activation will NOT carry over the Sysprep/Generalize! To finalize the install, run: Code: %windir%\System32\Sysprep\sysprep.exe Check 'Activate OOBE', the Generalize button and 'Shutdown', then 'OK'. In case you did all tweaks correctly system should shut down after a moment. Last point would be to re-capture the system to a install.wim. Since i use VMware WS for this i only need to start it as Admin and map the drive to the host system and can capture it with dism: Code: dism /Capture-Image /English /ImageFile:"d:\win\install.wim" /CaptureDir:"x:" /Name:"Windows 10 Pro" /Description:"Windows 10 Pro" /CheckIntegrity /Verify Since dism can be slightly messy especially when capturing or unmounting images, it's recommended to either export once or cleanup with wimlib-imagex. EXAMPLE SCENARIOS: #1. On a physical machine as described above. After Sysprep/Generalize/Shutdown the capture can be performed from a WinPE media (even a Windows Setup) to an additional partition/drive/usb-device. Afterwards simply start the machine to initialize the OOBE part of Windows setup and install as normal. #2. Would be the virtual route. Since i use VMware i will use it in this example and add a description for Virtual Box if any knowing user provides one. After the VM entered Audit mode, i recommend to either snapshot the state or backup the VM-folder. It can spare a lot of time if anything fails, and when experimenting someting always fails . Again after Sysprep/Generalize/Shutdown close VMware and restart as Admin, then in the Settings of the Audit Mode VM navigate to the Hard Disk Settings and 'Map' the drive to make it accessible. It needs to run VMware as admin to allow Dism to recognize the Windows install, otherwise it will throw an error. In case you have a spare partition you can configure the VM to use the real disk/partition. In both cases simply capture the Install.