You are viewing limited content. For full access, please sign in.

Question

Question

creating a silent install for laserfiche 12

asked on October 5

Hello - I have been reading and trying to decipher many of these powershell scripts that run the LFGET.exe in silent mode for end users.

I have about 150 computers that I want to update Laserfiche to 12 by way of EndPoint central and silent installation.  I have tried many different powershell scripts and each one when I run it gets an error that the powershell script is not correct.  I have tried using the laserfiche Installer whitepage and also a few of the powershell scripts published to this site.  I just can't get this to work in my environment.

 

Any help would be appreciated.  

0 0

Replies

replied on October 5
1 0
replied on October 5

I have read all of those and I am still getting an error with the Powershell script.  I am not by any means a programmer and am just wondering what I am doing wrong.  I had attached the original script in my original post.  

0 0
replied on October 7

To determine if this is a PowerShell script issue or an  EndPoint Central issue I would manually execute the script on a test computer. 

I am making the assumption that you sanitized the attached script but in reality you are replacing the XXXX with a valid Installation code, replacing the "LFDS Server name" with your actual server name, and replacing "LicenseSiteName" with your actual license site name.  If my assumption is incorrect, please replace those values in your script with correct values.  

If the script executes without error on the test computer then the script is valid and the issue resides in Endpoint Central either in how it is being packaged or how it is being deployed.  I don't have enough knowledge of EndPoint Central to provide any assistance there.

0 0
replied on October 10 • Show version history

Hi Kristin,
I reviewed the command you attached and found that the issue is likely related to the command syntax.

Your current command combines both install-local-package and install-product into a single LFGet operation. These are two separate LFGet commands and cannot be used together in the same execution.

For an online installation, the command should look more like:

.\LFGet.exe install-product `
  --product WindowsClient `
  --installation-code "XXXXXXXX" `
  --iacceptlicenseagreement `
  --iagreetoprereqs


Alternatively, for an offline installation, the command should look more like:

.\LFGet.exe install-local-package `
  --package "\path_to_downloaded_package\WindowsClient 12.0.2603.1630.exe" `
  --iacceptlicenseagreement `
  --iagreetoprereqs


Please note that the command must be executed separately for each product you want to deploy. In other words, the --product parameter used with online installations accepts only a single product, not a list of products. Similarly, the --package parameter used with offline installations accepts only a single package path, not a list of package paths.

Additionally, if all you need to install are the desktop client components listed in your script, these components do not require licensing. Therefore, the following parameters are not necessary:
--licensing-mode lfds
--license-server "LFDS Server Name"
--license-database "LicenseSiteName"

If you're still encountering issues after making these changes, please provide the PowerShell error message or the LFGet log output (with sensitive information removed). This may help us better determine what's causing the issue.

0 0
replied on October 10

For a deployment to approximately 150 computers, I would recommend taking a look at the PowerShell wrapper scripts provided by Samuel in the following Answers post:
New Laserfiche version 2025 H2 (Fall release) -- Unattended Installation (LFGet.exe) - Laserfiche Answers


One of the benefits of these scripts is that they can run LFGet actions against multiple products, so you don't need to execute a separate command for each one. Samuel has included several examples in the post as well. If anything is unclear, feel free to ask here and we'd be happy to help.

1 0
You are not allowed to follow up in this post.

Sign in to reply to this post.