Follow

After installing KES on machines where Windows roaming profiles are in use, user profiles fail to load when user logs in and the user gets a temporary profile. Why does this happen?

KB#:  KKB000417

QUESTION

After installing KES on machines where Windows roaming profiles are in use, user profiles fail to load when user logs in and the user gets a temporary profile. Why does this happen?

ANSWER

This was tracked down to the use of "Scan for Tracking Cookies" in the Resident Shield settings within the security profile.

Cookies are stored within the user profile and if Resident Shield tries to remove / disinfect them as the profile loads, it prevents the profile from loading successfully

Possible resolutions include: -
- uncheck "Scan for Tracking Cookies" setting in Resident Shield
- exclude Temporary Internet Files directory in roaming profile configuration (refer to Microsoft documentation for details)

MORE INFORMATION

See Microsoft documentation for further information about roaming profiles

http://technet.microsoft.com/en-us/library/bb726990.aspx

APPLIES TO

Kaseya Endpoint Security
Microsoft Windows Server (all versions)

 

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request

0 Comments

Article is closed for comments.