Continuum Link: Difference between revisions

From RangerMSP Wiki - PSA software for MSPs and IT services providers
Jump to navigation Jump to search
No edit summary
 
(13 intermediate revisions by 3 users not shown)
Line 1: Line 1:
=Introduction=
=Introduction=
The CommitCRM-Continuum Integration automatically creates tickets in CommitCRM from alerts and service tickets generated by the Continuum system, or from tickets created manually by the Continuum NOC. Users can then close the Ticket in CommitCRM, and it will be closed in Continuum.
The RangerMSP-Continuum Integration automatically creates tickets in RangerMSP from alerts and service tickets generated by the Continuum system, or from tickets created manually by the Continuum NOC. Users can then close the Ticket in RangerMSP, and it will be closed in Continuum.


The CommitCRM integration with Continuum includes:
The RangerMSP integration with Continuum includes:


# Two-ways Ticket Integration.
# Two-ways Ticket Integration.
#* Continuum’s Tickets create Tickets in CommitCRM.
#* Continuum’s Tickets create Tickets in RangerMSP.
#* Closing a Ticket in CommitCRM closes the Ticket in Continuum.
#* Closing a Ticket in RangerMSP closes the Ticket in Continuum.
#* CommitCRM Tickets can be assigned to Continuum’s NOC / Service Desk.
#* RangerMSP Tickets can be assigned to Continuum’s NOC / Service Desk.
#* New Tickets in Continuum can be created from CommitCRM’s Tickets
#* New Tickets in Continuum can be created from RangerMSP’s Tickets
#* Comments for Tickets can be sent from CommitCRM to Continuum.
#* Comments for Tickets can be sent from RangerMSP to Continuum.
# The ability to link Account to Site in Continuum or create Account from Site.
# The ability to link Account to Site in Continuum or create Account from Site.
# The ability to link Asset to Device in Continuum or create Asset from Device.
# The ability to link Asset to Device in Continuum or create Asset from Device.


Once the CommitCRM-Continuum Integration has been configured, Continuum
Once the RangerMSP-Continuum Integration has been configured, Continuum
Ticketing System is disabled and Ticket management is performed solely in CommitCRM.
Ticketing System is disabled and Ticket management is performed solely in RangerMSP.


Ticket can still be viewed in Continuum (read-only); however, the master Ticket is managed in CommitCRM. When closing a Ticket in CommitCRM it is closed in Continuum. When closing a Ticket in Continuum it adds a History Note to the Ticket in CommitCRM, however, the Ticket stays open.
Ticket can still be viewed in Continuum (read-only); however, the master Ticket is managed in RangerMSP. When closing a Ticket in RangerMSP it is closed in Continuum. When closing a Ticket in Continuum it adds a History Note to the Ticket in RangerMSP, however, the Ticket stays open.




'''''Technical Note'''''<br>
'''''Technical Note'''''<br>
''The integration is based on a new Service running on your CommitCRM server (called CommitCRM RMMServer Service), which accepts all alerts and Tickets from Continuum and creates the Ticket in CommitCRM.''  
''The integration is based on a new Service running on your RangerMSP server (called CRM RMM Server Service), which accepts all alerts and Tickets from Continuum and creates the Ticket in RangerMSP.''  




=Continuum Settings=
=Continuum Settings=
This section describes the Setup steps required in the Continuum Portal in order to start working with CommitCRM as your PSA system in Continuum.
This section describes the Setup steps required in the Continuum Portal in order to start working with RangerMSP as your PSA system in Continuum.
<br><br>
<br><br>
'''Important Notes''':
'''Important Notes''':
# Once the CommitCRM-Continuum Integration has been configured on Continuum Portal, it takes a few hours (up to 24 hours) until the new settings apply on the Continuum back-end. Note that even if all settings seem correct on Continuum side, you should '''wait a few hours''' until the CommitCRMServer service can connect and download data.  
# Once the RangerMSP-Continuum Integration has been configured on Continuum Portal, it takes a few hours (up to 24 hours) until the new settings apply on the Continuum back-end. Note that even if all settings seem correct on Continuum side, you should '''wait a few hours''' until the RangerMSPServer service can connect and download data.  
# Once CommitCRM is activated as your PSA in Continuum Portal, Continuum Ticketing System is disabled and Ticket management is performed solely in CommitCRM.  
# Once RangerMSP is activated as your PSA in Continuum Portal, Continuum Ticketing System is disabled and Ticket management is performed solely in RangerMSP.  
# Since all Ticket Management is disabled in Continuum, Continuum email alerts for Tickets will also be disabled, and you will no longer get email alerts for new Tickets from Continuum Portal. In case you want to receive email alerts for new Tickets (arriving from Continuum Portal) via CommitCRM, you may consider using Commit Alerts Server module, which sends email alerts for new updates in the CommitCRM system. See more details in [[Alerts_Server|Commit Alerts Server]].
# Since all Ticket Management is disabled in Continuum, Continuum email alerts for Tickets will also be disabled, and you will no longer get email alerts for new Tickets from Continuum Portal. In case you want to receive email alerts for new Tickets (arriving from Continuum Portal) via RangerMSP, you may consider using RangerMSP Alerts Server module, which sends email alerts for new updates in the RangerMSP system. See more details in [[Alerts_Server|RangerMSP Alerts Server]].
<br>
<br>
To allow CommitRMM service to connect with Continuum and sync with it, a Continuum Partner Security code (also known as PSG) is required.
To allow CRM RMM service to connect with Continuum and sync with it, a Continuum Partner Security code (also known as PSG) is required.


To setup Continuum PSG:
To setup Continuum PSG:


# Login to the Continuum Portal with Admin account and go to ''Setup''.  
# Login to the Continuum Portal with Admin account and go to ''Admin''.  
# The ITS Portal Setup window is displayed. Click ''PSA integration'' in the left column. <br>[[File:Continuum_link_settings.png]]<br><br>
# The ITS Portal Setup window is displayed. Click ''My Company'' > ''PSA integration'' in the left column. <br>[[File:Continuum_link_settings.png]]<br><br>
# Click the link “CommitCRM” option.<br>[[File:Continuum link generate code.png]]<br><br>
# Click the link “RangerMSP” option.<br>[[File:Continuum link generate code.png]]<br><br>
# Copy the Security Code on the screen and click '''Enable'''. This will lock the Code to your account. Use this Code to complete the configuration in CommitCRM. See [[Continuum_Link#CommitCRM_Setup|CommitCRM Setup]].
# Copy the Security Code on the screen and click '''Enable'''. This will lock the Code to your account. Use this Code to complete the configuration in RangerMSP. See [[Continuum_Link#RangerMSP_Setup|RangerMSP Setup]].
# Now on the same page click '''Activate'''. You will receive message “CommitCRM Activated Successfully”. <br>[[File:Continuum link activate.png]]<br><br>
# Now on the same page click '''Activate'''. You will receive message “RangerMSP Activated Successfully”. <br>[[File:Continuum link activate.png]]<br><br>
# After receiving the "Activated successfully" message, it takes a few hours until the new settings apply on the Continuum back-end. Note that even if all settings seem correct on Continuum side, you should '''wait a few hours''' until the CommitCRMServer service can connect and download data.  
# After receiving the "Activated successfully" message, it takes a few hours until the new settings apply on the Continuum back-end. Note that even if all settings seem correct on Continuum side, you should '''wait a few hours''' until the RangerMSPServer service can connect and download data.  


<br>
<br>
Line 47: Line 47:
<br>
<br>


=CommitCRM Setup=
=RangerMSP Setup=
'''Please make sure to enable the integration with CommitCRM on the Continuum side (see [[Continuum_Link#Continuum Settings|Continuum Settings]]) before you proceed with the CommitCRM side setup below.'''
'''Please make sure to enable the integration with RangerMSP on the Continuum side (see [[Continuum_Link#Continuum Settings|Continuum Settings]]) before you proceed with the RangerMSP side setup below.'''
<br><br>
<br><br>
To set up CommitCRM to work with Continuum, the following steps are required:
To set up RangerMSP to work with Continuum, the following steps are required:


