Login script problem - cannot make it work

[Zurd 4]

Push installs is working fine, however the user has to be logged on, we'd like to use the Logon script installation procedure instead. The documentation covering this topic doesn't provide much information, I cannot make it work. Not sure what the field "Folder", "Share" and "Script folder" should point to. Clicking Edit gives me an empty box.

 

Any information regarding this would be greatly appreciated. A screenshot even more.

[PatrickL 21]

Zurd,

 

   The purpose of this field is to help create a logon script for you to point to using Group Policy. In the manual (download at: hxxp://download.eset.com/manuals/eset_era_5_userguide_enu.pdf ) in section '4.2.3.1 Export ESET Installer to Folder / Logon Script' it gives a decent description. In the dialogue at ERA when on the Remote Install Tab, right click and select Export to Folder or Logon Script. The first line is Type - and should default to the correct seeint of ESET Security Products for Windows. The next line down is package and should be the package you want to build the installer for (einstaller.exe by default). In the next one down, listed as Folder, select the network location where you want tostore the einstaller.exe file that will be the core of the installation (it needs to be a location that all computers have access to.

 

the next part is about selecting the preexisting startup script that you want to inject the ESET installation line into. In Share, you need to point to where the einstaller is located (easily referenced from the folder category in the first part). Next in the Script folder, you need to point to a folder that houses your prexisting scripts. You can use the Files dropdown to filter the contents that appear at the bottom once the fodler is selected. The idea is that you are going to inject the line to run the einstaller.exe into the existing startup script file. You can edit it to the right if you select the edit option at the bottom. Once all this is completed to your preference, you can select Export to Logon Script and it will inject the isntaller line into the selected Script file from the menu above it.

 

[Zurd 4]

Everything's clear except the part about the "Script folder" field.

 

Are we trying to modify the autoexec.bat file on the client's computer? Are we adding a script in the Startup folder of the client's computer? How do the client's computer knows it has to run the ESET login script when it's booting up? Especially when it's a laptop not connected to the network at the moment.

 

Where is this script? Do we need to create one beforehand? Is the script the einstaller.exe file or the ESET Endpoint Security.msi file?

 

Cheers

[Arakasi 549]

Hello,

 

Especially when it's a laptop not connected to the network at the moment.

 

 

The logon method works well for notebooks that are often used outside the local network. Installation is performed
after they log onto the domain.

 

 

 

How do the client's computer knows it has to run the ESET login script when it's booting up?

 

 

These explicit instructions taken from the manual explain how the login script works to some extent.(download at: hxxp://download.eset...erguide_enu.pdf ) in section '4.2.3.1 Export ESET Installer to Folder / Logon Script'

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 installed.
2) Click next to Folder to select the directory where the einstaller.exe file is located and available within the network,
and then click OK.
3) In the Share field, make sure that the path is correct or edit it if necessary.
4) Click … next to Script Folder to select the folder where the script is located and modify the mask if necessary (Files).
5) In the Files section, select the file into which the line calling einstaller.exe will be inserted.
6) Click Export to Logon Script to insert the line.
7) Location of the line can be modified by clicking Edit >> and saved by clicking Save.

 

I can only assume this acts similar to Active Directory when the user logs on for logon script.

Edited April 5, 2014 by Arakasi

[Zurd 4]

PatrickL: Next in the Script folder, you need to point to a folder that houses your prexisting scripts.

 

 

I can only assume this acts similar to Active Directory when the user logs on for logon script.

 

 

 

Thanks, that's what I needed and not a copy/paste of the ESET documentation that i already read multiple times.

 

A knowledge of the AD login script is needed and you need to have an already login script on your domain. Unfortunately that simple sentence is not in the ESET documentation. We didn't had any login script in the domain which is why it wasn't working of course.

 

You can easily make it work by reading this:

hxxp://www.petri.co.il/setting-up-logon-script-through-active-directory-users-computers-windows-server-2008.htm