[1703, cu] First Logon time

[HereIGoAgain2601]

Hello,

 

Just curious as to whether anybody has managed to get the first logon time down to under a minute? We have a variety of SSD / HDD machines and are getting complaints about slow logins. Upon testing this seems to be only the first logon, the second logon's are around 10 seconds or under, which is great but not so great as most of our logins will be first time ones!

 

We are looking at between 2-3 minutes for the first time logon currently. We are running 1703 with all the apps removed, the exception being photos and calculator.

It seems our GPOs are processed within 30 seconds, the remainder is the "preparing windows".

 

Any ideas what else we could try?

[mavhc]

If you enable logging you might see where it's slow https://technet.microsoft.com/en-us/library/cc978342.aspx

[Arthur]

What type of profiles do your users have?

 

Any ideas what else we could try?

Do you have the following GPOs set? Even though the article mentions mandatory profiles it's probably still worth doing with other types of profiles.

 

https://docs.microsoft.com/en-gb/windows/client-management/mandatory-user-profile#apply-policies-to-improve-sign-in-time

 

Apply policies to improve sign-in time

When a user is configured with a mandatory profile, Windows 10 starts as though it was the first sign-in each time the user signs in. To improve sign-in performance for users with mandatory user profiles, apply the Group Policy settings shown in the following table. (The table shows which operating system versions each policy setting can apply to).

 

• Show first sign-in animation (Disabled)
  
• Turn off Microsoft consumer experiences (Enabled)
  
• Allow Cortana (Disabled)
  

Also, do you use Impero?

 

www.edugeek.net/forums/impero-direct-support/189213-preparing-windows-slow-logon-some-pcs.html#post1623416

Edited November 20, 2017 by Arthur

[LeMarchand]

Wired or wireless? Ours aren't too bad wired, but slow wireless.

[HereIGoAgain2601]

We are having the issue on both wired and wireless. Don't use imepro, and have all those GPOs turned on. Using local profiles as using mandatory seemed to make it worse.. every login would be 2-3 mins rather than first and then 15 seconds on the second logon. Don't use Impero here, we have LanSchool

[Guest Guest]

Do you have many apps provisioned? I found that with all of the default apps left in place first logins are much slower than if you remove what’s not needed.

[HereIGoAgain2601]

We only have Photos app and Camera provisioned everything else has been stripped out

[Guest Guest]

Do you have verbose logon messages enabled? It may shed some light on what process is causing the issue

[zag]

Out of interest, how does it compare to Windows 7?

 

Is Windows 10 slower on first local profile load? This was one of the reasons we are not migrating to it as our Windows 7 machines only take 25 seconds.

[ollyyllo]

Can confirm Arthur's suggestions all help alot.

Show first sign-in animation (Disabled)

Turn off Microsoft consumer experiences (Enabled)

Allow Cortana (Disabled)

 

Running Windows 10 1703 with first logon about 1 min on HDD and about 40 sec on SSD. Group policies take about 15 secs (I think i can improve that though)

Using Local Profiles, tried roaming and mandatory, could only get local to work in a reasonble time.

 

Do you have a simple start menu tiles layout (LayoutModifications.xml)

I remember when testing it seemed to improve logon times having it rather than not.

 

Are you redirecting the start menu, I found doing so caused problems and slowdowns?

Not sure if that's the case for everyone, but if you are using the LayoutModifications GPO, I dont see there is much benefit in redirecting the startmenu anyway.

[HereIGoAgain2601]

Hi, Yes Windows 10 much slower on the initial first profile load. We didn't have this problem with Windows 7. Fully Windows 10 now.

We have the Verbose messaging enabled, the problem is not GPO related. We speed through that and end up at Preparing Windows which is apparently something to do with the user profile / app creation part of the first logon.

 

Looking at moving back to roaming profiles. We moved away when using 1511 due to issues, but it seems to take a minute off the login times. The first login is 30 seconds using roaming profiles.

[KK20]

Do you use old fashioned printer scripts or printer preferences? We found that the old printer scripts on an asymmetrical VBS worked faster than printer preferences (which are sequential). Local and roaming take about 35 seconds for us - there is no time difference (pupils are roaming, staff are local). If a printer is offline then preferences took a few seconds (per printer) longer.

[zag]

So Windows 10 basically has double the initial login in time as windows 7? That's shocking!

 

I understand that Windows 10 comes with more features and things to setup, but that really is a huge down side to upgrading

[HereIGoAgain2601]

The logon times and boot up is a massive problem for us. Sometimes we can have users logged on in 2 mins, sometimes it takes 5+ minutes.

We are using group policy preference printers but this works well for us, we are prestaging the drivers onto the machines so the process is pretty quick. Only problem currently is with default printer not setting until the second logon, seems to be a bit of a known issue.

 

Been doing some testing and turning off the always wait for the network at boot up GPO seems to help take 2 minutes off boot up times but obviously could see issues with GPO change if we turn this off..

[alfatec]

It is all down to the profile. We are using 1709 and our first logon time for staff or student is between 15-20 seconds and that is on non SSD. We strip out the apps from our Wim file and follow the Rankin profile creation. When editing your .dat file you must ensure there are no references to any users or anything on your network. We also copy the packages folder and TileDataLayer from the original profile to the default profile. This removes issues with the start menu. 1709 does seem alot quicker than 1607 and 1703 on first login.

[HereIGoAgain2601]

Thanks, we stripped out all the apps from the WIM but didn't edit any profiles. I will give that a go see if we can make any improvements and will try 1709.

LTSB keeps getting suggested but I am loathed to switch to this model

[alfatec]

With 1709 we still use Edge and have no problems. What we also do is install the printer as a local printer but connected to the print server. This means that you do not need to map printers in group policy. Just ensure you make your default profile in audit mode, use the copy profile method, edit your .bat reg file, apply permissions and all should be fine.

[HereIGoAgain2601]

Thanks we are going to try 1709 on a few test machines and see if that makes a difference

[Timetable]

Hi there,

 

May i ask if you had a Fail safe Profile creation method as i have followed two in 1709 and it seems to work, but when we login the user doesn't get the start menu.

 

We currently have roaming profiles and want to go to a mandatory roaming profile for all users but in our test machines it just wont load the start menu... i must be missing something somewhere, which is why i am wondering what the best creation process is.

[ITGURU]

Login times here:

First time login with new roaming profile preparing windows: 30 seconds - HDD

next login using previously created profile - 15 seconds - same pc.

windows 10 education build 1703 x64 4gb ram,