New
#560
Good to get an expert opinionTaken out of context anything can be claimed to be wrong. The context of that statement of mine you quoted would have become clearer if you had also quoted the first sentence of the same post:
In domain environment an admin can for instance redirect user profiles to server. That effectively overwrites the visual customizations made by user.
That being said, this tutorial is like Ten Forums in general for private users. The tutorial's purpose is to show how to customize a Windows install image to be used in a workgroup (no domain) environment.
Kari
Any new info on the Star Menu problem after using CopyProfile in 1703?
in SYSPREP breaks the start menu in Creators Update v1703
It seems after reading portions of this thread that 1703 is considered "broken" at the moment for imaging, is that true? I also have ran into 1703 imaging issues. My current issue is that the "SetupComplete.cmd" script ends prematurely. Anyone else having that problem?
Dustin
Just wanted to ask - I followed the steps in the video where it says to turn the VM off when you are being asked for Microsoft Account / Setup user account - so I captured this image but it is still asking me to pick a keyboard etc? I thought the answer file would resolve this and make it a silent install?
I am using the CopyProfile option to retain the customized OEM information, but I noticed that this has the effect of also copying the install.wim file from the desktop to the new user account. Is there a way to prevent this?
EDIT: Apparently there is! I can use an install.wim file from an external drive.
Hi rocky, welcome to Ten Forums.
This note is from beginning of Part Six of tutorial:
Note
Please read before proceeding:
Sysprepping with the Generalize switch and CopyProfile=TRUE has a small issue or rather a small inconvenience: it leaves the last used user folders (#1 in screenshot below) and recent files (#2) of built-in admin to end user's Quick Access:
A very simple and fast workaround is to add this batch file to built-in admin's %appdata%\Microsoft\Windows\Start Menu\Programs\Startup folder in Audit Mode before running Sysprep. Name it as you want to using the .bat extension, I named it RunOnce.bat:
The batch file explained:Code:echo Y | del %appdata%\microsoft\windows\recent\automaticdestinations\* del %0
- echo Y | = Pipes (sends) a letter Y to the command given after the Pipe (|) character
- del %appdata%\microsoft\windows\recent\automaticdestinations\* = Resets the Quick Access to defaults. This command expects the user to enter either Y for Yes or N for No. As the Y will be in this case piped, user interaction is not needed but instead the Y will be entered automatically
- del %0 = Deletes the batch file itself after it has been run. Leaving this away, not deleting the batch file, would reset the Quick Access every time the user signs in
File is now saved in built-in admin's Startup folder, which will be copied among other customizations to Default User Profile when you sysprep with CopyProfile set TRUE using the /generalize switch.
Now whenever a new user account will be created, be it the initial user created in OOBE or any user created anytime later, the batch will be run once for each user resetting the Quick Access to defaults and then removing itself.
Other than this minor inconvenience I have not found any whatsoever issues in Audit Mode, Sysprep, generalizing and CopyProfile functions.
Kari
Got pointed here when I asked on reddit if anyone else had any clue on how to customise W10 for all new users after my previous method of using copyprofile broke search.
It seems that this is a common W10 1703 issue and not just my issue.
I am using MDT to edit the unattend.xml file (which reduces the number of steps required to do the customisation significantly. I am trying to follow georg49 suggestion of editing the WIM file, but since I am using MDT I am not sure if this is possible .. any ideas?
Thanks