The items in the support folder are prereqs, like .net, visual studio runtime, that sort of thing. The reason you get that prompt is that if prereqs fail, the user can still choose to install the product, which are what's in the Client folder. If you run as full -silent I believe prereqs aren't even checked so you can just try that. Granted, those prereqs are being installed for a reason, you you want to ensure they get included - but that's why the difference.

That said, why are you splitting up the installation? The Client does expect the Support folder to be located at that location relative to it. That's because multiple components (Client, Server, Admin) share those prerequisite and we wouldn't want to force you to download 3 copies of them.

In our case we are pushing out the Client over a very slow connection and are trying to minimize the size of the package as much as possible. We're only including the MSIs that we need for these particular machines (Client, Office Integration and Snapshot). The rest of the components are not necessary and we'd like to reduce the time it takes to deploy.

We've tried configuring SCCM to include both the Client and Support folders but the setup.exe still doesn't seem to find the Support folder when attempting the install.

We are going to attempt the -silent mode to see how that goes, but as you said, the pre-reqs are there for a reason and we'd prefer to have them install properly so the client won't have any issues later on.

Thanks Josh.

I'll check with our deployment team and see if they're individually added each of the folders or if they're pointing to the parent of the two.

For the client you don't need everything, but you definetly need 'Client', 'Support' and 'OCR' (if on 9.1 or later).

Our deployment team did as suggested and deployed a single folder and within that folder it had both the Client and Support folder with the required MSIs. They still had issues as the client computer could not find the support folder MSIs.

Are there any examples our deployment team could refer to with SCCM to confirm they have everything configured properly? Or, can you advise on what logs to look into to see where the issues are? I'm curious if this works differently in the 9.0+ installers than it does in the 8.3.2 and if that could be causing our issues.

Also, when deploying just the Client to a workstation, is it recommended to use the full source Laserfiche installers (servers, client, admin tools, etc.) and then just use the setup.exe to limit what is installed? I'm curious if we're making this harder on ourselves by trying to limit the install package to be just the Laserfiche client.

Thanks again for your feedback!