Automatic Scan using Remote Install

[Guest Steve]

Hi,

 

Is it possible to perform an automatic scan using the Remote Install function. I would like to run an automatic scan across the network on a weekly basis to discover any devices that do not have ESET installed and automatically push the client out?

 

thanks,

Steve

[drewd 6]

I see that you would like to automatically initiate deployment of the ESET antivirus client, to machines where it is not yet installed.

 

You can accomplish this via a Windows Login Script.

 

A Windows logon script will allow you to assign tasks that will be performed when a user logs on to a particular

computer.

 

Since a login script is essentially a text file, you can just use a simple text editor to insert a line into the

script that will call the file einstaller.exe from a predefined network share.

 

This will initiate the remote push installation of the ESET antivirus client, from the ERA Server on the network, to

the intended endpoint client machine.

 

Here are the instructions regarding how to deploy the ESET antivirus client via login script:

 

I. You will need to set the Default Logon for Email and Login Installations.

 

The Default Logon window  lets you set the user credentials and domain  information required to access your client

computer on the network and manage the ESET product installed:

 

1) Open ERAC, select the Remote Install tab, right-click any entry within the Computers tab pane, select Set the

Default Logon for Email and Login Installations from the context-menu, and then enter the required data:

 

User name

Password

Domain/Workgroup

 

2) After you enter the data, press the Set Logon button to save the information on the server.

 

 

Note:

 

The account under which the installation of the package is to be performed must be an account with administrator

rights or, preferably, a domain administrator account, and this logon information will only remain stored until the

next server restart.

 

 

 

II.  You will need to create an install package.

 

How to create an installation package

 

hxxp://kb.eset.com/esetkb/index?page=content&id=SOLN2982#create_package

 

 

 

III. You will need to edit the login script to add the line calling einstaller.exe from the predefined network share, and export the einstaller.exe file that is associated with the package that you intend to deploy, to a network share:

 

1) Right-click an entry on the Remote Install tab, click Export to Folder or Logon Script and select the Type and

name of the Package to be automatically installed.

 

2) Click next to Folder to select the directory where the einstaller.exe file will be located and available within a network share, and then click OK.

 

3) In the Share field, make sure that the path is correct or edit it if necessary.

 

4) Click Export to Folder to export the einstaller.exe agent to the shared folder.

 

5) Click … next to Script Folder to select the folder where the script is located and modify the mask if necessary.

 

6) In the Files section, select the file into which the line calling einstaller.exe will be inserted.

 

7) Click Export to Logon Script to insert the line.

 

8) Location of the line can be modified by clicking Edit >> and saved by clicking Save.

 

 

NOTE:

 

Here is some additional information from Microsoft, regarding how to create and use a logon script:

 

Creating logon scripts

 

hxxp://technet.microsoft.com/en-us/library/cc758918(v=ws.10).aspx

 

 

Assign user logon scripts via GPO

 

hxxp://technet.microsoft.com/en-us/library/cc781361(v=ws.10).aspx

 

 

Note:

 

Immediately after the agent successfully completes the remote installation process, it marks the remote client with

a flag prohibiting repeated installations of the same installation package. The flag is written to the following registry key:

 

HKEY_LOCAL_MACHINE\Software\ESET\ESET Remote Installer

 

If the Type and Name of the package defined in the einstaller.exe agent match the data in the registry, the installation will not be performed. This prevents repeated installations from targeting the same workstations.

Edited June 25, 2013 by drewd

[Guest Steve]

Hi Drewd,

 

Thanks for the excellent detailed response. I am aware of the ability to install via AD as per detailed post by ESET themselves, However, I'm really looking to capture any devices that in the rare event of the installation failing via AD, I had a secondary method to automatically install the software, or failing that at least an automated report detailing any devices on the network that do not have ESET installed. I guess I could do this via powershell but I would prefer to just use the Remote Install feature if at all possible?

 

Many thanks,

Steve