Author Topic: Permissions to install on remote machine  (Read 19332 times)

0 Members and 1 Guest are viewing this topic.

jonlockley

  • Guest
Permissions to install on remote machine
« on: June 11, 2004, 11:43:25 AM »
I am having some problems with remotley installing the client. We have a education network where we lock down the client stations as much as possible. I cannot seem to install in these stations, its fine on others that dont have the restrictions.

What client services, permisisons need to be running on the client for the istall to run. An alternative to this would be a .msi file of the network client so that we can deploy it using network tools.

I have tried creating an msi with lots of errors.

Any Ideas?


Offline Vlk

  • Avast CEO
  • Serious Graphoman
  • *
  • Posts: 11664
  • Please don't send me IM's. Email only. Thx.
    • ALWIL Software
Re:Permissions to install on remote machine
« Reply #1 on: June 11, 2004, 11:46:13 AM »
Well the account you specify in the deployment task must have local admin rights on the target(s).

Furthermore, it is assumed that this account has full access to the file system and the registry.
If at first you don't succeed, then skydiving's not for you.

jonlockley

  • Guest
Re:Permissions to install on remote machine
« Reply #2 on: June 11, 2004, 11:48:26 AM »
I used a domain admin account and I still get permission denied messages

Offline Vlk

  • Avast CEO
  • Serious Graphoman
  • *
  • Posts: 11664
  • Please don't send me IM's. Email only. Thx.
    • ALWIL Software
Re:Permissions to install on remote machine
« Reply #3 on: June 11, 2004, 11:50:04 AM »
Let's see the logs.
First, the management_server\data\log\aswrinst.log, and then the setup.log's from that machine(s) -- provided we've gotten so far that the installation actually started on those machines.
If at first you don't succeed, then skydiving's not for you.

jonlockley

  • Guest
Re:Permissions to install on remote machine
« Reply #4 on: June 11, 2004, 12:02:20 PM »
aswrinst

06/11/04 10:52:19:   rinstInstall begin
06/11/04 10:52:19:   Init 50 60 C:\WINNT\TEMP\asw2E.tmp C:\Program Files\Alwil Software\Management Tools\InstPkgs\setup_av_net.exe NULL C:\WINNT\TEMP\asw2D.tmp 0
06/11/04 10:52:19:   Store
06/11/04 10:52:19:   Set CHERWELLCURRIC\N1-THREE
06/11/04 10:52:19:   N1-THREE: CallBack 201
06/11/04 10:52:19:   StartThread
06/11/04 10:52:19:   Loop
06/11/04 10:52:19:   SpawnThreads
06/11/04 10:52:19:   N1-THREE: StartSetup
06/11/04 10:52:19:   N1-THREE: CallBack 202
06/11/04 10:52:19:   N1-THREE: WNetAddConnection2 \\N1-THREE\C$ CHERWELLCURRIC\administrator error 1219
06/11/04 10:52:19:   N1-THREE: WNetAddConnection2 \\N1-THREE\ADMIN$ CHERWELLCURRIC\administrator error 1219
06/11/04 10:52:19:   N1-THREE: RemoveOnError
06/11/04 10:52:19:   N1-THREE: CallBack 211 C:\Program Files\Alwil Software\Management Tools\DATA\log\CHERWELLCURRIC_N1-THREE.log


Install log

06/11/04 10:52:19:   Set CHERWELLCURRIC\N1-THREE
06/11/04 10:52:19:   CallBack 201
06/11/04 10:52:19:   StartSetup
06/11/04 10:52:19:   CallBack 202
06/11/04 10:52:19:   WNetAddConnection2 \\N1-THREE\C$ CHERWELLCURRIC\administrator error 1219
06/11/04 10:52:19:   WNetAddConnection2 \\N1-THREE\ADMIN$ CHERWELLCURRIC\administrator error 1219
06/11/04 10:52:19:   RemoveOnError





Offline Vlk

  • Avast CEO
  • Serious Graphoman
  • *
  • Posts: 11664
  • Please don't send me IM's. Email only. Thx.
    • ALWIL Software
