-
Posts
61 -
Joined
-
Days Won
2
damtechmatt last won the day on July 17
damtechmatt had the most liked content!
About damtechmatt
-
Rank
Newbie
Profile Information
-
Location
U.K.
Recent Profile Visitors
1,254 profile views
-
Cedric_B reacted to a post in a topic: Windows Defender - Vulnerability & Patch Management
-
Not sure thats correct. The versions are for Agent. Not Protect.
-
-
Hi. When upgrading the agent in Protect Cloud, the link for the release notes is showing the wrong information URL: repository.eset.com/v1/com/eset/apps/business/era/agent/v11/11.3.1091.0/agent_x64.msi.changelog.html URL states 11.3 which is the correct version, but the release notes are still explaining 11.0.503.0
-
utilizedsynonym reacted to a post in a topic: Protect Cloud Interface Changes
-
Leon0815 reacted to a post in a topic: Protect Cloud Interface Changes
-
Glad to see that the Worst Functionality Problem is coming back (again) Is there an official place to suggest feedback for the portal? Little things like 'Switch Power' really should be 'Power Options'. Things like that
-
damtechmatt reacted to a post in a topic: Protect Cloud Interface Changes
-
Also experiencing the disabled Actions button. Using the 'Advanced Filters' is more clicks just to get the same information that was readily visible. Doesn't have to be a permanent column, but at least let us choose if we want it!
-
Is there anyway to see a full email log thats gone through ECOS I've had a client ring this morning to say that EES has found and removed a threat in Outlook (Great, doing its job), but im wondering why ECOS didnt pick it up first?
-
DavidFainshtein reacted to a post in a topic: Protect Cloud Interface Changes
-
Yeah. Its gone back to the 'new' version for me too!
-
Eset installation VIA RMM CMD
damtechmatt replied to Dough Fritters's topic in ESET Endpoint Products
We host an MSI of the agent, with a config.ini file, that gets the agent to connect to our PROTECT Cloud instance, in a folder called PreReq. Download both to a folder, and run the MSI for the agent. The installer will check for any config files, and auto use them, so you dont need to specify them in any parameters. Once it shows up in PROTECT Cloud, we install the right product for the user, with the appropriate licence, then move the device to the right folder. You could have your script download the MSI for your protection product and install it too, and use the parameters to auto licence it, but we dont need that ourselves. EG: msiexec /qn /i ees_nt64_enu.msi ACTIVATION_DATA=key:AAAA-BBBB-CCCC-DDDD-EEEE -
Looks like whatever changes were done have been reverted thankfully! The Worst Functionality Problem column is back. @Marcos Whilst I appreciate if there are multiple issues, it cant show them all, thats what the number icon is for. However removing it completely was not the solution, and hopefully its back for good.
-
SteffenK reacted to a post in a topic: Protect Cloud Interface Changes
-
DavidFainshtein reacted to a post in a topic: Protect Cloud Interface Changes
-
Anyone?
-
Hi Has there been an update to Protect Cloud overnight. All the columns are mixed up, and when I go into 'Attention required' or 'Security Risks' it no longer tells you what the problem is, and I cant see a column to add back in to show it?!
-
Duplicate PC entries in ESET Protect console
damtechmatt replied to Panagiotis Goudas's topic in ESET PROTECT
Yes. If you delete a machine from the console, it will ask if you want to deactivate it too, which will reduce your licence count. -
One ESET Customer - Multiple 365 domains on ECOS
damtechmatt replied to damtechmatt's topic in ESET Cloud Office Security
Thank you. Gave it a go this morning and yes, working great! One ESET Customer with all the ECOS licences. Three 365 tenants, sharing that licence bundle. Working great! -
damtechmatt changed their profile photo
-
TLDR: Can I link multiple 365 tenants to a single ESET Protect Complete customer? I have a customer that's a single Protect Complete customer, but has multiple 365 tenants (for reasons) Can I keep them as a single ESET customer, but link their multiple 365 tenants to that one ESET customer? Or am I best to split their ESET licence into the various 365 tenant companies?