Custom Installation

Top  Previous  Next

Why do a Custom Installation?

You will need to perform a custom installation if any of the following apply to your installation:

 

You wan to use an existing SQL Server installation to host the mSuite configuration database
You want to distribute the mSuite services across multiple machines
You are installing a 2nd or subsequent mSuite server that will share the same mSuite configuration database as an existing mSuite server.  See Adding another mSuite server.

 

This process assumes that all of the necessary preparation is complete (see Preparation).

 

   Running the installer

1.Run the installer CommonTime_mSuite_Installer.exe.  If you are prompted with a dialog saying that the publisher cannot be verified, click the run button to continue with the installation.
2.Click the Next button on the Welcome screen
3.Accept the license agreement and click the Next button
4.On the Setup Type screen, select Custom and then click the Next button
5.In the Custom Setup choose the components to install
Configuration Service - this is a service that is used by all other services to access the configuration database.  You must have at least 1 configuration service in an mSuite installation.  You may choose to have multiple configuration services if you are planning a resilient implementation.
Server Files - this is the rest of the mSuite services - CMS, Authentication Server, mNotes Server, Chat Server etc.  This installer always installs all of these components.  You can configure which services to run on a particular machine.
Administration Console - this installs just the Administration Console software.  Use this option to install additional Administration Consoles on administrators or help desk machines.  

Note: If you are planning a complex installation, it's important to work out the topology of this before you start the installation.  Pay particular attention to the distribution of the components and the network addressing between the components.  This planning exercise will make it clear how all of the components will communicate, and will also indicate what firewall configuration requirements are required.  Please feel free to contact support@commontime.com for help and recommendations on complex installation scenarios.

 

6.Once you have selected the components to install make sure that Install to and Install Logs to are set to the correct locations and then click the Next button to continue.

Note: Logs can take large amounts of space when a system has a large number of users, make sure that the logging volume has the necessary space for these logs.  If the volume runs out of space system behaviour becomes unpredictable and unstable.

 

7.If you are installing a Configuration Server, you will now have to choose whether to create a new database or use an existing database.  If you are creating a new database, you will also have to paste the key using the Paste & Verify button.  Click Next to continue.

Note: Choose use an existing database if you are installing a second configuration service that is sharing a database for resilience.  You can also choose this option if you have an existing mSuite database and you are just reinstalling software components. Note: the mSuite installer cannot be used to update an mSuite 4.3x database.

 

8.If you are installing a Configuration Service, you will now have to specify the location of the database.  Select or enter the name of the Database Server.  The control list / Browse... button will display all of the discoverable SQL servers.  You can type an alternative if your server is not a member of the list.  A hostname or IP address will work in this control as well.
9.Enter the name of the database to be created or used in the Database Name field.
10.Connect using: requires you to understand the security configuration of the SQL server that will host the database.  Seek the assistance of your Database Administrator if necessary.  Once you have set the authentication method and any required credentials, press Next to continue.

Note: The configuration service runs as a machine service, it is important that the chosen authentication method will support this mode of operation.

 

11. You will now see the Ready to Install screen - click the Install button.  You can complete the installer by clicking the Finish button.
12. Continue the installation with the next section - The configuration wizard - this will only be launched if it is required.

 

   The configuration wizard

The configuration wizard supplements the installer.  It determines and configures the settings that cannot be made prior to the software being installed.  It is launched automatically at the end of the installation process.

1.Click Next on the Welcome page.
2.mSuite always creates an administration account, this is always given the username Admin - on the Enter Admin Account Password page, enter and confirm the password to be used for this account.  This password is case sensitive.  Click Next to continue.

Note: Use a strong password that should not be shared or used by other members of the admin team.  You can create more administrators for the system later.  Make sure that you remember the password, this is the master admin account!

 

3.You will now see the configuration wizard restart all of the services.  The completion page will now be displayed.  Click Finish to complete this process.
4.You may well see a pop-up from the notification area to inform you that you have Actionable Alerts to process.
5.The mSuite Admin Console will be launched to allow you to process the Actionable Alerts.
6.Continue with the next section - Clearing the Actionable Alerts.

 

   Clearing the Actionable Alerts

See Admin Console layout for on overview of the console if you are not familiar with the Microsoft MMC.

Actionable Alerts are used to highlight configuration problems and also to indicate any required final steps.

 

