[1703, cu] Local profile blank, no roaming profiles

[LemonEntry]

Two staff have this morning come to the office with laptops that have blank local profiles, despite being in use since September. Desktop contents, web history, Outlook profile, tile preferences all gone. I've not seen this before without it being at my behest! Both state Friday afternoon as the last time it was working, with one discovering the issue Saturday morning, the other this morning after not working over the weekend. Updates not a factor.

 

Anyone know where I can start looking for solutions? I'm working through System and Application event logs, and nothing in the User Profile Service log aside from normal information entries.

 

Edit: Windows Defender AV, nothing special.

Edited June 18, 2018 by LemonEntry

[Steve21]

What AV do they use? I know a couple of people had the problems with Avast/AVG when doing the last April update it wipes bits

 

Steve

[LemonEntry]

Windows Defender. Nothing there, either.

[Oaktech]

Time and Date OK? Do you have a GPO profile deletion set up that could have been fooled by a clock wobble?

[LemonEntry]

Staff laptops should be specifically excluded from local profile deletion, but there is such a policy in place. I'll check the GPO links... Good suggestion!

 

Edit: Not that. Profile deletion is applied to only student laptops and ICT suites. Staff laptops have "Comp > Admin Temp > System > User Profiles > Delete older than X days" specifically disabled by another policy.

Edited June 18, 2018 by LemonEntry

[witch]

Seems an odd suggestion given that their local profiles have gone, but have you tried actually deleting their local and roaming (or whatever you use) profiles, restarting and see if they rebuild them?

[LemonEntry]

Seems an odd suggestion given that their local profiles have gone, but have you tried actually deleting their local and roaming (or whatever you use) profiles, restarting and see if they rebuild them?

 

The policy is already rebuilt, but blank. They've lost planning that was stored on the desktop, which is all I'm worried about. I still would like it to not happen to anyone else!

 

(Staff already know not to store things on the desktop; I'm not on the hook. Just trying to avoid derailing into a talk about following policy... I'm only interested in resolving the technical issue!)

Edited June 18, 2018 by LemonEntry

[Oaktech]

The policy is already rebuilt, but blank. They've lost planning that was stored on the desktop, which is all I'm worried about. I still would like it to not happen to anyone else!

 

(Staff already know not to store things on the desktop; I'm not on the hook. Just trying to avoid derailing into a talk about following policy... I'm only interested in resolving the technical issue!)

 

Now might be the time to redirect the desktop - up to you whether you force a mandatory desktop they can't change or continue to allow access.

[LemonEntry]

Now might be the time to redirect the desktop - up to you whether you force a mandatory desktop they can't change or continue to allow access.

 

Well yes, I'd very much like to do that, but have been vetoed by SLT (I'm all CYA on this, data stored on the desktop is totally not my problem if it disappears, regardless of reason). I'd just like to know why it happened now, not when we pushed 1703, or when we installed the February updates, or whatever else may have caused it, and why it's only these two. Comparing the logs is going to be a chore... Just wondered if anyone had seen something like it and had an idea of a reasonable starting point for diagnosis.

[LemonEntry]

Just a quick update to demonstrate my idiocy... The policy to not delete profiles was disabled, hence they disappeared.

 

[Oaktech]

Just a quick update to demonstrate my idiocy... The policy to not delete profiles was disabled, hence they disappeared.

 

 

Nailed it...

 

Seriously though, we all do stuff like that from time to time. I couldn't work out why one of our windows tablets just wouldn't pick up a load of settings. Did all kinds of analysis on it. Realised after a couple of days that I hadn't moved it from the Build OU to the production OU.