Remote Uninstall NOD32, Windows Installer 4.5

Discussion in 'ESET NOD32 Antivirus' started by borxud, Jul 1, 2009.

Thread Status:
Not open for further replies.
  1. borxud

    borxud Registered Member

    Joined:
    Jul 1, 2009
    Posts:
    2
    I'm testing ERAS / ERAC and NOD32 on WinXP SP3 machines with Windows Installer 4.5.

    The problem I'm having is remote uninstallation of password protected clients.

    ##Parameters##
    NOD32: /UNINSTALL /PWD=""thepassword"" (2 sets of double quotes) ESS: qn!

    The uninstallation initiates fine, yet a message box displays "Enter a valid password to continue uninstallation" on the workstation.

    I have uninstalled through add/remove using the same password I supplied through the parameter.

    ##einstaller.log##
    Status 1012, ID 0: Failure during the package uninstall - exit code: 1603, additional code: 2, description: Fatal error during installation.
    Status 20006, ID 0: Service stuff cleanup finished with return code 0.
     
    Last edited: Jul 1, 2009
  2. WayneP

    WayneP Support Specialist

    Joined:
    Apr 9, 2009
    Posts:
    339
    Hello borxud,

    The NOD32 side is for v2.7 clients and the ESS side is for all v3 and v4 clients of NOD and ESS. So with this in mind, you want to put the following:

    PASSWORD=yourpassword

    This will allow you to uninstall the machines that require a password.
     
  3. borxud

    borxud Registered Member

    Joined:
    Jul 1, 2009
    Posts:
    2
    Thanks for clearing that up Wayne.

    Does ERAC update itself to reflect that the clients were uninstalled? The test machines I uninstalled remain listed on the Clients tab. ERAC should remove them immediately after a successful uninstallation.

    BTW,

    The PASSWORD parameter is not listed on the options for ESS.

    The ERA manual glosses over remote uninstallation.
     
  4. WayneP

    WayneP Support Specialist

    Joined:
    Apr 9, 2009
    Posts:
    339
    The clients stay in the RAC after push uninstalling. You have to manually remove them from the clients list.

    We are aware of this and I'm going to pass the info to the proper channels to get it resolved.
     
  5. edwin3333

    edwin3333 Registered Member

    Joined:
    Aug 29, 2007
    Posts:
    244
    So, for Nod32 4.0.437 the uninstall string to silently uninstall would be;

    start /wait "a" "%ProgramFiles%\ESET\ESET NOD32 Antivirus\callmsi.exe" /x {2EEBAC31-3EEF-4118-91CB-1A286A507DB2} /qn PASSWORD=mypassword

    right?

    And if I want no restart then

    start /wait "a" "%ProgramFiles%\ESET\ESET NOD32 Antivirus\callmsi.exe" /x {2EEBAC31-3EEF-4118-91CB-1A286A507DB2} /qn /norestart PASSWORD=mypassword
     
    Last edited: Jul 24, 2009
  6. WayneP

    WayneP Support Specialist

    Joined:
    Apr 9, 2009
    Posts:
    339
    edwin3333,

    If you had the installer file still, you can always use:

    msiexec /uninstall /quiet install_package.msi PASSWORD=yourpassword
     
  7. edwin3333

    edwin3333 Registered Member

    Joined:
    Aug 29, 2007
    Posts:
    244
    Thanks but... umm., but it says in bold graphic type not to do that right here;

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

    Doing msiexec is no different than add/remove programs, right?

    Anyway, the /norestart isn't working on my command line. I'm putting NOCLOSE in the registry to avoid the forced restart. Is there a proper way to pass no restart to callmsi.exe?
     
  8. WayneP

    WayneP Support Specialist

    Joined:
    Apr 9, 2009
    Posts:
    339
    My mistake, you are correct. That method is prone to errors, so we recommend uninstalling from the Start Menu.

    The Remote Administrator options specify using REBOOT="ReallySupress" so that should be what you specify on the command line.
     
Thread Status:
Not open for further replies.