N-central Help

Deploy SolarWinds N-central agents through Kaseya

This procedure describes the process for migrating remote networks from Kaseya to SolarWinds N-central, using the KaseyaMigrationandRemoval.exe tool. This is deployed through Kaseya, and when executed on a Windows device will stop the Kaseya Security Service, download and install a SolarWinds N-central Windows agent.

This tool is subject to environmental variables and should be tested before mass deployment. Sometimes security software, security settings and/or network firewall settings may prevent successful deployment, and remote access may be required to recover orphaned devices.

Prerequisites

Make sure you have created the customers that you want to migrate remote networks (see Add a new customer) or imported them from Kaseya (see Duplicate customer lists from Kaseya. It is best practice to give the customers exactly the same name in SolarWinds N-central as in Kaseya to allow integration with certain PSAs.

You will need to have the Access Codes for these customers. These can be found in SolarWinds N-central from the Service Organization level by clicking Administration > Customer/Sites.

Download and unzip KaseyaMigrationandRemoval.exe from the SolarWinds MSP Resource Center at https://community.solarwindsmsp.com/Community/Scripts-Automation-Policies.

Create the Kaseya agent

  1. Sign-in to Kaseya, and select Agent Procedures from the left menu.
  2. Below Installer Wizards, click Application Deploy.
  3. Ensure the Send the installer from the KServer option is selected, and click the here link at the end of the option to upload KaseyaMigrationandRemoval.exe.
  4. In the pop-up window, click Private files, then click Upload a file.
  5. In the new pop-up window, click KaseyaMigrationandRemoval.exe , then click Open.
  6. Close this pop-up window, and click Next.
  7. From the Select the install package to send to the remote machine drop-down menu, click (Priv) KaseyaMigrationandRemoval.exe.
  8. From the What kind of installer is this? drop-down menu, click Other.
  9. In the Specify command line box, enter your SolarWinds N-central Server URL and Customer Access Code in the following format:
  10. severuri:your-Ncentral-server-url:portnumber customerid:customer-access-code

    For example: serveruri:ashbury.n-able.com:443 customerid:109

  11. Click Next.
  12. Label the Agent Procedure <CUST_NAME> KaseyaMigrationandRemoval
  13. where <CUST_NAME> is the customer name associated with the Customer Access Code specified above. Do not choose to reboot the machine after installing the application.

  14. Click Create.

Recommended Kaseya agent procedure modifications

It is best practice to eliminating the use of environment variables, as described below. This has been found to yield higher migration successes.

  1. Click Private > My Procedures and double-click <CUST_NAME> KaseyaMigrationandRemoval.
  2. Select the second step, Write file...
  3. In the Setup Options in the right pane, enter c:\KaseyaMigrationandRemoval.exe in the Enter the full path and file name box
  4. Click Save.
  5. Select the third step, Execute #agentDrv#temp .....
  6. Enter c:\KaseyaMigrationandRemoval.exe in the Enter the full path and file name field.
  7. Click Save and Close.

Deploy KaseyaMigrationandRemoval agent procedure

You should deploy the KaseyaMigrationandRemoval Agent Procedure to a single device within a remote environment to verify:

  • The Kaseya Agent associated to the device goes offline
  • The device is created within SolarWinds N-central

If satisfied with testing, you may proceed with executing the KaseyaMigrationandRemoval agent procedure to multiple devices. Keep in mind all devices will be registering with the Customer/Site represent by the Customer Access Code specified when creating the agent.

  1. Click Private > My Procedures and double click <CUST_NAME>KaseyaMigrationandRemoval.
  2. If required, you can modify the current view to list specific devices you want to migrate from Kaseya to SolarWinds N-central.
  3. Select the check box before the device(s) to which you want to deploy the KaseyaMigrationandRemoval Agent Procedure.
  4. Click Run Now.

The status of devices that have deployed the KaseyaMigrationandRemoval.exe application will change from green to gray within Kaseya, and those same devices will begin to populate the All Devices view of your SolarWinds N-central server.

Next customer Kaseya agent procedure

When you have migrated all the devices for one customer, you can proceed to the next step.

  1. Click Private > My Procedures and select (do not double click) <CUST_Name>KaseyaMigrationandRemoval.
  2. Click Rename Procedure.
  3. Enter the name of the name customer: <NEXT_CUST_NAME>KaseyaMigrationandRemoval.
  4. Click Save.
  5. Click Private > My Procedures and double-click <NEXT_CUST_NAME>KaseyaMigrationandRemoval.
  6. Select the third step, Execute C:\KaseyaMigrationand .
  7. Enter the arguments to pass to the executable box, update the customerid to reflect the next customer's Access Code. For example, in the screenshot below it has been changed to "472".
  8. Click Save and Close.

You can then deploy the agent procedure to this and subsequent customers, in the same way as described in Deploy KaseyaMigrationandRemoval agent procedure above.

To review all devices that have been imported into SolarWinds N-central, leverage the License Usage Report. This can be viewed from the Service Organization level by clicking Reports > Administrative > License Usage.