LogoLogo
Movebot HomeLogin
  • Welcome
  • CONNECTIONS
    • SharePoint Online
    • Google Workspace Drives
    • Windows File Server
    • Dropbox Business
    • Egnyte
    • Box
    • BIM 360 Docs
    • Amazon WorkDocs
    • Citrix ShareFile
    • Google Workspaces Gmail
    • Outlook Online (Office 365) EWS
    • Exchange Server
    • IMAP Server
    • pCloud
    • Block Storage
      • Amazon S3
      • Azure Files
      • Azure Blob
      • Google GCS
      • Backblaze B2
      • Wasabi
    • Other Connectors
      • SFTP Server
      • Google Drive (Personal)
      • Dropbox Personal
      • SharePoint via Application Access
  • Features
    • Overview
    • Data Migrations with Movebot
    • Mail Migrations with Movebot
    • Calendar Migrations with Movebot
  • Using Movebot
    • Overview
    • Scan and Discovery
      • Project Discovery Scan
      • Searching Scan Results
      • Adding Transfers from Scan
      • Warnings and Issues
    • Transfer Mapping
      • Add User Mappings
      • Add Team/Shared Drives
      • Add Network Mappings
      • Import CSV Mappings
      • Excluding Content
    • Permissions and Metadata
      • Mapping Permissions
      • Scanning permissions
      • Manual Permissions
    • Transfer Execution and Cutover
      • Deltas and Changes
      • Failures and Errors
      • Pausing/Resuming
      • Scheduling
      • Data Localization
  • Platforms Guides
    • Overview
    • Google
      • SharedWithMe content
      • Sharing and Ownership
      • Performance and Limits
      • Deduplication of files/folders
      • Delegating Domain Wide Authority
      • Mail ingestion methods
    • SharePoint
      • Granting OneDrive Access
      • Performance Limits and SharePoint Ludicrous Mode
    • Windows Fileservers
      • Server Requirements
      • Proxy Configuration
      • Non-GUI Environments
      • Running the Movebot Agent as a Service
      • Logging and Debugging
    • Dropbox
      • Namespaces and Limitations
    • Others
      • Exchange Web Services (EWS)
        • How to disable EWS throttling
  • Troubleshooting
    • Performance and Speed
    • Errors and Failures
      • Common Errors
        • Error: user-not-active
        • Error: token-expired
        • Error: unknown-error
        • Error: user-not-found
        • Error: file-not-found
        • Error: invalid-filename-characters
        • Error: duplicate-file-name
        • Error: permissions-mapping-incomplete
        • Error: access-denied
        • Error: uploaded-size-mismatch
    • Hipaa Regions
  • Login to Movebot
Powered by GitBook
On this page

Was this helpful?

Export as PDF
  1. Platforms Guides
  2. Windows Fileservers

Running the Movebot Agent as a Service

Learn how to run the Movebot Agent as a Service for file server transfers.

Last updated 10 months ago

Was this helpful?

The Movebot Agent (Couchdrop Cloud Connector) can be run as a Windows service.

Installing the agent as a service requires some understanding of how Windows services work and the service must be configured to run as the same user that is performing the configuration.

Before starting, make sure that you have installed the Couchdrop Cloud Connector by Make sure you have run and configured everything properly and check that it is working. We recommend closing the desktop configuration app and systray application before starting the service.

Next in a command line, open the Couchdrop Cloud Connector folder located under Program Files and run the following command.

.\couchdrop-cloud-connector-service.exe install

Next, open the service manager:

services.msc

Find the service for "Couchdrop Cloud Connector" and open it.

Adjust the Log On configuration specifying the user account that you are logged in as the account to run the service under. This step is important as the agent configuration is stored under the user's profile. Without configuring the correct user, the service will not properly connect.

Finally, you can start the service. Once it's running, you can reopen the Couchdrop Cloud Connector configuration application and it should show the service as Running in Background.

Tags: agent

following the steps outlined here
.