Jump to content

dsmith6

Members
  • Posts

    5
  • Joined

  • Last visited

About dsmith6

  • Rank
    Newbie
    Newbie

Profile Information

  • Gender
    Not Telling
  • Location
    USA

Recent Profile Visitors

506 profile views
  1. I see that you got it working... Here is our PDQ settings for future reference.
  2. The new version looks to have fixed the error I was getting. Thanks
  3. I did see the new version (6.5.2107.1) for download on the website. I also checked to see if the All In One installer version (6.5.2107.1) was available on Remote Administrator, but it was still the older version (6.5.2094.0). I'll check again Monday.
  4. Hello all, Has anyone experienced an unexpected return code of 5013 during the install of the ESET Endpoint Antivirus 6.5.2094.0 All In One installer? ESET installs as part of our OS deployment using MDT. I have no issues with Win7 or Win10 1607 Deployments but get the 5013 error with Win10 1703. ESET starts to install and then does a Rollback at the end of the install. What's really interesting, is after the rollback and error, the ESET software is installed on the client and is working. Any feedback would be helpful. Thanks, Dave
  5. That fixed our problem also. ERA_Installer_x64_en_US.exe --silent --accepteula --avr-disable I can now deploy this with our PDQ software silently. Testing this out with our MDT Server as I type this.
×
×
  • Create New...