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

Question

Question

Migrating Laserfiche to New Domain

Updated February 1, 2016
asked on February 1, 2016

I need to move our LF Server to a new domain but wanted to see if anyone could chime in on anything that I might want check out before the move?  I've already created active domain groups that are in current use with folks who have been merged over, so, everything in my mind tells me I need just re-join and all should work BUT I'd love a second opinion, thanks!

0 0

Answer

SELECTED ANSWER
replied on February 1, 2016

Personally I'd stick with the LF users and groups approach and assign your security with the LF groups in the repository. You can still link the LF group to a domain account/group, but if and when you come to change domains again in the future, you only have to 're-associate' the groups with LF groups rather than having to start assigning security again in the repository or trying to piece together the SID's.

 

0 0

Replies

replied on February 1, 2016

Hi Tim

 

Migrating domains is always a tough one in my opinion, particularly if you are using domain accounts rather than LF users & Groups. The reason behind this is that when you move domains, the SID of the AD user changes and then just shows as a number in the admin console. One thing to check before you do the switch is the current SID of the AD users and groups. That way you have some way of linking everything back up again after the move.

 

Hope this helps! smileyyes

0 0
replied on February 1, 2016 • Show version history

Thanks Chris for the input, I'll be sure to check for that.

 

Just to elaborate more, our old domain utilizes the old way of applying permissions LF Users and Groups, which people are still using on the old domain fine.  For our new domain (and since now we can utilize AD groups for direct permissions) I've built Organizational Units to represent each type of permission I'd like to grant and imported that group into Laserfiche and applied it to our repositories appropriately.  So as we migrate users they are added to an AD Group and that's it.  I've also utilized the IP address instead of the FQDN not sure if that'll make it easier on me but I knew the IP wouldn't change. 

 

Thanks for all your help!

0 0
SELECTED ANSWER
replied on February 1, 2016

Personally I'd stick with the LF users and groups approach and assign your security with the LF groups in the repository. You can still link the LF group to a domain account/group, but if and when you come to change domains again in the future, you only have to 're-associate' the groups with LF groups rather than having to start assigning security again in the repository or trying to piece together the SID's.

 

0 0
replied on February 1, 2016

I really appreciate your insight, I'll way out my options and moved forward.  Thanks again!

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

Sign in to reply to this post.

Details
Related Posts
Loading ...