[1803, au] Slow logons - other user welcome screen

[HereIGoAgain2601]

Hi,

 

In the last week or two we are seeing very slow logons to Windows 10 clients running 1803. We have been running the OS since September and not seen these issues.

I am wondering if it's down to the cumulative updates - the latest we have installed is 2018-10 but just installing 2018-11 to see if this helps.

 

Has anybody else seen this - when the user enters their credentials it sits on the welcome spinning screen. It takes a good 5+ minutes before the other user text is replaced with their username and then the highly detailed logon messages show and logon proceeds as normal.

 

Can't see anything helpful in event viewer.

 

Thanks

[HereIGoAgain2601]

Think we have narrowed this down to the firewall blocking some IPs for Azure hybrid AD.

[Primus]

Any further info on this? We've been seeing intermittent issues on 1803 with long first logons.

[HereIGoAgain2601]

Do you use Hyrbid AD with Azure?

 

We have been using 1803 fine since September but only just started having these issues - the logon screen would stay spinning on Welcome and then eventually change the "other user" to say the username and then go onto the normal apply group policies etc.

 

We turned Hybrid AD on during October, but only just seeing issues since the end of last week.

 

We have put this rule in our firewall and seems to have solved it for now, but also come across Azure documentation for all of the subnets they use. The IPs reside in there so going to ask our provider to get the full list of subnets allowed.

 

[Primus]

No we don't but I wouldn't be at all surprised if it's trying to get out to something Microsoft based and hanging as a result - it's just another avenue for us to investigate.

[thimon]

Thought I'd ask, are you using SSD's? Have found Windows 10 takes an absolute aaage to logon with standard HDDs.

[Primus]

Yup SSDs - this is the very first logon where the local profile is created, sometimes it takes no more than 1 minute - other times it hangs and takes up to 5 minutes - pressing ctrl-alt-delete then cancel seems to get past it tho.

[Primus]

Just to revisit this, my current working theory is UE-V so I've disabled it for now.