The following is an excerpt from the data manager.config file located under "All Users" on systems that utilitze the Key Downloader;

 <IsUploaderEnabled>true</IsUploaderEnabled>
  <UploaderSettings>
    <IsMoveUncPathEnabled>false</IsMoveUncPathEnabled>
    <IsSSPEnabled>true</IsSSPEnabled>
    <CreateDebugTripFiles>false</CreateDebugTripFiles>
    <UncPath>\\remotehost\DataManager</UncPath>
  </UploaderSettings>
  <NetworkDownloaderSettings>
    <Port>3984</Port>
    <MaximumConnections>200</MaximumConnections>
  </NetworkDownloaderSettings>
  <EthernetDownloaderSettings>
    <Port>3985</Port>
    <MaximumConnections>200</MaximumConnections>
  </EthernetDownloaderSettings>
  <IsPassiveEnabled>true</IsPassiveEnabled>
  <MapDirectoryInternal>C:\Documents and Settings\All Users\Application Data\GEOTAB\Checkmate\Maps</MapDirectoryInternal>
</ServerSettings>

My question would be if the data manager.config needs to be modified under each individual users folders that access GEOtab. Currently, the above exists under "All Users," but both the uploader and passive are disabled under each config file that exists for each user;

 <IsUploaderEnabled>false</IsUploaderEnabled>
  <UploaderSettings>
    <IsMoveUncPathEnabled>false</IsMoveUncPathEnabled>
    <IsSSPEnabled>true</IsSSPEnabled>
    <CreateDebugTripFiles>false</CreateDebugTripFiles>
    <UncPath>\\remotehost\DataManager</UncPath>
  </UploaderSettings>
  <NetworkDownloaderSettings>
    <Port>3984</Port>
    <MaximumConnections>200</MaximumConnections>
  </NetworkDownloaderSettings>
  <EthernetDownloaderSettings>
    <Port>3985</Port>
    <MaximumConnections>200</MaximumConnections>
  </EthernetDownloaderSettings>
  <IsPassiveEnabled>false</IsPassiveEnabled>
  <MapDirectoryInternal>C:\Documents and Settings\All Users\Application Data\GEOTAB\Checkmate\Maps</MapDirectoryInternal>
</ClientSettings>

tonypartheniou wrote "Typically all changes should be made through the user interface and not through the config file, although the config file can be used if it helps deploy the software efficiently."

The interface was not configured correctly when the rollout of 5.3 occured. Even after doing the changes through the interface, the changes are never applied to the data config file even after stopping the services and restarting GEOtab. I'm not sure if they have fixed this error in 5.3 yet. If they have, then we will follow those given procedures. However, just an FYI that this is a current glitch we encountered when installed 5.3; we had to manually configure the data manager.config files on each PC that used the key downloader.

Thanks,