ITJS2015 Posted June 21, 2016 Posted June 21, 2016 Have you tried turning off windows defender and IPV6 IPV6 are for class C networks which I don't think you will need, seems that you work in a school. The windows defender is like security essentials but if you already have your AV on it shouldn't really matter. I would recommend these settings and see if it make a difference
ITJS2015 Posted June 21, 2016 Posted June 21, 2016 Or Ideally if its a big issue I would create a blank OU and put a test computer in there with windows 10 and time each GP when you apply to the OU and see how long it takes. I would apply one by one and see which one is the biggy
TSEARS Posted June 21, 2016 Posted June 21, 2016 Thats what I did... Worked wonders! I started at my school a few months a go and login times were between 5 minutes to 20 minutes for each user! So my first project was to fix that. I went through one by one and re-created a lot of the policies, not only that they had a few login scrips running which was duplicating everything GP was doing! So now we have (What I think) quite reasonable login speeds for local profiles Fresh boot new profile login: 40 Seconds Fresh boot, profile already created: 8 seconds Normal login, profile already created: 2 seconds Just got to sit down and go through them all, took around a day but well worth it - helped me make a very good first impression! Also, check for any scripts running! 1
mullet_man Posted June 21, 2016 Posted June 21, 2016 I've tested the latest insider build which doesn't seem to have made much difference to logins, which is a bit of a bummer really. Cold boot new user - takes about 2m 30s to login 2nd user after cold boot - takes about 50s - 60s 2nd logins after profile has been created are about 10-15s so that's fine. It's that initial login after a cold boot which is really bugging me.
TSEARS Posted June 21, 2016 Posted June 21, 2016 Have you got "Display highly detailed status messages" enabled in group policy to see what its getting stuck on?
kennysarmy Posted June 21, 2016 Posted June 21, 2016 I've tested the latest insider build which doesn't seem to have made much difference to logins, which is a bit of a bummer really. Cold boot new user - takes about 2m 30s to login 2nd user after cold boot - takes about 50s - 60s 2nd logins after profile has been created are about 10-15s so that's fine. It's that initial login after a cold boot which is really bugging me. LTSB? or if not have you tried an LTSB build to compare?
mullet_man Posted June 21, 2016 Posted June 21, 2016 Have you got "Display highly detailed status messages" enabled in group policy to see what its getting stuck on? Is this different to verbose messaging? The slowest part is the Preparing Windows section. Will it show more information if I enable that setting? LTSB? or if not have you tried an LTSB build to compare? No am on Education, I might build a LTSB to see. Is that what you were using?
TSEARS Posted June 21, 2016 Posted June 21, 2016 Is this different to verbose messaging? The slowest part is the Preparing Windows section. Will it show more information if I enable that setting? No am on Education, I might build a LTSB to see. Is that what you were using? We're on Education and its working fine - We removed the built in Windows apps before uploading the image to SCCM
mullet_man Posted June 21, 2016 Posted June 21, 2016 We're on Education and its working fine - We removed the built in Windows apps before uploading the image to SCCM How long does a user take to login? What type of account are they? local, roaming? Am removing all the apps during the image process via MDT.
kennysarmy Posted June 21, 2016 Posted June 21, 2016 Is this different to verbose messaging? The slowest part is the Preparing Windows section. Will it show more information if I enable that setting? No am on Education, I might build a LTSB to see. Is that what you were using? Yes, LTSB.
Joanne Posted June 21, 2016 Author Posted June 21, 2016 +1 for LTSB. Doesn't configure all the apps on initial login!
TSEARS Posted June 21, 2016 Posted June 21, 2016 How long does a user take to login? What type of account are they? local, roaming? Am removing all the apps during the image process via MDT. Fresh boot new profile login: 40 Seconds Fresh boot, profile already created: 8 seconds Normal login, profile already created: 2 seconds We run with local profiles with redirected documents and app data
mullet_man Posted June 21, 2016 Posted June 21, 2016 Yes, LTSB. +1 for LTSB. Doesn't configure all the apps on initial login! Thank you. I think that might be my next test.
mullet_man Posted June 21, 2016 Posted June 21, 2016 Fresh boot new profile login: 40 Seconds Fresh boot, profile already created: 8 seconds Normal login, profile already created: 2 seconds We run with local profiles with redirected documents and app data What kind of spec are your devices?
TSEARS Posted June 21, 2016 Posted June 21, 2016 Mainly i3s, with 4gb RAM, but normal disks and not SSDs unfortunately. The computers in the engineering department are i5s with 8gb RAM also with normal disks. I don't notice any difference on login time between the i3s and i5s
Asgard Posted June 28, 2016 Posted June 28, 2016 Fresh boot (i3 4GB RAM SSD) From login screen to working desktop - 11 seconds each and every time (Mandatory Profile) - if it didn't persist on creating the start menu database that would shave a couple of seconds off. Win10 Enterprise 1511 x64
Asgard Posted June 29, 2016 Posted June 29, 2016 So is that for a first time login?? Hi, it's every login - profiles are cleared on logout. Mandatory profile weighs in about 309kb.
Jobos Posted June 29, 2016 Posted June 29, 2016 Hi, it's every login - profiles are cleared on logout. Mandatory profile weighs in about 309kb. How did you manage to get the profile that small? Our mandatory profile is 908KB.
Asgard Posted June 29, 2016 Posted June 29, 2016 Hi I'm wanting to say Witchcraft based on how hard Microsoft make anything remotely easy with Win10. However, I really need to say that it was with the outstanding help/guidance/tips from a few of the wizards of Edugeek - @juls , @timbo343, @gavinh and @3s-gtech This link is sort of the holy grail of links by @gavinh (http://www.edugeek.net/forums/windows-10/163160-w10-mandatory-profile-issues.html#post1397548) - I did this in combination with booting into Audit Mode (Thanks @juls). I now need to decide; Stick with Kixtart for login processing or swap to something else. 1
Joanne Posted June 29, 2016 Author Posted June 29, 2016 OK I'm actually going to do some times now... I've been a bit vague with mine! I've just re-imaged a machine with a HDD. I'll be re-imaging machines with SSDs later so can do the comparison! Core i3, 4GB RAM, HDD - First Logon - 1:28 - Second Logon (after restart) - 0:32 I know for a fact that the SSDs are hugely quicker. I just haven't timed them right after a re-image
sparkeh Posted June 29, 2016 Posted June 29, 2016 I am using an i3, 4gb RAM with SSD running Win 10 Education x64 v1511. Th Windows image has all the modern apps stripped and the GPO to disable the welcome animation is set (weirdly this does seem to improve performance for us and doesn't just display a black screen as I read others post, it gives you the 'preparing windows' message om the login screen). I have also created a default profile that is picked up on first login (not a mandatory profile, I don't want to use those at the moment as there appears to be issues with win 10 and mandatory profiles, this is a default/template profile that is applied on initial login). So results from login screen to fully loaded desktop (includes applying all our GPOs): Initial login = 9 seconds Subsequent logins = 3 seconds Not bad really.
3s-gtech Posted June 29, 2016 Posted June 29, 2016 (edited) Just timed up on my test VM (the only proper Windows 10 machine in the school still, despite the amount of work that I've put into getting it all working!). 60 seconds for a fresh logon, mandatory profile (still chunky at 7MB). VM spec is two CPUs, 2GB RAM, running on a RAID 10 array. I'd expect a workstation to be similar, though network bottlenecks may occur with mass logons. Need to get the profile size down without breaking it. Other notes: Running Win 10 Education x64 v1511 Not bothered much with removal of built in apps beyond Candy Crush Classic Start Edited June 29, 2016 by 3s-gtech
Zoom7000 Posted April 11, 2018 Posted April 11, 2018 Option 2 is to disable the "App Readiness" service. When this is disabled Windows wont bother trying to setup any of the modern apps at logon. The Settings app and Cortana will still work, but you sacrifice having Edge. We have decided to go with IE 11 as the default browser for best compatibility with existing systems (online exams, intranet etc.) and also install Google Chrome. We also install Microsoft Calculator Plus as an alternative to the modern app. @Winner - Have you experienced any issues with Windows Updates failing using option 2? From the investigations that I did here, my PCs were failing to install Windows Updates (specifically, monthly cumulative roll ups) until I re-enabled the App Readiness service. This of course is going to increase login times 1
Joanne Posted April 26, 2018 Author Posted April 26, 2018 Oh my good lord... just created a new image with Windows 10 Education 1709. It's taking 701 seconds for a pupil account to log on. This is not acceptable.
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