satellite360

Good to know. I opened a ticket but yet to hear anything back. Thanks.

Fully patched versions of Microsoft Office 2019 are getting flagged up as vulnerable by the ESET Vulnerabilities and Patch Management add-in. The version of Office 2019 is 16.0.10411.20011 with latest patch 1808 (Build 10411.20011). Is this correct behaviour? Thanks.

I opened a ticket and had a back and forth with support who established there was an issue communicating with ESET servers. At some point everything started working but support told me they had not made any changes so it would appear to have been a local issue though we made no network changes so I have no idea where the problem lay or how it was resolved.

Not quite sure what details you want from the task history - not seeing any mention of 'Security product' so perhaps I'm looking in the wrong place. Grateful if you could give clear instruction on where i should be looking. EES is pretty standard - we have a standard policy set on all clients but nothing unusual is set there. Anyway, I have raised a ticket as advised so hopefully I can progress via that channel. Thanks for the support.

Not sure how to confirm validity of the license - no errors showing on ESET Protect or EBA. All looks fine: I can see all the products we are paying for but only 'ESET Endpoint Security + ESET Server Security' is showing as having units installed, the newer products we we have just started paying for all showing as 0 installed. Attempting to access https://edf.eset.com returns a 404 page not found error in the web browser but I can ping it without any problem. EBA is showing one license with the various products listed below it, and no offline license files. Thanks

@MartinK - prerequisites should be good, clients are Windows 10 and 11 running EES version 11+. The following tasks: * Product Activation (Enable Vulnerability & Patch Management) - via context menu * Product activation - via ESET LiveGuard show failed for all clients that have connected. All clients show the same alerts: * ESET Vulnerability management is non-functional * ESET Patch management is non-functional Rebooting client does not solve the problem. I'm guessing it is license related but the licenses show up just fine in EBA and under ESET Protect License Management with 0/xxx users.

Thanks for the pointers @MartinK ESET Solutions is showing ' enablement in progress' for all clients - no idea how to progress beyond there, rebooting the clients has no effect. Similarly, after enabling V&PM for all clients via the Solutions wizard, none of them actually enable, so when I check an individual computer it is still showing as unenabled and licenses remains as 0/xxx units. Grateful if you could advise how to proceed.

ESET Solutions is showing ' enablement in progress' for all clients - no idea how to progress beyond there, rebooting the clients has no effect. Grateful if you could elaborate on where i can set up the 'deploy' wizard for V&PM. Thanks.

Hi all Grateful for some guidance on how to enable LiveGuard Advanced and Vulnerability & Patch Management using ESET Protect. The products are listed under License Management showing 0/xxx units and I've assigned to client devices via the relevant policies but none of the clients are picking up the changes. Clients already have Endpoint Security 11 installed. Thanks

Thank you.

Thanks - and is there any reason to keep the Rogue Detection Sensor installed or is that also redundant?

Hi I have recently migrated from a local install of Protect Server (v.9) to Protect Cloud having followed this guide: https://help.eset.com/protect_cloud/en-US/stop_using_cloud.html?cloud_migration.html All is working fine but I still have ESET Protect Server running on the local server. Is there a recommended method for uninstalling given that it is no longer in use? Thanks

I ended up reinstalling on the client which resolved the problem.

I have a client laptop that is showing as connected on both the client itself and via the Eset Business Account site (eba.eset.com/ba/devices) but the last connected time on the Protect Cloud is not updated and is showing a different software version to what is actually running on the device. Any advice on how to correct this? Thanks.

Pleased to report that upgrading to Management Agent 7.0.577.0 resolved the problem. Thanks.