This is the new way of 9.5, no easy way around it. You could try the startasuser.exe in the LDClient map. That doesn't need any passwords or anything and just kicks off the command after as the logged in user, i.e.:
c:\program files (x86)\LANDesk\LDclient\startasuser.exe notepad.exe
1 of 1 people found this helpful
Did you try "startasuser.exe" in LDCLIENT folder?
To both Frank and Jary,
We’d tried using startasuser, and we’ve been trying again this week, but each time has produced more issues.
For instance, some of our tasks are custom status windows, utilities, etc. that we use for development. As an example, we have a custom full screen ‘Maintenance in Progress’ window that we want to appear if we are doing in-place re-imaging and don’t want any user to try to use the computer during system configuration. Under 9.0, we ran that exe as the first task, this message appeared, and provisioning continued. If we try to run that using startasuser, then the message usually appears, but landesk waits for startasuser to exit, and startasuser doesn’t exit until that message is closed.
I say ‘usually’ because we’ve also had issues with placement of startasuser tasks relative to placements of reboots during provisioning. We’re still trying different orders of tasks, but it seems that if we try to use startasuser during the first boot into windows, it fails to display. But if we add a reboot before the startasuser task, the program will be visible.
We’re going to continue trying to get these to work, but we may end up giving up on some of the little things that we had working under 9.0. We’ll also have to deal with minimal feedback (the result code) to fix problems that kill the deployment, whereas we used to be able to see any visible errors from software installers.
Thank you both for your assistance