Windows 10- moving from 1511 to 1607 in audit mode?
-
@adukes40 I don’t know about all of them, but you can make a themepack on your current computer, activate that in audit mode, then run defprof and it should transfer everything that a theme can contain (background for sure, I think colors too).
Not sure what you want to alter about the start menu, if you mean rearranaging stuff and what not, I remember people having trouble with that, not sure if defprof is able to do that for you (mine remains default, so no experience there)
-
@adukes40 said in Windows 10- moving from 1511 to 1607 in audit mode?:
mainly backgrounds, colors, Lock Screens, and start menu.
The backgrounds, and colors can be set in the admin account, and then when you sysprep the system reference your unattend.xml file with the copyto setting in the unattend.xml file to copy the settings from the admin account to default user.
As for the start menu that one is a bit tougher and we are still struggling with that one. But basically you need to either create the perfect start menu on a test computer and then export the configuration to an xml file and then have it setup to that when a new user logs into a win10 system the exported menu xml file is imported into the user’s profile. You can also set a registry key to point to this xml file, but it restricts the user from changing/customizing their own menu.
-
@george1421 Yes, I don’t use unattend files myself (and I find defprof more reliable than unattend as well), though, so hence the alternative. My start menus aren’t broken on deploy at any rate, which was a huge issue with customizing the start menu without defprof
-
@Quazz I’m not familiar with defprof so I need to look into that and learn something new today, thank you for the tip!
-
Guess I will try the package idea. So just make a fresh machine thats activated, make changes, export the theme, then import on the audit mode machine?
-
@adukes40 said in Windows 10- moving from 1511 to 1607 in audit mode?:
Guess I will try the package idea. So just make a fresh machine thats activated, make changes, export the theme, then import on the audit mode machine?
This is what we did for our win7 base image. Setup the environment exactly like we wanted on a development machine and then exported the theme into a theme pack and loaded the theme pack during some post image deployment tasks.
-
@adukes40 Yes. Although according to @george1421 you should be able to make those changes anyway (without themepack)? (I seem to recall being unable to in Windows 8, maybe 10 too though, IT MIGHT DEPEND ON THE VERSION (eg HOME vs ENTERPRISE)
Cool thing about themepack though is that they’re cross compatible on Windows 7 and above (maybe vista too? never tested it)
-
@Quazz On Win7 it let you do it, but Win10 won’t do it without activation. Never had to do it with a theme pack. Probably a good idea anyway to keep consistency between remakes of images.
-
I am back to my Win 10 machine, and while in audit mode, I cannot set certain settings without windows being Activated. I have tried on LTSB and EDU. EDU give me some extra breathing room, but still cant set lock screens and other settings.
-
@adukes40 That stuff we will typically set in the setupcomplete.cmd file once the system has been deployed and OOBE runs. We’ll use MDT (or audit mode) to place all of the files needed on the reference computer before capture but then let the setupcomplete.cmd move the settings into place post deployment.
-
@adukes40 At my old job, my co-worker managed the start menu via group policy. So there’s that path.
