unattended installation of Laserfiche Products

SELECTED ANSWER

replied on February 19, 2014

Pretty much all of our installation packages these days use the same frontend setup.exe bootstrapper project and therefore also use most of the same commands, even if they aren't specifically documented. First off, you can run setup.exe -? on them to get some of the commands specific to that package. Also, a good tip is to run a logged setup installation (Setup.exe -log "C:\logFolder") and you can actually see what paramaters setup is passing along to your msi's.

Basically all the installation packages that use this particular setup.exe have the same command paramaters as what is documented for Server/Client. INSTALLDIR, ACTIVATIONKEY, INSTALLLEVEL to determine which components to install (if you just want everything you can usually just put 1000 here) or LICENSEPATH, SVCACCOUNTNAME/SVCACCOUNTPASSWORD for services, etc... If you have a command line that works for Server or Client, there's a pretty good chance it'll work just like that for the others, you just might need to experiment a bit (and logging a representative setup run should help with that if something turns out to be non-obvious).

Now, this only applies to newer packages, like IA 8.1.3, WA 9.0, etc... Basically, if the setup.exe looks and acts the same as the Client/Server's, it will use the same parameters.

3 0

View 1 previous reply

replied on February 20, 2014

Justin,

Thanks a lot for the details.

I was building command line to run Quickfields and Workflow but I have a confusion.

Here is my command line for LF Server:

"D:\Install\setup.exe" -silent -log "C:\Logs\ServerInstall" INSTALLLEVEL=150 LICENSEPATH="E:\lf.licx"

LFSSVCACCOUNTNAME="Domain\SRVUser" LFSSVCACCOUNTPASSWORD="Password" LFFTSSVCACCOUNTNAME="Domain\SRVUser" LFFTSSVCACCOUNTPASSWORD="Password"

For Workflow, I changed it like:

"D:\Install\setup.exe" -silent -log "C:\Logs\WFInstall" INSTALLLEVEL=1000

LFWFSSVCACCOUNTNAME="Domain\SRVUser"

LFWFSSVCACCOUNTPASSWORD="Password"

LFWFSubscriberSVCACCOUNTNAME="Domain\SRVUser"

LFWFSubscriberSVCACCOUNTPASSWORD="Password"

Key words for workflow 9.1 and workflow subscriber service in the command above are suspicious? specially the subscriber one.

I first assumed it's the service name but apparently it's not because the service name for LF Server is LFS (keyword for cmd line is: LFSSVCACCOUNTNAME) and the service name for LF Full-Text Indexing is LfFTSrv (keyword for cmd line is: LFFTSSVCACCOUNTNAME).

My guess is that the keyword I would be passing for LF Workflow Server is: LFWFSSVCACCOUNTNAME and for subsciber: LFWFSubscriberSVCACCOUNTNAME ???

Above keyword for subscriber service looks wrong to me.

Any suggestions please?

Thanks

2 0

replied on February 20, 2014

The Workflow installation is not set up to configure the service user for the either one of the Workflow services. Both services need to be configured beyond just specifying the service login, so their accounts are specified through the Workflow Configuration Manager.

0 1

replied on February 20, 2014

In general (independent of Miruna's specific comment above), you only need to use the keywords if you want to send commands specifically to different modules. So if you wanted to use a certain value in all cases, you could just use SVCACCOUNTNAME. You can do that in the Server installation as well. You only need to specify both LFSSVCACCOUNTNAME and LFFTSSVCACCOUNTNAME if you want them to be different for each product.

3 0

replied on February 25, 2014 • Show version history

Thanks a lot Justin.

Very useful

0 0

Question

Question

unattended installation of Laserfiche Products

Answer

Replies

Sign in to reply to this post.