Windows 10 Logon Times

[Joanne]

Righty... I've got an image I'm happy with.

 

It takes 1:32 for initial logon. 4 seconds for subsequent. 35 seconds after reboot.

 

What are your times and how did you get them down? I'm pretty sure I've got the correct GPOs set for the initial logon thing... but maybe not.

Edited March 15, 2016 by Joanne

[Michael]

If the first logon involves creating the profile, that's about right.

[Joanne]

Yeah it will be. Suppose it isn't much different on Windows 7.

[thimon]

24 seconds for initial login on an SSD and an old AMD Athlon x2, initial logon animation disabled via GPO and using Enterprise LTSB edition.

[Michael]

Disabling the logon animation does exactly that - disables the animation, it doesn't speed things up. I actually think it's better if the end user can see something's happening/changing, rather than nothing visible at all.

 

You also have to consider the environment you're in and whether you're wired or wireless, it makes a big difference.

 

On my own personal notebook with an i5 CPU, 16GB mem, 1TB SSD, it takes less than 15 seconds to switch on from cold and logon.

[thimon]

Disabling the logon animation does exactly that - disables the animation, it doesn't speed things up. I actually think it's better if the end user can see something's happening/changing, rather than nothing visible at all.

 

I have actually found that it does speed up the login times here. I've tried with the same user with the setting enabled and disabled and they log in a lot faster with the animation disabled (I deleted the profile afterwards each time). And in terms of nothing being visible at all, when the animation is disabled it's just like when a profile is being created in Windows 7, it states that it's preparing your desktop, or something similar

[Michael]

You'd be surprised how impatient some end users can be! As far as I'm aware, the GPO description mentions nothing of speeding up logon times to the best of my knowledge.

[gshaw]

First login profile creation is awful, subsequent ones are lightning fast

[Joanne]

I have the animation disabled... although after looking the machine wasn't in the correct OU for that policy! D'oh. No SSDs here.... YET!

[Winner]

I'm trying to optimise first logon at the moment, I've found that disabling the App Readiness service can make a big difference BUT you won't get any modern apps including Edge. If you're intending to use IE11 or Chrome as your default browser then it's worth giving it a try.

[thimon]

I'm messing around with the LTSB version, no Edge with that version anyway

[Joanne]

Yeah I'm on LTSB too.... no candy crush or xbox app to worry about!

[cadams10]

Are these login times for local or roaming profiles?

[Joanne]

mine are local with redirected folders

[timbo343]

LTSB i feel is the way to go. I think login times will be dramatically reduced as its not populating the start menu with the "Silly Apps".

[thimon]

The problem is you cannot install Edge, not from what I've seen. Not an issue at the moment as we all prefer IE here, but maybe further down the line we would want the option to install Edge...

[timbo343]

The problem is you cannot install Edge, not from what I've seen. Not an issue at the moment as we all prefer IE here, but maybe further down the line we would want the option to install Edge...

 

Ive not properly looked but isnt it a "feature" that can be turned on or off?

[thimon]

Ive not properly looked but isnt it a "feature" that can be turned on or off?

 

The LTSB version of Windows comes with Edge completely removed.

[Michael]

You can disable Edge with AppLocker for everyone's reference.

[Winner]

Hi Michael, Just testing this and it works great. In your environment have you used AppLocker to block all modern apps without any issues? I'm thinking of the obscure stuff that gets generated in the users appdata\local\packages folder such as parental controls, xbox game callable UI etc.

[Michael]

Most yes, apart from the likes of Photos (top of my head).

[CJS-90]

I'm at approximately 45 seconds on an old Dell 755 with Core 2 Quad, 8GB and a 128GB SSD.

 

Perfectly ample for me

[Arthur]

How to reduce your Windows 10 first logon time by circa 66%

 

 

http://appsensebigot.blogspot.com/2016/04/windows-10-part-8-speeding-up-first.html

 

We also studied the logon process using Lakeside SysTrack, and found that the biggest cause of slowdowns and alerts on our Windows 10 deployments was due to huge disk I/O, normally around the logon period but also within the user session itself. From this we've extrapolated the conclusion that Windows 10 is optimized for SSDs, and if possible, you should deploy it on systems where the OS drive is solid state. This tallies with what I've been hearing, that Microsoft based their operating system development around three large customers from the US who have been using SSDs as standard for four or five years now.

[gshaw]

Glad someone has done this investigation, will have to give the Default Profile a go as we're pushing a custom Start Menu at the moment via MDT.

 

As far as removing the Modern Apps has anyone done this as a step in MDT? Would prefer not to mess with the source media if I can help it and likewise would like to deploy images direct from ISO rather than creating reference images as we did in the Win7 days.

 

Rather poor that MS haven't had a TechNet team doing the research and providing guidance. Same with the way there's never been any clear guidance on CBB vs LTSB and techs are left to figure it out for themselves.

Edited April 7, 2016 by gshaw

[Arthur]

As far as removing the Modern Apps has anyone done this as a step in MDT?

Here's a good PowerShell script for removing apps in an MDT task sequence...

 

www.scconfigmgr.com/2016/03/01/remove-built-in-apps-when-creating-a-windows-10-reference-image

 

In this script, I’ve taken another approach compared to those created by other community members. Since new versions of Windows 10 will emerge 2-3 times a year, I don’t want to update a script to support the new version that might incorporate new Universal Apps. Instead, I’m white-listing Universal Apps that I want to keep (like the Calculator), and remove everything else. In my experience, this should lead to the least amount of maintenance and that’s what I’m all about.

 

# Get a list of all apps
$AppArrayList = Get-AppxPackage -PackageTypeFilter Bundle | Select-Object -Property Name, PackageFullName | Sort-Object -Property Name

# Loop through the list of apps
foreach ($App in $AppArrayList) {
   # Exclude essential Windows apps
   if (($App.Name -in "[color="#FF0000"]Microsoft.WindowsCalculator[/color]","[color="#FF0000"]Microsoft.WindowsStore[/color]","[color="#FF0000"]Microsoft.Appconnector[/color]","[color="#FF0000"]Microsoft.WindowsCommunicationsApps[/color]","[color="#FF0000"]Microsoft.WindowsSoundRecorder[/color]")) {
       Write-Output -InputObject "Skipping essential Windows app: $($App.Name)"
   }
   # Remove AppxPackage and AppxProvisioningPackage
   else {
       # Gather package names
       $AppPackageFullName = Get-AppxPackage -Name $App.Name | Select-Object -ExpandProperty PackageFullName
       $AppProvisioningPackageName = Get-AppxProvisionedPackage -Online | Where-Object { $_.DisplayName -like $App.Name } | Select-Object -ExpandProperty PackageName
       # Attempt to remove AppxPackage
       try {
           Write-Output -InputObject "Removing AppxPackage: $AppPackageFullName"
           Remove-AppxPackage -Package $AppPackageFullName -ErrorAction Stop
       }
       catch [system.Exception] {
           Write-Warning -Message $_.Exception.Message
       }
       # Attempt to remove AppxProvisioningPackage
       try {
           Write-Output -InputObject "Removing AppxProvisioningPackage: $AppProvisioningPackageName"
           Remove-AppxProvisionedPackage -PackageName $AppProvisioningPackageName -Online -ErrorAction Stop
       }
       catch [system.Exception] {
           Write-Warning -Message $_.Exception.Message
       }
   }
}