1.Expand the Monitoring node in the navigation tree, then expand Alerts, You will now be able to select Actionable Alerts in the navigation tree.
2.The action pane now display a list of Alerts that need to be processed to get the system fully operational. Leave the Getting Started alert until last.  Process and fix the other alerts first.
3.Select the Extended tab at the bottom of the action pane.
4.Click on the Alert that you want to rectify, to the left of the alert you will now see the available actions which include some or all of Configure (or Reconfigure), Do Not Run and Ignore.  There is also a description of the problem.  Mostly you will fix these by using Configure or Reconfigure.  Using Ignore or Do Not Run will allow you to get the rest of the system working, but depending on the alert, you will have a degraded or non-operational system.
5.The actions take you through a wizard - follow the instructions to make your changes.  On completion, the affected service will be restarted.  If your configuration is successful, the Alert will disappear from the action pane.
6.The mSuite server will always try to use the Internet Proxy (CSC).  If it has not been able to connect to the CSC, the Proxy connection failure actionable alert will appear.  Select it and click the Reconfigure link to the left of the alert.  On the Welcome screen, click Next then, on the Resolution Options screen, select Reconfigure Settings and click Next.
7.Choose from Use CommonTime switching center, Use enterprise DMZ proxy or Use local proxy and click Next.  If you are not sure which one to choose, please go to Proxy Configurations.
If you chose Use CommonTime switching center, you will then be asked for the Web Proxy Settings.  If you don't use a web proxy, click Next.  If you do use a web proxy, check the box marked Use web proxy and complete all the fields.
If you chose Use enterprise DMZ proxy then, on the DMZ Proxy Settings screen, enter the IP address (or host name) and Port that the mSuite server should use to make a connection to the proxy in the DMZ and click Next.
If you chose Use local proxy then, on the Local Proxy Settings screen, enter the IP address (or host name) and Port that the Proxy should use to listen for incoming connections from mobile devices and click Next.
8.When asked whether to Restart Services, answer Yes.  If the mSuite server is still not able to connect to the proxy, the Proxy connection failure actionable alert will re-appear.  You need to identify and fix the reason for the connection failure and then process the alert again.
9.Once all of the other Alerts have been addressed, it is time to process the Getting Started - Post installation steps alert.  Click on it then click the Configure link that appears to the left of the Alert.
10.Click Next on the Welcome page of the wizard.
11.On the Resolution Options page, select Configure settings (Recommended) and click the Next button.
12.By default mSuite will use Domino Internet Password authentication, and user self registration (Automatic User Creation).  In order for this to work correctly, your Domino Directory must have a Group that contains all of the people allowed to use mSuite.  The Create or Select a Domino Group page allows you to select an existing Group from the Domino Directory or create a new Group for this purpose.
13.After creating or selecting the Domino Group, you will be allowed to select users from the Domino Directory and add them to the group.  Once you have selected the users to add to the group click Next to continue.
14.If you chose to use either a DMZ Proxy or a Local Proxy, you will now see the Outside Host and Port screen.  In the Host and Port fields, enter the hostname (or IP address) and port that will be used by mobile devices to connect to the DMZ or Local Proxy.  This is the public IP address and port that will be used when devices connect to the Proxy via the internet.  This information will be used to configure the Outside connection information in the mSuite settings on the mobile devices.  Click Next.
15.You are now asked if you want to restart the services, if you have made any changes, select Yes.  Click Next to continue.
16.The completion page is now displayed with the URL for your provisioning portal already highlighted on the page.  Press CRTL-C to copy this to the clipboard.   You can then paste this somewhere to keep it safe.  It can be published on an intranet site, or sent by SMS to your mobile device users to allow them to provision their devices.

Note:If you need to find this URL again, right mouse click the node in the navigation tree that is underneath mSuite Administration Console, select All Tasks > View System Information from the pop-up menu.  The provisioning address is displayed along with other information about your mSuite system.  Again you can copy the URL so that you can send it to users by email, SMS or publish it on an intranet site.

   Reconfigure the system

The installer made assumptions during the installation process:

The system is using an Internet Proxy (the CSC)
The system is using Domino Directory Internet Password authentication with self registration (automatic user creation).

If this is not what you need you should reconfigure now before connecting devices.

 

  Authentication Method

If you want to choose an alternate authentication method see Configuring the Authentication Server

  Changing to a Local or DMZ Proxy

Local Proxy

