Rudi De Vos wrote:I tried to understand what the scheduler is doing different.
-Does it run as service, in what session is winvnc started, wht security context is used
#include "stdafx.h"
#include "windows.h"
int main()
{
system("C:\\Users\\rudi\\Desktop\\UltraVNC\\winvnc\\Release\\winvnc.exe -connect localhost");
return 0;
}
int main()
{
system("net stop uvnc_service");
Sleep(5000);
system("net startstop uvnc_service");
return 0;
}
Rudi De Vos wrote:Just tested and code is ok
The problem is that the schedular does winvnc.exe -connect in session0 and never reach the running winvnc app.[/b]
This is not a bug,
Rudi De Vos wrote:A solution todo what you more or less want
ultravnc.ini
service_commandline = -connect yourhost
- Code: Select all
int main()
{
system("net stop uvnc_service");
Sleep(5000);
system("net startstop uvnc_service");
return 0;
}
You schedular restart the uvnc service and the service try to connect one time to your viewer
Tki2001 wrote:Maybe TightVNC is not trying to locate its settings via the account it is installed upon. If a program does something, another one may, very well, do not do the same thing!.
Some special accounts on Windows have special folders on system, and SYSTEM is one of them. That's why if you try to run a program under the SYSTEM account won't find its configuration files on the normal folder, they will be located under the SYSTEM special folder.
If you try to run ultravnc under the SYSTEM account, then try to find a method to install UltraVNC under the SYSTEM account, and surely it will be fine to run, but truly not advisable.
Or run the task under the same user, ultravnc was installed with.
Rudi De Vos wrote:Updated server to avoid viewer timeouts
https://www.uvnc.eu/download/1217/winvnc1217.zip
Users browsing this forum: No registered users and 3 guests