Hi, I have a service app for remote access, all works well, just need to fine tune it know hence this strange question.
Basically my remote apps starts as a service so I can see the Logon screen etc, then when windows restarts/shutsdown the service is obviously stopped, but my service seems to be the last one to run on startup, the logon prompt is on screen for ages before my service is started, is this because it was the last service to be installed? is there a way to trigger which order services are started in?? or does windows start them all at once so maybe it's just my app taking so long to initialize?
Hope that makes sense, the service is set to Automatic and is using local account with Interactive := true
I also want to try and delay the Stop command when windows is shutting down/restarting etc, again my service seems to be among the first to be stopped so I don't see much of the shutdown process remotely, hopefully this is connected again to a Service Stop order list somewhere, I want my service to be among the last to be stopped, maybe I can resist this for a while from within my service? although that would be an ugly way to solve the prob.
Thanks in advance for any help with this!