Resolved - Preconfiguration warning

[Prisma]

Hello Rudi,

please excuse me to ask this question redundant, but the answer I got in February was a little bit confusing:
https://forum.ultravnc.net/viewtopic.php?t=29262

I can't reproduce the warning "This machine has been preconfigured...". So I have to be sure to hit the right setting with our next release.
Why should YY's mentioned solution

Code: Select all

[admin]
SocketConnect=0
HTTPConnect=0
DisableTrayIcon=1
AuthRequired=0
AllowProperties=1 <--- !

solve the problem? To allow changing the properties (e.g. allow re-enabling socket connections) should provoke the warning instead of preventing it.

Could you please explain me in short words why AllowProperties=1 is correct? AllowProperties=0 appears more logical. And you can see above: How to change properties without TrayIcon? Why this warning then?

[Rudi De Vos]

Code: Select all

 if (strlen(plain) == 0)
			 if (!m_allowproperties || !RunningAsAdministrator ()) {
				if(m_server->AuthRequired()) {
					MessageBoxSecure(NULL, sz_ID_NO_PASSWD_NO_OVERRIDE_ERR,
								sz_ID_WINVNC_ERROR,
								MB_OK | MB_ICONSTOP);
					PostQuitMessage(0);
				} else {
					if (!vncService::RunningAsService())
						MessageBoxSecure(NULL, sz_ID_NO_PASSWD_NO_OVERRIDE_WARN,
								sz_ID_WINVNC_ERROR,
								MB_OK | MB_ICONEXCLAMATION);
				}

[Prisma]

The code is unambiguous. OK, I'll put AllowProperties=1. But the sense of allowing to change properties to prevent a warning is not visible for me. But the good thing is: I don't have to understand it

[Rudi De Vos]

Another solution is to set a dummy password.

[Prisma]

Yes, I know. This was our previous solution. But with a random set password we produced chars winvnc wasn't able to process. So it seemed to be the safer way to disable auth by option.

No problem Rudi, I'll set AllowProperties=1
THX for Info

[Rudi De Vos]

setpasswd.exe: used by the installer to set a random password in ultravnc.ini
in case the password is empty.

[Prisma]

Sorry for bringing this post up again, but I was now able to reproduce this popup on a customers Server 2008 R2 with VNC 1.1.8.0. And the option

Code: Select all

AllowProperties=1

definitely didn't help. The popup appeared anyway. Here is again the complete config:

Code: Select all

[admin]
UseRegistry=0
UseDSMPlugin=1
DSMPlugin=vncstarter.dsm
SocketConnect=0
HTTPConnect=0
DisableTrayIcon=1
path=C:\Users\xxx\AppData\Local\Temp\xxx\
CaptureAlphaBlending=1
RemoveWallpaper=1
AuthRequired=0
AllowProperties=1
service_commandline=-autoreconnect ID:1234 -connect xxx.xxx.xxx
[poll]
TurboMode=0
PollFullScreen=1
EnableHook=1

Is it possible that the internal flag m_allowproperties isn't set in conjunction with DisableTrayIcon=1 ?? Or just a bug within 1.1.8.0?

[Prisma]

Popup disabled in 1.1.8.7