Difference between revisions of "ESET NOD32"

From WPKG | Open Source Software Deployment and Distribution
Jump to: navigation, search
m
(Added XML for EES5 and ERAC, and edited notes on install packages.)
Line 27: Line 27:
 
ESET's NOD32 and ESET Smart Security products use the same management console. This tool produces packages that play nicely with WPKG.
 
ESET's NOD32 and ESET Smart Security products use the same management console. This tool produces packages that play nicely with WPKG.
  
−
Use the Remote Install tab of ESET Remote Administrator Console to build an installation package per the ESET Remote Administrator manual. Build your package to run with <code>/qn REBOOT="ReallySuppress"</code>. Once you've entered the desired configuration, use "Export to Folder or Logon Script" to export your package as <code>einstaller.exe</code>. You can then launch this file from WPKG.
+
Go to the Remote Install tab of ESET Remote Administrator Console, then choose Manage Packages from the Actions menu to build an installation package per the ESET Remote Administrator manual. Build your package to run with <code>/qn REBOOT="ReallySuppress"</code>. Once you've entered the desired configuration, use "Export to Folder or Logon Script" to export your package as <code>einstaller.exe</code>. You can then launch this file from WPKG.
 +
 
 +
To prevent communication being interrupted and the install appearing to fail, use the configuration editor to set "Windows desktop 5/Personal firewall/Settings/Postpone Personal firewall module update until a computer restart" to Yes. This is a new feature in the version 5 desktop products.
  
 
When using the ERAC package editor, make sure entering and saving your update password is the very last thing you do before exporting, as otherwise it may not end up in the package.
 
When using the ERAC package editor, make sure entering and saving your update password is the very last thing you do before exporting, as otherwise it may not end up in the package.
  
 
A reboot is required when removing NOD32 or ESS, but a reboot is not normally required on installation.
 
A reboot is required when removing NOD32 or ESS, but a reboot is not normally required on installation.
 +
 +
== Note on upgrading ==
 +
 +
It's generally advisable to use ESET Remote Administrator Console to upgrade ESS and EES, but adding upgrade stanzas to these packages may work.
  
 
== NOD32 version 3.0.695.0 ==
 
== NOD32 version 3.0.695.0 ==
Line 106: Line 112:
 
     <exit code="1641" reboot="postponed" />
 
     <exit code="1641" reboot="postponed" />
 
     <exit code="3010" reboot="postponed" />
 
     <exit code="3010" reboot="postponed" />
 +
  </remove>
 +
 +
</package>
 +
</source>
 +
 +
==ESET Endpoint Security 5==
 +
 +
The same install package works for version 4 and 5 products, but uninstall is different. Automated uninstall may not be possible with version 5 products without turning off self-defense.
 +
 +
<source lang="xml">
 +
<package id="ess4"
 +
name="ESET Endpoint Security 5"
 +
revision="1"
 +
reboot="false"
 +
priority="0">
 +
 +
  <!-- Note: for upgrades, it's recommended that older versions of the
 +
      product be removed. Upgrade stanzas should do this. For easier testing,
 +
      it might be a good idea to have separate packages for each version of
 +
      the product. -->
 +
 +
  <check type="logical" condition="or">
 +
    <check type="uninstall" condition="exists" path="ESET Smart Security" />
 +
    <check type="uninstall" condition="exists" path="ESET Endpoint Security" />
 +
 +
    <!-- Uncomment to avoid stepping on other antivirus products, as it's hard to clean up the mess when this happens. -->
 +
<!-- <check type="uninstall" condition="exists" path="Trend Micro PC-cillin Internet Security 2007" /> -->
 +
<!-- <check type="uninstall" condition="exists" path="Trend Micro PC-cillin Internet Security 2008" /> -->
 +
<!-- <check type="uninstall" condition="exists" path="Trend Micro OfficeScan Client" /> -->
 +
