Moving Roles

Single Server Mode

In order to retain a single server mode setup by keeping the Management Server, Instance Host and Client Access Server on a single server, follow the instructions below. If only one of the roles in a single server mode setup should to be moved to another server, refer to corresponding section under Multi Server Mode in this article.

• Close all MailStore SPE related programs, except for the MailStore Service Provider Edition Configuration on the old server.
• Stop the MailStore SPE instance host, client access server and management roles.
• Transfer your MailStore SPE license to the new server through our license portal.
• Install MailStore SPE on the new server.
• Stop all roles on the new server.
• Remove all MailStore SPE related certificates from the new server's personal (MY) certificate store.

  

• Export the SSL certificates and private keys from the old server's certificate store and import it to the same location on the new server.

On Windows Server 2012 R2 you can use the following PowerShell command to export all certificats stored in the computers MY store as PFX containers to the current user's desktop

(Get-ChildItem Cert:\LocalMachine\My).Thumbprint | ForEach-Object { Export-PfxCertificate -Cert ("Cert:\LocalMachine\My\{0}" -f $_) -FilePath ("$env:USERPROFILE\Desktop\{0}.pfx" -f $_) -Password  (ConvertTo-SecureString -AsPlainText -Force "not_secure_234") }

Windows Server 2012 R2 Powershell command to import the previously exported certificates from the current user's desktop into the new server's certificate store

Get-ChildItem -Path $env:USERPROFILE\Desktop\ -Filter *.pfx | Import-PfxCertificate -Exportable -Password  (ConvertTo-SecureString -AsPlainText -Force "not_secure_234") -CertStoreLocation Cert:\LocalMachine\My

• Remove the %program files%\MailStore Infrastructure\config directory on the new server, replace it with the config directory from the old one.
• Transfer you instance data directories to the new server.
• When the name of the server has changed, open the management role configuration and adjust the Server Name.
• Start the management role.
• Log in into the management dashboard. When the server name has changed, the connection to the instance host and client access server should be failed.
• Open the client access server configuration and adjust the Server Name and the Management Server if it has changed. The Server Name must be in lower case. Perform the pairing.

  

• Start the client access server role.
• Verify that the connection to the client access server can be established in the dashboard.
• Remove the leftovers of the other client access server in the dashboard.
• Open the instance host configuration and adjust the Server Name and the Management Server if it has changed. The Server Name must be in lower case. Perform the pairing.

  

• Start the instance host role.
• Verify that the connection to the instance host can be established in the dashboard.
• Change the location of the instance host's base directory, if it has changed.

• Change the configuration of each instance to reflect the new Server Name and path.
• Remove the leftovers of the other instance host in the dashboard.

Multi Server Mode

Moving the Management Server

• Start the MailStore Service Provider Edition Configuration tool on a server that is a Management by double-clicking it's desktop icon. On Windows Server Core use the command line prompt to start the executable (default: %PROGRAMFILES%\MailStore Infrastructure\MailStoreInfrastructureConfig.exe.
• Stop the Management Server service.
• Transfer your MailStore SPE license through our license portal.
• Install the MailStore Service Provider Edition on the new server and set it up in Multi Server Mode
• Add the Management Server role on the new server, but do not start it yet.
• Transfer the file MailStoreManagementDatabase.json from the old server's configuration directory to the same location on the new server. By default this file resides in %programfiles\MailStore Infrastructure\config%.
• Start the Management Server service on the new server.
• Adjust the Management Server setting in the configuration of each Instance Host and Client Access Server by clicking on the corresponding Configure... button in the MailStore Service Provider Edition Configuration tool.
• Log on to the Management Console and check the dashboard for the connection status of servers and roles.

Moving an Instance Host

• Start the MailStore Service Provider Edition Configuration tool on a server that is a Instance Host by double-clicking it's desktop icon. On Windows Server Core use the command line prompt to start the executable (default: %PROGRAMFILES%\MailStore Infrastructure\MailStoreInfrastructureConfig.exe.
• Stop the Instance Host service.
• Install MailStore Service Provider Edition on the new server and set it up in Multi Server Mode.
• Add the Instance Host role.
• Pair with the Management Server.
• Start the Instance Host service.
• Log on to the Management Console and check the dashboard for the connection status of servers and roles.
• Follow the Moving Instances guide to move the instances to the new instance host.
• Remove the Instance Host role from the old server.
• Finally remove the instance host that still exist with the old host name.

Moving a Client Access Server

• Export the certificates, including their private keys, that are visible to the end users on the old client access server. By default these are MailStoreClientAccessServerHttp and MailStoreClientAccessServerImap, but not MailStoreClientAccessServerTcp.
• Import these certificates into the new server's personal (MY) certificate store.
• Start the MailStore Service Provider Edition Configuration tool on a server that is a Client Access Server by double-clicking it's desktop icon. On Windows Server Core use the command line prompt to start the executable (default: %PROGRAMFILES%\MailStore Infrastructure\MailStoreInfrastructureConfig.exe.
• Stop the Client Access Server service.
• Install MailStore Service Provider Edition on the new server and set it up in Multi Server Mode.
• Add the Client Access Server role.
• Pair with the Management Server.
• Adjust the certificate settings in the Configure Client Access Server Role dialog to use the imported certificates.
• Start the Client Access Server service.
• Log on to the Management Console and check the dashboard for the connection status of servers and roles.
• Remove the Client Access Server role from the old server.
• Finally remove the client access server that still exist with the old host name.