Posts Tagged ‘client management system’

Active Directory assigned home directories are not working in the mobilEcho client

Tuesday, November 8th, 2011

Introduction

mobilEcho includes the ability to automatically show a user’s Active Directory assigned home folder in the mobilEcho client app. These home directory locations are specified as a Windows file share (SMB) UNC path in the user’s Active Directory user account profile.

When setting up home directories in mobilEcho, it is important to consider the topology of your mobilEcho deployment.

mobilEcho includes a ‘Network Reshare’ feature, that allows a mobilEcho server to host a shared volume that gives access to data located on a second file server. The mobilEcho server uses the SMB/CIFS protocol to connect to the secondary file server.

If mobilEcho is installed directly on the server hosting your users’ Active Directory assigned SMB home folders, and a mobilEcho shared volume has been created with the same name and location as the SMB home folders shared volume, the mobilEcho UNC path to the home folders shared volume will be identical to the UNC path to the SMB home folders shared volume, and the UNC path specified in the user’s Active Directory profile home folder setting will be correct for both SMB access and mobilEcho access.

If you are using mobilEcho’s Network Reshare feature to give access to home directories on a secondary SMB file server, the SMB UNC path in a user’s Active Directory profile home folder setting will not match the mobilEcho UNC path, since mobilEcho servers access their home folders by connecting to a different server.

In this case, you will need to configure a Network Reshare Path Mapping, so that mobilEcho knows how to translate the SMB UNC path it gets from the Active Directory profile home folder setting to the mobilEcho UNC path that the mobilEcho client needs to know to connect to the home folder.

Configuring a Network reshare path mapping

  1. Click Servers & Folders in the top menu.
  2. Click the Add new path mapping button.
  3. Select the mobilEcho server where the mobilEcho network reshare shared volume is located. Then enter the name of the mobilEcho Shared Volume.
  4. Click Next.
  5. Enter the UNC Path that you would like to be redirected to the mobilEcho Shared Volume you specified in the previous step.
  6. Click Save.

Important note on server names in AD path vs. Network reshare path mapping

Because mobilEcho is matching on this path, the UNC Path needs to use the exact server name and SMB shared volume name as it appears in your users’ Active Directory user profile home folder setting. If an SMB home folder’s path in Active Directory uses a different name for the server than is entered in the path mapping setting (such as “\\fileserver.company.com\sharename” vs. “\\fileserver\sharename”) the home directory will not work in the mobilEcho client. If you’ve used more than one method for representing your server’s name in the Active Directory profile home folder setting for your users, you will need to create a path mapping for each variation on the server name.

Setting the minimum allowed mobilEcho client version on a mobilEcho server

Tuesday, November 8th, 2011

Introduction

Each mobilEcho file server contains a minimum client version setting. If a client earlier than this version 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.

Setting the minimum client version

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

Deployments with multiple mobilEcho server

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.