Question

Migrating to new domain - domain suffix

Updated December 10, 2013

asked on December 6, 2013

We have a client about to migrate to a new domain. When the repository is attached, or picked up via broadcast, the domain suffix is included (i.e. server.domain.local). If this were to change would the client continue to pick up the server assuming the scan network for repositories wasn't disabled?

If that option was disabled, would it still pick up the server based on server name alone?

0 0

Answer

APPROVED ANSWER

replied on December 10, 2013

Laserfiche uses Service Connection Points to broadcast repositories to the network. The exact mechanism is described here. In your case, you may need to delete and republish the SCP for the repository after you move your Laserfiche Server to a new domain.

1 0

Replies

replied on December 6, 2013

We had a client do this a few weeks ago. The repository broadcast still showed up as the old name, but was resolving properly to the Laserfiche server from the clients using "Scan Network for Repositories", I'm not certain in the case of having it attached.

However, we did have to delete every domain user reference in the license manager and Users section of the repository and re-add them manually as some users were able to still get into the server, while others weren't.

Hope that helps.

1 0

You are not allowed to follow up in this post.

Question

Question

Migrating to new domain - domain suffix

Answer

Replies

Sign in to reply to this post.