Deploying the new Logon App 4.1.0.97_x64 failing
I have the msi in a share on a server along with the wlconfig.cfg file as always has been. Whether I try to push it with a script through our NinjaRMM or just run the file manually from a PC, the LogonApp installs but then fails to work saying the configuration file is invalid and to contact an admin. Then it just allows you right in.
I see this in my log output: MSI (s) (F0!B0) [10:23:23:115]: Product: Logon App -- C:\Program Files\WatchGuard\Logon App\Resources\wlconfig.cfg - File not found.
This path does not even exist on the machine. There is no watchguard path under Program files.
If I go back to using the last installer I downloaded AuthPoint_Logon_App-4.0.1.84_x64 then it deploys just fine and works as expected.
This is my command
msiexec /i "\servername\deployment$\authpoint\AuthPoint_Logon_App-4.0.1.84_x64.msi" /qn /log \servername\deployment$\authpoint\output.log CONFIG_PATH="\servername\deployment$\authpoint\wlconfig.cfg"
Comments
It should create that path during install. You state it works fine if you deploy the last installer v4.0.1. So I am assuming this only happens on the latest v4.1.0?
If its happening on the latest version only, what does the output.log show when you run it via msiexec?
We may need more details. I suggest getting a case created so we can review the data and see if there is something on the computer blocking the installer from creating the path.
Another thing, is if you already have 4.0.1 installed and are upgrading to 4.1.0, then the path is already created.
We had a much older version installed that was deployed via a GPO. I have a script that deletes the files and and reg entries for it as it was unable to be uninstalled. It never showed up on control panel when it was deployed. I removed that version, then pushed the script above using the 4.1.0 version and it failed on 15-20 in the environment (a successful failure, it reported success but only the app installed, not the config). Unfortunately I do not have the log as my scripts recreates the log on each install and I forgot to save it from when I created the ticket and tried the old version which works fine so I pushed the older version out to all the PC's as they were all broken
So I went from an old 3.something version (years old) to 4.1.
4.1 installed but did not work (the interface was new so it did install...)
Uninstalled 4.1 and went back to 4.0.1 which worked no issue on all machines
I installed the same 4.0.1 version to 5 other companies a couple weeks ago also with no issues coming from the old 3. version. I just saw yesterday that a newer version was out so I grabbed that instead of deploying the same one they used.
Gotcha. So nothing reported that matches your issue. I think we would just see if we could repro the issue and gather data on it. And put it in a case so we can investigate thoroughly.