Push installation difficulities from W2K3

[Manz]

Dear all,

We had a problem when use the push installation from Windows 2003 server.
But this is not happen when push installation from Windows 2000 server.

We already follow the instructions for installation, but still no lucky.
Domain Controller is Windows 2003.

The error message when do the diagnostics is :
-------------
Computer: PC1
Domain: MYDOM
Get Info Diagnostics, server: MYSERVER, user: administrator
Setting IPC$ Connection Result Code: 1240 (The account is not authorized to log in from this station.)
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: MYSERVER, user: administrator
Setting ADMIN$ Connection Result Code: 1240 (The account is not authorized to log in from this station.)
Setting IPC$ Connection Result Code: 1240 (The account is not authorized to log in from this station.)
Registering ESET Installer as a Service Result Code: 5 (Access is denied.)

--------------
We already use the administrator user and password account.
when we use the :
net use \\PC1\ipc$ -> result is ok can establish

in windows explorer : type in address \\pc1\admin$ -> can show all file.

we already turned off the simple file sharing feature, but still no luck.
In windows 2000 we didn't found any problem ...

ESET : 3.0.642 Business edition.

Anyone can help to resolve this promblem.

Thankz
Manz

[Manz]

I'm hit the problem again :... hiks

Computer: PC2
Domain: MYDOM
Get Info Diagnostics, server: NMYSERVER, user: administrator
Setting IPC$ Connection Result Code: 1203 (No network provider accepted the given network path.)
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: MYSERVER, user: administrator
Setting ADMIN$ Connection Result Code: 1203 (No network provider accepted the given network path.)
Setting IPC$ Connection Result Code: 1203 (No network provider accepted the given network path.)
Registering ESET Installer as a Service Result Code: 1722 (The RPC server is unavailable.)

Anyone can help me please....

[mkuntic]

Just deploy it via Group Policy.

[Manz]

-{ Quote: "Just deploy it via Group Policy." }-

What do you mean ? just deploy it via group policy ?

Can you show us step by step procedures ???

Thanks

[mkuntic]

http://www.windowsnetworking.com/articles_tutorials/Group-Policy-Deploy-Applications.html

http://www.google.hr/search?q=group+policy+msi+deployment

[Manz]

Wow ... thanks ... but, configuring one by one of computer to joining to the server ... it time consumable ...

[Manz]

Why this case only some computer ?
does have a simple configuration set and security policy ?

[hillrb]

-{ Quote: "Just deploy it via Group Policy." }-

Simple enough, but how do you push a config with that?

[mkuntic]

Put the cfg.xml into the same folder where the MSI resides.

[hillrb]

Really? That works? That's how I'd love it work. I previously had asked my sales engineer about deploying through AD and he didn't think it could be done unless it was something I had configured in the Logon scripts area with the "einstaller.exe" file they create.

I'll certainly give it a try. That's how Symantec did it. I was so used to it.

*edit*
Does it matter what the name of the xml file is?

[mkuntic]

Yes. It must be named "cfg.xml".
All the details are available in the official NOD RA documentation.

[hillrb]

Thanks!

[YeOldeStonecat]

-{ Quote: "Wow ... thanks ... but, configuring one by one of computer to joining to the server ... it time consumable ..." }-

Are you saying you're running active directory..but many servers and workstations are not members of it? If so...err...why aren't them joined to the domain? Because you're beginning to see ..through having things not work properly as they would with a good AD setup, the fallback of having just a peer to peer setup.

[Manz]

-{ Quote: "Are you saying you're running active directory..but many servers and workstations are not members of it? If so...err...why aren't them joined to the domain? Because you're beginning to see ..through having things not work properly as they would with a good AD setup, the fallback of having just a peer to peer setup." }-


Nope, i mean, we have to configure the antivirus one by one, but in previous thread already describe it ... we'll to trying ...

Thanks