Jump to content

ShaneDT

Members
  • Content Count

    154
  • Joined

  • Last visited

  • Days Won

    3

ShaneDT last won the day on November 25 2018

ShaneDT had the most liked content!

Profile Information

  • Gender
    Not Telling
  • Location
    Australia

Recent Profile Visitors

1,016 profile views
  1. Thanks Marcos. Final question that hasn't yet been answered, and is potentially pretty critical. If I upgrade the server to the latest version, will I have any issues if any of the client computers are still running an older version of the agent (all 7.0 or above, most are already 7.2)? Will they still connect OK?
  2. Marcos, you're not reading my posts. I'm talking about upgrading the server! Forget it, I'll email partner support...
  3. Hi Marcos, So you recommend go straight to the latest version using Client Task / SMC Components Upgrade? Just run it, let it finish and I guess restart the server? Nothing else to do? Will I have any issues if any of the client computers are running an older version of the agent (all 7.0 or above, most are already 7.2)? Do I also need to upgrade Apache or is this upgraded along with Components Upgrade? If not is there documented process to upgrade Apache? Are there any other components that need to be separately upgraded on the server?
  4. GregA so you have the latest version ESMC server and the latest version of the agent installed on your client computers and you're still getting the warning message? Very strange. Marcos does ESET have any idea what is suddenly triggering this warning? Clearly it's not the server or agent version that is the problem. On my own server I have this warning appearing on maybe a third of my customer computers, regardless of what version agent is installed. And nothing changed on my server or customer computers that I'm aware of that could have triggered it. It appears to be affecting a random
  5. Hi Marcos, no I'm asking about upgrading the server. Server is currently 7.0.553. So you recommend go straight to the latest version using Client Task / SMC Components Upgrade? Just run it, let it finish and I guess restart the server? Nothing else to do? Will I have any issues if any of the client computers are running an older version of the agent (all 7.0 or above, most are already 7.2)? Do I also need to upgrade Apache or is this upgraded along with Components Upgrade? If not is there documented process to upgrade Apache? Are there any other components that need t
  6. Hi ESET support. Hope everyone is well. I've started getting "ESET Management Agent is outdated" alerts on some computers this week even though the Agent on these computers is already v7.2 and most have been updated to the latest 7.2.1266. So I guess it's time to stop putting off upgrading the server. Some questions. I'll create certificate and database backups first. Are there any known issues with upgrading from 7.0.553.0 to 7.2.11.1? Should I use the Help / Update Product method or Client Task / SMC Components Upgrade or manually download the latest ESMC and do a manual upgrad
  7. Yep, but the option is and has been there in the policy settings since I've been selling ESET (circa v6). If the option doesn't work it shouldn't be there, but it really is an option that we need. Every other vendor has had automatic program updates for aeons.
  8. Campbell IT I don't know that you're understanding what your problem is. If your computers are upgraded to 7.3, they are not shutting down due to upgrading, they are shutting down due to a bug in this version that triggers a shut down after a scheduled scan. You need to go into your policy settings and turn off the scheduled scans. And as far as I'm aware the 'Program Update' policy does not and has never worked? I've never been able to get any of my endpoints to automatically update the EES software. Always have to deploy it manually from the server.
  9. Same issue with some but not all computers upgraded to 7.3.2032 with scheduled scans configured via policy in ESMC. Have had a mad scramble the last few days to get all computers on 7.3 due to the W10 2004 blue screen issues...
  10. Should I enter it with the quotations? So; "/" Cheers.
  11. What do you enter for Mac computers in the 'Scan Targets / Edit Rule' option when configuring scheduled scans in ESMC policies for Mac's? ESMC policy requires you to enter values. And it won't allow you to complete the scheduled task without entering a value. I want to configure daily In Depth scheduled scans to scan the entire computer. The equivalent Windows policy simply has a check box 'Scan all Targets'. Thanks.
  12. Sorry Peter but it's 12:30am here and I don't wish to spend hours of my time providing logs for what is a known problem! The amount of time I've wasted troubleshooting vendor problems this week is ridiculous!! I've manually installed the agent using the server assist option and installed EES using the direct download link. PITA but at least I can call it a night.
  13. This has been a known issue for months. Please someone at ESET just fix it. Several hours wasted again.
  14. Yes set to autoselect no issues with firewall. Can access repository just fine. Quite simply the servers are just tooooooooo slow!
×
×
  • Create New...