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

Question

Question

LF Client deployment via Active Directory

asked on July 28, 2016

A customer wants to deploy the LF Client using Active Directory, however the customer has said that to do this they require a single msi file. (I am not familiar with deployment via AD so I don't know if this is true or not). The LF Client installation file set currently consists of a mix of msi and cab files.

The customer is not using Microsoft SMS (System Management Server) or Microsoft SCCM (System Center Configuration Manager).

Assuming the customer is correct (i.e. the client cannot be deployed because it is a mixture of msi and cab files) can anyone tell me how to deploy the client via AD?

Alternatively, if anyone knows that the client can be deployed via AD with the current client installation file set, can you let me know how you did it?

Thanks,

pete.

0 0

Replies

replied on August 8, 2016

Hi Mark,

Many thanks for the response. The article addresses the unattended installation requirement however, not being familiar with software deployment via AD, I needed a bit more to give to the customer.

 

Hi all,

Here is the response I received from LF. It covers:

  • Creating a batch file for unattended installation
  • Formatting a Command-Line or Unattended Installation String
  • The automated distribution process using Microsoft Group Policy Objects (GPO). (MSDN webpage).
  • Unattended install script for use with Group Policy. (LF Answer 47732. Script posted by Blake Smith. Thanks Blakeyes).

 

Links are in the LF response:

The LFI client is split into multiple MSI files by design. To run multiple MSI files automatically, you can create an batch file to install Laserfiche run the create a batch file to install Laserfiche using a command line prompt or install Laserfiche using an unattended installation string. To automate the distribution process, you can use the Microsoft Group Policy Objects (GPO) to set condition to run the batch files to install on different machines. This will save system administrators manual effort to type in to command prompt on each machine. Check out this discussion for a sample Unattended install script.

Thanks to Mark and an unknown LF engineer for the responses and to Blake for the script.

pete.

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

Sign in to reply to this post.