eab 21 Posted March 11 Share Posted March 11 (edited) We are trying to figure out what the official default policies are for the ESET Endpoint products. Starting with Windows, we are using the ESET Endpoint Security client software, and some of our PCs have 4 applied policies: While other PCs have 3 applied policies: Meanwhile, these are the policies offered by ESET Protect: And this one is listed under Custom policies: Which of these policies is currently the official default for ESET Security Endpoint on Windows? Edited March 11 by eab Quote Link to comment Share on other sites More sharing options...
Administrators Marcos 5,082 Posted March 11 Administrators Share Posted March 11 The only policy applied by default is the auto-update policy. Here is a screenshot taken from a freshly deployed virtual appliance: Quote Link to comment Share on other sites More sharing options...
eab 21 Posted March 11 Author Share Posted March 11 (edited) Are you using the same client software? (we are using ESET Endpoint Security 11) If so, why is it that we have this 'Common features' policy set by default? And, as you can see in the screenshots, we don't even have any 'Auto-updates' policy. 🤷♂️ What's even more bewildering is that the 'Common features' policy shows on the PC info (screenshots above) as being disabled (grayed out) with the status 'Product not installed'. Edited March 11 by eab Quote Link to comment Share on other sites More sharing options...
Administrators Marcos 5,082 Posted March 11 Administrators Share Posted March 11 I assume that the default auto-update policy was unassigned from the All group and then a new auto-update policy was created by an administrator and assigned to "All" like in my test case (I didn't unassign the default policy, hence there are two): Also the lable "Product not installed" is a known visual bug which occurs when you manually add a common features policy. The default auto-update policy displays "Actual" in the Status column. Quote Link to comment Share on other sites More sharing options...
eab 21 Posted March 11 Author Share Posted March 11 (edited) This is really confusing. I never manually set this 'Common features' policy, and I cannot locate any policy named 'Auto-updates' either. We used to host ESET Protect on-site, and then we migrated to the Cloud-based ESET Protect. Is there any way to completely reset all policies to the "default"/"original" state? The only official documentation containing a list of policies for Windows ESET Endpoint Security that I can find is this one for on-prem ESET Protect: https://help.eset.com/ees/11/en-US/how_apply_policy.html?how_apply_policy.html ... and it doesn't say anything about an anto-update or 'common features' policy. It seems like 'Common features' is not even a policy, but a policy group. All policies inside are locked with 'Managed by ESET Protect' appearing when you hover over with the mouse cursor. Only the very first one, 'Enable product auto-update', is assigned, and it's assigned to the 'All' computer group. This must be the equivalent of your 'Auto-updates' policy. Edited March 11 by eab Quote Link to comment Share on other sites More sharing options...
Administrators Marcos 5,082 Posted March 11 Administrators Share Posted March 11 I've checked ESET PROTECT and it uses the very same default policy. Other policies must have been selected from the list of built-in policies and assigned to groups or clients. It is possible that the audit log contains information about changes in policy assignments. Quote Link to comment Share on other sites More sharing options...
eab 21 Posted March 12 Author Share Posted March 12 (edited) The only difference seems to be the 'Policy Product' name - you have 'Auto-updates' and I have 'Common features'. The 'Policy Name' is identical. This is what the settings for my 'Enable product auto-update' policy looks like: This policy should work for both the Windows and Linux ESET Endpoint products which we use: For our Linux PCs it shows up correctly: Whereas for our Windows PCs it shows up as disabled with the 'Product not installed' message: One thing I did notice was that the 'Parent Name' for the policy in Linux is 'Linux Computers', whereas for the policy in Windows its 'All'. Is this 'Parent Name' column referring to the Computer Group that the policy is assigned to? Because, if so, that's wrong - the policy is assigned to the 'Windows computers' Computer Group, and not to 'All': Edited March 12 by eab Quote Link to comment Share on other sites More sharing options...
eab 21 Posted March 13 Author Share Posted March 13 On 3/11/2024 at 2:30 PM, Marcos said: I assume that the default auto-update policy was unassigned from the All group and then a new auto-update policy was created by an administrator and assigned to "All" like in my test case (I didn't unassign the default policy, hence there are two): Also the lable "Product not installed" is a known visual bug which occurs when you manually add a common features policy. The default auto-update policy displays "Actual" in the Status column. Could you please show me what the settings are for your 'Enable product auto-update' policy? Quote Link to comment Share on other sites More sharing options...
Administrators Marcos 5,082 Posted March 13 Administrators Share Posted March 13 10 hours ago, eab said: Could you please show me what the settings are for your 'Enable product auto-update' policy? I'm sorry but I don't understand your question. Perhaps the best course of action would be raising a support ticket. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.