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

Question

Posted to Laserfiche Lounge

Question

Laserfiche Lounge

Sharepoint Integration

Laserfiche
Updated August 14, 2019
asked on May 4, 2017

I have a client who is interested in using Sharepoint Integration, however before they go forward, could I get the following questions answered?

 

  • Based on the installation instructions, it appears the Sharepoint Installer is installing via an .exe file.  Which indicates that it is installing files directly into the SharePoint servers.  Could you elaborate on the installation itself?  Meaning is this installing files and folders in its own directory and/or in the SharePoint directory?
  • I see that a Web Part comes with the installation.  Does the installer simply add in the web part solution files to a directory for deployment?
  • What would happen upon retraction of the Web Part to the SharePoint content database(s)?
  • We currently have four SharePoint Servers in our farm and one Office Web Apps Server.  Two of the servers are run the Application Services while the other two are Web Front End Servers.  Does the installer only need to be added to the Application Services servers?
  • Once installed, what would the result be of uninstalling the software?
  • Once installed, is there any possible issues during major upgrades to the databases (for example SharePoint 2013 to SharePoint 2016)?
  • Microsoft’s patch cycle is now more aggressive than ever, how can this software be impacted by a patch release?
  • Will the install automatically stop SharePoint’s Claims to Windows Token Service?
  • Could you elaborate a bit on how a user would move a file from SharePoint into Laserfiche?
  • Could you elaborate on what happens to the file itself during the move?
  • Could you elaborate on how Kerberos authentication is configured for the communication in SharePoint Search Center?
0 0

Answer

APPROVED ANSWER
replied on May 4, 2017
  • It installs files into its own folders and installs supporting dependencies into the GAC.
  • Yes.  It also installs a tool to deploy the web part and make required changes to the SP web.config file.
  • The web part would no longer be usable.
  • You would install it on all 4 SP machines.  Different pieces will be relevant on different machines, but the installer doesn't separate them out.
  • The software will be removed.  Web Parts won't be automatically retracted, but they will no longer function properly.
  • The current integration is not compatible with SharePoint 2016.  We hope to have that updated for later this year.
  • I wouldn't anticipate any problems, but it's not really possible to say that arbitrary environment changes won't have an impact.
  • No.
  • Laserfiche would be configured as a records center.
  • It can stay or it can be deleted or it can be replaced with a link, depending on configuration.
  • The search center should be able to delegate the user's identity to the Laserfiche server.  Because C2WTS is involved, only constrained delegation can be used.
1 0

Replies

replied on May 5, 2017

Thank you Brian, I appreciate you taking the time to respond. That cleared up a lot and I'll pass on your response to the customer

0 0
replied on August 14, 2019

This was an informative read.  Forgive me if my question sounds remedial but I'm slightly newer to Laserfiche in general.  Has Laserfiche been updated to accommodate SharePoint 2016?  I have a customer who is looking for a full integration and I'd like to confirm this before my conversation with them.  

0 0
replied on August 14, 2019

Yes, there is an updated SharePoint Integration module that supports SharePoint 2016. This is available in the Laserfiche 10.4 and higher installation packages that are available from the Support Site.

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

Sign in to reply to this post.

Details
Related Posts
Loading ...