1803 very slow first logon

[ADMaster]

I'm testing 1803, I have two VMs with identical specs, same host, same physical disk, same OU.

I noticed in 1709 the very first logon after an image is slower then the rest, I don't know if its still downloading content or what.

1803 takes 10+ minutes to logon for the first time. They are not exactly scientific and some seam to be contrary, but here are my tests.

I repeated the test twice by reverting to a snapshot and rebooting.

 

Anyone else seeing these login times.

 

TEST 1
1709 first logon first boot 2:13.63
1803 first logon first boot  10:41.77
1709 subsequent 20.53
1803 subsequent 24.56
1709 new user second user logon after boot 47.48
1803 new user second user logon after boot 1:09.7
1709 new user after reboot 45.60 
1803 new user after reboot  49.59
TEST 2
1709 first logon first boot  2:00:13
1803 first logon first boot 11:12.18
1709 subsequent 14.66
1803 subsequent 45.08 
1709 new user second user logon after boot  37.15
1803 new user second user logon after boot  1:08.81
1709 new user after reboot 49.15
1803 new user after reboot  28.94

Edited November 27, 2018 by vikpaw
user request to correct typo

[gaz350b]

My guess is a driver issue probably something to do with intel graphics and a program failing to launch and hits a 10 minute timeout. I’ve seen this on 1709. Might have been 1703 not sure....

 

As for the 1st time after a reimage I’m going to say it’s probably creating the default profile.

Edited June 27, 2018 by gaz350b

[alfatec]

What profiles are you using and how are you making them? I have 1803 as a fresh image and first login is about 20 seconds, second logon is about 5 seconds. I use local profiles.

[Rawns]

Are you using roaming profiles?

 

We are seeing an issue currently on 1803 where users have roaming profiles and when logging on/off, their Local and LocalLow folders are being synced to/from the server as well as the Roaming folder. The Local and LocalLow folders should not be synced but for some strange reason we've yet to identify, they are causing slow logon/logoff times.

[alfatec]

I thought roaming profiles were no longer recommended for Windows 10. Mandatory or Local or UE-V.

[ADMaster]

I have local profiles and everything is done during OSD.

 

I did notice one drive wasn't getting removed properly so I'm imaging again and will give it another go.

 

My process...

standard OSD format apply wim etc.

run customization scripts, branding, startup repair, pc reset, 3d objects, onedrive, start layout, file associations, remove apps, consumer experience, edge icon, chrome first run, defender first run, print drivers.

 

Some of those scripts such as chrome and defender first run modify the default ntuser.dat file.

Then I install software.

Adobe reader, chrome, drive fs, vlc, office, lanschool, enable cred guard, June CU and then gpupdate.

 

I'm running the image again without the June CU and office to cut time. I should be able to post results within the hour.

 

Thanks,

[ADMaster]

I should probably break this thread off, but I’m having trouble getting one drive to remove in 1803.

Onedrive doesn’t seem to work, but the icon is still in the start menu.

 

The method that has worked for the last several versions involves a few reg keys and adding the onedrivesetup.exe /uninstall command to the runonce key.

I tried calling the uninstall from a run command set, but it erred.

I also tried calling it through pdq yesterday and it returned an error code, but the icon was gone. I didn’t get a chance to test the time, but it seemed faster.

 

I just did another image with the pdq method and the icon is there and took 10 min for the first admin login.

 

I don't know if this is part of the problem or something separate.

 

Thanks,

[reprised]

Hi ADMaster,

 

Did you ever resolve the issue with slow initial login after sccm deployment? I'm deploying Win 10 1803 and have exactly this problem. The first user that logs in takes about 10 minutes to log in but any subsequent logins by other users are pretty quick.

[ADMaster]

I've stuck with 1709 this last year. I plan to test 19h1 this summer after it hits vlsc. I read in another thread it sped up logon times.

I also think part of my problem was modifying the default ntuser.dat file. There are some changes in programs / GPOs that may mean I don't need to do that to achieve the same result.