Installation issues and Windows 2k8 R2

Hi all,

Attempting to use the latest downloaded v4 of NOD32 with a Windows Server 2k8 R2 install. Having some issues installing. We can install it manually then configure to talk to the server, but we can't seem to get it to push out from the RA nor can we get it to install using the package if it's exported from the RA. We have to install manually then reconfigure to get it to work. Not sure what's going on or why. Any suggestions on what to look at?

Remote install error message is:
Could not setup IPC connection to target computer, probably due to a wrong username or password (SC error code 6, GLE error code 1326)

No error message anywhere if we try to use the package... It just fails.

Last attempt was using an Enterprise Admin. Machine is domain joined.

Remote install diagnostics:
Get Info Diagnostics, server: SERVER, user: ADMIN
Setting IPC$ Connection Result Code: 0 (The operation completed successfully.)
Remote Registry Connecting (OS Info) Result Code: 0 (The operation completed successfully.)
Remote Registry Opening (OS Info) Result Code: 0 (The operation completed successfully.)
Remote Registry Reading (OS Info) Result Code: 0 (The operation completed successfully.)
Remote Registry Connecting (ESET Security Product Info) Result Code: 0 (The operation completed successfully.)
Remote Registry Opening (ESET Security Product Info) Result Code: 5 (Access is denied.)
Remote Install Diagnostics, server: Update, 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.)

Any ideas about what to check?

 

Hello Brimstar,

You can install the software and have it import the settings by having the configuration file named cfg.xml and having it in the same folder as the msi file. It will still go through the questions during installation, but you can choose to set the update parameters later and it will skip that and take what you put in the xml file.

If you need to push install, I would try removing the /qn option and stepping through the setup to see what errors you may get during the install.

 

Got it working now, actually. Changed the Remote installer service from a local security account to a domain account with the right to adjust the registry.