Login speed (or lack of)

[gshaw]

I don't think there's a dedicated thread for this so thought I'd make one to try and get some feedback from others regarding logon times on Windows 10 images. So far it's been pitiful on our test machines, anything from 30 seconds to more than 60 to set up a new user profile on a shared device (Surface 3, Dell Venue 11 Pro, VM)

 

In a shared use scenario that's going to give a very poor user experience, especially with Chromebooks booting in 10 seconds (OK, different product, web only etc etc but users don't really care about that, just how long it takes for the kit to be ready to use).

 

I've heard LTSB is better but we'll need to build a few machines to test, likewise I wonder if the stripped down images some have been building helps too as less apps have to be provisioned in the first-run process.

 

Would be very interested to hear of the results others have had, some useful info would be:

 

• Windows 10 Edition
  
• Windows 10 Build Number
  
• Default image or customised with apps removed?
  
• Time taken for a new user to log in, from clicking login button to seeing the desktop
  
• Hardware used (if there's a wild difference in results between different kit)
  

Edited January 7, 2016 by gshaw

[Oaktech]

The only test machine I've done so far boots in about 40 seconds and first-logs-in wired in about 30 seconds and wirelessly in about 45.

 

It's an HP 2560p i5with 4gb ram and an HDD. It's a custom LTSB image with all non essential apps removed.

 

Printers seem to be the killer at the moment, as soon as I add any printer it immediately adds 20 seconds to the login.

[Fontayne56]

How big are your default profiles i'm struggling to get mine under 250mb !!

[Oaktech]

How big are your default profiles i'm struggling to get mine under 250mb !!

 

Students are getting the standard mandatory profile and it's 86mb. Staff profile, is about 180mb.

[win]

Printers seem to be the killer at the moment, as soon as I add any printer it immediately adds 20 seconds to the login.

 

i found the exact same problem with the HP universal driver. When using a different printer e.g. brother the login speeds improved alot.

[Michael]

One small tip I can offer - if creating a mandatory profile, copy it to your local C: drive, say C:\Users\Win10 before capturing.

 

Everyone else can use standard roaming profiles from your file server(s).

[psydii]

Windows Performance Analyser is your friend.

 

WPT: Updated version of “Windows Performance Toolkit” from Windows 10 Technical Preview ADK or SDK - The troubleshooters and problem solvers... - Site Home - TechNet Blogs

The Windows 7 Boot Process (sbsl) - TechNet Articles - United States (English) - TechNet Wiki

 

 

@jeffstokesmsft may be interested in this or know colleagues who are tracking such things.

[gshaw]

No mandatory profiles on our machines. The Win 10 devices are mainly for staff right now so literally just creating a new local profile with domain login. Edited January 7, 2016 by gshaw

[juls]

• Windows 10 Edition - Enterprise
  
• Windows 10 Build Number - RTM 10240
  
• Default image or customised with apps removed? - Customized all default apps removed - due to sysprep error (will remove all of them anyway)
  
• Time taken for a new user to log in, from clicking login button to seeing the desktop - 40 seconds unfrozen, with deep freeze and the computer frozen the time increases to about a minute.
  
• Hardware used (if there's a wild difference in results between different kit) - i5, 7200rpm HD, 8gb ram, and the model is a Lenovo m93z.
  
• User profile size - Default is 220mb (made a lot of mklinks to transfer adobe data and other various programs out of appdata to another location)
  

 

 

Also on our network we are in the process of upgrading our DC's to 2012 r2. The logon speed was timed connected to our 2008 DC's and the w10 computer receiving all policy that a w7 would get.

 

Windows 7 Logon times are about the same with the profile size being around 180mb. We have about 10 GPO's being applied at logon.

 

I've also noticed first logon after deployment takes about 5 minutes or more to logon to local admin.

 

Our group has been contemplating waiting on going to 10 because of various issues we have experienced with sysprep and peripheral compatibility.

Edited January 7, 2016 by juls

[Fontayne56]

In the user App Data Cortana is 41mb !!

/Appdata/Local/Packages/Microsoft windows.Cortana ........ Any way of scaling this down a bit !! ??

 

Also In ....

 

\Appdata\local\Microsoft\windows\webcache is 42.mb and in the same place Notifications are 35.8 any of scaling these down ?

 

Cheers

 

Ryan

[psydii]

Those locations should not be roaming.

[Fontayne56]

Its still copied when a new user is logged on .... ???

[juls]

Yes it is if its included in the default profile.

[Fontayne56]

So i need to scale these entry's then any help appreciated.

 

 

In the user App Data Cortana is 41mb !!

/Appdata/Local/Packages/Microsoft windows.Cortana ........ Any way of scaling this down a bit !! ??

 

Also In ....

 

\Appdata\local\Microsoft\windows\webcache is 42.mb and in the same place Notifications are 35.8 any of scaling these down ?

 

Cheers

 

Ryan

[psydii]

I'd start here: https://technet.microsoft.com/en-us/library/mt637066(v=vs.85).aspx

 

Also I'd use the Windows performance analyser to check just how long it was taking to create/copy those files and folders.

 

Microsoft has in the past taken particular effort to optimise the boot/login process.. so I would be surprised if a large file copy for a feature on-critical feature was really 'blocking'.