Changes

= Install without ESET Remote Administrator General notes =

http://www.eset.eu/knowledge-base/ess-eav-specific-installation And according to [http://www.appdeploy.com/packages/detail.asp?id=1506 appdeploy], the uninstall should be doable via; MsiExec.exe /I{35EB8A68= Potentially-BED1-42DE-97CC-91A7DCA4A701} Other less helpful but interesting useful links;==

= Install with ESET Remote Administrator = Warning about upgrading ==

ESETWhile adding upgrade stanzas to these packages has been seen to work, it's generally advisable to use ESET Remote Administrator Console when mass-upgrading NOD32 and , ESET Smart Security products use the same management consoleand ESET Endpoint Security. This tool produces packages that play nicely The reliability of remote upgrades is very good with WPKGthe version 5 server and console.

= Install from MSI = ESET provides MSI packages of its business-edition products, and the management console can produce MSIs customized with your site-specific configuration. This is more reliable than the EXE-based method because it doesn't need to communicate with the server to complete installation. If you wish to customize the package (e.g. to point it at your management server), 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 (see page 35). Once you've entered the desired configuration, use the "Save As..." buttons to export your package as an "ESET Install Msi File With Configuratoin" for 32- and 64-bit clients. You can then install this file with msiexec. If you're not using ERAS, the MSI that ESET provides will work without customization. == ESET Endpoint Security 5 ==<source lang="xml"><package id="ess4" name="ESET Endpoint Security 5" revision="3" 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; msiexec /norestart /qn /i &quot;%SOFTWARE%\eset\ees-with-config-x86.msi&quot;"> <exit code="0" /> <exit code="3010" reboot="postponed" /> <exit code="1641" reboot="postponed" /> </install>  <install cmd="%COMSPEC% /C if exist &quot;%PROGRAMFILES(x86)%&quot; msiexec /norestart /qn /i &quot;%SOFTWARE%\eset\ees-with-config-x64.msi&quot;"> <exit code="0" /> <exit code="3010" reboot="postponed" /> <exit code="1641" reboot="postponed" /> </install>  <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 with ESET Remote Administration Server remote-install = ESET's management console can produce an EXE which, when launched, silently downloads installation packages from the management server and installs them. This process can be more fragile than MSI-based installation. 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 the "Export to Folder or Logon ScriptSave As..." buttons to export your package as <code>einstaller.exe</code>an "ESET Install Execute File" for 32- and 64-bit clients. You can then launch this file from WPKG.