Author Topic: remote install to Vmware VM - failed and solved :)  (Read 6301 times)

0 Members and 1 Guest are viewing this topic.

Restless

  • Guest
remote install to Vmware VM - failed and solved :)
« on: June 28, 2006, 04:44:06 PM »
I installed trial ADNM on my PC, and I'm trying to make remote install work on XP Pro VM running under VMware Server on same PC

First I had no mirror, but created one manually. Succeeded in creating distribution msi package, but attempt to start "delivery" fails:

the log:
Quote
06/28/06 11:56:23:   rinstInstall begin
06/28/06 11:56:23:   Init 50 60 C:\WINDOWS\TEMP\asw3BE.tmp C:\Program Files\Alwil Software\Management Tools\InstPkgs NULL C:\WINDOWS\TEMP\asw3BD.tmp 0
06/28/06 11:56:23:   CreateProcess C:\Program Files\Alwil Software\Management Tools\InstPkgs\setup.exe error 2
06/28/06 11:56:23:   TerminateAll
06/28/06 11:56:24:   rinstInstall end 2

in main AMS window it sais that reason for failure is "Access is denied"

On both remote PC and my own I have account with same user/pass and admin priviledges, with which i try remote install.

Perhaps I'm missing something simple.... :)

« Last Edit: June 29, 2006, 11:56:14 AM by Restless »

Offline Vlk

  • Avast CEO
  • Serious Graphoman
  • *
  • Posts: 11658
  • Please don't send me IM's. Email only. Thx.
    • ALWIL Software
Re: remote install failed
« Reply #1 on: June 28, 2006, 04:54:07 PM »
Wait a moment, I see some confusion here.

The installation process is like this:
- you create an installation package (in the console)
- you start a deployment task, that EITHER creates a MSI file that you can then distribute by your own methods (group policy, MS SMS, etc) OR push the installation directly to the machines.

So, saying

Quote
Succeeded in creating distribution msi package, but attempt to start "delivery" fails:

sort of doesn't make any sense. Maybe you meant "Succeeded in creating installation package" (not msi)?


Anyway, from the log it seems that the package is somehow corrupt. Is the mirror fully built? Is the AMS machine connected to the Internet?


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

Restless

  • Guest
Re: remote install failed
« Reply #2 on: June 29, 2006, 08:04:31 AM »
sorry, what I meant was that I created 2 "server tasks", one to "create deplyable msi package", and another task which is to directly remote install
First tasks runs fine - a 14MB msi package was created, but the second task fails with details as above.
I tried the user/pass I set through "net use" or browsing and it works .
Mirror has to be ok - after all it did make the msi package ...

more: I changed login to AMS to be same as the user/pass needed to access remote PC
Tried creating msi package again - it works.
Tried remote installing - and the error is a bit different:
Quote
06/29/06 09:01:15:   rinstInstall begin
06/29/06 09:01:15:   Init 50 60 C:\WINDOWS\TEMP\asw80A.tmp C:\Program Files\Alwil Software\Management Tools\InstPkgs NULL C:\WINDOWS\TEMP\asw809.tmp 0
06/29/06 09:01:15:   Store
06/29/06 09:01:15:   Domains: ,
06/29/06 09:01:15:   Init workgroup\chavv-vm1
06/29/06 09:01:15:   chavv-vm1: GetAccount
06/29/06 09:01:15:   chavv-vm1: not found in domain list
06/29/06 09:01:15:   chavv-vm1: Finished with error
06/29/06 09:01:15:   TerminateAll
06/29/06 09:01:16:   rinstInstall end 87

My PC is in domain, the remote PC is in "workgroup",  it was added manually by me in computers list, by entering its IP address.

Offline vojtech

  • Avast team
  • Advanced Poster
  • *
  • Posts: 939
    • ALWIL Software
Re: remote install failed
« Reply #3 on: June 29, 2006, 09:57:02 AM »
Go to the deployment task's properties, select page Login Accounts and create an entry with the workgroup name and credentials for the remote computer.

Restless

  • Guest
Re: remote install failed
« Reply #4 on: June 29, 2006, 11:41:37 AM »
Go to the deployment task's properties, select page Login Accounts and create an entry with the workgroup name and credentials for the remote computer.

That I had already made.
Tried setting Domain to "workgroup" or to "*" - a small change! :)
Quote
06/29/06 11:01:00:   rinstInstall begin
06/29/06 11:01:00:   Init 50 60 C:\WINDOWS\TEMP\asw985.tmp C:\Program Files\Alwil Software\Management Tools\InstPkgs NULL C:\WINDOWS\TEMP\asw984.tmp 0
06/29/06 11:01:02:   Store
06/29/06 11:01:02:   Domains: workgroup,
06/29/06 11:01:02:   Init workgroup\chavv-vm1
06/29/06 11:01:02:   chavv-vm1: GetAccount
06/29/06 11:01:02:   chavv-vm1: Queueing
06/29/06 11:01:02:   StartThread
06/29/06 11:01:02:   Loop
06/29/06 11:01:02:   SpawnThreads
06/29/06 11:01:02:   chavv-vm1: StartSetup
06/29/06 11:01:02:   chavv-vm1: Connecting
06/29/06 11:01:12:   chavv-vm1: WNetAddConnection2 \\chavv-vm1\C$ chavv-vm1\administrator error 1326
06/29/06 11:01:12:   chavv-vm1: WNetAddConnection2 \\chavv-vm1\ADMIN$ chavv-vm1\administrator error 1326
06/29/06 11:01:12:   chavv-vm1: RemoveOnError
06/29/06 11:01:12:   chavv-vm1: Finished with error
06/29/06 11:01:12:   TerminateAll
06/29/06 11:01:12:   rinstInstall end 0

EDIT:

Success !
I noticed that trying to "net use" the PC is successful when using its IP (192.168...) , but fails when using the name (no idea atm why, that can be solved, but anyway, the problem is not AMS related :D )
So in Computer catalog I set the "name" of the PC to its IP address... and remote install passed successfully ...which is a bit weird - I'd expect that connections are made by IP, not by name, ie if I am adding a PC manually it looks that the attempts to install will be through "names" not through actual IP - one can enter not real names, expecting that IP is the important part ...

« Last Edit: June 29, 2006, 11:56:51 AM by Restless »

Offline vojtech

  • Avast team
  • Advanced Poster
  • *
  • Posts: 939
    • ALWIL Software
Re: remote install to Vmware VM - failed and solved :)
« Reply #5 on: June 29, 2006, 04:15:20 PM »
I think it will not work using the name only when you test it in VM that has the network connection set to NAT, because the name is incorrectly translated to the IP address of the virtual (VMware) interface of the physical computer where the VM is running.