Centralized Settings

You can configure centralized settings that will be applicable for all Connect instances that have not any existing prevaling settings. Centralized settings and Agent options can be applied on the following levels:

  • Global. Global Agent Options (Connect tab) will be applied for all Connect instances that have not company-level settings.
  • Company-level. Company-level settings override the global ones. You can confugure custom settings for the company as described here.

Enable Centralized Configuration

Centralized configuration is available only for Managed Connect instances version 3.4 and later. This configuration will be automatically applied to all online instances of Connect Agent version 3.4 and later. Previous Connect Agent versions will not be affected.

  1. Update the Connect as described here to start using centralized configuration management.

  2. Open Settings > Global Access Options. You will be prompted to enable centralized configuration.

  1. Click the link to enable centralized configuration. You will be prompted to check and save the global configuration settings.

The following options are available to configure for all Connect instances downloaded after these options are configured:

  • Allow remote access to computers. Select this check box to enable remote access and control to user computers using Connect.

Security

  • Enable Direct (authorized) access. This option allows you pre-authorize joining all active sessions without any additional confirmation by remote computer user.
  • Approval methods to join active sessions. If Enable Direct (authorized) access is not enabled, you can select the remote user confirmation method to join active session. You can configure the PIN length to increase safety or reset PIN in case you suspect it may be compromised. If you want to secure remote connections to remote users instead of using a PIN every time, you can set up a custom password. It is recommended to use long custom passwords for security reasons and keep them in safe place. If you want to secure quick connections to remote users instead of using a different PIN every time, you can set up a custom password. To use custom password, select Require password before connecting with logon credentials.
  • Allow outgoing connections. By default, outgoing connections are disabled for remote computers, but you can enable outgoing connections for remote users.
  • Allow access to UI. Allows access to the Connect graphic user interface for users of remote computers. In this case you can protect application setting by password to prevent its changing by the remote user.

Service

  • Update Connect Agent automatically. This option allows automatic updates of Connect Agent as soon as the new version becomes available. Select this option to update Connect Agent on all online computers automatically.
  • Logging Level By default logging level is low. You can select the logging level you want.

Proxy Settings

On Proxy Settings area select the proxy usage settings. By default, Do not use proxy option is set. If you select Manual proxy configuration option, specify the proxy server adress and port number. For example, if the proxy server's address is http://proxy.example.microsoft.com (https is not currently supported) and the port number is 80, the setting in the Proxy Host box should appear like this: proxy.example.microsoft.com

If necessary, select Basic Authentication and provide credentials for connection.

  1. Save the settings. This settings will be applied to all Connect instances versiom 3.4 or later. If necessary, you can override these settings on the company level as described here. Consider, from this point you cannot return to the per-instance configuration management. But, if necessary, you can create a new company to manage any Connect instance with specific needs.
https://git.cloudberrylab.com/egor.m/doc-help-mbs.git