# Backup CommitCRM Database.
# Backup RangerMSP Database.
# Initialize Continuum PSG.
# Initialize Continuum PSG.
# Install CommitRMMServer.
# Install CRM RMM Server.
# Validate CommitRMMServer downloads Continuum Sites and Devices to the CommitCRM server.
# Validate CRM RMM Server downloads Continuum Sites and Devices to the RangerMSP server.
# Link Accounts and Assets in CommitCRM(*) to Sites in and Devices Continuum.
# Link Accounts and Assets in RangerMSP(*) to Sites in and Devices Continuum.
# Enable Continuum Integration.
# Enable Continuum Integration.
<br>
<br>
''* Note:<br>
''* Note:<br>
''The full integration with Continuum on the CommitCRM side will be '''disabled''' by default until you activate it explicitly, and Tickets will not be transferred to CommitCRM until then. This is to make sure users first link Continuum Sites to CommitCRM Accounts to avoid many duplicate Accounts which may be created if Tickets arrive before the links take place. Once all Accounts are linked, users should enable the integration, see [[Continuum_Link#Enable_Continuum_Integration|Enabling Continuum Integration]] ''.
''The full integration with Continuum on the RangerMSP side will be '''disabled''' by default until you activate it explicitly, and Tickets will not be transferred to RangerMSP until then. This is to make sure users first link Continuum Sites to RangerMSP Accounts to avoid many duplicate Accounts which may be created if Tickets arrive before the links take place. Once all Accounts are linked, users should enable the integration, see [[Continuum_Link#Enable_Continuum_Integration|Enabling Continuum Integration]] ''.


==Backup CommitCRM Database==
==Backup RangerMSP Database==
Before starting to work with the Continuum integration, make sure to [[Backup_and_Restore_FAQ|backup your CommitCRM database]].  
Before starting to work with the Continuum integration, make sure to [[Backup_and_Restore_FAQ|backup your RangerMSP database]].  


The integration includes linking and importing sites and devices into CommitCRM and it is strongly recommended to backup your system before starting to work with it.
The integration includes linking and importing sites and devices into RangerMSP and it is strongly recommended to backup your system before starting to work with it.


==Initialize Continuum PSG==
==Initialize Continuum PSG==
After you finish setting up the Security Code (PSG) at the Continuum Portal (see [[Continuum_Link#Continuum Settings|Continuum Settings]]), you can move on to the next step and enter the PSG into CommitCRM settings.
After you finish setting up the Security Code (PSG) at the Continuum Portal (see [[Continuum_Link#Continuum Settings|Continuum Settings]]), you can move on to the next step and enter the PSG into RangerMSP settings.
<br><br>
<br><br>
To initialize the PSG in CommitCRM:
To initialize the PSG in RangerMSP:
* Open  <Installation_DIR>\RMM\CMTZenithLink.ini
* Open  <Installation_DIR>\RangerMSP\RMM\CMTZenithLink.ini
* Copy the Security Code value from Continuum PSA Settings window as described above in [[Continuum_Link#Continuum_Settings|Continuum Settings]], and paste your Continuum Partner Security Code as the value for token PSG:
* Copy the Security Code value from Continuum PSA Settings window as described above in [[Continuum_Link#Continuum_Settings|Continuum Settings]], and paste your Continuum Partner Security Code as the value for token PSG:
  PSG=<Your-Continuum-Security-Code>
  PSG=<Your-Continuum-Security-Code>
Line 77: Line 77:
<br>
<br>


==Install CommitCRM RMMServer Service==
==Install CRM RMM Server Service==
After you finish setting up all of the required settings (see [[Continuum_Link#Initialize_Continuum_PSG|Initialize Continuum PSG]]), you can move on to the next step and install the CommitCRM RMMServer service.
After you finish setting up all of the required settings (see [[Continuum_Link#Initialize_Continuum_PSG|Initialize Continuum PSG]]), you can move on to the next step and install the CRM RMM Server service.


The CommitRMMServer runs as a Windows Service on your server.
The 'CRM RMM Server' runs as a Windows Service on your server.


'''Before you install the CommitCRM RMMServer'''
'''Before you install the CRM RMM Server'''
#Make sure to complete the Setup steps prior to installing the Windows Service.
#Make sure to complete the Setup steps prior to installing the Windows Service.
#Make sure to allow the CommitCRM RMMServer Service in your DEP settings.
#Make sure to allow the CRM RMM Server Service in your DEP settings.


This part of the installation should be performed on the server itself.
'''This part of the installation should be performed on the server itself.
When logged in to the server with a Window's Administrator account, open a command prompt window and enter the following command:


<Installation_DIR>\RMM\CommitRMMServer.exe -install


''Note: The <Insallation_Dir> must refer to a LOCAL server path (e.g. c:\ or D:\Software, etc.) and NOT to a shared network name/path.''  
<u>Automatic installation</u> &nbsp;&nbsp;&nbsp; &nbsp;    (requires RangerMSP 14 and up)
 
Log in to to your Server with a Window's Administrator account and run the installer from:
<blockquote>'''''<Installation_DIR>\RangerMSP\Utils\Install\InstallServerSideWindowsServices.exe'''''</blockquote>
<br>
 
OR &nbsp;&nbsp;- &nbsp;<br><br>
<u>Manual installation</u>
# Open a command prompt window: Right-click the command prompt icon and and choose 'Run As Adminsitrator'.
# Type the following command:<br><blockquote><tt> <Installation_DIR>\RangerMSP\RMM\CRMRMMServer.exe -install</tt></blockquote><u>Note</u>: The <Installation_Dir> must refer to a LOCAL server path (e.g. C:\ or D:\Software, etc.) and NOT to a shared network name/path.
# Wait for a success message to appear, indicating the service was installed successfully.
# Open the Windows Services Management windows from <i>Control Panel > Administration Tools > Services</i>.
# Verify that a Window's service called '''CRM RMM Server''' is now displayed the services list.
# If the service is not there, make sure again that you are running the command prompt Window using 'Run as Administrator' and try again.


A Window's service called CommitCRM RMMServer is now displayed in the system services management window (Control Panel > Administration Tools > Services). If the service is not displayed, make sure you are running the command prompt "As Administrator".
<br><br>
<br><br>
'''Start Service''':<br>
'''Start Service''':<br>
Using the Window's Services Management window start the service (right-click > Start). Make sure that it is set to start automatically (Startup type > Automatic) each time the server is restarted.
Using the Window's Services Management window start the service (right-click > Start). Make sure that it is set to start automatically with a ''Delayed Start'' ('''Startup type > Automatic Delayed Start''') each time the server is restarted.


<br>
<br>


==Download Sites and Devices Files==
==Download Sites and Devices Files==
In order for the Tickets arriving from Continuum to be created for the correct Account and Asset, all Continuum Sites should first be linked to the parallel CommitCRM Accounts, and Devices must be linked to Assets.
In order for the Tickets arriving from Continuum to be created for the correct Account and Asset, all Continuum Sites should first be linked to the parallel RangerMSP Accounts, and Devices must be linked to Assets.
<br><br>
<br><br>
Managing the links requires downloading the list of Sites and Devices from Continuum. This is done automatically by CommitCRM RMMServer once it is activated(*). Note that the Continuum Integration must NOT be enabled at the CommitCRM side yet at this point; only the service should be activated in order for it to download the Sites and Devices details.
Managing the links requires downloading the list of Sites and Devices from Continuum. This is done automatically by CRM RMM Server once it is activated(*). Note that the Continuum Integration must NOT be enabled at the RangerMSP side yet at this point; only the service should be activated in order for it to download the Sites and Devices details.
<br><br>
<br><br>
''(*)Important Note: <br>After the CommitCRM-Continuum Integration has been configured on Continuum Portal, it takes a few hours (up to 24 hours) until the new settings apply on the '''Continuum back-end'''. Note that even if all settings seem correct on Continuum side, you should '''wait a few hours''' until the CommitCRMServer service can connect and download data.''  
''(*)Important Note: <br>After the RangerMSP-Continuum Integration has been configured on Continuum Portal, it takes a few hours (up to 24 hours) until the new settings apply on the '''Continuum back-end'''. Note that even if all settings seem correct on Continuum side, you should '''wait a few hours''' until the 'CRM RMM Server' service can connect and download data.''  
<br>
<br>
<br>
<br>


Once the settings have been applied at Continuum Portal (which can take a few hours, see note above), and the CommitCRM RMMServer is activated, it tries to connect to Continuum and download the following files:
Once the settings have been applied at Continuum Portal (which can take a few hours, see note above), and the 'CRM RMM Server' is activated, it tries to connect to Continuum and download the following files:


* <server>\CommitCRM\Dbsys\ZenithSites_RMAZenithINFOTECHID1.cmt   
* <server>\RangerMSP\Dbsys\ZenithSites_RMAZenithINFOTECHID1.cmt   
* <server>\CommitCRM\Dbsys\ZenithDevices_RMAZenithINFOTECHID1.cmt
* <server>\RangerMSP\Dbsys\ZenithDevices_RMAZenithINFOTECHID1.cmt




Both files are used by the Continuum Links manager in CommitCRM client to link Continuum Sites and Devices to equivalent CommitCRM Accounts and Assets.
Both files are used by the Continuum Links manager in RangerMSP client to link Continuum Sites and Devices to equivalent RangerMSP Accounts and Assets.


Make sure both files exist before moving on to the next step which is Linking Accounts and Assets.
Make sure both files exist before moving on to the next step which is Linking Accounts and Assets.


'''Handling Errors'''<br>
'''Handling Errors'''<br>
In case CommitCRM RMMServer fails to download Sites and Devices details, the system will alert the user with a message when attempting to use the Continuum Links Manager (e.g. from Accounts > Tools > Open Continuum Links Manager). In such case, refer to the [[Continuum_Link#Troubleshooting|Troubleshooting]] section.
In case CRM RMM Server fails to download Sites and Devices details, the system will alert the user with a message when attempting to use the Continuum Links Manager (e.g. from Accounts > Tools > Open Continuum Links Manager). In such case, refer to the [[Continuum_Link#Troubleshooting|Troubleshooting]] section.


==Link Accounts and Sites==
==Link Accounts and Sites==
When a Ticket arrives from Continuum it is created in CommitCRM and automatically linked to the Account which is associated with the Site specified for the Ticket. In case the Site is not associated to any CommitCRM Account, a temporary Account is created and the Ticket is linked to it.<br>
When a Ticket arrives from Continuum it is created in RangerMSP and automatically linked to the Account which is associated with the Site specified for the Ticket. In case the Site is not associated to any RangerMSP Account, a temporary Account is created and the Ticket is linked to it.<br>
To avoid redundant temporary Accounts from being created, all Continuum Sites should first be linked to the equivalent CommitCRM Accounts. Only when all Accounts are associated to Sites, a System Administrator should enable the integration. See [[Continuum_Link#Enable_Continuum_Integration|Enable Continuum Integration]].
To avoid redundant temporary Accounts from being created, all Continuum Sites should first be linked to the equivalent RangerMSP Accounts. Only when all Accounts are associated to Sites, a System Administrator should enable the integration. See [[Continuum_Link#Enable_Continuum_Integration|Enable Continuum Integration]].


'''Link Accounts to Sites'''<br>
'''Link Accounts to Sites'''<br>
Line 137: Line 148:


==Enable Continuum Integration==
==Enable Continuum Integration==
Enabling Continuum Integration on the CommitCRM server (assuming the Continuum setup was already performed) will immediately start importing Tickets from Continuum into CommitCRM. Make sure to [[Continuum_Link#Link_Accounts_and_Assets|link your Continuum Sites with CommitCRM Accounts]] prior to enabling the integration on CommitCRM's side, to avoid duplicate Account creation. See more details in [[Continuum_Link#Link_Accounts_and_Assets|Link Accounts and Assets]].
Enabling Continuum Integration on the RangerMSP server (assuming the Continuum setup was already performed) will immediately start importing Tickets from Continuum into RangerMSP. Make sure to [[Continuum_Link#Link_Accounts_and_Assets|link your Continuum Sites with RangerMSP Accounts]] prior to enabling the integration on RangerMSP's side, to avoid duplicate Account creation. See more details in [[Continuum_Link#Link_Accounts_and_Assets|Link Accounts and Assets]].
<br>
<br>
To enable Continuum Integration on CommitCRM's side and start Tickets transfer from Continuum:
To enable Continuum Integration on RangerMSP's side and start Tickets transfer from Continuum:
 
# Open  <Installation_DIR>\RangerMSP\RMM\CmtZenithLink.ini
# Change the value for ''ProcessContinuumUpdatesQueue'' to Y (by default it's set to N in order to allow user first to perform links between Continuum sites/devices to RangerMSP).
# Restart 'CRM RMM Server' Service.
 
==Uninstall CRM RMM Server Service==
 
Should you ever need to uninstall the RMM Server service, follow this procedure:
 
# Open Command Prompt as administrator (e.g. right click the option and select the Run as Administrator).
# Navigate to the \RangerMSP\RMM folder.
# Then type: CRMRMMServer.exe -uninstall
# Wait for a while and you should receive a verification that the service was uninstalled successfully.


# Open  <Installation_DIR>\RMM\ CMTContinuumLink.ini
# Change the value for ''ProcessContinuumUpdatesQueue'' to Y (by default it's set to N in order to allow user first to perform links between Continuum sites/devices to CommitCRM).
# Restart CommitCRM RMMServer Service.
<br>
<br>


=Two-Ways Ticket Integration=
=Two-Ways Ticket Integration=
Only after installing the CommitRMMServer, linking between Accounts and Sites and enabling the Integration, will the Ticket integration come into action.
Only after installing the 'CRM RMM Server', linking between Accounts and Sites and enabling the Integration, will the Ticket integration come into action.




Once the integration is enabled, all Tickets are managed only from CommitCRM.
Once the integration is enabled, all Tickets are managed only from RangerMSP.




Line 156: Line 177:




* New Ticket in CommitCRM from Continuum: Tickets arriving from Continuum automatically create Tickets in CommitCRM.
* New Ticket in RangerMSP from Continuum: Tickets arriving from Continuum automatically create Tickets in RangerMSP.
* New Ticket in Continuum from CommitCRM: Tickets can be created in Continuum from CommitCRM.
* New Ticket in Continuum from RangerMSP: Tickets can be created in Continuum from RangerMSP.
* Reassign: Tickets can be assigned to Continuum’s NOC and Virtual Service Desk from CommitCRM.
* Reassign: Tickets can be assigned to Continuum’s NOC and Virtual Service Desk from RangerMSP.
* Update: Notes can be added to Tickets in CommitCRM and be sent to Continuum.
* Update: Notes can be added to Tickets in RangerMSP and be sent to Continuum.
* Close: Tickets can be closed from CommitCRM and will then be closed automatically in Continuum
* Close: Tickets can be closed from RangerMSP and will then be closed automatically in Continuum




Line 167: Line 188:


* Any updates to the Ticket details will not update the Ticket in Continuum.
* Any updates to the Ticket details will not update the Ticket in Continuum.
* Closing a Ticket in CommitCRM will close the Ticket in Continuum.
* Closing a Ticket in RangerMSP will close the Ticket in Continuum.
* Closing a Ticket in Continuum will not change the Status in CommitCRM.
* Closing a Ticket in Continuum will not change the Status in RangerMSP.




The following diagram demonstrated the work-flow when working with CommitCRM-Continuum integration:
The following diagram demonstrated the work-flow when working with RangerMSP-Continuum integration:


[[File:Continuum-workflow.png]]
[[File:Continuum-workflow.png]]
Line 180: Line 201:
==New Ticket==
==New Ticket==


New Tickets arriving from Continuum automatically create a Ticket in CommitCRM by the CommitCRM RMM server.
New Tickets arriving from Continuum automatically create a Ticket in RangerMSP by the CRM RMM server.




A standard (*) automatic Ticket creation process includes:
A standard (*) automatic Ticket creation process includes:


# Ticket arrives at the CommitCRM RMM Server.
# Ticket arrives at the CRM RMM Server.
# Ticket is created in CommitCRM.
# Ticket is created in RangerMSP.
# Ticket is linked to an Asset.
# Ticket is linked to an Asset.
# Ticket appears in CommitCRM Ticket Inbox.
# Ticket appears in RangerMSP Ticket Inbox.




Line 194: Line 215:




When a new Ticket is created in Continuum (by a user or from an Alerts), CommitCRM RMMServer pulls the new ticket details and creates the Ticket in CommitCRM.
When a new Ticket is created in Continuum (by a user or from an Alerts), CRM RMM Server pulls the new ticket details and creates the Ticket in RangerMSP.


The new Ticket details in CommitCRM include:
The new Ticket details in RangerMSP include:


# Ticket description taken from the Continuum Ticket description.
# Ticket description taken from the Continuum Ticket description.
Line 208: Line 229:
== New Ticket in Continuum ==
== New Ticket in Continuum ==


Once the CommitCRM-Continuum integration is enabled, all Tickets are managed only from CommitCRM. To create a Ticket in Continuum (e.g. assign work to the Continuum NOC team), Ticket should be created first in CommitCRM, and then transferred to Continuum.
Once the RangerMSP-Continuum integration is enabled, all Tickets are managed only from RangerMSP. To create a Ticket in Continuum (e.g. assign work to the Continuum NOC team), Ticket should be created first in RangerMSP, and then transferred to Continuum.




To create a Ticket in Continuum:
To create a Ticket in Continuum:


# Create the Ticket in CommitCRM and open the Ticket Window.
# Create the Ticket in RangerMSP and open the Ticket Window.
# Go to Tickets > Tools > Create/Update Ticket in Continuum.  
# Go to Tickets > Tools > Create/Update Ticket in Continuum.  
# The following window will open:
# The following window will open:
Line 221: Line 242:
# Choose the assignee. Ticket can be assigned to:
# Choose the assignee. Ticket can be assigned to:
#* NOC Team
#* NOC Team
#* CommitCRM
#* RangerMSP
#* Virtual Services Desk
#* Virtual Services Desk
# Add a Note if needed.
# Add a Note if needed.
Line 227: Line 248:




Note that the CommitCRM Ticket has to be linked to an Account that is linked to a Continuum site and Asset linked to a Device (optional)
Note that the RangerMSP Ticket has to be linked to an Account that is linked to a Continuum site and Asset linked to a Device (optional)


==Ticket Updates==
==Ticket Updates==
When working with the CommitCRM-Continuum Link, Tickets are managed only in CommitCRM. <br>
When working with the RangerMSP-Continuum Link, Tickets are managed only in RangerMSP. <br>


The following updates in Continuum are possible:
The following updates in Continuum are possible:
Line 242: Line 263:




While Tickets can be closed in Continuum, such an event does not affect the Ticket Status in CommitCRM.
While Tickets can be closed in Continuum, such an event does not affect the Ticket Status in RangerMSP.




Line 248: Line 269:
== Reassigning Tickets ==
== Reassigning Tickets ==


Once the CommitCRM-Continuum integration is enabled, all Tickets are managed only from CommitCRM. To reassign a Ticket in Continuum (e.g. assign work to the Continuum NOC team), it should be reassigned via CommitCRM.
Once the RangerMSP-Continuum integration is enabled, all Tickets are managed only from RangerMSP. To reassign a Ticket in Continuum (e.g. assign work to the Continuum NOC team), it should be reassigned via RangerMSP.




To reassign a Ticket in Continuum:
To reassign a Ticket in Continuum:


# Select the Ticket in CommitCRM.
# Select the Ticket in RangerMSP.
# Go to Tickets > Tools > Create/Update Ticket in Continuum.  
# Go to Tickets > Tools > Create/Update Ticket in Continuum.  
# The follow window will open:
# The follow window will open:
[[File:Continuum_reassign_ticket.png‎]]
# Choose the assignee. Ticket can be assigned to:
# Choose the assignee. Ticket can be assigned to:
#* Keep current assignment.
#* Keep current assignment.
#* NOC Team
#* RangerMSP
#* Virtual Services Desk
#* Virtual Services Desk
# Add a Note if needed.
# Add a Note if needed.
Line 264: Line 288:




Note that the CommitCRM Ticket has to be linked to an Account that is linked to a Continuum site and Asset linked to a Device (optional)
Note that the RangerMSP Ticket has to be linked to an Account that is linked to a Continuum site and Asset linked to a Device (optional)
 
 


== Receiving Tickets Back from Continuum ==
== Receiving Tickets Back from Continuum ==


Once the CommitCRM-Continuum integration is enabled, all Tickets are managed only from CommitCRM. However, it is possible to assign work to the Continuum NOC team) via CommitCRM.  
Once the RangerMSP-Continuum integration is enabled, all Tickets are managed only from RangerMSP. However, it is possible to assign work to the Continuum NOC team) via RangerMSP.  


When a Ticket is assigned to NOC Team or Virtual Service Desk Team they can return the Ticket to CommitCRM.
When a Ticket is assigned to NOC Team or Virtual Service Desk Team they can return the Ticket to RangerMSP.




Line 278: Line 300:


# When the NOC Team or Virtual Service Desk Team resolve the problem and updated Ticket status to "Work completed"  
# When the NOC Team or Virtual Service Desk Team resolve the problem and updated Ticket status to "Work completed"  
# When the NOC Team need approval or additional information from the Partner they send the ticket back to Partner (i.e. CommitCRM) with status="Approval Required" or "Info Needed".
# When the NOC Team need approval or additional information from the Partner they send the ticket back to Partner (i.e. RangerMSP) with status="Approval Required" or "Info Needed".




A Ticket that is returned to CommitCRM:
A Ticket that is returned to RangerMSP:


# Ticket goes into Inbox
# Ticket goes into Inbox
Line 290: Line 312:
== Adding Notes ==
== Adding Notes ==


Adding Notes to a Ticket will update the Note in Continuum and will add an Audit entry for this action in CommitCRM. The Note can be viewed in CommitCRM in the History area of the Ticket.
Adding Notes to a Ticket will update the Note in Continuum and will add an Audit entry for this action in RangerMSP. The Note can be viewed in RangerMSP in the History area of the Ticket.




To Add a Note in Continuum:
To Add a Note in Continuum:


# Select the Ticket in CommitCRM.
# Select the Ticket in RangerMSP.
# Go to Tickets > Tools > Create/Update Ticket in Continuum.  
# Go to Tickets > Tools > Create/Update Ticket in Continuum.  
# The follow window will open:
# The follow window will open:
Line 305: Line 327:
==Closing Tickets==
==Closing Tickets==


When working with the CommitCRM-Continuum Link, Tickets are managed only in CommitCRM. Whenever a Ticket is Completed in CommitCRM it is also being automatically closed in Continuum.
When working with the RangerMSP-Continuum Link, Tickets are managed only in RangerMSP. Whenever a Ticket is Completed in RangerMSP it is also being automatically closed in Continuum.




To close a Ticket:
To close a Ticket:


# Open the Ticket in CommitCRM.
# Open the Ticket in RangerMSP.
# Change the Ticket status to Completed (can be done from the toolbar, by dragging to a status or by changing the status manually).
# Change the Ticket status to Completed (can be done from the toolbar, by dragging to a status or by changing the status manually).
# Ticket is automatically closed in Continuum.
# Ticket is automatically closed in Continuum.




Note that Tickets that are being closed via Continuum, will not affect the Ticket Status in CommitCRM.
Note that Tickets that are being closed via Continuum, will not affect the Ticket Status in RangerMSP.


=Managing Continuum Links=
=Managing Continuum Links=
In order for Tickets arriving from Continuum to be opened under the correct Account and Asset, you must create an association between Sites and Devices in Continuum to Accounts and Assets in CommitCRM.
In order for Tickets arriving from Continuum to be opened under the correct Account and Asset, you must create an association between Sites and Devices in Continuum to Accounts and Assets in RangerMSP.


Creating the links is done using the ''Continuum Links Manager'' Window via CommitCRM.
Creating the links is done using the ''Continuum Links Manager'' Window via RangerMSP.


''Note: CommitCRM RMMServer service must first be installed in order for the Continuum Sites and Devices to be downloaded to the CommitCRM server. See more details in [[Continuum_Link#Download_Sites_and_Devices_Files|Download Sites and Devices Files]].''  
''Note: CRM RMM Server service must first be installed in order for the Continuum Sites and Devices to be downloaded to the RangerMSP server. See more details in [[Continuum_Link#Download_Sites_and_Devices_Files|Download Sites and Devices Files]].''  


==Link Account to Site==
==Link Account to Site==
In order for Tickets arriving from Continuum to be opened under the correct Account, you must create an association between sites in Continuum to Accounts in CommitCRM, or create an Account in CommitCRM for this Site.
In order for Tickets arriving from Continuum to be opened under the correct Account, you must create an association between sites in Continuum to Accounts in RangerMSP, or create an Account in RangerMSP for this Site.


Note that multiple Sites in Continuum can be linked to the same Account in CommitCRM, since the Sites may represent several physical sites for the same client, thus represented in the same CommitCRM Account.
Note that multiple Sites in Continuum can be linked to the same Account in RangerMSP, since the Sites may represent several physical sites for the same client, thus represented in the same RangerMSP Account.


Use the Continuum Links Manager Window to create the association:
Use the Continuum Links Manager Window to create the association:
Line 334: Line 356:
# In the Wizard which opens you can find a list of available un-linked sites from Continuum. This list gets updated every hour. In case you receive a message about a missing file, this means the initial setup hasn't been completed yet. For more details refer to [[Continuum_Link#Download_Sites_and_Devices_Files|Download Sites and Devices Files]].
# In the Wizard which opens you can find a list of available un-linked sites from Continuum. This list gets updated every hour. In case you receive a message about a missing file, this means the initial setup hasn't been completed yet. For more details refer to [[Continuum_Link#Download_Sites_and_Devices_Files|Download Sites and Devices Files]].
# Select the Site you want to link, and click Next. The following screen appears: <br>[[File:Continuum-link-account-wizard.png‎]]<br>
# Select the Site you want to link, and click Next. The following screen appears: <br>[[File:Continuum-link-account-wizard.png‎]]<br>
# In above screen you should choose the CommitCRM Account to be linked to the external record:
# In above screen you should choose the RangerMSP Account to be linked to the external record:
## Find the parallel Account(**) using the search options:
## Find the parallel Account(**) using the search options:
###Search for Account by keyword/s.
###Search for Account by keyword/s.
###See Account list recommended by the system based on the Site name.
###See Account list recommended by the system based on the Site name.
###Once you have chosen the Account, click Link to Account.
###Once you have chosen the Account, click Link to Account.
##OR create a new Account based on the selected Site details(*).<br>''(*) Note: When creating a new Account in CommitCRM based on the Site from Continuum, only the Site name is copied to CommitCRM. No other details are transferred.<br>(**) Note: that multiple Sites in Continuum can be linked to the same Account in CommitCRM, since the Sites may represent several physical sites for the same client, thus represented in the same CommitCRM Account.
##OR create a new Account based on the selected Site details(*).<br>''(*) Note: When creating a new Account in RangerMSP based on the Site from Continuum, only the Site name is copied to RangerMSP. No other details are transferred.<br>(**) Note: that multiple Sites in Continuum can be linked to the same Account in RangerMSP, since the Sites may represent several physical sites for the same client, thus represented in the same RangerMSP Account.
''
''
<br><br>
<br><br>
Line 348: Line 370:
==Unlink Account From Site==
==Unlink Account From Site==


Accounts in CommitCRM must be linked to Sites in Continuum in order for Tickets to be created under the correct Account. If you want to cancel a link between an Account and a Site, you can use two methods:
Accounts in RangerMSP must be linked to Sites in Continuum in order for Tickets to be created under the correct Account. If you want to cancel a link between an Account and a Site, you can use two methods:


Use the Continuum Account Link Manager (recommended, this way you can see the linked Site details before removing the link):
Use the Continuum Account Link Manager (recommended, this way you can see the linked Site details before removing the link):
Line 361: Line 383:


# In the Accounts window, find the Account you want to unlink.
# In the Accounts window, find the Account you want to unlink.
# Go to ''Accounts > Tools > Remove Link between CommitCRM Record and Continuum''.
# Go to ''Accounts > Tools > Remove Link between RangerMSP Record and Continuum''.
# If the Account is linked to more than one site, ALL links will be removed.
# If the Account is linked to more than one site, ALL links will be removed.


Line 368: Line 390:


==Link Asset to Device==
==Link Asset to Device==
In order for Tickets arriving from Continuum to be linked to the correct Asset, you must create an association between Devices in Continuum to Assets in CommitCRM, or create an Asset in CommitCRM for this Device.
In order for Tickets arriving from Continuum to be linked to the correct Asset, you must create an association between Devices in Continuum to Assets in RangerMSP, or create an Asset in RangerMSP for this Device.


Use the Continuum Links Manager Window to create the association:
Use the Continuum Links Manager Window to create the association:
Line 382: Line 404:
##OR create a new Asset based on the Device details(*).  
##OR create a new Asset based on the Device details(*).  


''(*) Note: When creating a new Asset in CommitCRM based on the Device from Continuum, the following fields are copied: Device Name, Serial Number and Manufacturer. Other technical device details are copied to the Asset Note field.''
''(*) Note: When creating a new Asset in RangerMSP based on the Device from Continuum, the following fields are copied: Device Name, Serial Number and Manufacturer. Other technical device details are copied to the Asset Note field.''
<br><br>
<br><br>
At this point the Asset and Device are linked.
At this point the Asset and Device are linked.
Line 390: Line 412:
==Unlink Asset From Device==
==Unlink Asset From Device==


Assets in CommitCRM must be linked to Sites in Continuum in order for Tickets to be linked to the correct Asset. If you want to cancel a link between an Asset and a Device, you can use two methods:
Assets in RangerMSP must be linked to Sites in Continuum in order for Tickets to be linked to the correct Asset. If you want to cancel a link between an Asset and a Device, you can use two methods:


Use the Continuum Links Manager (recommended! this way you can see the linked Site details before removing the link):
Use the Continuum Links Manager (recommended! this way you can see the linked Site details before removing the link):
Line 396: Line 418:
# In the Asset Window, go to Assets > Tools > Continuum Links Manager.
# In the Asset Window, go to Assets > Tools > Continuum Links Manager.
# In the Window which opens hit the ''Linked External Records'' tab to find Assets which are already linked.
# In the Window which opens hit the ''Linked External Records'' tab to find Assets which are already linked.
# This tab displays a list of linked Assets in CommitCRM and displays the linked Device details in the bottom pane. This list gets updated every hour.
# This tab displays a list of linked Assets in RangerMSP and displays the linked Device details in the bottom pane. This list gets updated every hour.
# Select the Asset you want to unlink, and click Remove Link.
# Select the Asset you want to unlink, and click Remove Link.


Line 402: Line 424:


# In the Assets window, find the Asset you want to unlink.
# In the Assets window, find the Asset you want to unlink.
# Go to ''Assets > Tools > Remove Link between CommitCRM record and Continuum''.
# Go to ''Assets > Tools > Remove Link between RangerMSP record and Continuum''.




=Ticket Creation – Special Cases=
=Ticket Creation – Special Cases=
In case the Site or Device is not linked to the equivalent Account and Asset in CommitCRM, the Ticket will still be created, and the missing entity will be handled by the system in the following manner:<br>
In case the Site or Device is not linked to the equivalent Account and Asset in RangerMSP, the Ticket will still be created, and the missing entity will be handled by the system in the following manner:<br>
[[File:Zenith_Integration_Full_Flow.png]]
[[File:Continuum_Integration_Full_Flow.png]]




==Ticket from Unknown Site==
==Ticket from Unknown Site==


In case a Ticket arrives from Continuum for an anonymous Site which is not linked to any Account in CommitCRM, a new Account is automatically created with the name:
In case a Ticket arrives from Continuum for an anonymous Site which is not linked to any Account in RangerMSP, a new Account is automatically created with the name:


[Continuum AUTO CREATED] + Site name in Continuum.
[Continuum AUTO CREATED] + Site name in Continuum.
Line 420: Line 442:
[Continuum AUTO CREATED] + ACME company
[Continuum AUTO CREATED] + ACME company


If such an Account already exists in CommitCRM (from previous tickets), the new Account will still be created, so multiple Accounts with the same name may exist in the system.
If such an Account already exists in RangerMSP (from previous tickets), the new Account will still be created, so multiple Accounts with the same name may exist in the system.


The Ticket is then created and linked to this automatically created Account. New Continuum Tickets will also be linked to this Account as long as a permanent Account is not created for this Site.
The Ticket is then created and linked to this automatically created Account. New Continuum Tickets will also be linked to this Account as long as a permanent Account is not created for this Site.


When technicians find this Ticket, they should:
When technicians find this Ticket, they should:
# If a "real" Account already exists for this site, merge both Accounts to the master CommitCRM account for this site.
# If a "real" Account already exists for this site, merge both Accounts to the master RangerMSP account for this site.
# If this site is new and does not exist in CommitCRM, make this the master Account for this site, and rename it to its real name.
# If this site is new and does not exist in RangerMSP, make this the master Account for this site, and rename it to its real name.
# After the merge, all links to Continuum Sites will be merged into the Master Account so there is no need to re-link the Account to the Site.
# After the merge, all links to Continuum Sites will be merged into the Master Account so there is no need to re-link the Account to the Site.


Line 433: Line 455:


==Device Not Linked to Asset==
==Device Not Linked to Asset==
In case a Ticket arrives from Continuum and is linked to a Device which is not linked to any Asset in CommitCRM:
In case a Ticket arrives from Continuum and is linked to a Device which is not linked to any Asset in RangerMSP:
# The Ticket is created and linked to Account.
# The Ticket is created and linked to Account.
# Device details are filled in the Ticket Description.
# Device details are filled in the Ticket Description.


==Tickets without a Site==
==Tickets without a Site==
In Continuum, manual Tickets can be unrelated to any specific customer site (e.g. a support Ticket against Continuum NOC Support). In this case, the Ticket which arrives at CommitCRM is not linked to a Site.
In Continuum, manual Tickets can be unrelated to any specific customer site (e.g. a support Ticket against Continuum NOC Support). In this case, the Ticket which arrives at RangerMSP is not linked to a Site.


In case the Ticket is not linked to a Site, the Ticket is created and linked to the your own business’ Account, i.e. the first Account created in CommitCRM which represents your own business.
In case the Ticket is not linked to a Site, the Ticket is created and linked to the your own business’ Account, i.e. the first Account created in RangerMSP which represents your own business.


=Troubleshooting=
=Troubleshooting=
In case CommitCRM RMMServer fails to download Sites and Devices details, the system will show the user a message when opening the Continuum Links Manager (e.g. from Accounts > Tools > Open Continuum Links Manager).
In case CRM RMM Server fails to download Sites and Devices details, the system will show the user a message when opening the Continuum Links Manager (e.g. from Accounts > Tools > Open Continuum Links Manager).


First, make sure all setup and installation steps were performed properly:
First, make sure all setup and installation steps were performed properly:
# Initialize Continuum PSG.
# Initialize Continuum PSG.
# Install CommitCRM RMMServer.
# Install CRM RMM Server.
# Validate CommitCRM RMMServer downloads Continuum Sites and Devices to the CommitCRM server.
# Validate CRM RMM Server downloads Continuum Sites and Devices to the RangerMSP server.
<br>
<br>
See full details in [[Continuum_Link#CommitCRM_Setup|CommitCRM Setup]].
See full details in [[Continuum_Link#RangerMSP_Setup|RangerMSP Setup]].


<br>
<br>
If all steps were completed, it is possible the CommitCRM RMMServer has failed to pull the files due to an error. To check this please log into CommitCRM client and from the menu select Tools > System Tools > Advanced > Check for Server Side Error Reports.
If all steps were completed, it is possible the CRM RMM Server has failed to pull the files due to an error. To check this please log into RangerMSP client and from the menu select Tools > System Tools > Advanced > Check for Server Side Error Reports.


If no error file exists at this location, please contact CommitCRM Support for further assistance.
If no error file exists at this location, please contact RangerMSP Support for further assistance.


<br>
<br>
After the initial setup, to start working with the Continuum Link, you should complete the following steps:
After the initial setup, to start working with the Continuum Link, you should complete the following steps:
# Link Accounts and Assets in CommitCRM to Sites in and Devices Continuum.
# Link Accounts and Assets in RangerMSP to Sites in and Devices Continuum.
# Enable Continuum Integration.
# Enable Continuum Integration.


See full details in [[Continuum_Link#CommitCRM_Setup|CommitCRM Setup]].
See full details in [[Continuum_Link#RangerMSP_Setup|RangerMSP Setup]].


=CommitCRM Privileges=
=RangerMSP Privileges=
In order for a user to manage Continuum Links (with Sites and Devices) the user should have Continuum Integration Privileges.
In order for a user to manage Continuum Links (with Sites and Devices) the user should have Continuum Integration Privileges.



Latest revision as of 08:04, 8 July 2020

Introduction

The RangerMSP-Continuum Integration automatically creates tickets in RangerMSP from alerts and service tickets generated by the Continuum system, or from tickets created manually by the Continuum NOC. Users can then close the Ticket in RangerMSP, and it will be closed in Continuum.

The RangerMSP integration with Continuum includes:

  1. Two-ways Ticket Integration.
    • Continuum’s Tickets create Tickets in RangerMSP.
    • Closing a Ticket in RangerMSP closes the Ticket in Continuum.
    • RangerMSP Tickets can be assigned to Continuum’s NOC / Service Desk.
    • New Tickets in Continuum can be created from RangerMSP’s Tickets
    • Comments for Tickets can be sent from RangerMSP to Continuum.
  2. The ability to link Account to Site in Continuum or create Account from Site.
  3. The ability to link Asset to Device in Continuum or create Asset from Device.

Once the RangerMSP-Continuum Integration has been configured, Continuum Ticketing System is disabled and Ticket management is performed solely in RangerMSP.

Ticket can still be viewed in Continuum (read-only); however, the master Ticket is managed in RangerMSP. When closing a Ticket in RangerMSP it is closed in Continuum. When closing a Ticket in Continuum it adds a History Note to the Ticket in RangerMSP, however, the Ticket stays open.


Technical Note
The integration is based on a new Service running on your RangerMSP server (called CRM RMM Server Service), which accepts all alerts and Tickets from Continuum and creates the Ticket in RangerMSP.


Continuum Settings

This section describes the Setup steps required in the Continuum Portal in order to start working with RangerMSP as your PSA system in Continuum.

Important Notes:

  1. Once the RangerMSP-Continuum Integration has been configured on Continuum Portal, it takes a few hours (up to 24 hours) until the new settings apply on the Continuum back-end. Note that even if all settings seem correct on Continuum side, you should wait a few hours until the RangerMSPServer service can connect and download data.
  2. Once RangerMSP is activated as your PSA in Continuum Portal, Continuum Ticketing System is disabled and Ticket management is performed solely in RangerMSP.
  3. Since all Ticket Management is disabled in Continuum, Continuum email alerts for Tickets will also be disabled, and you will no longer get email alerts for new Tickets from Continuum Portal. In case you want to receive email alerts for new Tickets (arriving from Continuum Portal) via RangerMSP, you may consider using RangerMSP Alerts Server module, which sends email alerts for new updates in the RangerMSP system. See more details in RangerMSP Alerts Server.


To allow CRM RMM service to connect with Continuum and sync with it, a Continuum Partner Security code (also known as PSG) is required.

To setup Continuum PSG:

  1. Login to the Continuum Portal with Admin account and go to Admin.
  2. The ITS Portal Setup window is displayed. Click My Company > PSA integration in the left column.


  3. Click the link “RangerMSP” option.


  4. Copy the Security Code on the screen and click Enable. This will lock the Code to your account. Use this Code to complete the configuration in RangerMSP. See RangerMSP Setup.
  5. Now on the same page click Activate. You will receive message “RangerMSP Activated Successfully”.


  6. After receiving the "Activated successfully" message, it takes a few hours until the new settings apply on the Continuum back-end. Note that even if all settings seem correct on Continuum side, you should wait a few hours until the RangerMSPServer service can connect and download data.


For more details on Continuum Setting, click to review the Continuum configuration guide


RangerMSP Setup

Please make sure to enable the integration with RangerMSP on the Continuum side (see Continuum Settings) before you proceed with the RangerMSP side setup below.

To set up RangerMSP to work with Continuum, the following steps are required:

  1. Backup RangerMSP Database.
  2. Initialize Continuum PSG.
  3. Install CRM RMM Server.
  4. Validate CRM RMM Server downloads Continuum Sites and Devices to the RangerMSP server.
  5. Link Accounts and Assets in RangerMSP(*) to Sites in and Devices Continuum.
  6. Enable Continuum Integration.


* Note:
The full integration with Continuum on the RangerMSP side will be disabled by default until you activate it explicitly, and Tickets will not be transferred to RangerMSP until then. This is to make sure users first link Continuum Sites to RangerMSP Accounts to avoid many duplicate Accounts which may be created if Tickets arrive before the links take place. Once all Accounts are linked, users should enable the integration, see Enabling Continuum Integration .

Backup RangerMSP Database

Before starting to work with the Continuum integration, make sure to backup your RangerMSP database.

The integration includes linking and importing sites and devices into RangerMSP and it is strongly recommended to backup your system before starting to work with it.

Initialize Continuum PSG

After you finish setting up the Security Code (PSG) at the Continuum Portal (see Continuum Settings), you can move on to the next step and enter the PSG into RangerMSP settings.

To initialize the PSG in RangerMSP:

  • Open <Installation_DIR>\RangerMSP\RMM\CMTZenithLink.ini
  • Copy the Security Code value from Continuum PSA Settings window as described above in Continuum Settings, and paste your Continuum Partner Security Code as the value for token PSG:
PSG=<Your-Continuum-Security-Code>
  • Save your changes.


Install CRM RMM Server Service

After you finish setting up all of the required settings (see Initialize Continuum PSG), you can move on to the next step and install the CRM RMM Server service.

The 'CRM RMM Server' runs as a Windows Service on your server.

Before you install the CRM RMM Server

  1. Make sure to complete the Setup steps prior to installing the Windows Service.
  2. Make sure to allow the CRM RMM Server Service in your DEP settings.

This part of the installation should be performed on the server itself.


Automatic installation       (requires RangerMSP 14 and up)

Log in to to your Server with a Window's Administrator account and run the installer from:

<Installation_DIR>\RangerMSP\Utils\Install\InstallServerSideWindowsServices.exe


OR   -  

Manual installation

  1. Open a command prompt window: Right-click the command prompt icon and and choose 'Run As Adminsitrator'.
  2. Type the following command:

    <Installation_DIR>\RangerMSP\RMM\CRMRMMServer.exe -install

    Note: The <Installation_Dir> must refer to a LOCAL server path (e.g. C:\ or D:\Software, etc.) and NOT to a shared network name/path.
  3. Wait for a success message to appear, indicating the service was installed successfully.
  4. Open the Windows Services Management windows from Control Panel > Administration Tools > Services.
  5. Verify that a Window's service called CRM RMM Server is now displayed the services list.
  6. If the service is not there, make sure again that you are running the command prompt Window using 'Run as Administrator' and try again.



Start Service:
Using the Window's Services Management window start the service (right-click > Start). Make sure that it is set to start automatically with a Delayed Start (Startup type > Automatic Delayed Start) each time the server is restarted.


Download Sites and Devices Files

In order for the Tickets arriving from Continuum to be created for the correct Account and Asset, all Continuum Sites should first be linked to the parallel RangerMSP Accounts, and Devices must be linked to Assets.

Managing the links requires downloading the list of Sites and Devices from Continuum. This is done automatically by CRM RMM Server once it is activated(*). Note that the Continuum Integration must NOT be enabled at the RangerMSP side yet at this point; only the service should be activated in order for it to download the Sites and Devices details.

(*)Important Note:
After the RangerMSP-Continuum Integration has been configured on Continuum Portal, it takes a few hours (up to 24 hours) until the new settings apply on the Continuum back-end. Note that even if all settings seem correct on Continuum side, you should wait a few hours until the 'CRM RMM Server' service can connect and download data.


Once the settings have been applied at Continuum Portal (which can take a few hours, see note above), and the 'CRM RMM Server' is activated, it tries to connect to Continuum and download the following files:

  • <server>\RangerMSP\Dbsys\ZenithSites_RMAZenithINFOTECHID1.cmt
  • <server>\RangerMSP\Dbsys\ZenithDevices_RMAZenithINFOTECHID1.cmt


Both files are used by the Continuum Links manager in RangerMSP client to link Continuum Sites and Devices to equivalent RangerMSP Accounts and Assets.

Make sure both files exist before moving on to the next step which is Linking Accounts and Assets.

Handling Errors
In case CRM RMM Server fails to download Sites and Devices details, the system will alert the user with a message when attempting to use the Continuum Links Manager (e.g. from Accounts > Tools > Open Continuum Links Manager). In such case, refer to the Troubleshooting section.

Link Accounts and Sites

When a Ticket arrives from Continuum it is created in RangerMSP and automatically linked to the Account which is associated with the Site specified for the Ticket. In case the Site is not associated to any RangerMSP Account, a temporary Account is created and the Ticket is linked to it.
To avoid redundant temporary Accounts from being created, all Continuum Sites should first be linked to the equivalent RangerMSP Accounts. Only when all Accounts are associated to Sites, a System Administrator should enable the integration. See Enable Continuum Integration.

Link Accounts to Sites
Before starting to work with the Continuum Integration, an Administrator must first link all Accounts to the equivalent Sites in Continuum. This step is required in order for Tickets arriving from Continuum to be opened under the correct Account.

To Link Accounts to Sites in Continuum see Link Account to Site.

Link Assets to Devices
Before starting to work with the Continuum Integration, an Administrator must first link all and Assets to the equivalent Devices in Continuum. This step is required in order for Tickets arriving from Continuum to be opened under the correct Asset.

To Link Assets to Devices in Continuum see Link Asset to Device.

Enable Continuum Integration

Enabling Continuum Integration on the RangerMSP server (assuming the Continuum setup was already performed) will immediately start importing Tickets from Continuum into RangerMSP. Make sure to link your Continuum Sites with RangerMSP Accounts prior to enabling the integration on RangerMSP's side, to avoid duplicate Account creation. See more details in Link Accounts and Assets.
To enable Continuum Integration on RangerMSP's side and start Tickets transfer from Continuum:

  1. Open <Installation_DIR>\RangerMSP\RMM\CmtZenithLink.ini
  2. Change the value for ProcessContinuumUpdatesQueue to Y (by default it's set to N in order to allow user first to perform links between Continuum sites/devices to RangerMSP).
  3. Restart 'CRM RMM Server' Service.

Uninstall CRM RMM Server Service

Should you ever need to uninstall the RMM Server service, follow this procedure:

  1. Open Command Prompt as administrator (e.g. right click the option and select the Run as Administrator).
  2. Navigate to the \RangerMSP\RMM folder.
  3. Then type: CRMRMMServer.exe -uninstall
  4. Wait for a while and you should receive a verification that the service was uninstalled successfully.


Two-Ways Ticket Integration

Only after installing the 'CRM RMM Server', linking between Accounts and Sites and enabling the Integration, will the Ticket integration come into action.


Once the integration is enabled, all Tickets are managed only from RangerMSP.


The Ticket integration includes:


  • New Ticket in RangerMSP from Continuum: Tickets arriving from Continuum automatically create Tickets in RangerMSP.
  • New Ticket in Continuum from RangerMSP: Tickets can be created in Continuum from RangerMSP.
  • Reassign: Tickets can be assigned to Continuum’s NOC and Virtual Service Desk from RangerMSP.
  • Update: Notes can be added to Tickets in RangerMSP and be sent to Continuum.
  • Close: Tickets can be closed from RangerMSP and will then be closed automatically in Continuum


Notes:


  • Any updates to the Ticket details will not update the Ticket in Continuum.
  • Closing a Ticket in RangerMSP will close the Ticket in Continuum.
  • Closing a Ticket in Continuum will not change the Status in RangerMSP.


The following diagram demonstrated the work-flow when working with RangerMSP-Continuum integration:

See more details on Ticket updates in the sections below.


New Ticket

New Tickets arriving from Continuum automatically create a Ticket in RangerMSP by the CRM RMM server.


A standard (*) automatic Ticket creation process includes:

  1. Ticket arrives at the CRM RMM Server.
  2. Ticket is created in RangerMSP.
  3. Ticket is linked to an Asset.
  4. Ticket appears in RangerMSP Ticket Inbox.


(*) See how the system handles non-standard scenarios in Ticket Creation Special Cases.


When a new Ticket is created in Continuum (by a user or from an Alerts), CRM RMM Server pulls the new ticket details and creates the Ticket in RangerMSP.

The new Ticket details in RangerMSP include:

  1. Ticket description taken from the Continuum Ticket description.
  2. Ticket is assigned to the Account manager for this Account (if defined). Otherwise the Ticket Manager is taken from Default Ticket Manager defined in Tools > Options > Tickets (Admin) > Default Manager.
  3. History Note is automatically added to the Ticket with the creation date and time from Continuum.
  4. Ticket is linked to the relevant Asset. If the system cannot determine the Asset, the Continuum Device details are added as a note to the Ticket. See more details in Device Not Linked to Asset.


After the Ticket is created it is automatically added to the Tickets Inbox.

New Ticket in Continuum

Once the RangerMSP-Continuum integration is enabled, all Tickets are managed only from RangerMSP. To create a Ticket in Continuum (e.g. assign work to the Continuum NOC team), Ticket should be created first in RangerMSP, and then transferred to Continuum.


To create a Ticket in Continuum:

  1. Create the Ticket in RangerMSP and open the Ticket Window.
  2. Go to Tickets > Tools > Create/Update Ticket in Continuum.
  3. The following window will open:

  1. Choose the assignee. Ticket can be assigned to:
    • NOC Team
    • RangerMSP
    • Virtual Services Desk
  2. Add a Note if needed.
  3. Click OK to create the Ticket in Continuum.


Note that the RangerMSP Ticket has to be linked to an Account that is linked to a Continuum site and Asset linked to a Device (optional)

Ticket Updates

When working with the RangerMSP-Continuum Link, Tickets are managed only in RangerMSP.

The following updates in Continuum are possible:



Note that Updating Ticket details (such as Description, assigned technician or any other details) will not affect the Ticket in Continuum.


While Tickets can be closed in Continuum, such an event does not affect the Ticket Status in RangerMSP.


Reassigning Tickets

Once the RangerMSP-Continuum integration is enabled, all Tickets are managed only from RangerMSP. To reassign a Ticket in Continuum (e.g. assign work to the Continuum NOC team), it should be reassigned via RangerMSP.


To reassign a Ticket in Continuum:

  1. Select the Ticket in RangerMSP.
  2. Go to Tickets > Tools > Create/Update Ticket in Continuum.
  3. The follow window will open:

  1. Choose the assignee. Ticket can be assigned to:
    • Keep current assignment.
    • RangerMSP
    • Virtual Services Desk
  2. Add a Note if needed.
  3. Click OK to reassign the Ticket in Continuum.


Note that the RangerMSP Ticket has to be linked to an Account that is linked to a Continuum site and Asset linked to a Device (optional)

Receiving Tickets Back from Continuum

Once the RangerMSP-Continuum integration is enabled, all Tickets are managed only from RangerMSP. However, it is possible to assign work to the Continuum NOC team) via RangerMSP.

When a Ticket is assigned to NOC Team or Virtual Service Desk Team they can return the Ticket to RangerMSP.


For example:

  1. When the NOC Team or Virtual Service Desk Team resolve the problem and updated Ticket status to "Work completed"
  2. When the NOC Team need approval or additional information from the Partner they send the ticket back to Partner (i.e. RangerMSP) with status="Approval Required" or "Info Needed".


A Ticket that is returned to RangerMSP:

  1. Ticket goes into Inbox
  2. Update is logged in the Ticket's History as an audit entry.


Adding Notes

Adding Notes to a Ticket will update the Note in Continuum and will add an Audit entry for this action in RangerMSP. The Note can be viewed in RangerMSP in the History area of the Ticket.


To Add a Note in Continuum:

  1. Select the Ticket in RangerMSP.
  2. Go to Tickets > Tools > Create/Update Ticket in Continuum.
  3. The follow window will open:
  4. Update the Note.
  5. Click OK to add notes to the Ticket in Continuum.


Closing Tickets

When working with the RangerMSP-Continuum Link, Tickets are managed only in RangerMSP. Whenever a Ticket is Completed in RangerMSP it is also being automatically closed in Continuum.


To close a Ticket:

  1. Open the Ticket in RangerMSP.
  2. Change the Ticket status to Completed (can be done from the toolbar, by dragging to a status or by changing the status manually).
  3. Ticket is automatically closed in Continuum.


Note that Tickets that are being closed via Continuum, will not affect the Ticket Status in RangerMSP.

Managing Continuum Links

In order for Tickets arriving from Continuum to be opened under the correct Account and Asset, you must create an association between Sites and Devices in Continuum to Accounts and Assets in RangerMSP.

Creating the links is done using the Continuum Links Manager Window via RangerMSP.

Note: CRM RMM Server service must first be installed in order for the Continuum Sites and Devices to be downloaded to the RangerMSP server. See more details in Download Sites and Devices Files.

Link Account to Site

In order for Tickets arriving from Continuum to be opened under the correct Account, you must create an association between sites in Continuum to Accounts in RangerMSP, or create an Account in RangerMSP for this Site.

Note that multiple Sites in Continuum can be linked to the same Account in RangerMSP, since the Sites may represent several physical sites for the same client, thus represented in the same RangerMSP Account.

Use the Continuum Links Manager Window to create the association:

  1. In the Accounts Window, go to Accounts > Tools > Continuum Links Manager.
  2. In the Wizard which opens you can find a list of available un-linked sites from Continuum. This list gets updated every hour. In case you receive a message about a missing file, this means the initial setup hasn't been completed yet. For more details refer to Download Sites and Devices Files.
  3. Select the Site you want to link, and click Next. The following screen appears:

  4. In above screen you should choose the RangerMSP Account to be linked to the external record:
    1. Find the parallel Account(**) using the search options:
      1. Search for Account by keyword/s.
      2. See Account list recommended by the system based on the Site name.
      3. Once you have chosen the Account, click Link to Account.
    2. OR create a new Account based on the selected Site details(*).
      (*) Note: When creating a new Account in RangerMSP based on the Site from Continuum, only the Site name is copied to RangerMSP. No other details are transferred.
      (**) Note: that multiple Sites in Continuum can be linked to the same Account in RangerMSP, since the Sites may represent several physical sites for the same client, thus represented in the same RangerMSP Account.



At this point the Account and Site are linked.

To cancel this link between the Account and Site, hit the Linked Accounts tab to find the Account and remove the link. See Unlink Account From Site.

Unlink Account From Site

Accounts in RangerMSP must be linked to Sites in Continuum in order for Tickets to be created under the correct Account. If you want to cancel a link between an Account and a Site, you can use two methods:

Use the Continuum Account Link Manager (recommended, this way you can see the linked Site details before removing the link):

  1. In the Accounts Window, go to Accounts > Tools > Continuum Links Manager.
  2. In the Window which opens hit the Linked Records tab to find Accounts which are already linked.
  3. This tab displays a list of Accounts linked to Sited and displays the linked Site details in the bottom pane (if the details are available). This list gets updated every hour.
  4. Select the Account you want to unlink, and click Remove Link.
  5. Note: Some Accounts may be listed more than once in the Linked Accounts tab, if they are linked to multiple Continuum sites. Each link can be removed separately.

OR use the quick option:

  1. In the Accounts window, find the Account you want to unlink.
  2. Go to Accounts > Tools > Remove Link between RangerMSP Record and Continuum.
  3. If the Account is linked to more than one site, ALL links will be removed.

Note: Removing the link between the Account and the Site in Continuum will also result in removing the links between the Account's tickets and assets to the ones in Continuum.


Link Asset to Device

In order for Tickets arriving from Continuum to be linked to the correct Asset, you must create an association between Devices in Continuum to Assets in RangerMSP, or create an Asset in RangerMSP for this Device.

Use the Continuum Links Manager Window to create the association:

  1. In the Assets Window, go to Assets > Tools > Continuum Links Manager.
  2. In the Wizard which opens you can find a list of available un-linked Devices from Continuum. This list gets updated every hour.
  3. Select the Device you want to link, and click Next. The following screen appears:

  4. Find Asset:
    1. Find the equivalent Asset using the search options:
      1. Search by name.
      2. See Assets recommended by the system based on the Device name.
      3. Once you have chosen the Asset, click Link to Asset.
    2. OR create a new Asset based on the Device details(*).

(*) Note: When creating a new Asset in RangerMSP based on the Device from Continuum, the following fields are copied: Device Name, Serial Number and Manufacturer. Other technical device details are copied to the Asset Note field.

At this point the Asset and Device are linked.

To cancel the link between the Asset and Device, hit the Linked External Records tab to find the Asset and remove the link. See Unlink Asset From Device.

Unlink Asset From Device

Assets in RangerMSP must be linked to Sites in Continuum in order for Tickets to be linked to the correct Asset. If you want to cancel a link between an Asset and a Device, you can use two methods:

Use the Continuum Links Manager (recommended! this way you can see the linked Site details before removing the link):

  1. In the Asset Window, go to Assets > Tools > Continuum Links Manager.
  2. In the Window which opens hit the Linked External Records tab to find Assets which are already linked.
  3. This tab displays a list of linked Assets in RangerMSP and displays the linked Device details in the bottom pane. This list gets updated every hour.
  4. Select the Asset you want to unlink, and click Remove Link.

OR use the quick option:

  1. In the Assets window, find the Asset you want to unlink.
  2. Go to Assets > Tools > Remove Link between RangerMSP record and Continuum.


Ticket Creation – Special Cases

In case the Site or Device is not linked to the equivalent Account and Asset in RangerMSP, the Ticket will still be created, and the missing entity will be handled by the system in the following manner:


Ticket from Unknown Site

In case a Ticket arrives from Continuum for an anonymous Site which is not linked to any Account in RangerMSP, a new Account is automatically created with the name:

[Continuum AUTO CREATED] + Site name in Continuum.

For example, a Ticket which is created in Continuum for a site called "ACME company", the Account which is automatically created for this site will be called:

[Continuum AUTO CREATED] + ACME company

If such an Account already exists in RangerMSP (from previous tickets), the new Account will still be created, so multiple Accounts with the same name may exist in the system.

The Ticket is then created and linked to this automatically created Account. New Continuum Tickets will also be linked to this Account as long as a permanent Account is not created for this Site.

When technicians find this Ticket, they should:

  1. If a "real" Account already exists for this site, merge both Accounts to the master RangerMSP account for this site.
  2. If this site is new and does not exist in RangerMSP, make this the master Account for this site, and rename it to its real name.
  3. After the merge, all links to Continuum Sites will be merged into the Master Account so there is no need to re-link the Account to the Site.


Device Not Linked to Asset

In case a Ticket arrives from Continuum and is linked to a Device which is not linked to any Asset in RangerMSP:

  1. The Ticket is created and linked to Account.
  2. Device details are filled in the Ticket Description.

Tickets without a Site

In Continuum, manual Tickets can be unrelated to any specific customer site (e.g. a support Ticket against Continuum NOC Support). In this case, the Ticket which arrives at RangerMSP is not linked to a Site.

In case the Ticket is not linked to a Site, the Ticket is created and linked to the your own business’ Account, i.e. the first Account created in RangerMSP which represents your own business.

Troubleshooting

In case CRM RMM Server fails to download Sites and Devices details, the system will show the user a message when opening the Continuum Links Manager (e.g. from Accounts > Tools > Open Continuum Links Manager).

First, make sure all setup and installation steps were performed properly:

  1. Initialize Continuum PSG.
  2. Install CRM RMM Server.
  3. Validate CRM RMM Server downloads Continuum Sites and Devices to the RangerMSP server.


See full details in RangerMSP Setup.


If all steps were completed, it is possible the CRM RMM Server has failed to pull the files due to an error. To check this please log into RangerMSP client and from the menu select Tools > System Tools > Advanced > Check for Server Side Error Reports.

If no error file exists at this location, please contact RangerMSP Support for further assistance.


After the initial setup, to start working with the Continuum Link, you should complete the following steps:

  1. Link Accounts and Assets in RangerMSP to Sites in and Devices Continuum.
  2. Enable Continuum Integration.

See full details in RangerMSP Setup.

RangerMSP Privileges

In order for a user to manage Continuum Links (with Sites and Devices) the user should have Continuum Integration Privileges.

User without privilege for Continuum will not be able to link and unlink Continuum Sites, Devices and Tickets. The user will be able to view the Continuum Links Management Window in order to see the unlinked and linked Sites and Devices, however, the window will open for read-only purpose.

To give a user the ability to update links, they need to have the Continuum Integration Privilege:

  1. Find the user's Privileges Group from the Employee's window > Employee Tab.
  2. Then check that the Privileges Group includes the Continuum Privilege:
    1. Go to File > Users & Privileges > Privileges.
    2. Choose the relevant group from the drop down menu and make sure that the Continuum Integration privilege is selected.


See Also