<!-- <check type="uninstall" condition="exists" path="ESET NOD32 Antivirus" /> -->
 +
  </check>
 +
 +
  <install cmd="%COMSPEC% /C if not exist &quot;%PROGRAMFILES(x86)%&quot; &quot;%SOFTWARE%\einstaller-x86.exe&quot; /qn">
 +
    <exit code="0" />
 +
    <exit code="3010" reboot="postponed" />
 +
    <exit code="1641" reboot="postponed" />
 +
  </install>
 +
 +
  <install cmd="%COMSPEC% /C if exist &quot;%PROGRAMFILES(x86)%&quot; &quot;%SOFTWARE%\einstaller-x64.exe&quot; /qn">
 +
    <exit code="0" />
 +
    <exit code="3010" reboot="postponed" />
 +
    <exit code="1641" reboot="postponed" />
 +
  </install>
 +
 +
  <!-- Untested but may work with EES 5 -->
 +
  <remove cmd='MsiExec.exe /qn /x{950B1859-7F95-4CCF-8674-0F843B58CCAB}' >
 +
    <exit code="0" />
 +
    <exit code="1605" />
 +
    <exit code="1614" />
 +
    <exit code="1641" reboot="postponed" />
 +
    <exit code="3010" reboot="postponed" />
 +
  </remove>
 +
 +
</package>
 +
</source>
 +
 +
=Install ESET Remote Administrator Console=
 +
 +
ESET Remote Administrator Console should be installed on management workstations.
 +
 +
<source lang="xml">
 +
<package id="erac"
 +
name="ESET Remote Administrator Console"
 +
revision="%version%"
 +
reboot="false"
 +
priority="0">
 +
 +
  <variable name="version" value="5.0.242.0" />
 +
 +
  <check type="uninstall" condition="exists" path="ESET Remote Administrator Console" />
 +
  <check type="logical" condition="or" >
 +
    <check type="file" condition="versiongreaterorequal" value="%version%" path="%PROGRAMFILES%\ESET\ESET Remote Administrator\Console\console.exe" />
 +
    <check type="file" condition="versiongreaterorequal" value="%version%" path="%PROGRAMFILES(x86)%\ESET\ESET Remote Administrator\Console\console.exe" />
 +
  </check>
 +
 +
  <install cmd="msiexec /qn /i &quot;%SOFTWARE%\eset\era_console_nt32_enu-%version%.msi&quot; ">
 +
    <exit code="0" />
 +
    <exit code="1638" />
 +
  </install>
 +
  <upgrade cmd="msiexec /qn /i &quot;%SOFTWARE%\eset\era_console_nt32_enu-%version%.msi&quot; ">
 +
    <exit code="0" />
 +
    <exit code="1638" />
 +
  </upgrade>
 +
 +
  <remove cmd="MsiExec.exe /qn /x{6E5A47E7-4E1F-4507-95D0-59F9E8BC05BD}">
 +
    <exit code="0" />
 +
    <exit code="1605" />
 +
    <exit code="1614" />
 
   </remove>
 
   </remove>
  

Revision as of 21:23, 9 October 2012

NOD32 is commercial anti-virus software. For more information see http://www.eset.com/

Install without ESET Remote Administrator

An XML still needs to be written, but here's a basic set of instructions on how it can be done via command line;

http://www.eset.eu/knowledge-base/ess-eav-specific-installation

And according to appdeploy, the uninstall should be doable via;

MsiExec.exe /I{35EB8A68-BED1-42DE-97CC-91A7DCA4A701}

Other less helpful but interesting links;

http://kb.eset.com/esetkb/index?page=content&id=SOLN2185

http://kb.eset.com/esetkb/index?page=content&id=SOLN166

http://kb.eset.com/esetkb/index?page=content&id=SOLN2227

http://kb.eset.com/esetkb/index?page=content&id=SOLN828

http://kb.eset.com/esetkb/index?page=content&id=SOLN82

