If TeamViewer Host is already installed on a machine and contains a static password for example for a third party administrator, it is not possible to connect to the machine over the dashboard. This is caused by the GFIMAX password placed as second or third password in the TeamViewer host password management and the agent fails to complete the integration or to identify the GFIMAX password.
For each device in N-Central, OSInfo and OSType are written to the Notes field in the corresponding Autotask configuration item. I'd like the ability to disable this. We'd like to put our own notes for each device in Autotask, but N-Central overwrites them with each sync. The device notes field also syncs with ITGlue so those notes are overwritten as well.
Currently we have our Autotask PSA integrated with the Solarwinds RMM. We can open tickets and view tickets created from the failed check outages without having to manually search in Autotask. We need the same ability to open the link to the configuration in IT Glue. Special notes for devices should be saved in our documentation source, i.e. IT Glue, but without this, getting everyone to manually find the computer in ...more »
Would like backup integration for Mac/Linux client machines in order to not have two dashboards for managing devices.
PSA type of integration with Salesforce CRM.
Solarwinds themselves use Salesforce as a CRM.
Code that can be customized and would allow N-Central to communicate with the Salesforce.
ConnectWise introduced the ability to merge tickets back in July 2016. After trying to verify compatibility with N-Central at the time, we learnt that merged tickets were not supported through N-Central as the associated ticket numbers wouldn't track back correctly after the merge takes place. I assumed that this would mean N-central would talk to ConnectWise about it, but it looks like that never happened or talks halted ...more »
I feel really stupid having to request this, but SolarWinds won't do anything without it. Whilst patching our PSA recently and facing outages, we have found that depending on the type of PSA issue you are facing (eg connectivity, backend sql problem), the failure notice you receive from a ticket not being created/updated will always include details of the customer and notification recipient, but for some inexplicable ...more »
ConnectWise and SolarWinds DO sync endpoint quantities. The issue is that the the actual additions are left under the company in one large bucket. They are not parsed per Agreement Addition. This must be done manually by clicking the checkbox. Issues is that as machines are added and replaced, this becomes cumbersome to do manually and also there is no good way to know to actually DO this. This means, the only way ...more »
PSA Integration relies on direct, uninterrupted communication with the PSA solution. API may encounter a network time out and not retry sending the information.
Establish some kind of queuing logic much like a mail server that could queue the messages for retry.
I see that there is integration within Slack for a few competitor solutions and we would love it if MSP Manager could integrate with Slack as well.
We use RMM and MSP Manager. There seems to be a lack of configuration for the integration to MSP Manager. I would like more options of what and how tickets get created. For example, we have our site and devices in RMM to monitor and test on our own Servers and Lab. I would like the option to exclude these from creating tickets in MSP Manager.
Currently, only one Agreement per Agreement Type can be used when integrating with ConnectWise through Billing Profiles, though the functionality in CW exists to have multiple Agreements. Some reasons for the desired functionality: 1. Client with two network infrastructures used for two purposes. We have one client that has 1) their internal network and 2) a hosting network for their clients. They have different contracts ...more »