1 of 1 people found this helpful
Urm - yeah ... Windows Context / sessions for one. That's your likely problem cause.
If User "Bob" launches a process, then logged-on user "Jane" won't usually see it.
The "run as a different user" option in Windows works a little different if memory serves - since it doesn't "just" launch the process in a different user-name.
If you specify what client OS / what LANDesk version you're using, we could look at the same setup to see if there's anything that we can see to help out perhaps? (just so we're comparing apples to apples, as it were) ?
In addition - check the stuff I posted in this thread here -- Software won't install on Windows 10 if not logged in -- to help you make sense of what's going on perhaps.
Could be that just basic troubleshooting / log trawling (I list what logs are where & how to enable debug logging) will get you the answer to your stuff.
Hope that helps.
Thank you very much for this information!
We decided to make some changes and get it working while running as Local System, or the currently logged in user.
It was our assumption, that despite being ran as another user, the UI would still be there, just as if we did runas from the command line, but obviously, weren't sure how LANDESK was executing the run as a different user.
The link you provided has a lot of good information also, so thank you for that.