I've been in and out of Audit Mode, but I've never done it after upgrading. And unless it's changed from Windows 7 and Windows 8.1, when you go to do the generalization, Sysprep checks to see if the image has been upgraded. If it has, an error message appears telling you that you can't generalize an upgraded image.
Anyways I'm trying it right now, will report back.
Just a few pointers:
- You can always boot to Audit Mode even after the OOBE, command is
%windir%\System32\Sysprep\Sysprep.exe /audit /reboot- When rebooted to Audit Mode and if you like to re-customize the default user profile, it will only affect all future user accounts but does not affect existing ones already present when you booted to Audit Mode. You can of course remove all existing user accounts if necessary before sysprepping
- If rebooted to Audit Mode and existing user accounts are kept, you cannot use those usernames when back in OOBE after sysprepping. To create the initial user in OOBE you can for example simply create a dummy local user, let Windows finish the OOBE and boot to this dummy's desktop, sign out and sign in to your original admin account and remove the dummy account
- Sysprepping an upgraded Windows is of course possible and only needs a key and a DWORD deleted in the registry and changing the value of two DWORDs. Instructions in this tutorial: Users Folder - Move Location in Windows 10 - Windows 10 Forums, scroll down to the last part named Upgrade and its Step 2
Kari
Thanks, the registry key trick worked.
One more thing is that I also needed to remove an app that was pushed to my laptop based on the OEM key, it's an HP one in my case. That caused an error with Sysprep, saying it cannot be provisioned for all users. Removed the app, and Sysprep proceeds as usual.
Has anyone tried to upgrade one of their Windows 10 (10240) imaged machines built with the copy profile option? I did this week and I logged onto the machine with a new profile. The start button / search was broke. Right mouse clicking on a pinned shortcut also did not work. I deleted the profile and rolled back to (10240) and everything worked again. Any similar experiences?
Has anyone attempted to deploy Windows 10 without Sysprep? My current thinking is that, under certain circumstances, it may be easier to deploy without Sysprep.
This is our current gameplan:
- Do Sysprep the employee machines, which users will be logging into using domain accounts. We will not be using CopyProfile because it is a feature Microsoft no longer supports. ICD has replaced CopyProfile. Instead, we will make manual changes to the default profile (by adding files to C:\Users\Default and by changing registry changes to ntuser.dat).
- Do not Sysprep the public/kiosk machines, which will have generic local user accounts and nobody will be logging into. We will rearm the image just before taking it using SLMGR -REARM so that KMS sees the machines as separate computers.
Has anyone attempted deployment without Sysprep?
Quick: To get into the audit mode in Windows 10 1511 update (TH2) just omit the pass to connect the wireless net if appears. When you press the KB combination an error will appear (my instalation is in spanish, but says like "Threre is a installation problem")
A lot of words... (explaining)
Today I trying to create a sysprepped with copy profile option with a lot preinstalled software (wharever software really...) to test the copy profile function and other handred rare things... My first surprise comes when I press the SHIFT+CTRL+F3 keyboard combination to enter in audit mode, an installation error appears!, but for that stupid reasons I clicked on "omit this step" link and trying the combination, and works... May be there I will publish a log for this work, and if any one has any question, please use a this thread:
Windows 10 1511 sysprepping and imaging log - Windows 10 Forums
I have been watching this message board for a few months now and searching for an answer. Finally I think I am on the right path but only to find more issues.
I create the base image with two users, then sysprep only to find my start menu and cortana do not work...
What I found is that there is an app in the Packages folder of the user that is causing this problem...I have narrowed it down to six apps but figured why not post and let others play as well...
Once you have the start menu issue log into the administrator account and delete everything in
"C:\users\%user%\AppData\Local\Packages"
when you log back into your account boom the start menu work and cortana....
the new issue.
the apps you deleted no longer open...
I am trying to narrow down what app is causing the issue and find a way to fix it to get this thing done once and for all (am tired or syspreping machines over and over).
Quote