Push Install Windows 7

[unclep4ul]

Hi, I am trying to do a push install of NOD 32 version 4 to a windows 7 machine.

I keep getting the following error : Could not install ESET Installer on target computer (SC error code 11, GLE error code 5).

I have turned off Window Firewall and am using the Domain Administrator account to perform the install.

Computer:	C-eb
Domain:	D01
Get Info Diagnostics, server: C-PLD, user: administrator
	Setting IPC$ Connection	Result Code: 0	(The operation completed successfully.)
	Remote Registry Connecting (OS Info)	Result Code: 53	(The network path was not found.)
	Remote Registry Connecting (ESET Security Product Info)	Result Code: 53	(The network path was not found.)
Remote Install Diagnostics, server: S-sql1, user: administrator
	Setting ADMIN$ Connection	Result Code: 0	(The operation completed successfully.)
	Copying ESET Installer	Result Code: 0	(The operation completed successfully.)
	Setting IPC$ Connection	Result Code: 0	(The operation completed successfully.)
	Registering ESET Installer as a Service	Result Code: 5	(Access is denied.)

Can anybody advise me what I can do to resolve this?

Many thanks in advance.

[Marcos]

Does configuring the ERAS service to run in the domain admin account instead of the local system account (default) and restarting the service make a difference?

[unclep4ul]

That worked perfectly, thank you very much Marcos!

[JoTho]

I get the same error but we do not have a domain and thus no domain admin account to use. Is there a need to have matching accounts on ERAS server and workstation? Thanks.

[dmaasland]

Try disabling UAC

[JoTho]

Ok, thanks. I found that UAC alone did not allow the Upgrade option to work. I had to also set the Network to 'Work' from 'Public' AND Turn Firewall off on Private networks. After those changes 2 Win7 workstations upgraded. To not have to turn off the FW isn't it port 2222 or 2223 that needs to be opened? Thanks.

[dmaasland]

From the ERA manual:

2.1.3 Ports used
The chart belowlists the possible network communications used when ERAS is installed. The process EHttpSrv.exe
listens on TCP port 2221 and the process era.exe listens on TCP ports 2222, 2223, 2224 and 2846. Other communications
occur using native operating systemprocesses (e.g., ”NetBIOS over TCP/IP”).
Protocol Port Description
TCP 2221 (ERAS listening)
Default port used by theMirror feature integrated in ERAS (HTTP
version)
TCP 2222 (ERAS listening) Communication between clients and ERAS
TCP 2223 (ERAS listening) Communication between ERAC and ERAS
If all the programfeatures are in use, the following network ports need to be open:
Protocol Port Description
TCP 2224 (ERAS listening)
Communication between the agent einstaller.exe and
ERAS during remote install
TCP 2846 (ERAS listening) ERAS replication.
TCP 139 (target port fromthe point of viewof ERAS)
Copying of the agent einstaller.exe fromERAS to a
client using the share admin$
UDP 137 (target port fromthe point of viewof ERAS) “Name resolving” during remote install.
UDP 138 (target port fromthe point of viewof ERAS) “Browsing” during remote install
TCP 445 (target port fromthe point of viewof ERAS)
Direct access to shared resources using TCP/IP during
remote install (an alternative to TCP 139)
The predefined ports 2221, 2222, 2223, 2224 and 2846 can be changed if they are already in use by other applications.
To change the default ports used by ERA, click Tools > ServerOptions… To change port 2221, select the Updates tab
and change the HTTP server port value. Ports 2222, 2223, 2224 and 2846 can bemodified in the Ports section on the
Advanced tab.
The predefined ports 2222, 2223, 2224 and 2846 can also bemodified during the advanced installmode (ERAS).

http://download.eset.com/manuals/ese...rguide_enu.pdf - Page 10

[tony_m]

Additionally:

ESET Remote Administrator Push Installation Requirements and Checklist

[hinomara]

Originally Posted by unclep4ul

That worked perfectly, thank you very much Marcos!

Hi.
Happy to see that you have solved your problem... but unfortunately I'm just now having the exact same problem, when pushing install to Windows 7 machines, i try to push using a domain administrator.
Can you tell me what you did?

Tks

[jimwillsher]

Rather than pushing as Domain Admin, which account is your ERAS service running under? Can you try with it running under the domain admin account?


Jim