ash77

Just to let you know, the other terminal server got it's update to 2099.7 through the regular channel. All is working well, profiles are removed nicely at logoff. I think you can mark this as solved. To bad @krab is not responding in his own thread.

Hi @JozefG I posted this information earlier and assumed you needed other information and could only think of the Server OS version that was missing, sorry. ESET Management Agent 10.0.1126.0 ESET Server Security 10.0.12014.0 Detection Engine 28365P (20231207) Modules status Updated That said, I did another couple of tests and it seems like it is working now. The cached copy of the profile is being removed at logoff. I guess I was convinced the server was rebooted after the update of the Configuration Module, guess not. I'll keep an eye on it for a couple a days and report back in the coming week.

Windows 2016 Standard

Correct

Configuration module is version 2099.7, this should be the fixed version? Configuration module;2099.7;5-12-2023 Just did a quick test and the local profile folder of a test user is not removed and the same file is still present on the server.

Hi @Peter Randziak, I got version the following version installed on the server with the pre-release policy: ESET Management Agent 10.0.1126.0 ESET Server Security 10.0.12014.0 Detection Engine 28365P (20231207) Modules status Updated The other servers have the same but without the P trailing the Detection Engine version. Does this mean the pre-release policy is working? Where can I find the version of the Configuration module on the server?

Can I switch to pre-release for one server? Created a new policy and the configuration for that server states pre-release. But still no updates found. In de admin section I can switch to pre-release, but I think that will switch the release branch for all system.

Any update on this?

Hope this will be fixed soon, have to reboot server and clean-up local copies of profiles every other day to keep everything running smoothly. At logon windows will create a %username%.001 folder for the users profile, but some third-party applications and printdrivers will run into problems having a dot in the foldername.