I've created a deployment of MicroStation Connect 10.13 which is set up with a passive (non-interactive) UI. It installs as expected when manually double-clicking the exe. However when this same exe is executed via PDQ Deploy, it apparently stalls out as if it was running the install wizard in interactive mode, so the deployment installation never finishes. What is causing this problem and how do I work around it? The folder on the server is a UNC path, if that matters.
Found that calling .BAT from PDQ Deploy, which in turn runs the EXE is a viable work-around.
I'm assuming that the lyt file was not getting read initially. Im not familiar enought with PDQ but would also suggest that you can just have it process the msi files rather than the setup executable.
Hi David,
I have a question re PDQ from another user. Please could you tell us more about your .BAT solution?
Marc
The line in the batch file simply calls the exe, like this
start "" /min /wait "\\serverpath\Bentley MS CE\10.13.01.01\Setup_MicroStationx64_10.13.01.001.exe"
The "start /wait" command keeps the batch file from continuing to the next step until setup is complete.
The /min switch is necessary to work around a bug in Windows 10 v1903 with calling exe's from bach files.
I just now figured out why PDQ won't run the exe directly -- default behavior is to copy the target locally before execution, which would separate it from the folder with the supporting files. In PDQ Deploy -> Preferences -> Performance, change Copy Mode from Push to Pull, and that might resolve the problem.