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?

[TobyLa]

This is very strange, a mod commented on this page and another user 3dmaxer has already opened a ticket over a month ago. 

I gave it a shot and opened also a ticket and got a response just minutes after. Lansweeper support is aware of the problem. The problem will be fixed in a future version, the bug ID is LAN-18106 (look for this id in the next changelogs if the fix for it is included.

I don't know why the support is unable to communicate with some mods to comment here or at least let 3dmaxer know what to expect. Hope this post helps you guys 💪

[3dmaxer]

Last response I received on this issue was that they "escalated this case to our Development Team with high priority." back on 1/15.

[FrankSc]

Dear, 
We are raising the priority of this. We understand that a few customers are experiencing the same issue. 
We'd hope to provide a more accurate timing on when this can be handled, but analysis is still ongoing. We hope to fix this soon in a next release.

[TobyLa]

At least: it seems they did exactly that and we don't have to wait another month. 

[chthompson]

Still no update on this issue.  My case saw that Lansweeper service was not up to date, but it is from what I see 

v. 12.6.1.32

[3dmaxer]

We are on the same version, and are also waiting for a resolution to this issue.

[chthompson]

Same problem.  Task Schedule Error. No logged on user was found. Credential   Win11 clients

updated creds and verified permission 

Windows Server 2019 does not have this problem.  remote deployment windows comes up and runs the cmd of the deployment.

[TobyLa]

I can confirm there's a weird behavior with the "current user" in LS. I don't know if this happens since v12.6.1.32 but I recognized a lot of deployment errors when deploying "as currently logged in user". Everything wents fine while deploying with system account credentials.

The error message I get is:

Result: Package timeout reached. Task Error: The task has not yet run.. Timeout: (300Sec).

I didn't touch the script in a year and I went pretty fine already and also runs when running it manually in user-context. It's definitely a LS problem so I wanted to search for this case in this forum but this post was on the top of all topics 🙂

I didn't open any tickets so it would be great if I could get a response as well if there is something found and/or fixed...

[3dmaxer]

I opened a support case in mid December on this issue.  This broke on us around December 4th, and we were not sure if this was due to Windows patching, or a LS update.