siegfried

No errors thrown in Powershell. It just always sets $true in de c:\programdata\Wayk\WaykNow.cfg file.

Regards

Siegfried

Hi,

Now the WaykNow.cfg does add the "VersionCheck", but it is always true, no matter if i use Set-WaykNowConfig -Global -VersionCheck $true or $false.

Regards

Siegfried

Hi,

Since version 2020.1.4 when i type the @ (altgr+2 on our azerty keyboard) character in a remote session, the window minimizes and the screen is lost.

The sessions keeps connected, but i only see this window:

Hi,

When I use the powershell command Set-WaykNowConfig -Global -VersionCheck false nothing happens.

When I use the command line option "C:\Program Files\Devolutions\Wayk Now\WaykNow.exe" config --global VersionCheck false, everything works like expected and i see the "VersionCheck": false appear in the c:\programdata\Wayk\WaykNow.cfg.

Is this option not implemented in the powershell commands?

Regards

Siegfried

Hi,

I have just checked with version 2020.1.3.

The other 2 commands work now but the Set-WaykNowBranding -Global -BrandingPath ... throws an error now.

Set-WaykNowBranding : A parameter cannot be found that matches parameter name 'Global'.

Regards,

Siegfried

Our deployment tool uses an admin user to run the powershell commands. This is elevated.

When i run this commands locally on my client (with an elevated powershell shell) i get the same error messages for the Set-WaykNowConfig settings.

Regards

Siegfried

Hi,

We deploy Wayk Now with powershell. After the installation we run following commands to have our own branding and change 2 settings.

Set-WaykNowBranding -Global -BrandingPath branding.7z

Set-WaykNowConfig -Global -AllowPersonalPassword false

Set-WaykNowConfig -Global -ControlMode AllowRemoteControlServerOnly

The branding does work but the other 2 commands error out with permission denied to c:\Programdata\Wayk

Are these settings not allowed Global?

How can we change the settings remotely for all the users on that computer?

Kind regards

Siegfried

Hi Richard,

Just did the updates. The connectcore failed issue is indeed solved!

Thanks

Siegfried

Hi,

At first sight, that matches my issue. I'll wait for the update to test it further in RDM.

thanks for the help!

Siegfried

Hi Richard,

Works like a charm now! Thanks!

Will this fix also be included in a future version of Remote Desktop Manager? There i still get ConnectCore failed:

regards

Siegfried

Hello,

In attachment the log file.

regards

Siegfried

Hello,

I have the same error message with this option enabled.

regards

Siegfried

Hi,

I have installed Wayk Now on 2 hosts with the msi installer.

When trying to connect i always get the error message "The connection could not be established". When I choose the prompt for permission authentication method, the client side can accept the request, but then i get the error message popup on the operator side.

kind regards

Hi,

Just letting you know that we didn't had any connection problems in the last week.

Siegfried

I have the same problem for a week now. Happens every now and then. the logfile is in attachement.

Siegfried

thanks for the quick reply and resolving!

When I use Private vault search on a Wayk Now session with Secure Remote Delegation, I get an error message saying The username is required!