It is always a bad idea to insert in the packet definition references to files over the network.
When the sofware distribution job is executed normally is executed under LocalSystem accoubt that has no, or limited. power to access the network.
So add the MSP file as additional files and do not reference the network directly in the package definition.
Then try to use in the parameter:
after adding the file as additional file and modifying the command have you tried to reset the package hash before trying to re-distribute it?
what delivery method are you using?
Can you try to use a delivery method that avoids the RUN FROM SOURCE option?
As a test please try to create a delivery method Push and in the network usage section select "Use Download from source to deploy files"
If this will still not work have a look to the logs on the client side ("C:\Program Files (x86)\LANDesk\LDClient\Data" on a 64bit and "C:\Program Files\LANDesk\LDClient\Data" on a 32bit one).
You'd have a log that tells you something.
Another good test is to put the package on a HTTP share and odify the package definition to use HTTP instead of UNC. Normally HTTP is less ''troubled'' than UNC.
In UNC windows permissions mixage creates a lot of issues....
Alternatively, use the msp to patch your admin install point and then use msiexec.exe /i 2k3pro.msi REINSTALL=ALL REINSTALLMODE=vomus
It will take longer, but forces the target machine to be at the same version as the admin install. Simply patching the machine will cause version differences between the target machine and the install point and if the machine ever goes back to the unpatched admin point, it can downgrade or break the target machine. Patching the machine and admin install point separately without a recache can still cause the same problem.
You will have to tweak accordingly and possibly use a bat file to deploy it.
Note: this process will not work for any other version of office after 2003.
Hi,normaly i'm using policy supported push (run from source) to deploy packagesNow i tried to use the delivery method "push" with "download from source" and put the MSP-File as an additional file in the distribution package.I tried to use the package with following commands:I unchecked the Option "Use Windows Installer to install and control installation (MSIExec)" and put following commands in the command line section:/update outlook.msp /norestartThis is the only way landesk will be able to save my package.Now i pushed the package to a client and now there is a window on this client which shows following (windows_installer.jpg) and the package fails.I could see following log file on the client (sdclient_task366.log)Is it right that i have to use the option "Use Windows Installer to install and control installation (MSIExec)" ? But when i use this option the package could not be saved.Thanks.
@jmaci think this option is not desired in our environment, because i can't reinstall the complete Office Package just for this little Hotfix....