Difference between revisions of "ESET NOD32"

From WPKG | Open Source Software Deployment and Distribution
Jump to: navigation, search
(package definitions for NOD32 and ESS)
(Reverted some verbiage, and tweaked other bits)
Line 1: Line 1:
−
Here's a basic set of instructions on how it can be done via command line;
+
= 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
 
http://www.eset.eu/knowledge-base/ess-eav-specific-installation
Line 19: Line 21:
 
http://kb.eset.com/esetkb/index?page=content&id=SOLN82
 
http://kb.eset.com/esetkb/index?page=content&id=SOLN82
  
−
= Generic instructions =
+
= Install with ESET Remote Administrator =
  
−
ESET's NOD32 and ESET Smart Security products use the same management console. This tool makes silent installation very easy.
+
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.
 
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.
  
−
When using the ERAC package editor, make sure entering and saving your update password is the very last thing you do before exporting. Clients may not get it otherwise.
+
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.

Revision as of 21:15, 30 March 2010

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.

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 /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.

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.

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>

  <!-- Uncomment the following if you need to get rid of PC-cillin 2008 -->
<!--
  <install cmd="msiexec /qn /x{718d791f-f4e8-4aa7-98a6-15fded17bdd0}">
    <exit code="0" />
    <exit code="1605" />
    <exit code="1614" />
    <exit code="1641" reboot="true" />
    <exit code="3010" reboot="true" /> 
  </install>
-->
  <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

<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>
Retrieved from "https://wpkg.org/index.php?title=ESET_NOD32&oldid=7885"