Service stopping at reboot

[davidgrudek]

Does anyone know of a way to make the service for ultravnc be one of the last services to stop so if something hangs during a reboot that we can cancel it before it kicks you off.

Real Vnc does this and it would be nice to make UltraVNC do this. Not sure if this is a windows setting or ultravnc service thing.

[B]

I did not know RealVNC does that -- can you explain what or how it does in a bit more detail?

There was recent discussion of this concern at [post=72168][/post]

[davidgrudek]

Yes that is exactly what we are after.

In many cases we reboot a machine and it hangs on some service or app that puts up some dialog box to kill it. We cant see that because uvnc has already begun shutting down.

Remote desktop does not kick you out til the user is fully logged off. If uvnc could do the same then it would be greatly helpful.

Real vnc does this. How I do not know but I tested it and it does work.

[B]

Unfortunately in that thread we didn't make a clear enough distinction about UltraVNC running in <b>service</b> mode.

If it's running as a service, I think it <b>should</b> persist at least until the user is logged off, because ordinarily, for example during a log out/log in sequence, VNC will stay active right back to the login or Welcome screens.

In other words, it should already do what Real does if UltraVNC is running as a service.

Are you saying it does not?

Remote desktop, of course, is completely different -- your session doesn't exist outside your current login...

[davidgrudek]

No the second you click restart it closes the session. Sometimes you can get back in but many times you can not.

[B]

This seems to be the key, from http://msdn.microsoft.com/en-us/library ... S.85).aspx

Note that during service shutdown, the SCM does not take dependencies into consideration. The SCM enumerates the list of running services and sends the SERVICE_CONTROL_SHUTDOWN command. Therefore, a service may fail because another service it depends on has already stopped. To set the shutdown order of dependent services, use the SetProcessShutdownParameters function. The SCM uses this function to give its handler 0x1E0 priority. The SCM sends SERVICE_CONTROL_SHUTDOWN notifications when its control handler is called and waits for the services to exit before returning from its control handler.

Edit: For you does it seem to make a difference if on the first time you connect no user is yet logged in at the machine, so you're starting VNC control outside the context of that user?

[davidgrudek]

No, no difference.

[davidgrudek]

Is this something that will get fixed in the version 2 release?