Current Logged User

[3dmaxer]

I have a case open with support on this question, but looking for some forum member input on this.  We have been having issues deploying packages using the run as logged in user.

When we deploy a job to a computer to run as a logged in user, the job deploys to the PC, but fails due to the job not being set to to an actual logged in user.  When we check the scheduled task, we see that it has picked a user that is not logged into the PC.  In this case its an administrative account that is only used to login to a browser based app requiring elevated privileges.

Even when attempting to deploy to PCs where this admin account has never been used, we can see LS has created a scheduled task with that account configured to run under.

I have read that LS uses WMI to get among other thing the current logged in user.  If I run a WMI query (local and remote) I get the correct user every time.

Any ideas on why LS is getting the wrong logged in user, and it is cached someplace?

[Obi_1_Cinobi]

Hello there!

Thank you for following up, and our apologies for the lack of response here on the community forum. We understand how frustrating that can be, and we appreciate your patience.

Since you already have a support case open, you are on the right track. Our support team will continue assisting you directly through that case, where they have full visibility into your environment and can provide the most accurate guidance.

If you have any additional details or updates to share, we recommend adding them directly to your existing support case to help move things forward more efficiently.

Thank you for your understanding, and we appreciate your continued patience while our team works with you.