Unable to Push installation to Win7 SP1 Client

Hello,

We're trying to push the NOD32 installation to one of our Windows 7 SP1 clients but it is failing for an unknown reason.

The "State Text" returned is:
Failure during the package install - exit code: 1603, description: Fatal error during installation.

If I push "View All Logs" then an empty window opens.

I used "Remote Install Diagnostics". This tells me:
Computer.Domain.local
Diagnostics user context: DOMAIN\Administrator

Push installation simulation steps:
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.)
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: 0 (The operation completed successfully.)
Diagnostics conclusion: Result Code: 0 (The operation completed successfully.)

The Application Event Logs on the client machine show an MSI installation starting and then failing with error 1603.

The System Event Log reports:
The ESET Remote Installation Service service is marked as an interactive service. However, the system is configured to not allow interactive services. This service may not function properly.

On the server, we are running ESET Remote Administrator Server & Console version 4.0.138.

I have changed the ESET Remote Administrator service to start as the Domain Administrator and restarted the service.

I have verified on the client that this key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Windows\NoInteractiveServices is set to 0.

Does anyone have any ideas?

Thanks for your help!

 

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\FileSystem
Make sure the value "NtfsDisable8dot3NameCreation" is equal to 0
reboot...
try this maybe can help you.....

 

Could you confirm that installing EAV locally ends up with the same error? If so, create install logs as per the instructions at http://kb.eset.com/esetkb/index?page=content&id=SOLN406 and supply them to Customer care for perusal.

 

Aha! Thanks for the input guys, but we identified the problem. I had already read somewhere that a common cause of this error was if another virus checker was already installed.

Well, it turned out that Microsoft Security Essentials had been installed without anyone's knowledge (must have been a "just agree to everything that Windows Update offers"-sort of thing)

Once MSE was removed, ESET NOD32 installed "just like that"