Package EXE with GUI

[sullivane]

I have an EXE that was created from AutoIT, that pops a GUI informing the user of a shutdown in 2 minutes. The user has the option to postpone 30 minutes.

When I try and deploy this, it will not run (I assume it's because it's running under the scanning cred user not the use that is logged on to the PC).

I tried running under system and currently logged in, with same result.

Is there a way to have this run and show under anyone logged in?

[Susan_A]

Reports can be built under Reports\Create New Report. If you are interested in building or modifying reports, we would recommend reviewing some SQL tutorials, as the Lansweeper report builder uses standard SQL queries. This seems like a good tutorial.

Once you have your report, you can set up a scheduled deployment for it by following these instructions.

[sullivane]

Sorry, I am new to LanSweeper. How would I begin with that?

[Daniel_B]

If you deploy a package in mode "Currently logged on" and on the target machine there is no user logged on, the whole package execution will stop and it will be marked as failed. Executing another package as response to one package isn't supported. You might be able to set up a report on the tsysPackageLogs database table which checks on which machine which package wasn't successfully deployed and regularly initiate an alternative deployment on these machines.

[sullivane]

Question.

So this works, however if there is not a user logged on it fails (obviously). However it does not go to the next action, I am guessing that it's again because no user is logged on? Is there a way to, on fail, go to another deployment?

I tried using final action, but the entire process must just not run at all?

[sullivane]

HAHA. Must have had a typo before.

Thanks!!!!!!

[Daniel_B · Accepted solution]

The option "Currently Logged On" refers to the user who is logged on to the computer while the package gets deployed. Possibly you are facing another issue. Which deployment log message do you receive?

We recommend as well that you copy the Result Command of your deployment package step to a command prompt on an example target computer and execute it there. This likely helps you to find the cause of the issue.