NetMan07 Posted February 4, 2021 Posted February 4, 2021 Hi, Windows 10 Enterprise (1909), Windows 2016 Domain The last problem I’m struggling with before being able to deploy ‘Windows 10’ is the very long first logon time that occurs whenever a user logs onto a computer they’ve not used before (i.e. no existing local profile). It’s well griped about on the web as being caused by the modern apps provisioning. In open access/shared areas this long first logon time would be every time a user logged on in the majority of cases. How did you overcome this for your deployment? Thanks.
Steve21 Posted February 4, 2021 Posted February 4, 2021 Generally the first step is to remove all said modern apps that you don't use, as it'll provision them all even if not being used, that will make a large difference. After that, it's generally then down to hardware/default profiles etc Steve
Jcx500 Posted February 4, 2021 Posted February 4, 2021 We Remove all Modern apps while building the image using a powershell script
NetMan07 Posted February 4, 2021 Author Posted February 4, 2021 Thanks for the quick responses Steve and Jcx500. Can the modern apps be removed by script after an image has been deployed to a computer? If the modern apps have been removed, is there still a need to create default profiles? I'm trying to move away from the profiles model and use GPO more to control our users.
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now