Skip to end of metadata
Go to start of metadata

Starting and Stopping the mobilEcho File Server

To start the mobilEcho File Server, log into Windows with administrator privileges and launch the mobilEcho Administrator. If the mobilEcho service has not already started, the mobilEcho Administrator asks if you want to start the service.

In addition, you can start and stop the service from the Windows Service Control Panel on a standalone server or the Cluster Administrator on a cluster server.

Configuring the mobilEcho Server

This section gives an overview of configuring the mobilEcho service. Use the mobilEcho Administrator to view connected users, create shared volumes, and adjust specific machine settings. You can configure the local computer or remote computers on which mobilEcho is installed as long as you have administrative privileges.

To configure mobilEcho on the computer you are using, from the Windows Start menu, go to Programs/mobilEcho Server and select mobilEcho Administrator.

Setting up mobilEcho

Before using mobilEcho, review the default settings; you can make changes at this time or later. The Settings dialog box has the following tabs: File Server, Security, Search, and Logging. To change settings, do the following:

  1. Access the mobilEcho Administrator window.
  2. Click Settings
  3. Choose the settings appropriate for your use, then click OK to return to the mobilEcho Administrator window.
Setting File Server Options

HTTPS Port

If you require mobilEcho to operate on a port different from the default HTTPS port, 443, it can be configured here. mobilEcho clients connecting to a server with a non-default port will need to specify the port in the server name or IP address when they are configured. For example, if port 444 is used, ":444" would need to be appended to the server name. In this example, the server name entered would be: server.domain.com:444

Allow connections to SharePoint servers with self-signed certificates

mobilEcho can be configured to provide access to files located on SharePoint servers. If any SharePoint servers your users will access are using self-signed certificates, the mobilEcho server needs permission to connect to these SharePoint servers, despite the lack of a trusted 3rd party issued certificate. Enable this setting to allow access to SharePoint servers using self-signed certificates.

Allow connections to activEcho servers with self-signed certificates

mobilEcho can be configured to provide access to users' files located activEcho servers. If your activEcho server is using a self-signed certificate, the mobilEcho server needs permission to connect to this activEcho server, despite the lack of a trusted 3rd party issued certificate. Enable this setting to allow access to activEcho servers using self-signed certificates.

Using mobilEcho to provide mobile access to activEcho servers

A mobilEcho server is capable of giving access to activEcho files to mobile devices running the mobilEcho client app. This capability is configured by creating an activEcho volume in the mobilEcho Administrator Volumes window. In the mobilEcho client app, the activEcho volume is presented just like a standard mobilEcho volume, but is distinguished with a special activEcho icon. When the user connects to this activEcho volume, they will see only the activEcho folders that their account has access to.

The mobilEcho server does not require a mobilEcho serial number to allow activEcho volumes to be created. This activEcho volumes feature is included in the activEcho retail license. If a mobilEcho server trial expires and that server is configured to share activEcho volumes, those activEcho volumes will continue to allow users to connect indefinitely.

SharePoint Administrator Credentials

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.

Refresh Registry

The Refresh Registry button is used to apply changes that have been made directly to mobilEcho's registry key settings. Changes made to registry key settings typically do not take effect until after the mobilEcho File Server service is restarted. You can avoid a service restart and apply these changes immediately by clicking Refresh Registry. This is only necessary if you change mobilEcho settings directly in the registry.

Setting Security Options

Require that client is managed to access this server

If you select this option, all mobilEcho clients connecting to this server are required to be managed by a mobilEcho Client Management Server that is listed under Allowable management servers. This option ensures that all clients accessing the server have the settings and security options you require.

The server name entered here must match the management server name configured in the mobilEcho client app. Partial names may also be used to allow multiple client management servers in a domain, for instance. Partial names do not need wildcard symbols.

Allow mobilEcho iOS clients to access this server

If you uncheck this option, iOS devices will not be able to connect to the mobilEcho server and you won't be able to access the Management Server as well. If you select this option, you can further set which clients can connect by the options below.

  • Allow standard mobilEcho iOS client

