Re-federating Landmark

 3 Replies
 1 Subscribed to this topic
 32 Subscribed to this forum
Sort:
Author
Messages
LarryTD
New Member
Posts: 1
New Member

    Is it possible to re-register the Landmark system, and then refederate it again with LSF? Can a federated environment be unfederated for version 10.1.1?

     

    Asking for a friend.

    Carl.Seay
    Veteran Member
    Posts: 109
    Veteran Member
      It's not supported or documented by Infor. It is possible, but kind of painful.

      If you do venture that way, make sure to grab a backup of everything: LMK/LSF GEN DB's, LMK/LSF system directories, and LSF LDAP.
      AlanK
      Basic Member
      Posts: 16
      Basic Member
        We investigated this a little. Our issue was(is) that we implemented v10 on Windows 2008 R2 server since Win 2012 had no production installs at that time. Now Win 2008 R2 is no longer on mainstream support and there is Landmark functionality that the business unit would like that requires LMK 11 which requires Win 2012. From discussion with Infor there are no plans for inplace upgrades and there is no means of de-federating, upgrading and re-federating. The only option is a complete re-install of LMK and LSF servers followed by federation.
        A potential unoffical approach would be within an isolated VLAN to build out the LMK VM with the same IP and config and working files etc as Prod LMK server and then copy the Prod LSF server in to the VLAN and test if federation still works. From some dicussions the federation process is quite granular writing SIDs to the registries on either side etc so this would not be expected to work but these technicalities may be surmountable with time and being able to retest the process.
        AlanK
        Basic Member
        Posts: 16
        Basic Member
          Hi,
          Just mulling this over a little more - is there value in refederating? Refederating is needed to keep S3 users insync with LMK. If in the next 5 - 7 years or so we all need to be on CSF would it be better to just maintain users on both platforms rather that incur the cost and regression tesing needed to reinstall on both LMK and S3 and then refederate? Our V9 Process flow generated two files for new onboarding accounts and ISS does not handle security changes below the role level so there will always be some need for dual maintenace on both systems.