Good morning,

We have LF11 and are trying to encourage our users to use the Web Client, so we are trying to avoid widespread installs of the Windows client, but we are dependent on the Office integration and having difficulties installing it on user workstations. Our users are restricted from local admin privileges on their machines so if the install is happening per-machine, IT's typical process is to go to each workstation for the install because it requires elevation - this can get pretty time-consuming after a while.

We do not have Intune (are moving towards it but cannot use it at this time) and have found PDQ to be finicky; our preferred install method is to install via an MSI through GPO. Our IT team extracted the MSIs for the LFOffice-x64_en, the cab file for webtools, and the MSI for lfwebtools from the Windows client folder in the ISO package, but we are experiencing issues with the install. I recognize that the recommended method is to have the user run the EXE file themselves, but that's unacceptable with our security policy and is likely to cause more problems than it solves. 

Currently, there will be a security pop-up (see below, in the bottom-right) that comes up after the install is complete and the connection between Office and the Web Client is established by doing a Save to Laserfiche and adding the repository in Office - and if the pop-up action is not approved quickly enough, the pop-up disappears and blocks the Web Client from connecting to the Office integration. After this happens, the user then cannot open files from the Web client in Office on their desktop (they will endlessly be prompted to download the Office plugin and install it, despite it being installed on their machine).

I haven't been able to figure out where the dismissal is actually registered in Windows (so that I could potentially instruct users on how to approve the security request after the fact), so the only solution I have is to uninstall everything and then reinstall it myself manually so that I can catch the pop-up when it comes up, which defeats the whole point of the MSIs and GPO install procedure.

As it stands, I have a few questions and am hoping y'all can help:

1. Is it necessary to install the Windows client with both of those plugins? How do other orgs that restrict user install privileges and/or are preferentially using the Web client handle the install piece?

2. Is there documentation somewhere about the install order and dependencies of each component?

I wanted to test running the relevant MSIs from the Windows client install folder in case there is an issue with the MSIs we are using (which are isolated in an install folder), but am not sure which pieces might be prerequisites for others etc.

3. I tried creating a batch file like what is recommended in the silent install instructions, but it prompts for admin credentials on the local workstation - is there a good way to get around that? 

I tried researching but most of the solutions seem to require either nested batch files (ex a batch file that invokes another batch file) or PowerShell commands. If I'm running the installs (because even if IT pushes them out, the security pop-up mentioned before can still come up, so I need to assume that reinstalling is a possibility), I don't have admin privileges on everyone's computers. How do other orgs handle this requirement?

I really appreciate any insights that can be provided - this has been a frustrating sequence of trial and error attempts.

Thanks!