1

a client of mine uses the task manager to trigger (start) a process to do something. This process contains a UI, and needs to be a single instance at all times (been taken care of).

Everything runs smoothly from the task manager, accept if you need to set the task manager settings to:”run whether user is logged on or not” (see the answer why this is a problem here: http://social.technet.microsoft.com/Forums/en-US/c03d6691-b058-4f8d-961c-e8eba25bbaed/task-scheduler-problem-run-whether-user-is-logged-on-or-not

Ok..no problem. We just let the task run only if the user is logged on. Still works fine (even with computer locked).

But, this night windows had an update and the system automatically rebooted. Logging of the user and therefor the task manager was not able to run the tasks. :-(

Since the program has a UI (is needed), I cannot switch to “run whether user is logged on or not”. What would be best practice to:

  1. logon again as the user that needs to run the application
  2. make sure that the started application, is actually visible to the user, when he logs in? (unlockes the computer)

I know how to run processes with different user credentials in C#, but that’s not the solution for this problem.

Automatically logon a user (and lock the computer) when the computer has started, would be great. Is this in any way possible? Or is there another solution for my problem?

Regards,

Matthijs

user369122
  • 792
  • 3
  • 13
  • 33

3 Answers3

2

Create and install a Windows Service to do the actual work. This service will not require a logged on user and by definition only runs with once instance at a time, so this solves all of your problems.

Then let the UI communicate with the service through IPC and let the UI application start upon logon.

You can alternatively of course just let the user autologon, put a shortcut to the program in the startup folder and call the LockWorkStation() function after your application starts, but I would not take nor recommend that approach as it has security issues.

Community
  • 1
  • 1
CodeCaster
  • 147,647
  • 23
  • 218
  • 272
  • I was actually hoping for something else, but I was kind of "afraid" that your idea would be the only right one... too bad...but thanks anyway – user369122 Nov 14 '13 at 11:02
  • 1
    @user369122: you should not be too afraid of this answer. Compiling an application as service should be easy using Visual Studio. Writing a client-server applications for the first time might need some learning, but it is worth the effort. – Zane Nov 14 '13 at 11:09
  • @ Zane. With "afraid" I was more pointing out to the extra effort (and costs) to cut the whole project up in work and gui stuff. You are right that's not that hard to create a service. @ CodeCaster I'll discuss this with my client, but I'm not so keen on systems being available to everyone around. – user369122 Nov 14 '13 at 11:17
  • 1
    @CodeCaster start upon logon combined with LockWorkStation() is fine with the client. Thanks! – – user369122 Nov 14 '13 at 11:51
0

you can automatically login to a user account at startup with this :

http://technet.microsoft.com/en-us/magazine/ee872306.aspx

  1. Click Start, type netplwiz, and then press Enter.
  2. In the User Accounts dialog box, click the account you want to automatically log on to.If it is available, clear the Users Must Enter A User Name And Password To Use This Computer check box.
  3. Click OK.
  4. In the Automatically Log On dialog box, enter the user’s password twice and click OK.

The next time you restart the computer, it will automatically log on with the local user account you selected.

Xaruth
  • 4,034
  • 3
  • 19
  • 26
0

Automatic Windows logon as a predefined user is a convenient feature for single-user machines or home computers. This removes the hassle of unnecessary repetitive password entering in a secure environment and speeds up Windows startup and user profile warmup.

Howsoever, please do never forget that this is a kind of a security breach and should never be applied on computers, which could fall into hostile hands.

A detailed explanation of the procedure, without messing-up with the Windows registry, is available HERE.

user3130351
  • 85
  • 5