Install with ESET Remote Administrator

ESET's NOD32 and ESET Smart Security products use the same management console. This tool produces packages that play nicely with WPKG.

Go to the Remote Install tab of ESET Remote Administrator Console, then choose Manage Packages from the Actions menu to build an installation package per the ESET Remote Administrator manual. Build your package to run with /qn REBOOT="ReallySuppress". Once you've entered the desired configuration, use "Export to Folder or Logon Script" to export your package as einstaller.exe. You can then launch this file from WPKG.

To prevent communication being interrupted and the install appearing to fail, use the configuration editor to set "Windows desktop 5/Personal firewall/Settings/Postpone Personal firewall module update until a computer restart" to Yes. This is a new feature in the version 5 desktop products.

When using the ERAC package editor, make sure entering and saving your update password is the very last thing you do before exporting, as otherwise it may not end up in the package.

A reboot is required when removing NOD32 or ESS, but a reboot is not normally required on installation.

Note on upgrading

It's generally advisable to use ESET Remote Administrator Console to upgrade ESS and EES, but adding upgrade stanzas to these packages may work.

NOD32 version 3.0.695.0

<package id="nod32"
 name="NOD32"
 revision="5"
 reboot="false"
 priority="0">

  <check type="logical" condition="or">
    <check type="uninstall" condition="exists" path="ESET NOD32 Antivirus" />

    <!-- Uncomment the following to prevent installation on top of these products -->
<!-- <check type="uninstall" condition="exists" path="Trend Micro PC-cillin Internet Security 2007" /> -->
<!-- <check type="uninstall" condition="exists" path="Trend Micro PC-cillin Internet Security 2008" /> -->
<!-- <check type="uninstall" condition="exists" path="Trend Micro OfficeScan Client" /> -->
  </check>

  <!-- Add install lines here to remove older antivirus products, if required -->

  <install cmd='"%SOFTWARE%\einstaller.exe" /qn' >
    <exit code="0" />
    <exit code="3010" reboot="postponed" />
  </install>

  <!-- this string may change for other versions of the product -->
  <remove cmd='MsiExec.exe /qn /x{C10D6AB8-05BB-422D-AAE3-36D6E0381487}' >
    <exit code="0" />
    <exit code="1605" />
    <exit code="1614" />
    <exit code="1641" reboot="postponed" />
    <exit code="3010" reboot="postponed" />
  </remove>

</package>

ESET Smart Security 4.2.35

<package id="ess4"
 name="ESET Smart Security 4.2"
 revision="1"
 reboot="false"
 priority="0">

  <!-- Note: for upgrades, it's recommended that older versions of the
       product be removed. Upgrade stanzas should do this. For easier testing,
       it might be a good idea to have separate packages for each version of
       the product. -->

  <check type="logical" condition="or">
    <check type="uninstall" condition="exists" path="ESET Smart Security" />

    <!-- Uncomment to avoid stepping on other antivirus products, as it's hard to clean up the mess when this happens. -->
<!-- <check type="uninstall" condition="exists" path="Trend Micro PC-cillin Internet Security 2007" /> -->
<!-- <check type="uninstall" condition="exists" path="Trend Micro PC-cillin Internet Security 2008" /> -->
<!-- <check type="uninstall" condition="exists" path="Trend Micro OfficeScan Client" /> -->
<!-- <check type="uninstall" condition="exists" path="ESET NOD32 Antivirus" /> -->
  </check>

  <install cmd='"%SOFTWARE%\einstaller-ess.exe" /qn' >
    <exit code="0" />
    <exit code="3010" reboot="postponed" />
    <exit code="1641" reboot="postponed" />
  </install>

  <remove cmd='MsiExec.exe /qn /x{751CCF7A-CFF6-4A4B-9119-D4448D87B025}' >
    <exit code="0" />
    <exit code="1605" />
    <exit code="1614" />
    <exit code="1641" reboot="postponed" />
    <exit code="3010" reboot="postponed" />
  </remove>

