NOD32 Push Installation

Discussion in 'Other ESET Home Products' started by Beetz, Apr 24, 2008.

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

    Beetz Registered Member

    Joined:
    Apr 24, 2008
    Posts:
    3
    Hi all,

    i'm just trying tu ose the NOD Remote Admin Console and did yesterday a push installation to a client in the network.
    Everything worked fine, excepted a small point in the configutration.
    In the installation package i added my xml file.
    I checked to configuration after the installation and found out that the update server was not pushed in the config.
    All other config points a correct, only the update server did not work.
    Hay anybody an idea whyo_O

    Greetings
    Beetz
     
  2. Beetz

    Beetz Registered Member

    Joined:
    Apr 24, 2008
    Posts:
    3
    I'm wondering that nobody could help me!
    I tried now another version to install the NOD32 to a workstation.
    I made a folder which i stored on an flash stick as described in the "Administration Installation Guide" on page 78.
    The installation on the workstation was done, but again in the field of the update server is not my server, instead of it is the option "automatically choose" fixed.
    In the xml-file the update server is correct, so i do not know why this option does not work!
    Pls help me!!

    Greetings from Beetz
     
  3. mladen

    mladen Registered Member

    Joined:
    Nov 3, 2004
    Posts:
    45
    Location:
    Croatia
    Hi,

    I have been using NOD32 3.0 Remote Admin console for the push installation and my procedure was:

    1) create your package. Do configuration as needed (you do this using Installation Packages Editor). When you save your package, the XML config file is saved together with the package. You can also export XML config file and use it later (I will tell you how).

    2) choose the client where you want to install the package. After entering your login data you should be able to install it remotely.

    Later, if you want to propagate some changes to already deployed client, you have to create Configuration Task. For that you will need your exported XML file. XML config file is exported using Remote Install tab->Manage Packages. Open the package using Installation packages editor and choose Export Selected to ... Pay attention that you have to select ESET Smart Security, Eset NOD32 antivirus when you do the export, beacuse only the selected part will be exported.

    To create a configuration task you have to choose client(s) in the Clients view in Remote Adminstrator Console. Select client(s) and choose New->Configuration task. You will be asked which XML file do you want to use. There are only three steps which are pretty straight forward.

    I hope this will help you. I have done it many, many times and it was working just fine.

    Regards,
    Mladen

    PS. You have to enter path to your server like \\servername\foldername!!! (you can also use the IP Address instead of the server name)
     
Thread Status:
Not open for further replies.