Jump to content

Mike

Members
  • Content Count

    44
  • Joined

  • Last visited

  • Days Won

    1

Mike last won the day on June 25 2013

Mike had the most liked content!

Profile Information

  • Gender
    Not Telling
  • Location
    New Zealand

Recent Profile Visitors

636 profile views
  1. Thanks Marcos. WIll keep an eye out for that. What about ESMC client v7.0.447.0 (eg the other half of my question)? Is that OK, or does that need a newer version for compatibility with next MacOS version too? Might be worth an overview help page which has compatibility for all ESET products and lists the minimum versions that will work with next MacOS without problems. That way we can see at a glance the latest status, (eg currently wait for the next product version) and then when that product is released, it will state the exact version that is minimum required. Otherwise each time
  2. A Mac user is still getting the same warning on Eset Endpoint AntiVirus v6.9.60.0 I assumed this would be fixed in the v6.9 product line, as you said it would be fixed in the next version after v6.8 (or do you mean the v7 product line?) Equally, whilst I'm assuming that the warning is coming from Eset Endpoint, I guess there is an equal chance it is coming from the ESMC client (which is on v7.0.447.0). Any info on what are the minimum versions of both Endpoint and ESMC client are required for use with the next version of MacOS would be much appreciated.
  3. @HSW Are you talking about ESMC or Endpoint Security here? (I was referring to Endpoint Security & AntiVirus in this thread, but you raise an interesting point) I'm presuming that EES and EEA v7 will work fine with either ERAv6 or with ESMC v7, but I realised I haven't checked that specifically. Ideally at this stage I'd roll out some EESv7 test machines, whilst I remain on ERAv6. I'd then look at a switch to ESMC v7 at a later date, when I have more time. @everyone else. Thanks for the input and replies so far. Makes me more confident to invest the time in trialli
  4. As a small charity, we have very limited resources to test new products internally. Therefore I was wondering how other are finding v7 of EES and EEA? (ideally I'd have asked via a poll, but that isn't allowed for mere mortals!) So how about this for a poll substitute. What is your experience of Endpoint v7 products? Great. (Using it with no problems) OK. (Using it with only minor problems.) Tested. (Tried it, but having major problems, so not ready for widespread use.) Not tested yet. Other... Thinking you can just reply with the number that ma
  5. Awesome. That info is great. Sounds like the product we've been waiting for. Can't wait to test drive it! Thanks for sharing! Mike
  6. Thanks. That'll save me having to find it by nosing around again! (my situation is the same, in that the current default is the non-routeable sever name instead of externally routeable url, so now I'll be able to fix that forever now!) Thanks. Mike
  7. Perfect! I fully understand those dates are best guess right now, but that is really useful guidelines which will help me plan! Thanks. In terms of functionality, are we basically talking a cloud version of ERA? (eg similar functionally to local ERA install, but installed on ESET's servers as a cloud service)? Are there are known feature gaps that come with this cloud version compared to current local install of ERA?
  8. Thanks for the help! Do you mean I create two policies: One to send the settings I want (but which unfortunately locks those settings from being changed) A second less restrictive policy which I then apply afterwards which leaves the things I set in the first policy in place, but then allows local editing Is that what you mean? If so, do the two policies have to be manually set to the first policy, then after it has applied manually remove it switched to the second policy? (Or, can I apply both at once using the policy order to set and then unlock?) Also, in the
  9. Hi, I've only recently started exploring Policies and I'm finding them confusing and too restrictive. Am I missing the point, or is there another way to set configuration for Endpoint Security & Antivirus products using ERA 6.5 but in such a way that I also allow local changes to be made as well. Currently if I set anything via the Policy (say a rule to allow Skype through the firewall - although why this doesn't just work out of the box is beyond me!), that also locks the firewall so that the user can add their own exceptions. What I want to do is set a sensible set of default
  10. Sweet. I had the same query a while ago, and no answer was forthcoming. I did nose around the SQL at the time, and saw the entry required, but chickened-out from changing it in case it messed things up. Glad to hear that this tweak works fine! Will hunt it out and see if I can change ours too. Thanks for sharing the knowledge back with us all.
  11. Even very vague and non-committed time-frames are useful. I'm in the process of moving all our stuff here out to the Cloud, which makes sense for us as we are a charity and get the cloud stuff for free. However it looks like I'm going to need to maintain an onsite server and hybrid setup just so that ERA will run! Which is a lot of admin work to maintain for that one function.... equally I couldn't contemplate managing all our users remotely without ERA, so am in a tricky situation. No point using Azure for it, as that would just cost us dollars compared to hardware onsite we already paid
  12. That would be awesome Thanks. That is exactly what I wondering... if there were settings that I should tweak to optimise my Mac user's experience of ESET! If you are able to share your policy settings I'd be most grateful.
  13. A variety of issues. Each machine different (all on v6.4.246 though): EES = Firewall blocking Skype on automatic. Rules set to allow it, but user has still since turned firewall off. (Waiting for update from user) EES = Another user had "wheel of death" and browsing issues with EES installed. Took lots of hassles to remove EES. ERA 6.5 hasn't reported home for a month. User completely fed up of ESET. (Have a remote support session with ESET tomorrow to explore.) EEA = Mac has problems with Eset for a while, but is on latest 6.4.246 and user keeps disabling to get machine working
  14. I'd be wanting to find out why they are closing EEA down. If they are having issues with it slowing their Macs down to be unusable, or other similar issues, then blocking them from turning it off might stop them from closing EEA... but it will potentially greatly increase the user's frustrations!!! And maybe even leave them unable to user their Mac. We are having various issues with Endpoint on Macs, and as a result I also find that users keep turning it off. This to me suggests there is a deeper problem with Endpoint on Macs (a mix of both EEA & EES here). I don't see these same issues
  15. My guess is that it happened because the agent is designed to be upgraded using the Remote Administration upgrade task (it is called something like that), and because it was a fresh install (even though it was installed on top of the old agent), it has been detected as a fresh computer. I can't find the instructions for updating right now, but if you hunt around the knowledgebase you should find what you are looking for. You basically run an upgrade on the Remote Administration as though you are going to upgrade the ERA server itself , but you select all the computers you want to get the n
×
×
  • Create New...