Windx Security on Terminal Server

[Michael Greer]

A client has used the pxp1510-0001-WPI.exe program to install and configure windx on a terminal server running windows 2016.  It would seem that each user is confronted with the initial "Security" question.  Is there a way to provide a system wide answer to this and avoid it popping up for each windows user. It is only a matter of time (very little time) before someone answers this incorrectly.

[Devon Austen]

Use the WDXTRUST environment variable.

https://manual.pvxplus.com/?PxPlus%20Installation%20and%20Configuration/Customizing%20PxPlus/Environment%20Variables.htm#Mark3

[James Zukowski]

Will that work for their 2016 system? Documentation says it was added for 2017.

[Devon Austen]

The documentation is correct it was a feature added in PxPlus 2017 (V14). The original question stated they are using PxPlus 15.10.0001 which is PxPlus 2018 so they should be able to use it.

[James Zukowski]

Oops. I let myself get confused with "terminal server running windows 2016"...

[Michael Greer]

Devon,

While this will certainly work I was hoping to emulate the behavior where you select the "Disable" option to that initial security dialogue.  I know there is a Windx .ini file out there.  Would setting/deploying that have the desired effect?

[Mike King]

Michael

If you set the WDXTRUST environment variable to a list of sites, it effectively does a disable on the sites specified.

You can also update the WindX.ini file yourself if desired, although we strongly recommend against fully disabling the security.  If you do and the workstation happens across a web site with a "windx://someserver" URL, the system could auto-launch a WindX connection and gain access to all files on the workstation.

[Thomas Bock]

Michael

As you might not have access to each user's environment, you can disable the dialogue completely by modifying the panel SECURITY_CHK in [WDX]WindX/windx.de. Use this as the pre-display logic

Code Select Expand

cmd_str$="END",arg_1$="NO"