If you select this option, this mobilEcho server will allow users running the standard iOS mobilEcho client app to connect. If you do not want to allow iOS users to access this mobilEcho server, you can uncheck this setting.

  • Allow mobilEcho Good Dynamics managed iOS client

If you select this option, this mobilEcho server will allow mobilEcho users using the mobilEcho Good Dynamics managed client to connect. If you do not want to allow users with the mobilEcho Good Dynamics client to access this mobilEcho server, you can uncheck this setting.

  • Allow AppConnect managed mobilEcho iOS client

If you select this option, this mobilEcho server will allow users with mobilEcho clients enrolled in MobileIron. If you do not want to allow users enrolled in MobileIron to access this mobilEcho server, you can uncheck this setting.

Allow mobilEcho Android clients to access this server

If you select this option, this mobilEcho server will allow users running the Android mobilEcho client app to connect. If you do not want to allow Android users to access this mobilEcho server, you can uncheck this setting.

Allow username/password authentication

If you uncheck this option, users will not be able to connect via username and password and will be able to connect only via client certificate.

Allow client certificate authentication

If you uncheck this option, users will not be able to connect via certificate and will be able to connect only via client username and password. For information visit this article and this article.

Searching with mobilEcho

mobilEcho performs three types of file searches – local searches, filename index searches, and content searches.

Local Search

If a mobilEcho server does not support filename index or content search, the mobilEcho client defaults to searching its local list of files, in current folder being browsed, by filename.

Filename Index Search

An index search issues a single search request that is processed on the server side.

By default, mobilEcho maintains a search index to accelerate these searches. This index contains the name of every file on your mobilEcho volumes. With indexed searching enabled on the server, a mobilEcho client can search both the currently browsed folder and the entire current shared volume. These results are delivered very quickly because they are processed on the server side.

Content Search

A content search issues a single search request that mobilEcho processes on the server side. A content search returns files that contain the requested search term, in either the filename or the actual contents of the file.

Content search is enabled by default, but requires that the Windows Search service is enabled on the server and is configured to index the storage areas that are being shared as volumes by mobilEcho.

For instructions on installing and configuring Windows Search, please see GroupLogic's Network Spotlight Best Practices white paper. This document was authored for GroupLogic's ExtremeZ-IP File Server, which also uses Windows Search in much the same way. The section on enabling Spotlight search in ExtremeZ-IP can be skipped.

Setting Search Options

Index volumes for search

By default, indexed searching is enabled on all existing and newly created volumes. You can disable or enable indexed searching on a per volume basis in the individual volume’s Volume Properties dialog in mobilEcho Administrator. You can set this property at initial volume creation time or after the volume has been created. In order for changes to this setting to take effect, you must Restart the volume.

Maximum search index cache size

This cache is set to a maximum size of 20 MB by default. GroupLogic does not recommend changing this cache size. An index file containing 250,000 files is only about 8 MB in size. Leaving the cache limit at the default setting gives sufficient performance in almost all cases. If the index files on disk are larger than search index cache size, the file will be read from disk when the client does a search; however in many cases the file will be in the Windows file system cache so performance impact is minimal. When the server is running with limited physical memory, the cache size can be reduced to as little as 8 MB.

Default Path

By default on a standalone server, mobilEcho stores index files in the mobilEcho Indexes directory in the mobilEcho Server application folder. If you would like to locate the index files in a different location, click Browse to select a new folder.

Administrators can also specify custom index file paths for individual volumes; this setting overrides the global default path setting.

Use lazy indexing

By default, indexed searching uses any available system resource to keep its indexes current and cooperates with other system processes. It should not affect overall system performance adversely. However, when a server is under high load or is running many different services simultaneously, you can limit the system resources that search indexing consumes by enabling the Use lazy indexing checkbox. This setting takes effect immediately.

Automatically rebuild sparse index

