ZenWorks 2017 - Win10 - specific User Profile corruption
running ZCM2017 update 2a
Windows 10 v1809 up to date with July 2019 patches
zenworks agent version = 18.104.22.1685
Novell client version = 2 SP4 IR11
User source is eDirectory
not using roaming profiles
DLU policy - create local user, non-volatile
Imaged all of our Windows devices this summer so that they are all on the same Windows 10 version, 1809, along with the same Novell client version, and rest of our software packages.
ProblemUser logs into any machine, and after a couple additional logins (logout or restart), local profile becomes corrupt, second profile is created.
Creating a document in My Documents or Desktop will cause the profile to flake as well.
2nd profile is created on the machine for that user, which then goes through the whole new user setup process. Files on desktop/my documents are in the other profile
AnyOtherUser logs into same machine, no issues regardless of how many logins or documents.
over 1000 desktops using this new image.....
This one user is having the problem, no matter what machine they login to.
Besides getting to ZCM 2017 Update 4, any other thoughts?
anyway to cleanse user info from ZenWorks DB for a single user?
We can replicate the problem on our old image as well, the few machines that are still running it.
Re: ZenWorks 2017 - Win10 - specific User Profile corruption
The most common cause of this issue is that when a User Logs off from Windows, some process in Windows does not properly release his profile and keeps it locked even after logoff.
When the user goes to logon again, since the profile is locked Windows will generate a new Profile. (The Windows Event Viewer will clearly show these Events on both logoff and logon.)
Going forward, Windows will always now use this new profile.
ZCM is not directly related to this process, ZCM simply logs the user in, Windows itself determines if a Profile needs to be created and which profile to use.
The only time ZCM is directly involved in Profiles is when the DLU accounts are flagged as volatile. It will then delete the profile when it deletes the account.
I'd suggest trying to figure out what this user may be installing or doing different than other accounts.