Start application in foreground on Windows 2008 reboot

Hi Experts,

I have an application that needs to run in the foreground on a Windows 2008 server 24 x 7. The problem is how to overcome the need to reload the programme when the server reboots itself for some reason (e.g. Windows system updates). It is a hosted server in a datacentre on the Internet and at present we have to run an RDP session and keep it open then keep monitoring it - absolutely the wrong solution. We cannot convert the application to a background process.

We could install a VNC remote control server (like Tight VNC) on the server's Administrator console, connect over the VNC connection, login as a Windows 2008 user and run the application. Then just disconnect the VNC session and the application will continue to run - until the server reboots of course.

One solution would be to have a script with system commands to automatically start a user login session on reboot and load the application into that, but I don't know anything about scripts.

Any help would be greatly appreciated.

Thank you.

Stephen.



I think you should be able to start the application with Task Scheduler and then in General, set to run whether the user logs on or not.

Best to start as service, but you say this cannot be done.



I think you should be able to start the application with Task Scheduler and then in General, set to run whether the user logs on or not.

Best to start as service, but you say this cannot be done.



Combine this method to auto logon w/ John's post: https://support.microsoft.com/en-us/kb/324737
For an easy way to do this, which also encrypts the creds, use Autologon for Windows by Sysinternals



What is the application? Usually to start an application in the foreground, a login is require.
Does it matter which user logs in?
Placing a shortcut of the application in the startup folder of the %programdata%microsoftwindowsstart memuprogramsstartup
Place the shortcut to the application here. No matter which account logs in, the program will be started.



AutoLogon is certainly the way to go, combined with putting a shortcut to the application in the users Startup folder. If anyone else RDPs into the machine, I'm pretty sure the application should not get started.



Thank you for suggestions so far. It will take time secure some downtime and set up some tests. Thanks again.

Share this

Related Posts

There was an error in this gadget