Two main ones:
First, if you upgrade to 9.5 that now has an option to specify a user account to use during the installation.
Second, you build a batch file package (or other scripting) and use something like 'runas' to launch the installation with specific user rights.
LANDesk Silver ESP
The One-Stop Shop for LANDesk Enhancements
Update - WoW & State Notifier now integrate for even more functionality
Update - State Notifier now detects machine and user Idle states
In addition to what Mark indicated, If you have setup preferred servers and the account you use for this is a local admin on the machines, and your delivery method is Run From Source, it should use the preferred server credentials to install. Well at least it used to in 9.0. Worth a try,
Very interesting Zman
Can you install other packages that are in the same location as the MSI's? If not if might be a matter of share permissions. The user account might have access to the share but not the system account. We add our computer accounts to the share.
Also, what are the errors you are seeing? If you go into the \ldclient\data folder on a client and sort by date modified you should see two logs files with the same ID in the file name, open them up and look what it states and or post the info here.
Could also be the switches that are being used / not used.
Other MSI's work fine. Taking LANDesk out of the equation and running a cmd prompt as system and the msi still fail, install starts then says failed instantly. Run in a command prompt opened as administrator and they work fine...:(
Have you tried enabling MSI logging? If not, try it and upload both MSI logging as well as sdclient log file for that task (\ldclient\data\). MSI logging: http://support.microsoft.com/kb/223300