Scalix Forums

I wanted to add this to the forum to help anyone else that tries to install a new server and then move their Scalix setup from an old server to the new one. Inititial setup of the new server worked just fine, could connect with SAC and SWA, no problems.

Then restored the data from the old server /var/opt/scalix onto the new setup and the SAC stopped working. The error message indicated that the userid 228 was having problems but it turns out it wasn't anything to do with the user that was the problem.

What the problem was... fqdn settings. Once the data was restored from the old server the fqdn of the old server was restored along with the data. You need to run the command:

sxmodfqdn -o oldname -n newname

which will update the "data" that has been restored to the new information. There is a chapter in the Admin guide, Chapter 19, Updating Scalix after changing the Name of the Server. This is in effect what was done.

If you were able to setup the new server with exactly the same fqdn as the old server, say in the situation where you were taking the old server off you network, then you might get away with not having to use the sxmodfqdn. In most situations though you will want both servers in operation so you would not have them with the same fqdn.

Additional items to consider when you move your Scalix server from one system to another:

- Outlook Connector 'disables' rules at first login after migration.

- If the Outlook Connector was installed with a DNS alias for the Scalix Server, it reverts to the server name returned from the server by the connector. Therefore when renaming or moving servers and re-pointing the DNS alias you still need to delete and re-add the Scalix connector from the Outlook profile.

These were the experiences at one site and we'll update this post as more come to hand..