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

Question

Question

lfoffice_en vs. LFWebOffice103

Web Client Installation and Upgrades
Updated August 30, 2018
asked on August 1, 2018

When you are prompted to download the office integration through WebAccess you download the LfWebOffice103.  

In the install files in the Full Client there is an lfoffice_en file which seems to be the installer of the office integration.  

Is there a difference?  If someone wanted to push out that install to all machines because users cannot install the office integration would they use the lfoffice_en?

 

Thanks,

Chris

 

0 0

Replies

replied on August 1, 2018

Hi Chris, 

The LfWebOffice103 package is a zip containing the lfoffice_en msi package as well as a few other components such as the setup UI package itself and localized resources. It's basically a wrapper for the msi package in the same way that SetupLf.exe is a wrapper for it in the desktop client. The lfoffice_en msi itself is exactly the same. 

0 0
View 1 previous reply
replied on August 2, 2018

Thanks Justin,

So I would tell the client that they need to deploy the lfoffice_en then?

0 0
replied on August 2, 2018

Yes, that should be ok. For Scanning you would also need to include OCR which is part of the Scanning download package in addition to the lfscanning_en msi, but that's not relevant for the Office package. 

0 0
replied on August 30, 2018

What install msi is called from this screen?

Apparently people have the Office Integration already but are getting this prompt

0 0
replied on August 30, 2018

Hi Chris, 

It's always the same msi (lfoffice_en.msi). If you haven't enabled the chrome extension, the browser might not be able to detect that it is installed. It will also prompt you if an upgrade is needed (although I believe it indicates that differently). 

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

Sign in to reply to this post.

Details
Related Posts
Loading ...