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

Question

Question

Latest installation guide/help files

Version 10
Updated July 22, 2017
asked on July 18, 2017

Hello Laserfiche Experts.

The latest version of LFDS (10.2) has been released several days ago, right in time for the new installation. The process is different from previous version, could you please point me where can I get updated guides/help files, especially for cluster deployment. 

https://support.laserfiche.com/kb/1012253/current-online-laserfiche-product-help-files still refers to v10.

 

Problem I have now that after installing on two nodes with cluster option selected, both nodes have LFDS service running in Auto Startup and there is no New Laserfiche Directory Services resources added to the role. It shows role running and allows to move it from one node to another, however I could not confirm if this is proper setup.

Thank you,

 

 

0 0

Replies

replied on July 18, 2017

Hi Vladimir,

DId you follow the instructions in the following link

https://support.laserfiche.com/kb/1013718/directory-server-10-configuration-information-for-windows-failover-clustering- 

Regards,

Mark

1 0
replied on July 18, 2017

Hi Mark,

The link you're referring to is extraction from the help file and it refers to the v10, not 10.2.

Thank you,

0 0
replied on July 18, 2017

The clustering documentation from 10 is still applicable to 10.2: there have been no changes to the clustering procedure for standard installation of Directory Server + Sercurity Token Service on the same machine.

As we continue with our release rollout, we will update versions on various KB articles.

0 0
replied on July 19, 2017 • Show version history

Sorry Brianna,

At least one additional window has been added and there is no step 4.3 during installation and it is one of the vital steps. Also LFDS service is running on both nodes and set to Auto - don't think it is proper on the failover cluster.

  1. Using Windows Failover cluster Manager, under Roles, create and configure a new role.
    1. In the wizard, on the Select Role step, select Other Server.
    2. On the Client Access Point step, specify a cluster role name.
    3. When prompted to select a Resource Type, choose Laserfiche Directory Service Resource.
0 0
View 6 previous replies
replied on July 19, 2017

Can you add a screenshot of the extra window you're seeing?

Step 4.3 in the KB article above is not part of the installation (the entire step 4 is in Windows Cluster Manager)

The service status is covered by the note at the end of the steps.

0 0
replied on July 19, 2017 • Show version history

We have not made any changes to the clustering configuration. The additional window at the end of the installation is unrelated to clustering, and you can simply leave the default settings.

As mentioned, documentation will be updated as we continue the release rollout.

As Miruna noted, step 4.3 is not part of the Directory Server installation.

4. Using Windows Failover cluster Manager, under Roles, create and configure a new role.

It takes places in the Windows Failover Cluster Manager, as stated in the article you quoted.

We are leveraging the Windows feature here, with very little customization for LFDS. If you are unable to see that role after following the steps carefully, be sure that you:

  • Meet the OS requirements (Windows 2008 r2, 2012, or 2012r2)
  • Have installed the required Windows Features, Windows Failover Clustering
  • If on a 2012 machine, have installed https://support.microsoft.com/en-us/kb/2803748
  • Have installed all the required Directory Server components
    • Directory Server
    • Web STS
    • Clustering component
0 0
replied on July 19, 2017 • Show version history

Thanks Brianna, I understand now and you're absolutely right - LFDS went through without any problems. The right wording would be - cluster configuration steps in the help file should be adjusted. The problem is - client is waiting for this step to proceed and then move licensing to the new service... May be your developers have steps available? For example should I use Other Server role or General Service will work? If General Service is selected should it be created for LFDS and STS and what are dependences?

Thank you very much again and sorry for the confusion. 

0 0
replied on July 19, 2017

If that resource is not appearing in the Windows Failover Clustering manager and they have already checked the requirements I mentioned (specially the KB for the 2012 machine), I suggest they re-run the installer and choose to "modify", and make sure that the cluster feature is installed.

If it is selected but the resource is still not present, they could try uninstall->reinstall.

At that point, if the still do not see the resource, I recommend opening a support case. They'll ask you for more details, such as operating system, and would likely need to see screenshots of the Failover Configuration Manager.

0 0
replied on July 20, 2017

Thank you Brianna,

We're on 2012R2 and KB is not for this system, I went through both processes (modify and uninstall and install) making sure clustering is selected and during installation it actually passes cluster detection prerequisites.

Opened the case, will update when get it resolved.

Best Regards,

0 0
replied on July 21, 2017

Dear Vladamir,

I successfully installed the Directory Server cluster failover. But not without some challenges. I followed the KB: 1013718 instructions all right and the Laserfiche Directory Service Resource was installed fine, but I never got come online. So I resolved it by removing the Resource installed during the wizard installation and added the Directory Service as a Generic Service on the Directory Server Role and it worked fine. I hope you give it a try.

Regards,

Mark

1 0
replied on July 21, 2017

There are 2 parts to the Directory Service that come into play when setting up a failover cluster: the service itself and the login page (sometimes referred to as the WebSTS or LFDSSTS site in IIS).

If you're using LFDS for license management only (and not for single sign-on), then the login page is irrelevant. But if you're using it for single sign-on and the active node fails, your users won't be able to sign in if the login page is left on the dead node.

In 10.0, they both have to be on the same machine, so setting up the resource as a "generic service" is not enough because that would only handle the failover of the service, while the login page would be left on the failed node.

In 10.2, the service and the login page can be on different machines, so you can cluster the service as a generic service. However, if you do that, you also need to set up a cluster in IIS for the LFDSSTS site.

 

0 0
replied on July 21, 2017 • Show version history

Thank you very much Miruna,

I think will use Generic service (and Help Desk confirmed) without SSO first and if required will do cluster for LFDSSTS.

Best Regards,

0 0
replied on July 22, 2017

Thank you Mark - did installation yesterday, used Generic Service, however not inside Other Server Role - instead of it. Have some tests to do on Monday.

Best Regards,

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

Sign in to reply to this post.

Details
Related Posts
Loading ...