1.First, you need to configure the Local Proxy - see Configuring the Local Proxy.  When doing so, make a note of the Back end and Device settings as these will be required again later in the configuration.  The Device settings Listen address and Listen port must be published through your firewall.  Ask your Network Administrator to make the necessary configuration changes.  If the Listen address and/or Listen port are re-mapped in this process, make a note of the re-mapped address as this information will be needed to configure the Replication Policy for the mobile devices.
2.Next, you need to configure the Connection Management Server (CMS) so that it knows how to connect to the Proxy.
3.Expand the configuration node in the navigation tree and select Servers and Groups.  The action pane will display the configured servers.
4.Right mouse click the server and select Properties from the pop-up menu
5.Select the Connection Management tab.  It will highlight the currently-active template, which is normally the default template that we recommend not be altered (Default CMS Template). Click the Configuration Wizard button - with the magic wand icon. A Welcome screen will be shown.
6.On the Welcome screen, make sure that the check box Run the Connection Manager Service is checked and then click the Next button.
7.On the General Settings page, press Next to continue.
8.The next screen display the Proxy settings.  This provides the information that the CMS needs to be able to make an outbound connection to the Proxy.
9.The Proxy can be local, in the DMZ or on the internet (the CommonTime Switching Center or CSC).
10.Check the Use Proxy control to make the CMS direct all traffic via the Proxy.
11.For a Local Proxy, the settings depend on the Proxy location.  The IP address and Host must specify the machine address where the Proxy is running and the port that the Proxy is listening on for CMS connections.  Use the Back end settings that you used when configuring the Proxy.
12.Click Next repeatedly until you reach the completion page.
13.On the completion page, you have the choice of saving the settings as a new template or updating the existing properties.  You will normally update the existing properties - the default settings.  Templates are part of advanced configuration and you should only use them if instructed by CommonTime support.
14.Click Finish to complete the wizard.

 

DMZ Proxy

1.First, install the DMZ proxy on a machine located in the DMZ, see DMZ Proxy Installation.  Make a note of the values set for External Listeners and for Internal Listeners. External Listeners must be accessible through the outer firewall, if necessary ask you Network Administrator to make the necessary configuration changes.  If the External Listeners Address or Port are re-mapped in the firewall configuration, make a note of the re-mapped address.  This information will be needed to configure the Replication Policy for the mobile devices.
2.Next, you need to configure the Connection Management Server (CMS) so that it knows how to connect to the Proxy.
3.Expand the configuration node in the navigation tree and select Servers and Groups.  The action pane will display the configured servers.
4.Right mouse click the server and select Properties from the pop-up menu
5.Select the Connection Management tab.  It will highlight the currently-active template, which is normally the default template that we recommend not be altered (Default CMS Template). Click the Configuration Wizard button - with the magic wand icon. A Welcome screen will be shown.
6.On the Welcome screen, make sure that the check box Run the Connection Manager Service is checked and then click the Next button.
7.On the General Settings page, press Next to continue.
8.The next screen display the Proxy settings.  This provides the information that the CMS needs to be able to make an outbound connection to the Proxy.
9.The Proxy can be local, in the DMZ or on the internet (the CommonTime Switching Center or CSC).
10.Check the Use Proxy control to make the CMS direct all traffic via the Proxy.
11.For the DMZ proxy, the settings depend on the proxy location.  The IP address and Host must specify the machine address where the Proxy is running and the port that the Proxy is listening on for CMS connections.  Use the Internal Listeners settings that you used when configuring the DMZ Proxy.
12.Click Next repeatedly until you reach the completion page.
13.On the completion page, you have the choice of saving the settings as a new template or updating the existing properties.  You will normally update the existing properties - the default settings.  Templates are part of advanced configuration and you should only use them if instructed by CommonTime support.
14.Click Finish to complete the wizard.

  Correcting the Device mSuite Policy

Prior to commissioning any device, you now need to correct the Replication Settings policy to make sure that devices know how to connect to the system.

1.In the case of the DMZ Proxy, you will need the External Listeners settings or if they were re-mapped, the substitute information.
2.In the case of the Local Proxy, you will need the Back end settings or if they were re-mapped, the substitute information.
3.In the Replication Settings policy, set the Connections\Outside - Host and Port to the values from steps 1 or 2 above - see Replication Settings policy

  Commissioning the first device

Your mSuite system in now operational.  The final task is to get a mobile device operational:

1.If you are using self registration (automatic user creation), make sure that the device user is a member of the Domino Group that was selected or created during the Getting Started/Post-installation alert.  Otherwise, make sure they have an mSuite account profile.
2.Provision the device by any of the methods mentioned here.

Page url: http://msuitehelp.commontime.com/index.html?ct_install_custom.htm