Editing Gateway Servers

Access Restrictions

You can use the default access restrictions set in the Policies section or you can set custom access restrictions for each Gateway Server.

Setting custom access restrictions for this Gateway Server

1. Press the Down arrow next to the Details button.
2. Select Access Restrictions.
3. Open the Use Custom settings tab.
4. Select the specific access restrictions you want for this Gateway Server.
5. Press Apply.

General Settings

Display Name - Sets the display name of the Gateway Server.

Address for administration - Sets the address on which the Gateway Server is reachable by the Acronis Access Server.

Address for client connections - Sets the address on which mobile clients will connect to the Gateway Server.

Logging

The Logging section allows you to control whether the logging events from this specific Gateway Server will be shown in the Audit Log and allows you to enable Debug logging for this server.

To enable Audit Logging for a specific gateway server:

1. Open the web interface.
2. Log in as an administrator.
3. Open the Mobile Access tab.
4. Open the Gateway Servers tab.
5. Find the server for which you want to enable Audit Logging.
6. Press the Details button.
7. In the Logging section check Audit Logging.
8. Press the Save button.

To enable Debug Logging for a specific gateway server:

Note: The default location for the debug logs is: C:\Program Files (x86)\Acronis\Access\Gateway Server\Logs\AcronisAccessGateway

1. Open the web interface.
2. Log in as an administrator.
3. Open the Mobile Access tab.
4. Open the Gateway Servers tab.
5. Find the server for which you want to enable Debug Logging.
6. Press the Details button.
7. In the Logging section check Debug Logging.
8. Press the Save button.

Search

Index local data sources for filename search

By default, indexed searching is enabled on all Gateway Servers. You can disable or enable indexed searching for each Gateway Server in the Gateway’s Edit Server dialog.

Default path

By default on a standalone server, Acronis Access stores index files in the Search Indexes directory in the Acronis Access Gateway Server application folder. If you would like to locate the index files in a different location, enter the path to a new folder.

Support content search using Microsoft Windows Search where available

Support for content search of shared is enabled by default, and can be enabled or disabled by checking this option. You can enable or disable content searching for each Gateway Server in the Edit Server dialog.

In addition to enabling this setting, content search requires that the Microsoft Windows Search application be installed on the Acronis Access Gateway server and be configured to index any data source where content search is enabled. Windows Search is built into Windows Vista and no additional installation is required. It is also built into Windows Server 2008, but it is not enabled by default. To enable it add the Role called File Services in the Server Manager, and have the Windows Search Service enabled. Windows Search can be configured to index the necessary data sources by right clicking the Windows Search icon in the Start bar and selecting Windows Search Options. You can do Windows content searches on Windows reshares but the remote machine(s) must be in the same domain as the Gateway Server.

Note: The Data Source's volume path must be a hostname or a fully qualified name in order to use content search on Windows Reshares. IP addresses are not supported by Windows Search.

SharePoint

Entering these credentials is optional for general SharePoint support, but required to enumerate site collections. For example, say you have two site collections: http://sharepoint.example.com and http://sharepoint.example.com/SeparateCollection. Without entering credentials, if you create a volume pointing to http://sharepoint.example.com, you will not see a folder called SeparateCollection when enumerating the volume. The account needs to have Full Read access to the web application.

To give your account Full Read permission, follow these steps (for SharePoint 2010):

1. Open the SharePoint Central Administration.
2. Click on Application Management.
   
3. Under Web Applications click on Manage web applications.
4. Select your web application from the list and click on User Policy.
   
5. Select the checkbox of the user you want to give permissions to and click on Edit Permissions of Selected Users. If the user is not in the list, you can add him by clicking on Add Users.
   
6. From the Permission Policy Levels section, select the checkbox for Full Read - Has Full read-only access.
   
7. Press the Save button.

Advanced

Note: It is recommended that these settings only be changed at the request of a customer support representative.

• Hide inaccessible items - When enabled, files and folders for which the user does not have the Read permission will not be shown.
• Hide inaccessible items on reshares - When enabled, files and folders located on a network reshare for which the user does not have the Read permission will not be shown.

  Note: Enabling this feature can have a significant negative impact while browsing folders.

• Hide inaccessible SharePoint sites - When enabled, SharePoint sites for which the user does not have the necessary permissions will not be shown.
• Minimum Android client version - When enabled, users connecting to this Gateway will be required to have this or a later version of the Acronis Access Android client app.
• Minimum iOS client version - When enabled, users connecting to this Gateway will be required to have this or a later version of the Acronis Access iOS client app..
• Use Kerberos for SharePoint Authentication - If your SharePoint server requires Kerberos authentication, you should enable this setting. You will also need to make an update to the Active Directory computer object for the Windows server or servers that are running the Gateway server software. The Acronis Access Windows server needs to be given permission to present delegated credentials to your SharePoint server on behalf of you users. Enabling the Acronis Access Windows server to perform Kerberos Delegation:
  1. In Active Directory Users and Computers, locate the Windows server or servers that you have the Gateway Server installed on. They are commonly in the Computers folder.
  2. Open the Properties window for the Windows server and select the Delegation tab.
  3. Select Trust this computer for delegation to specified services only
  4. Select Use any authentication protocol, this is required for negotiation with the SharePoint server.
  5. You must now add any SharePoint servers that you would like your users to be able to access using Acronis Access . If your SharePoint implementation consists of multiple load balanced nodes, you will need to add each SharePoint/Windows node to this list of permitted computers. Click Add... to search for these Windows computers in AD and add them. For each, you will need to select the "http" service type only.
     

     Note: Please allow 15 to 20 minutes for these change to propagate through AD and be applied before testing client connectivity. They will not take effect immediately.

• Allow connections to SharePoint servers using self-signed certificates - When enabled, allows connections from this Gateway to SharePoint servers using self-signed certificates.
• Accept self-signed certificates from this Gateway Server - When enabled, allows connections from this Gateway to Acronis Access servers using self-signed certificates.
• Allow connections from Acronis Access servers with self signed certificates - When enabled, allows connections to this Gateway from Acronis Access servers using self-signed certificates.
• Show hidden SMB Shares - When enabled, shows hidden system SMB shares to the users.
• Client session timeout in minutes - Sets the time before an inactive user is kicked out of the Gateway Server.
• Use user principal name (UPN) for authentication with SharePoint Servers - When enabled, users will authenticate to SharePoint servers via their user principal name (e.g. hristo@glilabs.com), otherwise they will authenticate with domain/username (e.g. glilabs/hristo).