Quote from: Mike King on October 19, 2020, 11:11:14 PM
If you are still looking for a way to avoid being asked about how to avoid the security settings, have you considered using a .BAT file?

Something like this will work to connect to Simple CS:

@echo off
set WDXTRUST=%1
start windx://%1:scs/4093/

Save this as WindX.bat, and to connect simply enter the command (or create a shortcut) of

  windx server

Can you elaborate on this a little more?

Is this BAT file supposed to run each time or just on the 1st install?
What do you mean by enter the command or create a shortcut of windx server?

I need you to "dumb" this down a little more for me.... I understand what a batch file is...but I need to understand exactly how this works and what this does....

Quote from: Thomas Bock on October 16, 2020, 02:33:47 AM
Each user has his own environment. Maybe that is the reason.

Another way to circumwent the security check is to deploy a modified version of the library 'windx.en' in the WindX subdirectory on the client.
Add a pre display logic in the panel 'security_chk' to execute cmd_str$="END",arg_1$="NO"

I have absolutely no idea how to modify that library file.

Could you perhaps send me a modified version of it where this command string is inserted? This would make things so much smoother for deployment.

Thank you!

Is there anything that would prevent a domain admin from seeing the WindX security pop-up?
During our testing phase of the rollout, we installed on 2 domain admin computers (myself and a co-worker in our department) and neither one of us saw the security prompt upon installation, but our users are seeing it....

Anything that would be in place to cause a domain admin to NOT see the prompt by default?

Having one more issue.

If I put the environment variable in System Variables...should the prompt be popping up for WindX Security...or does it have to go into USER variables?

I put it in system variables with a PS script ran in the background and still had the prompt pop up for another user...

Ok so I managed to set the environment variable to bypass the security prompt, but now when a user logs into our ERP server (without having to answer the security prompt) we get the following error...
(see attached image)
This error does not come up if we answer the security prompt through normal install (without editing environmental variables)

Can anyone assist?

Quote from: Devon Austen on October 13, 2020, 09:22:24 AM
When doing the install on the client define a user Environment variable WDXTRUST to be the hostname or IP address of the WindX server.

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

Where are the Environment Variables defined at?

During installation on v17, after starting WindX...there is a security prompt about using WindX Security.
We are using PDQ deploy to deploy the software silently, is there a config file with a paramenter to answer this question automatically (to disable WindX security)
We don't want this popping up after installation.

Hi!
We're using an application called PDQ Deploy to upgrade WindX on our end-user PC's. We are attempting to use this application to silently remove the old version and install the new version without having to interfere with the end users PC's.

During the setup process for WindX we change the font of the WindX window to specific parameters.
Is there a configuration file that can be used for the deployment for the font size / type?

Any help or insight is appreciated.