Re:Permissions to install on remote machine
« Reply #5 on: June 11, 2004, 12:13:44 PM »
Aha, interesting.

1219 translates to the following: "Multiple connections to a server or shared resource by the same user, using more than one user name, are not allowed. Disconnect all previous connections to the server or shared resource and try again.. "
If at first you don't succeed, then skydiving's not for you.

jonlockley

  • Guest
Re:Permissions to install on remote machine
« Reply #6 on: June 11, 2004, 12:16:40 PM »
so if I create a admin user for avast alone will that get around the problem

jonlockley

  • Guest
Re:Permissions to install on remote machine
« Reply #7 on: June 11, 2004, 12:37:10 PM »
That'll be a no - any ideas as to the next step?

Offline Vlk

  • Avast CEO
  • Serious Graphoman
  • *
  • Posts: 11664
  • Please don't send me IM's. Email only. Thx.
    • ALWIL Software
Re:Permissions to install on remote machine
« Reply #8 on: June 11, 2004, 01:17:51 PM »
The problem is that the AMS machine already has a connection to the target -- but with a different set of credentials. Windows doesn't support connecting to a remote host with more than one set of credentials.

Do a net use command from a command prompt (on the AMS) to see if you have a mapping to that host. If so, either delete it (by using net use /d) or make sure the account specified in the avast deployment task is the same as you're currently logged on.

I hope this makes sense to you. :)

BTW is this NT4?

Vlk
If at first you don't succeed, then skydiving's not for you.

jonlockley

  • Guest
Re:Permissions to install on remote machine
« Reply #9 on: June 11, 2004, 01:19:22 PM »
server 2000, client xp

Offline Vlk

  • Avast CEO
  • Serious Graphoman
  • *
  • Posts: 11664
  • Please don't send me IM's. Email only. Thx.
    • ALWIL Software
Re:Permissions to install on remote machine
« Reply #10 on: June 11, 2004, 01:23:29 PM »
Now I've also read somewhere that if we used IP address instead of the computer name (like \\192.168.1.10\c$ instead of \\hostname\c$) we should not be seeing this problem. We'll modify the remote installer to take this into account...
If at first you don't succeed, then skydiving's not for you.

jonlockley

  • Guest
Re:Permissions to install on remote machine
« Reply #11 on: June 11, 2004, 01:26:53 PM »
Ok there was a entry in net use that i deleted but it failed again with the following log.

06/11/04 12:18:56:   Set CHERWELLCURRIC\N1-THREE
06/11/04 12:18:56:   CallBack 201
06/11/04 12:18:56:   StartSetup
06/11/04 12:18:56:   CallBack 202
06/11/04 12:18:56:   WNetAddConnection2 \\N1-THREE\C$ cherwellcurric\avast error 1219
06/11/04 12:18:56:   WNetAddConnection2 \\N1-THREE\ADMIN$ cherwellcurric\avast error 1219
06/11/04 12:18:56:   RemoveOnError


Offline vojtech

  • Avast team
  • Advanced Poster
  • *
  • Posts: 939
    • ALWIL Software
Re:Permissions to install on remote machine
« Reply #12 on: June 11, 2004, 02:37:50 PM »
Is it possible to create the connection with net use ?
net use \\N1-THREE\C$ /user:cherwellcurric\avast

jonlockley

  • Guest
Re:Permissions to install on remote machine
« Reply #13 on: June 14, 2004, 02:26:36 PM »
yep I can net use as requested

Josh Delcore

  • Guest
Re: Permissions to install on remote machine
« Reply #14 on: December 28, 2007, 05:49:39 PM »
I know this topic is old, but I wanted to post that I was having this same problem with a Windows 2000 server & Symantec Backup exec. I was using the server name & fixed it by changing the server name to the servers IP address. The error I got below disappeared and I was able to connect:

"Multiple connections to a server or shared resource by the same user, using more than one user name, are not allowed. Disconnect all previous connections to the server or shared resource and try again."

Thanks for the Thread.
Josh Delcore