unfortunately, provisioning always runs as local system. i filled out an enhancement request on this a while ago.
However, you can "trick" it by using one of LANDesk's own utilities "startasuser" which is the C:\Program Files\LANDesk\LDclient directory. This tool just launches the appliction as the user that is currently logged in.
So you could create an Execute File action and do something like this:
More info here: http://community.landesk.com/support/message/42498#42498
Enhancement request here: http://community.landesk.com/support/ideas/1457#comment-6365
Hi EMiranda, that's such a simple and elegant solution, thank you! I searched for a long time and never came across your old post about startasuser. Great utility, no need for RunAs and piping passwords either, very nice.
I haven't thoroughly tested this solution yet with 3rd party exe/msi applications but I ran a couple quick tests with Execute File with "cmd /c set" and importing a .reg file into CURRENT_USER and both worked like a charm.
As a side note, it looks like the LD_CLIENT_DIR environment variable isn't available to Execute File children (as compared to distribution packages) so I created a new StartAsUser public templates variable containing the string %%ProgramFiles%%\LANDesk\LDClient\startasuser.exe and that worked. From now on I simply need to specify %StartAsUser% as the target within each Execute File action whenever I need this level of functionality.
Many thanks again!