Systems Deployment Question
Configuring Windows 10 during a Scripted Installation
I've been using the K2000 for imaging for many years, but I would like to switch over to Scripted Installations and I see many on here have made that switch so I'm hoping I can get some help.
I've made a scripted image of Windows 10 1809 and LTSB 2019 with post-install tasks to install software (Office, VLC, Acrobat, etc.), and remove some of the bloatware, etc., but I'm wondering how you can better configure Windows for an educational environment (~600PCs).
1) How can you set the "default" desktop background, desktop shortcuts, the start menu groups and tiles, the taskbar shortcuts (have Cortana icon only on taskbar, remove MSStore, Edge, etc.), and other Windows settings?
Are you somehow doing this in the unattend file? or as Post-Install tasks? I want to set the defaults, but allow the user to make changes if desired.
I know I can set the Start/taskbar with an XML Group policy, but that does create some overhead and I want users to be able to modify it.
2) Secondly, the computers join the domain as the last PI task, but I want the built-in local administrator to remain active with a complex password. It comes in handy when there are network issues, etc. Our Group Policy does rename it after it joins the domain.
Currently, this works with my images. For my Scripted install it does autologon 3 times with the built-in admin (in unattend) to perform the PI Tasks, but it doesn't stay active. It could be a setting I'm missing in the unattend.
Any sample unattend or PI tasks that help with this would be most welcome.
Community Chosen Answer
1. Check out my Blog on the Start & Taskbar config.
2. The admin account you put in the unattend should stay active, it's the built-in 'Administrator' account which will be inactive.
You can add a post install task which enables the built in administrator and sets password.
net user administrator <complexpassword>
You can also delete the admin account you created in the unattend also.