[2004, 20h2] Can't sign you into your account

[jmoss]

Good morning all.

 

We have been having this issue now for a good few weeks. Staff are getting logged in with temporary profiles, causing a pop up to appear saying, "We can't sign into your account". This issue has been causing all sorts of issues as staff cannot access their local profiles.

 

This issue came about when we switched staff over to local profiles instead of roaming profiles. So far, the only temporary fix we have been able to find is going into the staff members AD account, adding a link back to a roaming profile, logging them in, removing the link on AD, then signing them out and in again, however it seems to be random how long this fix lasts. Argh!

 

Any help resolving this would be greatly appreciated as this issue is becoming a plague to us!

Edited July 29, 2021 by jmoss

[eddyc]

Good morning all.

 

We have been having this issue now for a good few weeks. Staff are getting logged in with temporary profiles, causing a pop up to appear saying, "We can't sign into your account". This issue has been causing all sorts of issues as staff cannot access their local profiles.

 

This issue came about when we switched staff over to local profiles instead of roaming profiles. So far, the only temporary fix we have been able to find is going into the staff members AD account, adding a link back to a roaming profile, logging them in, removing the link on AD, then signing them out and in again, however it seems to be random how long this fix lasts. Argh!

 

Any help resolving this would be greatly appreciated as this issue is becoming a plague to us!

 

When you removed all of their paths from AD, did you clean up all of the local machines and the local copies of the old networked profiles first? If not, the local profile will have some references to the old networked profile within it.

 

eddyc

[jmoss]

Yes, clearing out the profiles will sometimes prevent the error from appearing, but not in all cases. It will appear on brand new profiles, so we are looking at GPOs that may be causing it, as the event viewer also confirms it is looking for a roaming profile. However, we have not been able to find anything yet that appears to be forcing windows to look for a roaming profile.