MindLink Anywhere

The MindLink Management Center provides a user friendly interface to configure MindLinkand its client software (MindLink Anywhere, MindLink Mobile, MindLink API and the MindLink WebPart). The MindLink Management Center is installed alongside all MindLink core products and should be run on the server that is being configured.

The MindLink Management Center can be loaded from the shortcut on the desktop, or can be located in ProgramFiles\MindLink Software\ManagementTool. The Management Center will load with the logging configuration as the default page.

The MindLink Management Center can be loaded from the shortcut on the desktop, or can be located in:

%ProgramFiles\MindLink Software\MindLink Component\ManagementTool.

It will be named according to which componentof MindLink is installed. e.g. MindLink Mobile Management Center, MindLink Anywhere Management Center, MindLink API Management Center and MindLink SharePoint Management Center.

mlm icon image MLA icon image

Editing Configurations

edit config page

MindLink Management Center

1 - The navigation tree displays all of the available configuration sections. Clicking on a section will display the configuration options for the selected section in the configuration panel (2)

When a change has been made to any configuration setting, the navigation tree icon for the section in which the setting resides will change to icon, to indicate that there are unsaved changes.

2 - When a configuration option has been changed in any section, the Save Changes button will be enabled. Clicking the Save Changes button will save the configuration.

3 - The configuration section header shows the name of the currently displayed configuration section and a brief description of what the configuration section options affect.

4 - The configuration panel displays all configuration options for a section.

Saving Changes

changes icon

Save Changes Prompt

Clicking on the Save Changes button will attempt to save configuration changes. The MindLink Management Center can automatically configure port reservations, firewall exemptions and certificate bindings so that the Connector service will function correctly.

The MindLink Service will require a restart for these new settings to take effect

changes icon

Update Bindings Prompt

Clicking on the 'Save Changes'button will attempt toupdate bindings changes.

If required, The MindLink Management Center can automatically update certificate and port bindings. Select Save and Update Bindings to update the configuration

Configuration Sections

The MindLink Management Center will load with the logging configuration as its default page. The user can navigate through different configuration settings by using the navigation tree , which includes the following configuration sections:

  • Licence
  • Logging
  • General
  • Add-Ins
  • Lync/Skype for Business
  • Active Directory
  • Network
  • Feature
    • MindLink Anywhere
    • MindLink Mobile
      • Android
      • Apple
      • Server Pooling
      • Policies
    • MindLink API
    • MindLink for Sharepoint

Licence Files

The licence page ensures the products you are using are firstly; supported by MindLink and secondly; that only the correct products (as stated by contract) are in use.

Opening the license tab, you are given the ability to browse for a file. This will be the file you received within the correspondence with your account manager.

Click the Browse for license file button which will open file explorer. Navigate to your license file.

icon

Click the Browse for license file button which will open file explorer. Navigate to your license file. Selecting a valid license file will show similar details to the corresponding management center image below.

For MindLink Mobile

  • License Holder: This field specifies the Company name the license is issued to and also the product owner at the time of purchase.

  • Expiry date: The date the product expires. At this time (grace period built in) the product will cease to function.

  • Details: This field contains the product/s that the license has been issued for. MindLink will not run with an incorrect product license (a single license can be issued for multiple products).

icon

For MindLink Anywhere Same principles apply for MLA licenses, but there is an extra feature explained below.

icon

Enabled users: This capacity is based on the number of users who couldlog on, rather than the current number of users logged on.

The system periodically checks the number of users who could log on and starts rejecting new logons if it sees that the number of hypothetical users is larger than the licensed capacity.

If a license reaches expiry the following message will appear. Please contact your account manage to receive a current license within contract renewal.

icon

If a license is issued for a different product to the one you are attempting to run. The following message will appear stating the product this license is valid for. Please contact your account manager to discuss increasing your subscribed products.

icon

Logging

The logging section enables the user to configure the logging level as well as the log file location for the Connector Service.

Please note that logging on the Connector Service is performed using the Microsoft Enterprise Library Logging Application Block.

logging

By default logging is configured as follows:

  • Error level - Error class events
  • Warning level - Warning class events (Recommended)
  • Info level - Info class events
  • Verbose level - All class events

Logging Configuration

You can Configure the Connector service logging level and log file location by Clicking on the Browse button will let you find an absolute path to a new log file location, or you can manually edit the field to a path relative to the Connector Service install location.

The account used to run the Connector Service must have write access to the install location of the product in order to log to the rolling log file. The file can by default be found at %ProgramFiles%\MindLink Software\MindLink Application\ConnectorService\Logs\Connector.log

General

The General section lets the user configure the general settings that will be applied to the Connector Service.

icon

1 - Information service port: The port number used when behind a load-balancer to provide a service heart-beat.To allow collocation, Default Ports are as below and can be tested eg http://{server}:9007/Connector/InfoService/Status

  • MindLink API = 9006
  • MindLink Anywhere = 9007
  • MindLink SharePoint 9008
  • MindLink Mobile = 9009