In order to optimize runtime performance, the mobilEcho index file entries for files that have been deleted or moved from a volume are not physically removed from the index file at the time the actual file is deleted. The indexed search service ignores these deleted entries to keep search results accurate. However, the index file grows over time and, as the file gets larger, slows search performance to a small extent. The rate at which the index file grows is dependent on the number of files being added, moved, and deleted on the file server. In order to keep mobilEcho search performing at optimal levels, volumes’ indexes are routinely re-indexed and compacted. The interval at which this occurs is determined by the ratio of deleted (stale) records to valid entries in the index. By default, the mobilEcho search service re-indexes an individual volume when approximately one-third of that volume’s index file records are deleted, stale records.

Maintenance occurs on a per volume basis and only on volumes requiring re-indexing. While re-indexing, the volume’s existing search index is kept up to date and used to provide one hundred percent accurate search results. Re-indexing should not have any detrimental effect on other server processes while it is running. While mobilEcho is re-indexing an individual volume, a status of “Reindexing” shows in the Volumes dialog of the mobilEcho Administrator.

Support content search operations

Support for content search of shared volumes is enabled by default, and can be enabled or disabled by checking this option. You can enable or disable content searching on a per volume basis in the individual volume’s Volume Properties dialog. You can set this property at the time of initial volume creation or after the volume has been created. Enabling this setting takes effect for all new sessions using the volume.

In addition to enabling this setting, content search requires that the Microsoft Windows Search application be installed on the mobilEcho server and be configured to index any volume 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 installed on Windows 2003 Server and Windows XP by running Windows Update. It is listed as an optional install. Once installed, Windows Search can be configured to index the necessary volumes by right clicking the Windows Search icon in the Start bar and selecting Windows Search Options.

Support content search on all volumes

To support content search on all volumes, check this box.

Setting Logging Options

Full Logging

When enabled, Full Logging increases the level of detail recorded in the mobilEcho log file. This is typically only needed when working with GroupLogic technical support. Enabling full logging could potentially have an impact on performance and should be used only for troubleshooting.

Archive Active Log File

Click this button to ZIP archive the current mobilEcho log file and start a new log file. This can be used to reduce the size of your existing log file for archiving or to package your log file for delivery to GroupLogic technical support. Log files are located in the \Program Files\Group Logic\mobilEcho Server\Logs\mobilEcho\ folder on your system drive by default.

Adding License Numbers

Using the Licensing button on the mobilEcho Administrator window, you can enter the serial number for any licenses without stopping the mobilEcho service. When you enter license numbers while the mobilEcho service is running, mobilEcho clients stay connected and continue to use mobilEcho volumes.

You need to enter license numbers when:

  • you have a trial version of mobilEcho installed and you purchase a license for the product.
  • you are upgrading your user count.
  • you are converting from standalone server licensing to perpetual or annual enterprise licensing.

To add a serial number, do the following:

  1. Open the mobilEcho Administrator application.
  2. Click Licensing on the main mobilEcho Administrator window.
  3. Click Add License, enter the serial number, and click OK.
  4. The serial number will be displayed in the Active Licenses list and will take effect immediately.
  5. Click Close to return to the mobilEcho Administrator.

The Licensing window can also be used to replace serial numbers to upgrade user count.

Administering mobilEcho Remotely

You can configure mobilEcho on a remote computer if mobilEcho is already installed on that computer. You must have Windows administrative privileges on the remote computer. The experience of administering a remote server is very similar to that of the local server Administrator, except that the title of the Administrator dialog box shows the name or IP Address of the remote computer whose mobilEcho service you are configuring and you cannot browse for folders to share. Otherwise, you can configure the remote server just as you would a local server.

To administer a remote mobilEcho server, do the following:

  1. Hold down the Control key while you launch the mobilEcho Administrator. Alternatively, if there is no local installation of mobilEcho, mobilEcho Administrator will start immediately in remote mode.
  2. Type the name or IP Address of the remote computer and click OK.
  3. The mobilEcho Administrator will attempt to use your Windows credentials to log onto the server. If necessary, you will be prompted for an alternate username and password.

Using the mobilEcho File Server

After using the mobilEcho Settings dialog box to set up your server, security and search settings, you can create the volumes you want to share to you mobilEcho clients. You can also use the Users dialog box to see who is connected to the server.

