Follow these steps to install and configure the DataSync Client on your computer. The entire setup process typically takes about 10-15 minutes.
Right-click the downloaded installer file and select "Run as administrator".
The Setup Wizard will guide you through the installation:
Figure 1: The Setup Wizard welcome screen
Click Next to proceed. You will be presented with the license agreement:
Figure 2: Accept the license agreement to continue
C:\Program Files\DispatchScience\DataSyncClient)The installer will automatically:
Once installation is complete, you'll see the completion screen:
Figure 3: Installation complete - check the box to launch the Configuration Tool
Check "Launch DataSync Configuration Tool" and click Finish to open the configuration tool immediately.
After installation, open the DataSync Configuration Tool from the Start Menu.
Navigate to the Settings tab to configure your client:
Figure 4: The Settings tab in the Configuration Tool
Configure the following settings:
| Setting | Description |
|---|---|
| Client ID | A unique identifier for this client, automatically generated from the computer's MAC address. This field is read-only and ensures the same machine always uses the same ID |
| Server URL | The DataSync server URL (e.g., https://datasync.dsapp.io/). This will be provided by your administrator |
Note: The polling interval (how often the client checks for new data) is managed by the server and can be adjusted by your administrator from the DataSync portal.
Navigate to the Database tab to configure your local SQL Server connection:
Figure 5: Configure your local database connection
Enter your SQL Server connection string in the Connection String box, then click
Save Connection String. The value is stored locally in this machine's
appsettings.json (ConnectionStrings:LocalDb). Example connection strings:
Windows Authentication:
Server=localhost;Database=DataSyncLocal;Trusted_Connection=True;TrustServerCertificate=True
SQL Server Authentication:
Data Source=.;Database=DataSyncDb;Integrated Security=false;User ID=sa;Password=yourpassword;TrustServerCertificate=True;Encrypt=True;
Navigate to the Authentication tab and click "Sign In / Re-authorize".
Figure 6: The Authentication tab before signing in
Figure 7: Successfully authenticated with Azure AD
Click "Save Configuration" at the bottom of the window to save all your settings.
Navigate to the Service tab to start the Windows service:
Figure 8: Manage the Windows service from the Service tab
When a new version of the DataSync Client is available, you can update your existing installation without losing your configuration.
The update process is seamless:
appsettings.json file (containing Client ID, Server URL, database connection, and all other settings) is not overwritten. All your settings are kept as-is.%PROGRAMDATA%) are not affected by the update.The DataSync Configuration Tool provides a graphical interface for managing all client settings. This section provides detailed information about each tab and its options.
Essential connection and client settings:
| Setting | Description |
|---|---|
| Client ID | The unique identifier for this client, as assigned by the server based on your install key. This field is read-only and always comes from the server — it is not read from or overridden in appsettings.json. |
| Server URL | The base URL of the DataSync server (provided by your administrator) |
Note: The polling interval is managed by the server and can be adjusted by your administrator from the DataSync portal.
Configure your local SQL Server database connection. The client will synchronize data to this database.
| Element | Description |
|---|---|
| Connection String | The SQL Server connection string for your local database, stored in this machine's appsettings.json under ConnectionStrings:LocalDb. Edit it here and click Save Connection String to write it back to the file. |
| Test Connection | Tests the connection string currently shown in the box by attempting to connect to the database. |
| Save Connection String | Saves the connection string to appsettings.json. You'll be offered to restart the service so it picks up the new value. |
Client ID, Client Name and Tenant shown in the Configuration Tool always come from the server based on your install key — they are never read from local settings.
Note: The service reads the connection string when it starts. After you save a change, restart the DataSyncClient service for it to take effect.
Manage your Azure AD authentication status:
| Element | Description |
|---|---|
| Status | Shows current authentication state (Authenticated / Not authenticated) |
| Username | Your authenticated Azure AD account email |
| Token Expires | When your current authentication token expires |
| Sign In / Re-authorize | Opens browser for Azure AD sign-in |
| Clear Cached Tokens | Removes stored authentication tokens (useful for troubleshooting) |
Monitor and control the DataSync Windows service:
| Element | Description |
|---|---|
| Service Status | Current state: Running, Stopped, or Not Installed |
| Start | Start the service (requires administrator privileges) |
| Stop | Stop the service gracefully |
| Restart | Stop and restart the service |
| Refresh | Update the displayed service status |
| Open Event Viewer | Launch Windows Event Viewer to see service logs |
| Button | Description |
|---|---|
| Save Configuration | Saves all changes to the configuration file |
| Reload | Discards unsaved changes and reloads from disk |
| Validate | Checks for missing required fields without saving |
| Restart service after save | When checked, automatically restarts the service after saving |
The DataSync Client authenticates to the server with an install key (a
dsk_live_… token you obtain from the portal and set via the Configuration Tool).
The install key is what the service uses for all syncing.
When the Configuration Tool needs an install key it shows the Install Key dialog, which offers two ways to obtain one.
Option 1 — Generate with Microsoft sign-in (recommended)
Option 2 — Paste a key from the portal
Authentication tokens expire periodically for security. When your token expires, you'll see these symptoms:
To re-authorize:
If you experience persistent authentication issues, try clearing the token cache:
The easiest way to manage the service is through the Configuration Tool's Service tab:
Win + R, type services.msc, press EnterRun these commands as Administrator:
sc start DataSyncClient (Start the service)
sc stop DataSyncClient (Stop the service)
sc query DataSyncClient (Check service status)
The DataSync Client logs detailed information to multiple locations:
Windows Event Log:
eventvwr.msc)Log File:
[Installation Directory]\log.txt
| Component | Requirement |
|---|---|
| Operating System | Windows 10/11 or Windows Server 2016+ |
| .NET Runtime | .NET 10.0 or later (included in installer) |
| Database | SQL Server 2016 or later |
| Network | Internet access to DataSync server |
| Disk Space | 100 MB for application, additional space for local database |
Ensure outbound HTTPS (port 443) access to:
login.microsoftonline.com (Azure AD authentication)The DataSync Client supports automatic updates. When a new version is available on the server, the client will automatically detect, download, and apply the update without user interaction.
appsettings.json) is preserved during updatesThe updater writes a log file for troubleshooting:
C:\Program Files\DispatchScience\DataSyncClient\updater.log
If an update fails, the updater automatically rolls back to the previous version and restarts the service. No manual intervention is required.
A failed update does not stop data synchronization — the client keeps syncing on its current version the whole time. To avoid repeatedly retrying a problematic update, the client limits itself to a few attempts per version (spaced a few minutes apart) and then stops trying, leaving you running safely on your existing version. It will try again automatically later in case a corrected update has been published. If a client seems stuck on an old version, contact your administrator, who can remove it from the update or investigate using the log above.
Check Authentication:
Check Configuration:
| Error | Cause | Solution |
|---|---|---|
| "401 Unauthorized" | Token expired | Re-authorize using Configuration Tool |
| "403 Forbidden" | No tenant permission | Contact administrator |
| Sign-in page errors | Network/browser issues | Check network, try different browser |
| Issue | Possible Cause | Solution |
|---|---|---|
| No jobs available | No new data on server | Check with administrator |
| Connection timeouts | Network issues | Verify server URL and firewall |
| Database errors | Connection string invalid | Test connection in Config Tool |
| "Execution Timeout Expired" while applying a table | A very large table is slow to update on the local SQL Server | The client applies changes in batches so this is rare; if it persists, ensure the local SQL Server is not under heavy load and contact your administrator (the apply timeout is managed by the server — see note below) |
appsettings.json, so there is nothing to
configure on the client. If a very large table genuinely needs more time, contact your
administrator.
If you encounter issues not covered in this manual:
| Item | Location |
|---|---|
| Configuration File | [Installation Directory]\appsettings.json |
| Log File | [Installation Directory]\log.txt |
| Token Cache | %PROGRAMDATA%\DispatchScience\DataSyncClient\msal_token_cache.bin |
| Service Name | DataSyncClient |
| Default Install Path | C:\Program Files\DispatchScience\DataSyncClient |
This manual is maintained by Dispatch Science.