What does mSuite do for me if I don't have Domino?

You can now install mSuite in environments where Domino is not installed, for example in organizations who use Exchange, Groupwise or any other solution for corporate email, messaging and collaboration.  mSuite co-exists with any existing Mail or Messaging system and adds the following mobility services:


Device management

mSuite allows you to configure and control mobile devices from a single central administrations console to:


Deploy software and configuration information to mobile devices.
Report on the status of mobile devices.
Provision - (load or reload the appropriate software) devices over the air (OTA).
Easily deal with lost and stolen services - make sure that security isn't breached and that users are quickly and easily restored to productivity.
Deploying anti-virus solutions and updates.



mSuite ensures that your mobile device community doesn't cause security issues through a variety of security capabilities:


use mSuite to enforce security policy on mobile devices.
Encrypt data moving between the devices and corporate servers.
Encrypt data stored on the device.
Remote wipe lost or stolen devices
HTTP Tunneling - make sure that your corporate web policy applies to mobile devices
Application Tunneling - allow client server applications to utilize the mSuite security tunnel and connection management capabilities


Mobile applications

mSuite provides the infrastructure for mCapture and mDesign - the components of CommonTime's mobile application solution.


mCapture is a multi-platform mobile application run-time environment.  It supports any kind of mobile application from a simple inspection application to complex CRM implementations.
mDesign is the design studio for creating applications to be executed by mCapture.
mSuite provides application deployment, security and notification services to mobile applications.


Supporting mobile user communities

mSuite works in conjunction with LogMeIn™ to provide superior end user support.


Remote Control - take control of a remote device to educate, reconfigure or repair.
Show and Tell - over the air training - one to one and one to many.
Registry and File manipulation - copy files and registry settings to and from the remote device.



Installation Steps

Assuming that all of the necessary preparation is complete (see Preparation), then installation is a simple 4 step process.


1.Run the installer.
2.Configure the software.
3.Deal with any Actionable Alerts raised by the install/configuration steps.
4.Connect your first mobile device and provision it.


The recommended path in the installer is the simplest, and it will install the system with the minimum of configuration needed.  Using this path, the following configuration options will be set.


Proxy mode will be set to Internet Proxy (CSC) but can be changed later to Local Proxy or DMZ Proxy mode if required.
A self signed security certificate will be generated during the installation process.



  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, uncheck the check box labeled "Check this box to include the device and server components required for Lotus Domino integration for Recommended and Custom installations"
5.Select "Recommended" and then click the Next button.
6.On the Database Choice screen, select Create new database. Note: You can choose Use existing database only if you already have an existing mSuite database. However, you cannot upgrade an mSuite 4 database.
7.Now you need to copy your license key to the clipboard - find the email that contains the license key, drag across the key in the email to select it and use CTRL-C to copy the Key to the clipboard.  Make sure that you do not copy any leading or trailing space characters with the key.
8.Now switch back to the install and click the Paste & Verify button - you should now be able to see the serial number of your license and its expiration date.  Because of changes that have been made to product licensing, perpetual licenses now expire 50 years into the future.  Click Next to continue.
9.On the Destination Folder screen, change the Installation folder and the Log folder if necessary.  Click Next 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.


10.On the Ready to Install screen, click Install if you are happy with the configuration choices that you have made.
11.The installer will install all of the software, create the configuration database (the repository) and then run the configuration wizard.
12.You can complete the installer by clicking the Finish button.  Continue the installation with the next section - the configuration wizard


   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.By default, mSuite will use LDAP to authenticate users using Active Directory.  You need to provide the following information to make sure that LDAP is configured correctly.  If the mSuite machine is in the same Active Directory domain as the user, the configuration wizard will default these values - you must always provide the password, You may need to seek the help of your AD administrator to be able to properly configure these settings.
Host - the IP address of name of the machine running Active Directory
Port - the port to use to access AD, the default is 389
Filter - how to find the user during the authentication process, the default filter will identify user's by their windows account name without the domain.
Login DN - The account name to be used to login to Active Directory.  This must be a distinguished name.
Password - The password for the account used to log in to Active Directory
Base DN - The place in the AD tree where the search will start from when authenticating users.
4.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.
5.You may well see a pop-up from the notification area to inform you that you have Actionable Alerts to process.
6.The mSuite Admin Console will be launched to allow you to process the Actionable Alerts.
7.Continue with the next section - Clearing the Actionable Alerts.

       Clearing the Actionable Alerts

See Admin Console layout for an 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 displays a list of Alerts that need to be processed to get the system fully operational, normally there will only be one, the 'Getting Started' alert. Note: Leave the 'Getting Started' alert until last.  Process and fix any 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 Active Directory authentication and user self registration (see Automatic User Creation).  In order for this to work correctly, your Active Directory must have a Group that contains all of the people allowed to use mSuite .  Select the Active Directory Group page allows you to select an existing Group.  Click Next to continue.

Note: Users must be direct members of the group, they cannot be members of a group contained by the chosen group.

13.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.
14.You are now asked if you want to restart the services, if you have made any changes, select Yes.  Click Next to continue.
15.The completion page is now displayed.


   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, make sure that the device user is a member of the AD Group that was selected during the Getting Started/Post-installation alert.  Otherwise, make sure they have an mSuite account profile.
2.Provision the device by any of the normal provisioning methods.


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