Creating Volumes in mobilEcho

You can share NTFS directories located on your Windows server, or on a remote SMB/CIFS file share, for access by mobilEcho users. When mobilEcho users connect, they see these directories as file share volumes.

You can create volumes that provide access to an activEcho server.

You can also create volumes that provide access to a SharePoint 2007 or 2010 server, site, subsite, or document library. Volumes that point to an entire SharePoint server, or an individual site or subsite, allow the user to browse and navigate through sites, subsites, and document libraries they have access to.

Use the Volumes dialog box to create, modify, or delete individual volumes to share with mobilEcho users.

Click Volumes on the mobilEcho Administrator main window to display the Volumes dialog.

 

Note:

You cannot create a volume with the name enroll. This name is reserved for internal use.

 

Creating a Volume for a local folder or to re-share a location on another SMB/CIFS server

Folders residing directly on the Windows server running the mobilEcho server software can only be shared as mobilEcho volumes if they reside on an NTFS formatted disk. If you try to create a volume that is not on an NTFS formatted disk, mobilEcho will display an error message.

1. Create a new directory on an NTFS formatted volume on the server machine or find an existing directory that you want to use.

2. From the mobilEcho Administrator window, click Volumes.

3. On the Volumes dialog, click Create.

4. If you are running a Trial or Enterprise License version of mobilEcho Server, you will be asked to choose a volume location. If you want to share files on this server's physical storage, choose On this server. If you want to share an SMB/CIFS volume located on another server or NAS device, choose On another server.

If you choose On this server, you will be prompted to select a directory location on this server. Browse to the path of the folder you want to share and click OK.

If you are running a mobilEcho Server with a non-enterprise perpetual license that does not support resharing volumes on other servers, you will not see options for creating a volume that resides on another file server or on a SharePoint server.

If you choose On another server, you will be prompted to enter the path to the server or SMB share you'd like to make available with this mobilEcho volume. Enter the desired path and click OK.

Microsoft Distributed File System (DFS) namespaces

mobilEcho's network reshare feature can be used to make DFS namespaces available to mobilEcho users. Simply specify the DFS namespace's path when creating an On another server volume.

5. The Volume Properties window will appear.

6. Edit the Volume Name if you want to change the name.

7. Choose any additional settings required. Search index settings only apply to volumes pointing to folders on the local Windows server. 

8. Click OK to create the volume.

As soon as a volume’s status becomes Online for clients, mobilEcho clients can see and connect to it.

File search on volumes with remote paths

The mobilEcho search indexing service and Windows Search integration runs on each of your servers where mobilEcho is installed. When a mobilEcho volume is configured for a path On another server, these local services are not able to index the remote server. For this reason, indexed filename and content search will be disabled for all volumes with remote network paths. Users will continue to be able to search the folder they are browsing by filename from within the mobilEcho client application.

Creating a Volume that provides access to an activEcho server

The mobilEcho client app can be used to access and work with files on an activEcho server. When a mobilEcho user connects to an activEcho volume, they see the same set of files and folders that they have access to using the activEcho web interface. activEcho volumes simply need to point to the root HTTPS URL of an activEcho server.

1. From the mobilEcho Administrator window, click Volumes.

 2. On the Volumes dialog, click Create.

3. To share an activEcho server, choose On an activEcho server.

If you are running a mobilEcho Server with a non-enterprise perpetual license that does not support resharing volumes on other servers, you will not see options for creating a volume that resides on another file server or on a SharePoint server.

4. Enter the HTTPS URL to the root of the activEcho server you would like this volume to provide access to.

Important Note: Requirement for SSL certificate may need to be modified

mobilEcho accesses activEcho servers using a standard HTTPS connection, just like a user does from a web browser. If your activEcho server is not configured with a valid 3rd party SSL certificate, mobilEcho needs permission to allow this connection.

If your activEcho server uses a self-signed certificate, you will need to enable Allow connections to activEcho servers with self-signed certificates on the File Server tab of the Settings window.