2 - Maximum concurrent downloads: The maximum number of allowed concurrent file download requests.

If an attempt is made to download a file when the number of active file downloads to the server is equal to the number specified, the download will fail with an error indicating that the server limit is currently exceeded and to try again later.

3 - Maximum concurrent uploads: The maximum number of allowed concurrent file upload requests.

If an attempt is made to upload a file when the number of active file uploads to the server is equal to the number specified, the upload will fail with an error indicating that the server limit is currently exceeded and to try again later.

4 - Maximum file size for file uploads: If the configured connector supports file posting, the maximum size of files in kilobytes allowed to be uploaded.

If an attempt is made to upload a file that is larger than the specified size, the server will return an error indicating that the file is too large to upload.

5 - Enable instant messaging: When set, allows connected clients to use instant messaging.

When not checked, user presence will not be published, instant messaging will be disabled, and the client will be limited to group messaging functionality. Any client that exposes instant messaging functionality when instant messaging is disabled will receive failure notifications from the server when an attempt is made to use such functionality.

6 - Enable group chat: When set, allows connected clients to use group chat.

When not checked, group chat preferences are not loaded and users will not see any groups or chat rooms to which they are subscribed in their contacts list nor will they be able to search for and add groups.

7 - Allow user to disable instant messaging When set, allows users to specify whether they want to log on with or without the instant messaging capability enabled on their web or mobile client.

When not checked, users will not be able to choose to enable/disable instant messaging upon login and the setting will default to the configuration in the management tool .

8 - Allow user to disable group chat When set, allows users to specify whether they want to log on with or without the group chat capability enabled on their web or mobile client.

When not checked, users will not be able to choose to enable/disable group chat upon login and the setting will default to the configuration in the management tool .

9 - Enable file transfers in 1-1 conversations - Allows users to send between one another

10 - Enable audio calls - Enables audio calls for IM

11 - Enable setting profile pictures - Allows user to set profile pictures in the web client When not check profile pictuires can be view in the MindLink client, but users are not able to set a profile picture.

12 - Maximum message length: The number of characters that a single message can include.

If an attempt is made to send a message that is longer than the specified length, the server will not send the message and an information message will appear in the server logs.

13 - Maximum story length: The maximum number of characters that a single story can include.

If an attempt is made to send a story that is longer than the specified length the server will not send the story and will return an error indicating that the story exceeded the allowed story length.

Add-Ins

In this section the user can configure Group Chat add-ins across MindLink Anywhere and Tablet Platforms.

icon

  • When set, Group Chat add-ins will be displayed within compatible clients. When false, any configured client add-ins will not be displayed for any chat room.

  • MindLink Anywhere and MindLink mobile(on tablet devices)

Rewrite rules for Add-ins:

  • A set of key/value pairs that describe the client add-in proxy rules that should be applied to client add-in URLs.

See Section 5 for detailed instructions on setting up Group Chat Add-ins.

Lync/Skype for Business

The Adaptor section manages the selection of the underlying chat system to which to connect and the infrastructure DNS servers that define the chosen platform.

lync/sfb

lync/sfb

1 - Server Version: Select the chat platform version.

2 - Auto Provisioning Server Information: (Lync 2013/SFB Only) Enable the auto detection of the Front End Server. This will allow the server to detect any server changes within the Topology and auto configure the new servers. This requires Lync Core Components to be installed

3 - Auto Provisioning Application ID: (Lync 2013/SFB Only) Enter the Application ID of the trusted application on the Front End.

4 - Local Server Name: Manually enter the FQDN of the local machine

5 - Server Name: Manually enter the FQDN of the OCS/Lync/SFB front end or pool server.

6 - Server/Listen Ports: The default communication port for OCS/Lync/SFB used by the Front End Server to listen on when using trusted authentication.To allow Collocation the default ports are as below :

  • MindLink API => 4096
  • MindLink Anywhere => 4097
  • MindLink SharePoint => 4098
  • MindLinkMobile => 4099

7 - Platform Certificate: The certificate to use for establishing an MTLS connection with the OCS/Lync server.

8 - Enable Group Chat SDK Logging: Enabled by developers to debug SDK Issues on OCS 2007

9 - Auto Provision Group Chat Information: Automatic discovery of the lookup address for querying Group Chat Lync 2013 only. Use this option to look at multiple chat pools

10 - Lookup Server Address : Manually enter the lookup address for querying Group Chat. This is the address created upon activation, , use Get-csPersistentChatEndpoint to identify.

11 - Use untrusted connection: To Debug the communication protocol and transport mechanism during debug mode.

12 - Disable transport: The transport type between the Connector service and the OCS pool e.g. TLS or TCP during debug mode.

13 - Authentication Protocol: Domain protocol set to either NTLM or Kerberos.

14 - Conversation History: Enable conversation history saving and loading.

15 - Preferences:

16 - Private file transfrer cache - Specified direcory where private file transfers cache folders are kept