</package>

ESET Endpoint Security 5

The same install package works for version 4 and 5 products, but uninstall is different. Automated uninstall may not be possible with version 5 products without turning off self-defense. 

<package id="ess4"
 name="ESET Endpoint Security 5"
 revision="1"
 reboot="false"
 priority="0">

  <!-- Note: for upgrades, it's recommended that older versions of the
       product be removed. Upgrade stanzas should do this. For easier testing,
       it might be a good idea to have separate packages for each version of
       the product. -->

  <check type="logical" condition="or">
    <check type="uninstall" condition="exists" path="ESET Smart Security" />
    <check type="uninstall" condition="exists" path="ESET Endpoint Security" />

    <!-- Uncomment to avoid stepping on other antivirus products, as it's hard to clean up the mess when this happens. -->
<!-- <check type="uninstall" condition="exists" path="Trend Micro PC-cillin Internet Security 2007" /> -->
<!-- <check type="uninstall" condition="exists" path="Trend Micro PC-cillin Internet Security 2008" /> -->
<!-- <check type="uninstall" condition="exists" path="Trend Micro OfficeScan Client" /> -->
<!-- <check type="uninstall" condition="exists" path="ESET NOD32 Antivirus" /> -->
  </check>

  <install cmd="%COMSPEC% /C if not exist &quot;%PROGRAMFILES(x86)%&quot; &quot;%SOFTWARE%\einstaller-x86.exe&quot; /qn">
    <exit code="0" />
    <exit code="3010" reboot="postponed" />
    <exit code="1641" reboot="postponed" />
  </install>

  <install cmd="%COMSPEC% /C if exist &quot;%PROGRAMFILES(x86)%&quot; &quot;%SOFTWARE%\einstaller-x64.exe&quot; /qn">
    <exit code="0" />
    <exit code="3010" reboot="postponed" />
    <exit code="1641" reboot="postponed" />
  </install>

  <!-- Untested but may work with EES 5 -->
  <remove cmd='MsiExec.exe /qn /x{950B1859-7F95-4CCF-8674-0F843B58CCAB}' >
    <exit code="0" />
    <exit code="1605" />
    <exit code="1614" />
    <exit code="1641" reboot="postponed" />
    <exit code="3010" reboot="postponed" />
  </remove>

</package>

Install ESET Remote Administrator Console

ESET Remote Administrator Console should be installed on management workstations. 

<package id="erac"
 name="ESET Remote Administrator Console"
 revision="%version%"
 reboot="false"
 priority="0">

  <variable name="version" value="5.0.242.0" />

  <check type="uninstall" condition="exists" path="ESET Remote Administrator Console" />
  <check type="logical" condition="or" >
    <check type="file" condition="versiongreaterorequal" value="%version%" path="%PROGRAMFILES%\ESET\ESET Remote Administrator\Console\console.exe" />
    <check type="file" condition="versiongreaterorequal" value="%version%" path="%PROGRAMFILES(x86)%\ESET\ESET Remote Administrator\Console\console.exe" />
  </check>

  <install cmd="msiexec /qn /i &quot;%SOFTWARE%\eset\era_console_nt32_enu-%version%.msi&quot; ">
    <exit code="0" />
    <exit code="1638" />
  </install>
  <upgrade cmd="msiexec /qn /i &quot;%SOFTWARE%\eset\era_console_nt32_enu-%version%.msi&quot; ">
    <exit code="0" />
    <exit code="1638" />
  </upgrade>

  <remove cmd="MsiExec.exe /qn /x{6E5A47E7-4E1F-4507-95D0-59F9E8BC05BD}">
    <exit code="0" />
    <exit code="1605" />
    <exit code="1614" />
  </remove>

</package>
Retrieved from "https://wpkg.org/index.php?title=ESET_NOD32&oldid=11201"