Track desktop client events in x360Sync

Written By Tami Sutcliffe (Super Administrator)

Updated at July 27th, 2021

Overview

x360Sync is committed to providing administrators with advanced tools to fully manage organizations, user accounts, and data usage. In addition to tracking activity logs and generating detailed reports, administrators can integrate with Professional Service Automation (PSA) tools, as well as Remote Monitoring and Management (RMM) platforms, to quickly address issues that impact users and the health of the system.

Tracking Events with RMM Tools

The desktop client generates log files; however, these files can be difficult to review. As an alternative, you can isolate errors quickly by reviewing the Windows Application Event log. The Event log can be used to isolate event dates and times and can be referenced in conjunction with the desktop client log files to dive deep into issues with much greater efficiency.

Important desktop client events—including sync events, registration events, collision events, and service starts—are visible within the Windows Event Viewer and OS X Console, allowing you to proactively track activity and address issues that directly affect end users.

Within the Windows Event Viewer, the following events can be found in the Application section, and are categorized at the Information level. The Source of these events is listed as the name of the branded desktop client. 

Registration Events

The desktop client records the date, time, and initiator of registration and unlinking events. If a desktop client is unlinked, these particular events are very useful to help track the who or why of the incident.

Event Type

What it Means

Event ID

Desktop Client Registered

A new desktop client registered with the server, either by the desktop client contacting the server, or through an automated script.

1024

User <name> Registered

The user has successfully registered with the server, either from the desktop client UI, or through an automated script.

1026

User <guid> Unregistered

The user has successfully unregistered from the server (unlinked the desktop client), either from the desktop client UI, through an automated script, or from the web portal.

1027

All Local Users Unregistered

All local users successfully unregistered from the server during the desktop client uninstall process; this message is useful when one desktop client is uninstalled on a shared machine.

1028

User Registration Failed: <message>

An error occurred while attempting to register with the the server, either through the desktop client UI, or through an automated script. The <message> will indicate a possible cause of failure, such as a connection failure with the server.

1029

Desktop Client Unregistered

The desktop client unregistered with the server. 

1025

 

Sync Events

Sync events allow you to proactively monitor sync and backup events that affect end users. For example, using an RMM tool, you can automatically generate tickets based on certain event types.

Event Type

What it Means

Event ID

Sync Paused

File sync has been paused through the desktop client UI.

1280

Sync Resumed

File sync is unpaused (resumed) through the desktop client UI.

1281

Sync Error <rsub_id>:<message>

A sync or backup error occurred (either an up or down event) for the specified root subscription id. The <message> indicates the possible cause of failure; for example, batch add failure, db not found, revision not current, and so forth.

1282

Sync Successful <rsub_id>

A successful sync or backup event occurred (either an up or down event) for the specified root subscription id.

1283

 

Service Events

Service Start events allow you to better understand the desktop clients that have successfully started.

Event Type

What it Means

Event ID

Service Start

The desktop client service is starting.

512

 

Collision Events

Event IDs for collision events begin tracking when a collision is created, resolved, failed to resolve, and so forth. The desktop client log files can then be used with the Event ID of the incident to narrow down the timeframe in the log files.

Event Type

What it Means

Event ID

Collision Created

A collision is logged.

768

Collision Resolution

A collision is resolved.

769

Collision Failed

A collision was logged, but the conflicting content disappeared while attempting to resolve. Please contact Axcient Support.

770

Collision Message

A message has been generated in relation to a collision event.

771

 

Viewing Events in RMM Tools 

Optionally, you can utilize Remote Monitoring and Management (RMM) tools to proactively monitor these events. For example, when working with ConnectWise Manage® (Labtech), you can generate tickets, alerts, and create reports to optimize solutions for end users. 

For an overview on event log monitoring options with ConnectWise Manage® (Labtech), and for specific instructions on creating event log monitors, please reference the ConnectWise Manage® (Labtech) Creating Event Log Monitors help file.