|
|||
|
|||
I would like to ask for opinions regarding the use of CommitCRM in Azure, is it better to have a local server? can we connect SQL on the hosted server so we don't have to RDP? The Microsoft server options are kinda confusing, what is the best option to choose?
I appreciate that the questions here are not very specific, but we are deciding as to whether it is a good move to put CommitCRM in the cloud as our local server is nearing its EOL or to carry on with local resources and replace the server. Many Thanks Mike |
|
|||
|
|||
Many people have migrated their RangerMSP app to the cloud, and from what we can tell most went with Microsoft Azure and Amazon AWS.
Cloud server vs. On-prem - there are many different pros and cons here for each configuration so we can't say much, it's probably subjective and depends on your requirements. For example, people using QuickBooks Desktop usually prefer everything on-prem for the two apps to communicate, for others using QuickBooks Online this makes no difference, etc. You may also want to review a somewhat similar discussion in this thread. When hosted on a cloud server, the SQL backend for RangerMSP should be used and be installed where RangerMSP is installed (same server). Users then can access RangerMSP via the Web Interface from anywhere, or RDP to use the Windows client. When it comes to RDP licensing - you'll need to discuss this with your cloud provider. Hope this helps. |
|
|||
|
|||
You can.
You can use Remote Desktop Connection to accomplish this. Your Cloud server will need the appropriate licenses from Microsoft to get RDP set up. Once it is setup it works great. We also have Office 365 installed on the server to allow editing of spreadsheet, documents email, etc. This is how we have our CommitCRM application setup. |
|
|||
|
|||
If you visit this page and scroll to the bottom you will see the beginings of a Internet Based Desktop Client for CommitCRM.
https://dentaur.com.au/jupiter-serve...ient-explorer/ Currently only viewing Accounts in CommitCRM is supported. On that screen you also see if the Account is listed in Webroot, Naverisk and ITPortal. There is also a field showing the number of open tickets. However the current CommitCRM API does not implement 100% of the features in the current CommitCRM interface. So even if we finish our Internet Based Desktop Client, we will not be able to implement all the features in the CommitCRM interface. For example, the current API doesn't support Passwords, or Configuration Notes etc. |
|
|||
|
|||
Internet Based Desktop Client for RangerMSP is progressing.
https://dentaur.com.au/jupiter-explorer-rangermsp/ Insert new customer into RangerMSP and ITPortal at the same time. View existing customers in Webroot, RangerMSP, ITPortal and Naverisk Insert new contact into RangerMSP View existing contacts in RangerMSP View existing contracts in RangerMSP View Devices in Webroot and Naverisk From the RangerMSP screens add a customer into Webroot, or if in Webroot or ITPortal already show the relevant data. Next on the roadmap is to add support for Inserting new Assets and Tickets (and viewing the existing ones). Yes, I have left out modifying existing RangerMSP records. The Jupiter Server can already do that. Just haven't paused to implement that in Jupiter Explorer yet. |
|
|||
|
|||
It should run well indeed. Besides, if you're use Microsoft 365, you should probably switch to the direct, server side, silent two way calendar sync with 365 by using the dedicated plugin. Click to read more about 365 calendar sync.
Hope this helps! |