Jump to content

Disgruntledtech

Members
  • Content Count

    5
  • Joined

  • Last visited

Profile Information

  • Location
    USA
  1. I got the custom install working. Disregard previous post
  2. Working in a 24/7 environment that doesn't have IT staffed around the clock. Getting the OK to make users reboot, and rebooting the servers outside of windows update downtime is like pulling teeth. If we dont force the users to reboot after the upgrade, then they wont. We've been transitioning for a while now, but its a slow process. For v5 we're using ERAv5. We have no v6 at this point, so all of the rest of our clients are on v7 and we use eset management center for that. Can you link me an article to create the custom package fix for ERA? I've only created the initial default install so far.
  3. we have a lot of pcs and a few servers still running 5. Is there a way i can run a query somehow to figure out which PCs have a jacked up eset installation? Some PCs are fine..i guess they didnt reboot. I've come across 2 servers that i know have not been rebooted(checked uptime to make sure) yet the install is still screwed up on them. Only 1 of my users has called me so far to let me know that they're seeing error messages from windows action center that AV is not installed. I know i have a lot more users than that where the users just arent reporting or noticing their install is now bad. We have way too many pcs/vms/servers for our team to go through them one at a time.
×
×
  • Create New...