VSA > System > BMS Integration > Sync Configuration
In the VSA the Sync Configuration page configures VSA access to data in Vorex™. Once the configuration is activated, Vorex™ creates tickets for the VSA, based on ticket creation events detected in the VSA.
Prerequisites
The RMM Integration - Kaseya v2 record for the corresponding Vorex™ company you wish to integrate must already be configured and enabled for your VSA.
The Activate Service Desk checkbox in the VSA > Service Desk module—if installed—must be deactivated.
Actions
Edit - Configures the Vorex™ company account that creates tickets for this VSA.
Test - Tests the connection with the Vorex™ server and company account.
Resume / Enable Sync Processing
Resumes creating tickets in Vorex™.
Any ticket creation events in the VSA that have occurred since sync processing was paused are forwarded to Vorex™.
Pause Sync Processing
Halts ticket creation in Vorex™.
Ticket creation events continue to be queued, ready to create tickets when you resume sync processing.
Activate Integration Module
The VSA > Service Desk and Ticketing modules will no longer create tickets for any ticket creation events in the VSA. This includes tickets created for alerts and for inbound emails.
The email readers for Service Desk and Ticketing will no longer be polled.
Note: Existing tickets are not processed in this initial release of RMM Integration - Kaseya v2.
Deactivate Integration Module
Ticket creation events in the VSA begin creating tickets in the Ticketing module.
Procedure
In the VSA, select the System > BMS Integration > Sync Configuration page.
Click Edit.
Enter the following in the Edit Settings dialog.
URL of BMS Server - Enter the URL of your Vorex™ server.
Company - Enter your Vorex™ company name.
Username - Enter a Vorex™ login username. The Vorex™ "root" user account is recommended. See the prerequisites in Integrating Servers v2.
Password - Enter the password for your Vorex™ login username.
Select Asset Push Rule
Agent Assets Only - Only computers with agents installed on them are pushed to Vorex.
All Assets - Devices without agents can be promoted to assets. Both computers and devices promoted to assets are pushed to Vorex.
None - No assets are pushed to Vorex.
Ticket Processing Rules
Deduplicate matching tickets updated within <N> hours – Matching tickets can be sent to Vorex as a single ticket with a duplicate count of X within the designated time frame.
Reopen closed duplicate tickets – Closed duplicate tickets can be reopened after synchronization to Vorex.
Click Test to verify your VSA can access the Vorex™ server.
Click the Activate Integration Module.
Click the Resume/Enable Sync Processing button.
Both buttons must have a green checkmark to trigger the creation of tickets in Vorex™.
Configure ticket creation events in the VSA.
Optionally review log entries created by the VSA for ticket requests sent to Vorex™
System > BMS Integration > Sync Transaction Log - Displays a log of sync transactions between the VSA and Vorex™.
System > BMS Integration > BMS API Log - Displays a log of REST API requests related to the integration between the VSA and Vorex™.