Any user of Migration App v3.4.0 that needs to migrate data from a network share. 

This issue was resolved for Migration App v3.6.0 and above, but only for a fresh install.

  • If you are updating from v3.4 to v3.6, and you haven't already changed your logon as directed below, you will still need to follow the instructions for this workaround.
  • If you are updating from v3.4 to v3.6 and you have already changed your logon to the Local Windows User, that setting will be retained and you have nothing more to do.

This product is currently in Limited Availability. We invite any Customers interested in using the product to engage Egnyte Professional Services or their Customer Success Manager to have it enabled for their domain.


CMM Agent service cannot migrate data from network shares in its default configuration. This is because the CMM Agent service logs on initially as the Local System account.


By design, the Local System account has access only to local drives and cannot access any network shares. Therefore, when logged on as a Local System account, any attempt by Migration App to create a migration job that refers to a UNC path or a mapped drive as a source fails with an error. 

Network shares are accessible to privileged local users only. To access a network share, the CMM Agent service needs to be reconfigured to log on as a designated user account with access to a given resource.

Invoke the whoami and dir commands in Windows PowerShell to confirm access. If you need assistance with that, view Using whoami and dir Commands to Confirm Access to Network Share Resources.

We recommend operating the CMM Agent Service under the local user account from the very beginning if any of the network shares may be used in the future for data migration.

Once you have changed the Logon to Local User, any previously created migration jobs will no longer be operational.

Changing the CMM Agent Logon from Local System to Local User with Network Share Access

  1. First, you need to stop the CMM Agent service. Go to the system tray for Cloud Migration Manager Agent


    Select the meatball menu on the upper right corner (the triple dots) and select Stop service.


    Then click Stop to confirm you wish to stop the service.


    Now you can see the Agent is no longer connected to the cloud.


  2. Return to Windows Explorer, type Services in the search field, and open the application.


  3. Look for a service called CMM-Agent Service from the alphabetical listing. Note that it indicates it has logged on as the Local System.


    Right-click on that item to display the context menu and select Properties.


  4. From the Properties dialog, select the Log On tab. Then select the radio button for This account. Enter the machine name and local user, and then provide the password. Then click Apply. If you don’t know the machine name and local user, this article will walk you through the steps of using the PowerShell to determine them.


    A pop-up window will appear. Click OK.


    Then click OK to close out of the Properties window.

  5. Now return to the System Tray for Cloud Migration Manager Agent, go to the meatball menu, and select Start service. This should only take a few moments.


    Once the service has successfully started, it will indicate that it is Connected to cloud.


  6. Now return to the Services window and look for the CMM-Agent Service. You can see that it is no longer running as the Local System but is logged on as the user account with access to the network share. So you are ready to create a new Migration Job.


  7. Go to the Egnyte Migration Dashboard. Click on Create New Migration.

    In the resulting dialog window,
    • Specify a Migration Name of your choice.
    • Select a Source from the list of available Sources.
    • For Source Folder Path, enter \\server\matt\client files.
    • For Destination Folder Path, enter /Shared/Client Files or whatever you want the folder to be named on the destination.
    • Click Create Migration.


  8. The Migration Job interface will now display. Wait just a few moments until Migration Status changes from Initialized to Created. You may now initiate the Migration Job by clicking Scan.


Questions? Feature Requests? Other Feedback?

If you have feature suggestions or requests, feel free to submit them here, and make sure you mention Migration App in the text.

For more complex requests that would benefit from providing screen shots or other attachments, you may submit them to Be sure to include Migration App in the email title. Our Support team will push your comments to the Product team for consideration.