17 - Session timeout: This sets the timeout for MindLink Anywhere. The MindLink client will be set to an idle/away status after being disconected from the network after the configured time has elapsed.

Active Directory

active directory figure

1 - Enable Auto discovery of Global Catalogue

2 - OCS/Lync/ Forest Name: Select the relevant forest name in which platform is installed and base for AD operations for users.

3 - Server Name: Manually enter the FQDN of the LDAP server is Auto-Discover is not detecting correctly.

4 - Use Default Port: Default port number of the Global Catalog used to look-up user SIP addresses from Active Directory i.e. 3268.

5 -Port Number: To enter a custom port number to look-up user SIP addresses from Active Directory.

6 - Active Directory Time-out: Specify the time interval in seconds for Active Directory queries.

7 - Use Default Naming Context: Auto-discover the name of the root context of the directory. Use this is membership is not restricted.

8 - Naming Context: Manually enter full OU path if users are to be restricted to this AD OU object

9 - Search Filter: Must be configured, responsible for retrieving sip address for a user via Active Directory.

10 - Default user domain: The default domain that will be used if a user does log specify a domain in their user name when logging on.

11 - Restrict usage to members of an AD group. Restrict access to Membersof this AD Group to be able to log in

12 - Group Name: Select the Group from the dropdown (start typing the name to dynamically list) if users are to be restricted to this AD Group.

Call routing

Call routing

This section users can configure connections to STUN/TURN servers

Exchange Web Services

exchange

As of 17.7, administrators can now explicitly configure how the exchange server is resolved. This can be done automatically by ticking the Autodiscover Exchange Web Services box or the URL can manually be entered in the box below. Additionally, a list of well-known URLs can be added where the management tool will look to resolve the exchange server name based off of those URLs

Group Aliases

group aliases

1 - Enable group aliases: This enables aliases in chat rooms

2 - Database connection string Configure the connection string with the following syntax:

Server=FQDN SQL server; Initial Catalogue=SQL catalogue; Integrated Security=SSPI

or if you wish to use a Failover SQL partner you could use the following syntax :

Server=FQDN SQL server; Failover Partner=FQDN SQL partner; Initial Catalogue=SQL catalogue; Integrated Security=SSPI

3 - Override credentials for database operation If the user running the management tool does not have sufficient SQL permissions, then these can be overridden by a set of credentials that have sufficient permission by your SQL administrator.

4 - Test the conneciton: To check the validity of a relevant SQL database connection string and the override credentials , select 'Test'. The following steps may differ and as such are outlined in the two scenarios listed below.

Custom Preferences Repository

Following the 17.4 release of MindLink Anywhere and subsequently the inclusion of disabling group chat, the administrator is now able to keep a repository of user preferences. This enables the continuation of preferences across group chat sessions. This feature also allows for the ability to read preferences across nodes. An example, of such a deployment could be a file share across a network. This allows an administrator to store preferences across multiple machines within a network (if required). This means that changes made on one machine persist across multiple nodes when the same file store is referenced. In this sense, preferences can be stored cross-site.

IM

Above is the screen that administrators will be presented with when configuring the custom preferences repository. First there is the pathway in which the preferences are written to which can be anywhere that is capable of being read and written to; including across networks. Secondly there is also the abilty to test access to the pathway. In the event the file pathway referenced is not accessible it is possible to either A) change location (in the event it is invalid) OR Provision access rights to the service account running MindLink Anywhere; which is a pre-requisite to utilising the custom preferences repository.

Also worth noting is the possibility of having preferences persist during an outage such as in an active-passive disaster recovery scenario. If two machines are connected properly and preferences are shared it is possible that in the event machine A falls, machine B can pick the preferences up without any outage on the user side. Please note that a batch job would have to be setup to facilitate this transference of preferences across the machines

Advanced

Advanced tab

You can add debug keys (such as configuring Exchange Online or enable pre-release features) and you can also override any other configuration value. Examples of a couple custom setting keys include:

  • Configuration key: connector.uma.serverversion Value: Unknown
  • Configuration key: global.message.maxlength Value: 200

Notes when using custom settings:

  • Custom key/value

  • Invalid keys cause the host to crash

This section manages MindLink Anywhere settings that affect the way the web client is hosted and displayed to a user.

Disclaimer

1 - Web client port number: The port number at which the web client will be available. For example, if the port number is 9080 and HTTPS is enabled, then navigating to "https://{fqdn}:9080/ will display the web client.

2 - Use HTTPS: When set, hosts the web client over HTTPS. A valid certificate must be specified in order for the configuration to save successfully.

3 - Certificate: A valid certificate must be specified in order for the configuration to save successfully.

4 - Base Path: Appended text to the URL i.e. https://FQDN:port/yourbasepath .

5 - Session Timeout: The session time out period assigned to manage the session when long polling stops.

6 - Long Polling Session Timeout: Defines when long polling will stop.

7 - Enable disclaimer: Adds a disclaimer message when opening the web client.

8 - Enable differnet disclaimers based on requst headers:

Authentication

Authentication