Multi Server Mode Setup - Revision history

Ltalaschus: MFA hint added

2022-11-14T13:52:02Z

MFA hint added

Ltalaschus at 07:33, 18 July 2018

2018-07-18T07:33:22Z

Bmeyn: /* Set Up Management Server */

2018-05-30T15:29:44Z

Set Up Management Server

Bmeyn: /* Multi Server Mode Setup */

2018-05-30T15:29:18Z

Multi Server Mode Setup

Bmeyn: /* Multi Server Mode Setup */

2018-05-30T15:28:16Z

Multi Server Mode Setup

Ltalaschus: /* Set Up Management Server */

2018-05-29T12:08:04Z

Set Up Management Server

Dweuthen: /* Multi Server Mode Setup */

2018-04-17T12:15:41Z

Multi Server Mode Setup

Dweuthen: /* Multi Server Mode Setup */

2018-04-17T12:15:04Z

Multi Server Mode Setup

Ltalaschus: /* Pairing with Management Server */

2018-04-17T07:59:53Z

Pairing with Management Server

Ltalaschus at 07:58, 17 April 2018

2018-04-17T07:58:10Z

@@ Line 99: / Line 99: @@
 * Click ''Pair with this server''.
 * Enter the user name and password of a MailStore Service Provider Edition administrator.
 * Click ''OK'' to pair this role with the Management Server.
 * The fingerprint of the Management Server's TLS certificate is copied in the ''Management Server Cert'' field of the role to be installed.

@@ Line 9: / Line 9: @@
 * Click ''Add Server Role''
 * Select ''Management Server''
-* Enter your product key into the Product Key field and change Server Name to the fully qualified host name of the server (e.g. mgmt.ms-spe.test). Enter the user name , the full name (optional), the email address and the password of the initial administrator account that will be used to log on to the Management Console. The password must meet the [[Notes on Password Complexity|complexity rules]]. <p class="mswarning">'''Important notice: '''Changing the host name after the Management Server has been configured requires additional, mostly manual actions such as transferring the license, re-pairing Instance Hosts and Client Access Servers and making changes to the configuration database. Therefore it is recommend to not change the host name afterwards.</p>
+* Enter your product key into the Product Key field and change Server Name to the fully qualified host name of the server (e.g. mgmt.ms-spe.test). Enter the user name , the full name (optional), the email address and the password of the initial administrator account that will be used to log on to the Management Console. <p class="mswarning">'''Important notice: '''Changing the host name after the Management Server has been configured requires additional, mostly manual actions such as transferring the license, re-pairing Instance Hosts and Client Access Servers and making changes to the configuration database. Therefore it is recommend to not change the host name afterwards.</p>
 *: [[File:ms_spe_config_mgmt_01.png|center]]
 * Fill out the ''Configure Management Server Role'' form.

@@ Line 9: / Line 9: @@
 * Click ''Add Server Role''
 * Select ''Management Server''
-* Enter your product key into the Product Key field and change Server Name to the fully qualified host name of the server (e.g. mgmt.ms-spe.test). Enter the user name , the full name (optional), the email address and the password of the initial administrator account that will be used to log on to the Management Console. The password must meet the [[Notes on Password Complexity|complexity rules]]. <p class="mswarning">'''Important notice: '''Changing the host name after the Management Server has been configured requires additional, mostly manual actions such as transferring the license, re-pairing Instance Hosts and Client Access Servers and making changes to the configuration database. Therefore it is recommend to not change the hostname afterwards.</p>
+* Enter your product key into the Product Key field and change Server Name to the fully qualified host name of the server (e.g. mgmt.ms-spe.test). Enter the user name , the full name (optional), the email address and the password of the initial administrator account that will be used to log on to the Management Console. The password must meet the [[Notes on Password Complexity|complexity rules]]. <p class="mswarning">'''Important notice: '''Changing the host name after the Management Server has been configured requires additional, mostly manual actions such as transferring the license, re-pairing Instance Hosts and Client Access Servers and making changes to the configuration database. Therefore it is recommend to not change the host name afterwards.</p>
 *: [[File:ms_spe_config_mgmt_01.png|center]]
 * Fill out the ''Configure Management Server Role'' form.

@@ Line 9: / Line 9: @@
 * Click ''Add Server Role''
 * Select ''Management Server''
-* Enter your product key into the Product Key field and change Server Name to the fully qualified host name of the server (e.g. mgmt.ms-spe.test). Enter the user name , the full name (optional), the email address and the password of the initial administrator account that will be used to log on to the Management Console. The password must meet the [[Notes on Password Complexity|complexity rules]]. <p class="mswarning">'''Important notice: ''' Changing the hostname after the Management Server has been configured requires additional, mostly manual actions such as transferring the license, re-pairing Instance Hosts and Client Access Servers and making changes to the configuration database. Therefore it is recommend to not change the hostname afterwards.</p>
+* Enter your product key into the Product Key field and change Server Name to the fully qualified host name of the server (e.g. mgmt.ms-spe.test). Enter the user name , the full name (optional), the email address and the password of the initial administrator account that will be used to log on to the Management Console. The password must meet the [[Notes on Password Complexity|complexity rules]]. <p class="mswarning">'''Important notice: '''Changing the host name after the Management Server has been configured requires additional, mostly manual actions such as transferring the license, re-pairing Instance Hosts and Client Access Servers and making changes to the configuration database. Therefore it is recommend to not change the hostname afterwards.</p>
 *: [[File:ms_spe_config_mgmt_01.png|center]]
 * Fill out the ''Configure Management Server Role'' form.