5. The Volume Properties window will appear.

6. Edit the Volume Name if you would like to change the name.

7. Click OK to create the volume.
Creating a Volume that provides access to SharePoint 2007 or 2010 content

mobilEcho can provide access to files residing in document libraries on SharePoint 2007 and 2010 servers. A mobilEcho SharePoint volume can point to an entire SharePoint server, a specific SharePoint site or subsite, or a specific document library. These files can be opened, PDF annotated, edited, and synced, just like files that reside in traditional file server or NAS storage. mobilEcho also supports Check Out and Check In of SharePoint files.

SharePoint authentication methods supported

mobilEcho supports SharePoint servers that allow client authentication using NTLMv1, NTLMv2, and Kerberos. If your SharePoint server requires Kerberos authentication, you will need to make an update to the Active Directory computer object for the Windows server or servers that are running the mobilEcho server software. The mobilEcho Windows server needs to be given permission to present delegated credentials to your SharePoint server on behalf of you users.

Enabling the mobilEcho Windows server to perform Kerberos Delegation

  1. In Active Directory Users and Computers, locate the Windows server or servers that you have mobilEcho 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 mobilEcho. 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.
  6. 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.

To configure a SharePoint volume on the mobilEcho server:

1. From the mobilEcho Administrator window, click Volumes.

2. On the Volumes dialog, click Create.

3. If you are running a Trial or Enterprise License version of mobilEcho Server, you will be asked to choose a volume location. To share a SharePoint server, site, or document library, choose On a SharePoint server.


If you are running a mobilEcho Server with a non-enterprise perpetual license that does not support resharing volumes on other servers, you will not see options for creating a volume that resides on another file server or on a SharePoint server.

4. You are prompted to enter the URL of the SharePoint server, site, or subsite you would like this volume to point to. This is the same URL you would use in a web browser to access that server, site, or subsite. The URL can only include a SharePoint HTTP or HTTPS URL to the root location of the server or to the root location of a site or subsite. Do not use a URL path that includes a document library or other non-site folder name, or a file name like "default.aspx".

For volumes that point to a specific document library, after entering the URL to the site or subsite where the document library resides, enter the name of the document library in the Document library name field.

 
 
Required setting for HTTPS SharePoint servers with self-signed certificates

mobilEcho accesses SharePoint servers using SharePoint web services over a standard HTTP HTTPS connection, similar to how a user does from a web browser. If your SharePoint server is not configured with a valid 3rd party SSL certificate, and you've configured mobilEcho share an https:// SharePoint URL, mobilEcho needs permission to allow this connection.

Some SharePoint servers are configured to only allow HTTPS connections and will redirect any HTTP connections to HTTPS. In this scenario, if your SharePoint server is using a self-signed certificate, you will also need to give mobilEcho permission to allow this connection.

If your SharePoint server uses a self-signed certificate, you will need to enable Allow connections to SharePoint servers with self-signed certificates on the File Server tab of the Settings window.

 


5. The Volume Properties window will appear.


6. Edit the Volume Name if you would like to change the name.

7. Click OK to create the volume.

 
If you are using Personal Sites in your SharePoint configuration, you will not be able to browse them directly. If you add as a volume a specific SharePoint site, e.g. http://sharepoint2010.glilabs.com:2229/my/personal/user, it will just work. If the volume path leads to the folder above, e.g. http://sharepoint2010.glilabs.com:2229/my/personal/ or http://sharepoint2010.glilabs.com:2229/my/, you will receive an error when trying to open that volume, but you'll be able to provision folders within that volume, either by path ("user") or by using the %USERNAME% wildcard.

Volume Properties

Index volume for search

Filename indexed searching is enabled on newly created volumes. To disable this feature, remove the check from this checkbox; in addition, you must Restart the volume in the Volumes dialog for this change to take effect.

Use custom index file path

To specify an alternate index file location for a volume, place a check in this checkbox and select a path for the new index file location.

Support content searching

