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
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?
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:
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.
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.
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 )
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 …
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.
)