@@ Line 9: / Line 9: @@
 * Click ''Add Server Role''
 * Select ''Management Server''
-* Enter your product key into the Product Key field and change Server Name to the fully qualified host name of the server (e.g. mgmt.ms-spe.test).  Enter the user name , the full name (optional), the email address and the password of the initial administrator account that will be used to log on to the Management Console. The password must meet the [[Notes on Password Complexity|complexity rules]]. <p class="mswarning">'''Important notice: ''' Changing the hostname after the Management Server has been configured, requires additional, mostly manual actions such as transferring the license, re-pairing Instance Hosts and Client Access Servers and making changes to the configuration database. Therefore it is recommend to not change the hostname afterwards.</p>
+* Enter your product key into the Product Key field and change Server Name to the fully qualified host name of the server (e.g. mgmt.ms-spe.test). Enter the user name , the full name (optional), the email address and the password of the initial administrator account that will be used to log on to the Management Console. The password must meet the [[Notes on Password Complexity|complexity rules]]. <p class="mswarning">'''Important notice: ''' Changing the hostname after the Management Server has been configured requires additional, mostly manual actions such as transferring the license, re-pairing Instance Hosts and Client Access Servers and making changes to the configuration database. Therefore it is recommend to not change the hostname afterwards.</p>
 *: [[File:ms_spe_config_mgmt_01.png|center]]
 * Fill out the ''Configure Management Server Role'' form.

@@ Line 28: / Line 28: @@
 ** '''Path: ''' Directory on the file system where the debug log files are written into.
 * Click ''OK'' to add the Management Server role.
-* Click '''Start'' to start the Management Server service.
+* Click ''Start'' to start the Management Server service.
 *: '''Please note:''' As the startup process of the services is asynchronous, please wait up to 30 seconds. A service shown as running may still switch back to stopped during that period if an error occurred.
 * It is now safe to close the MailStore Service Provider Edition Configuration tool
@@ Line 52: / Line 52: @@
 ** '''Path: ''' Directory on the file system where the debug log files are written into.
 * Click ''OK'' to add the Instance Host role.
-* Click '''Start'' to start the Instance Host service.
+* Click ''Start'' to start the Instance Host service.
 *: '''Please note:''' As the startup process of the services is asynchronous, please wait up to 30 seconds. A service shown as running may still switch back to stopped during that period if an error occurred.
 * It is now safe to close the MailStore Service Provider Edition Configuration tool
@@ Line 86: / Line 86: @@
 ** '''Path: ''' Directory on the file system where the debug log files are written into.
 * Click ''OK'' to add the Client Access Server role.
-* Click '''Start'' to start the Client Access Server service.
+* Click ''Start'' to start the Client Access Server service.
 *: '''Please note:''' As the startup process of the services is asynchronous, please wait up to 30 seconds. A service shown as running may still switch back to stopped during that period if an error occurred.
 * It is now safe to close the MailStore Service Provider Edition Configuration tool

@@ Line 103: / Line 103: @@
 * The fingerprint of the role's TCP server's TLS certificate is transferred to the Management Database of the Management Server. This can be reviewed [[Management_Console_-_Infrastructure|here]].
-'''Please note:''' Pairing is carried out through the Management API. Therefore the Management API must be enabled on the Management Server and the Instance Hosts and Client Access Servers must be able to establish a connection to the HTTP server on the Management Server (Default TCP port: 8474).
+'''Please note:''' Pairing is carried out through the Management API. Therefore the Management API must be enabled on the Management Server and the Instance Hosts and Client Access Servers must be able to establish a connection to the API on the Management Server (Default TCP port: 8474).
 If your security policy does not permit establishing such a connection, pairing must be performed manually. Please refer to  [[Management Console - Infrastructure#Add New Instance Host|Add New Instance Host]] or [[Management Console - Infrastructure#Add New Client Access Server|Add New Client Access Server]] for further details.

@@ Line 21: / Line 21: @@
 ** '''Certificate: ''' Fingerprint of the TLS certificate used by the Management Server's HTTP server. Use the button next to the fingerprint to select a different certificate from the computer's certificate store.
 *; '''Management API Settings'''
-*; The Management API needs to be active when [[Pairing_with_Management_Server|Instance Hosts or Client Access Servers will be paired]] with this Management Server.
+*; The Management API needs to be active when [[#Pairing_with_Management_Server|Instance Hosts or Client Access Servers will be paired]] with this Management Server.
 ** '''Listeners:''' If the server is multihomed you can specify on which IP address and TCP port to listen for incoming connections to the Management Console and Management API (Default: *:8470)
 ** '''Certificate: ''' Fingerprint of the TLS certificate used by the Management Server's API server. Use the button next to the fingerprint to select a different certificate from the computer's certificate store.