Enables content searching on the volume by mobilEcho clients. This feature requires that Microsoft Windows Search is installed on the server. mobilEcho defaults to having content search enabled on all volumes.  To disable it on an individual volume, you must first uncheck Support content search on all volumes on the Search tab of the Settings dialog.

Search Index and Content Search settings apply only to "On this Server" volumes

mobilEcho is only capable of tracking live changes to files that exist in the storage on the Windows server where mobilEcho is installed. For this reason, only volumes located on directly on the mobilEcho server support fast indexed filename search and Windows Search integrated full content search.

Changing Permissions for Shared Files and Folders

mobilEcho uses the existing Windows user accounts and passwords. Because mobilEcho enforces Windows NTFS permissions, you should normally use Windows’ built-in tools for adjusting directory and file permissions. The standard Windows tools provide the most flexibility for setting up your security policy.

mobilEcho volumes that reside on another SMB/CIFS file server are accessed using an SMB/CIFS connection from the mobilEcho server to the secondary server or NAS. In this case, access to the secondary server is performed in the context of the user logged into the mobilEcho client app. In order for that user to have access to files on the secondary server, their account will need both "Windows Share Permissions" and NTFS security permissions to access those files.

Permissions to files residing on SharePoint servers are regulated in accordance to the SharePoint permissions configured on the SharePoint server. Users receive the same permissions through mobilEcho as they receive when they access SharePoint document libraries using a web browser.

Replicating Volumes

You may desire to make all your existing Windows File Shares or ExtremeZ-IP File Shares available to mobilEcho users. Each time you reopen the Volumes window, mobilEcho checks for any Windows SMB or ExtremeZ-IP AFP volumes that are not currently shared as mobilEcho volumes. If such volumes are found, the appropriate Replicate button is enabled.

When you click a Replicate button, the number of shares to be replicated is displayed and you are asked to verify that you want to replicate them.

Because someone could add or remove volumes to either the SMB or EZIP service at any time, when you reopen the Volumes window, note the state of the Replicate buttons. If they are dimmed (disabled), no new SMB or EZIP volumes have been added. If one of the corresponding mobilEcho volumes is removed, the button is enabled.

mobilEcho Users

The Users dialog box lets you view the users connected to the server.

To view the Users dialog box, click Users on the mobilEcho Administrator window.

User names and Location IP addresses identify users who are currently connected. Their idle times are also given. The dialog refreshes automatically.

Click on a column title to sort the list by a column.

Setting a minimum client version

Each mobilEcho file server contains a minimum client version setting. If a client of a version preceding the one set in that key attempts to connect to the mobilEcho server, it will receive a notice that it doesn't meet the minimum version requirement and will be refused connection.

When mobilEcho is first installed, this minimum client version is set to the earliest version that is compatible with the mobilEcho server. If the server is later upgraded to a new version of the mobilEcho file server software, this minimum client version setting will be modified only if necessary for compatibility, which usually won't be the case.

If you would like to set the minimum client version that you allow to connect to you mobilEcho server, you can do so by editing this registry key:

\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\mobilEcho\Parameters4\Refreshable\Pez\MinimumClientVersion

The version number entered in this registry key needs to match the version number as it appears in the mobilEcho client app's settings menu. For example, the minimum client version number for mobilEcho 2.X and 3.X servers to date is: 2.0.0.282

If you have multiple mobilEcho servers, you will need to set this registry key on each server if you would like the minimum client version requirement enforced by each server. Alternatively, if you're using the mobilEcho Client Management system to centrally manage your clients, you can set this setting on just the server that is acting as the client management server. Since all your clients call home to this server, they will be denied access the next time they do and will be prompted that they need to upgrade their client app.

Clients not meeting the minimum version requirement will not receive updated profiles or remote wipe commands

If you set the minimum client version setting on your mobilEcho Client Management server, any existing managed clients that are running an earlier version of the mobilEcho app will no longer be able to communicate with the server to receive updated management profiles or remote wipe commands. If you need to remote wipe a client running an older version of the mobilEcho app, you will need to modify this setting so that it's allowed to communicate with the server.

Labels
  • None