Deploying & Monitoring Bitdefender

Deploying & Monitoring Bitdefender

Introduction

This guide will outline how to deploy, monitor and manage Bitdefender Endpoint Security on Windows devices using Naverisk and the Bitdefender GravityZone Control Center.

Deployment

This section will cover how you can deploy BitDefender to your client’s workstations and servers using Naverisk.

Prepare the Deployment Package

Login to the Bitdefender GravityZone Control center https://gravityzone.bitdefender.com/ and under Network on the left hand panel select Packages.

You can either add a new deployment package (refer to the GravityZone documentation for details on creating packages), or choose an existing package.

Tick the desired package, and click Send download links.

Expand the Installation links section, then highlight and copy the Windows Downloader URL.

Configure the Naverisk Script Pack

A script pack to install BitDefender – BitDefender Deployment Kit – is available in the Routine Store, or may be pre-installed in your Naverisk console. 

If not already installed, download the script pack from the Routine Store, and upload it to your top client level under Settings > Script packs.

Edit the script pack, and under Parameters, enter the download URL that you copied from GravityZone. 

Important – Ensure that the URL is enclosed in “quote marks.” 
Save the script pack. It is now ready for use.

Deploying to Devices

Now that you have created your Bitdefender Deployment script, you can either run this manually through the Devices tab or create a scheduled job to deploy this script pack at a designated time.

Please note that the deployment process can take some time, possibly up to 15 minutes, depending on the speed of the client device and internet connection.

While we recommend deploying Bitdefender through Naverisk, you can also use the Bitdefender Remote Installation. You can find the details for this in the Bitdefender Control Center > Essential Steps when you first login to the console (as below).

Monitoring Windows Workstations

Naverisk can integrate into the Microsoft Windows Security Center to provide efficient Antivirus monitoring on your Workstation Devices. Naverisk is able to automatically retrieve information on the status of Antivirus, Firewall and Anti-Spyware software for alerting and reporting purposes, monitoring that the Antivirus or Anti-Spyware application is running, and that the definitions are up to date.

Note: Only Microsoft Workstation Operating Systems from Windows XP – SP3 onwards are supported by the Naverisk Security Center.

Please note that there may be variations on how specific applications are reported across different Windows versions. For example, Windows 7 reports Windows Defender as Anti-Spyware, while Windows 8.1 and 10 report it as Anti-virus.

In order to monitor Server Operating Systems you will require a device role. Configuring device roles to monitor Bitdefender are discussed later in this article.

Setting up Naverisk Security Center Monitoring

To set up Naverisk Security Center follow these steps below.

Log in to Naverisk, Navigate to settings and select the OS Templates Icon, 

Select the appropriate client and select the ‘Green Arrow’ to make changes to the desired Operating System Template,
Within the OS Template, select the desired security services and signatures to monitor, then save the template.
Naverisk has now picked up on Bitdefender Endpoint Security for a Windows 7 workstation below.

Monitoring Using Device Roles

Bitdefender can also be monitored using Naverisk device roles. This is particularly applicable to Windows servers, which do not support the Security Center, but can also be used on Windows workstations as well if desired.

A pre-configured Device Role for Bitdefender is included in Naverisk, and is also available for download from the Routine Store.

This monitors the Bitdefender component services, the Event Log for Bitdefender warnings, and checks the definitions. It will also warn if Bitdefender is not installed on a device.

This Device Role can be applied to both workstations and servers, either individually or in bulk.

To deploy individually:

1. Navigate to the Devices tab

2. Go into the Device you wish to add the Role to

3. Select the Monitoring tab

4. Select the ‘+’ symbol under the Device Roles Section

Here you will be presented with all the Device Roles you would have seen under the Device Roles in the Settings tab:

5. Select the AV Bitdefender – Endpoint Client role by ticking the check box on the right-hand side of the Device Role.

6. Select Save Roles to assign the Role to this Device.

You can also deploy the role in bulk to multiple devices:

1. Navigate to the Device tab.

2. Select a Client that you wish to deploy your Device Roles to.

3. Select the multiple Devices with the use of the check boxes situated next to the Device on the left hand side as per the screenshot below:

4. In the right-hand corner of your Naverisk Dashboard, next to New Device you will see a drop-down menu called Select a Task. Click on this drop-down and select Update Roles:

5. You will now be presented with a list of Device Roles that is available for assigning to your Devices:

6. Select the AV Bitdefender – Endpoint Client role by ticking the check box beside the role.

7. Click Add Roles.

For more details on working with Device Roles, see the Device Roles guide under Naverisk Help.

Alerting

Tickets are automatically created when issues arise with a Bitdefender client on any monitored device. These will be assigned an appropriate SLA classification depending on the severity of the issue. These tickets are generated from either the Security Center integration or the Device Role, depending on the type of client device.

Generating Alerts from GravityZone

Bitdefender endpoints communicate directly to the GravityZone Control Center when events such as threats being detected occur. It is easy to configure the console to send these alerts to Naverisk so that your AV monitoring/alerting can be consolidated in one location.

In the GravityZone Control Center, click on the alarm icon at the top left to open the Notifications panel, then the settings icon

On the settings page, configure your Naverisk support email address, and select the events that you want notifications generated. For each event, you can have a notification shown in the GravityZone Control Center, and/or sent as an email. Depending on the event, other options may be available such as event thresholds. Once you have configured the desired alerts, click Save.
Workstations – via Security Center

The Security Center is an integration from Microsoft Action Center, that uses the Microsoft Action Center API (Application Programming Interface), to retrieve and relay the data that is normally displayed in your Windows OS, to your Naverisk Web Interface.

This data is also integrated into Naverisk’s Reporting system. This allows you to run analytics of your device’s security, which over time can show you where the weak links are, helping you to strengthen your Clients’ security and allowing you to protect their data more efficiently.

Note: Security Monitoring is only compatible with Windows Workstation Devices due to Microsoft not including the Security Center within Server OS’s. You will need a Device Role to monitor Security on a Server.

The Security Center can be enabled by ticking each checkbox. The use of each section is as follows: 

Antivirus:

  • If Service monitoring is enabled, a Failure SLA ticket will be created if the Antivirus service is detected as Stopped for more than 600 seconds.
  • If Signatures monitoring is enabled, a Failure SLA ticket will be created if the Antivirus signatures are found Outdated for more than 600 seconds.

Firewall:

  • If Firewall Service monitoring is Enabled, a Failure SLA ticket will be created if the Firewall is detected as Disabled/Stopped for more than 600 seconds.

AntiSpyWare:

  • If Service monitoring is enabled, a Failure SLA ticket will be created if the AntiSpyWare service is detected as Stopped for more than 600 seconds.
  • If Signatures monitoring is enabled, a Failure SLA ticket will be created if the AntiSpyWare signatures are found Outdated for more than 600 seconds.

Each threshold can be increased or decreased, depending on your needs. The maximum threshold is 999 seconds.

Servers – via Device Roles

Each Bitdefender service and logged event, as well as the result of the definition check, are configured by default to create a ticket to warn you of an issue. The SLA severity of these tickets are also set by default to appropriate values. You can change these by editing the Device Role. Please refer to the Device Roles documentation for details on this.

Scheduling Scans & Updates

In order to schedule Bitdefender updates & scans, you will need to configure this through your Bitdefender GravityZone Control Center. We recommend scheduled updates and scans be configured in GravityZone, however you can also trigger updates and scans from Naverisk.

In the Control Center this can be done through the Policies Tab and configured to suit your needs:

Scheduled Update:

Scheduled Scan:

Once you have created your policy for the Update and Scans, you will then need to assign it to your Devices.

To do this, you will need to navigate to the Network tab and select the Device you wish to assign the policy too.

Once you have selected the Devices or group of Devices, click Assign Policy:

You can then select the appropriate policy that you wish to assign and click on Finish:

This policy will then filter down to your Bitdefender endpoints.

Running Scans & Updates from Naverisk

In addition to using the GravityZone Control Center, you can also manually trigger scans and updates as well as checking the Bitdefender endpoint status from Naverisk. A set of script packs are available in Naverisk, and are also available for download from the Routine Store.

BitDefender Tools – Get Update Status: Returns the time code of the last attempted and succeeded update. If these are different it indicates the update attempt failed.

BitDefender Tools – Is Update in Progress: Check to see if an update is currently running.

BitDefender Tools – Get Version: Returns the current version number of the installed Bitdefender client.

BitDefender Tools – Is Restart Needed: Determines if a system restart is required to enable full protection. This is sometimes required after initial installation or a client upgrade.

BitDefender Tools – Check Definition: Checks to see if the definitions have been updated in the last 24 hours.

BitDefender Tools – Start Update: Trigger a definitions update on the endpoint.

BitDefender Tools – Scan: Start a Quick Scan on the endpoint.

The results of these scripts will be returned in the usual manner for Naverisk Script Packs, and will also write the result to the device event log. If the Bitdefender device role has been applied to the device, an entry in the device Audit tab will be created, and an alert raised if required (e.g. definitions not updated).

Reports

Reports can be generated in Naverisk that show your customer’s antivirus status. Bitdefender also provides additional reporting via the GravityZone Control Center.

The Antivirus Detail report can be found under the Reports tab > Device > Antivirus Detail and will look like the below example:

Note: That data may be incomplete when clients are first configured. Waiting at least 24 hours for data to be retrieved and logged by Naverisk should provide you with better results.

The Antivirus Summary report can be found in the Reports tab > Client Facing > Antivirus Summary. It will appear as a pie graph as per the below example:

For more information on Deploying & Monitoring with Naverisk see our help guides located in the Naverisk Help Center.

Automate your service delivery with Naverisk:

Naverisk is an all-in-one RMM, Service Desk & PSA solution for MSPs and IT Professionals.

From monitoring and device management to ticketing and billing, Naverisk removes the need for running multiple programs.

Take advantage of Naverisk’s powerful automation features with a FREE demo today!

You will love the Naverisk experience. Try us today!

Cloud Service & Website Monitoring

Cloud Service & Website Monitoring

The Cloud Service & Website Monitor allow you monitor the availability and response of a website without having to install an agent on the web server. This is particularly useful for sites hosted externally by web hosting providers, who may not allow access to the underlying servers.

The website URL is monitored from one or more devices that have an Naverisk agent installed. This can be either a standard or advanced agent. The monitor measures the site response time, and is also able to test for specific text being returned from the server. By monitoring remotely, you can measure the real-world response time, including the effect of network and internet speed between the web server and monitoring device. By monitoring a URL from multiple devices, you add redundancy to the monitor, and measure performance from different locations.

Creating a Monitor

To monitor a website, a Passive Device must be added to the appropriate client. From the Devices tab, select New Device then click Create New Passive Device. Enter the device information as required then save.

The monitor then needs to be configured on a suitable device. This device can be on the same client as the passive device created above, or under a different client if required.

1. From the Monitoring tab, under Monitored URIs: select Add.

2. Enter the website URI, making sure the correct protocol is selected. The URI can be set to any available page on the site.

3. Under Device, choose the Passive Device created above

4. Set the other fields as required.

Searched Text: This is used to test for text returned within the tested web page. Setting this to text that you would see if the page is working correctly will allow the monitor to tell if the page is returning valid content or an error message. You can either test for content that should be present, or test if an error message is not present.

Threshold: An alert will be generated if the website does not respond within the configured time, allowing you to check for degraded performance.

Interval: The frequency that the monitor will poll the website

Failure threshold: The number of consecutive failed polls before an alert is raised. This can be set to a higher number to prevent occasional slow responses etc from creating alerts unnecessarily.

SLA Class: The desired classification. This would typically be set to Performance or Availability

SLA Status: The required SLA status severity used when an alert is created

SLA Trigger Text: Optional text added to the ticket trigger field when an alert is created. This can provide additional information or details about the alert.

Once the required fields have been completed, click save. Note that multiple URI monitors can be added to a device.

You will also need to save the OS template on the device so that the monitor is added.

Adding a Monitor to an OS Template

In addition to manually adding a Monitored URI to an individual device, you can also add one or more monitors to any OS Template.

Under Settings, go to OS templates and edit the required template. You can also copy an existing template or create a new one.

You can add a URI monitor under the Availability section. The monitor is configured in the same way as above. Once the template is saved, the URI monitor will be added to all devices currently using the template. when adding a URI monitor to an OS template, consideration should be given to the number of devices using that template, to prevent a large number of devices all monitoring the website and creating excessive load.

Further details on using OS templates can be found in the Knowledge Base.

Viewing Monitor Details

By opening the Passive Device created for the monitor, you can view tickets created by the monitor, and see the devices that the monitor is run from.

Advanced Concepts

Monitoring dynamic web pages

Many websites use dynamic pages driven by a back-end database. These can include catalogs, shopping cart sites, searches, blogs and forums. By referencing a dynamic page in the monitor, you can verify that the database and back-end code are performing correctly, however as the page is dynamic it can be difficult to search for specific text as it may not appear over time. For example, on a blog, if you are searching for text in a specific post, as new posts are added, the one with the text may eventually not be shown on the main page.

In many cases, we can request the specific article, post or other data within the URL. A typical example would look like:

www.website.com/search.php?article=text

Other sites may use what looks like a static URL (e.g. blogs) however the content is still fetched dynamically. Regardless of the method, by copying the specific dynamic page URL into the monitor will always return the expected page.

Using multiple monitors on one site

By configuring multiple monitors for one website, you can create more granular monitoring. Some examples include:

  • Different SLA Statuses. By creating monitors set to different threshold times, you can create alerts of increasing severity depending on how slow the site is responding.
  • Testing multiple pages in on a site. Create a monitor for each page required. Different threshold times could be created depending on the complexity/size of a page or whether it is static or dynamic.
  • Test for specific errors. By searching for a specific error message in each monitor (using the not-equal-to option), a separate alert will be raised for each error condition. The SLA Trigger Text field can be used to provide details of the error.
  • Monitor performance across distributed locations. By creating monitors on devices in multiple physical locations, the website performance can be verified from different networks/internet connections. This also provides monitoring redundancy.

Automate your service delivery with Naverisk:

Naverisk is an all-in-one RMM, Service Desk & PSA solution for MSPs and IT Professionals.

From monitoring and device management to ticketing and billing, Naverisk removes the need for running multiple programs.

Take advantage of Naverisk’s powerful automation features with a FREE demo today!

You will love the Naverisk experience. Try us today!

Configure Naverisk to Monitor Veeam Backups

Configure Naverisk to Monitor Veeam Backups

This guide will help you configure Naverisk to monitor Veeam backups. It should be read in conjunction with http://kb.naverisk.com/en/articles/2810682-backup-monitoring which describes the backup monitoring capabilities of Naverisk in more general terms.

This guide has been written and tested using the Veeam Agent for Windows, however it is also applicable for monitoring a central Veeam server, in which the event log name needs to be changed but all other settings remain the same.

Determining Veeam Event Log Entries

Veeam backup writes all events into an application event log called Veeam Agent (if using the Windows agent) or Veeam Backup (if using a Veeam server).

Log Entry Types

1. Backup Started

This entry is created each time a backup job is started, and has the event ID of 110, and a log level of Information. If the job does not run, no entry is created.

Log Entry Types

1. Backup Started

This entry is created each time a backup job is started, and has the event ID of 110, and a log level of Information. If the job does not run, no entry is created.

2. Backup Successful

This entry is created when the backup job completes successfully. The event ID is 190 and the log level is Information

3. Backup Failed

Should the backup job fail for any reason, a log entry is created, also with ID of 190, however the log level is Error.

We will use these three events to create monitoring in Naverisk that will create tickets if a backup does not start or if it starts and fails. It will also maintain the history of successful and failed backups for reporting purposes.

3. Backup Failed

Should the backup job fail for any reason, a log entry is created, also with ID of 190, however the log level is Error.

We will use these three events to create monitoring in Naverisk that will create tickets if a backup does not start or if it starts and fails. It will also maintain the history of successful and failed backups for reporting purposes.

Creating a Device Role

To provide correct alerting and reporting, the monitoring must be configured in a Device Role, and not by configuring the event log rules on an individual device. A device role template for Veeam Backups is available on our routine store, however we will discuss the procedure for creating one below. It is recommended that you read these steps even if you plan on importing the template, so you understand the settings used.

Create a new Device Role under Settings and give it an appropriate name (e.g. Backups – Veeam). You will then need to add Monitored Event rules for the three Event Log entries created by Veeam, described above.

1. Backup Start – This rule will check that the backup job starts as scheduled

Add a new event rule, and configure it as follows:

Event Source: Veeam Agent or Veeam Backup as applicable

Event Type: Information

Event ID: 110

Event Description allows matching of text in the event description, it is not required for Veeam backup monitoring.

Set the SLA Class to Backup. This class will only generate a ticket if the SLA status is Failure, and also allows reporting history to be kept.

SLA Status: Failure – we are checking for backups that do not run, so we want an alert to be generated.

Set the Ticket Group and Ticket Trigger Text to your preferences.

Reporting Status: None – if the backup does not run, we want a blank entry for that day in the report, to indicate no backup was made

Tick Timed Event. When this is enabled, a ticket is generated if the event (backup started) is not received during the time window specified. If the backup starts and generates the event, this is detected, and no ticket is generated.

Set the desired start and end time. This should encompass the scheduled start time of the backup job, with some margin before and after to allow for any difference in system time. Note that it is not necessary to cover the entire backup period, just the time is should start.  Note that the start and end time must not cross 12:00am e.g. Start 11:30pm, End 12:30am.

If a backup job is started outside the specified time period, a ticket will be generated to warn you of an unscheduled backup starting.

2. Backup Successful – This rule checks for successful completion. A ticket is not generated, however the event is recorded for reporting.

Add a new event rule, and configure it as follows:

Event Source: Veeam Agent or Veeam Backup as applicable

Event Type: Information

Event ID: 190

SLA Class: Backup

SLA Status: Information

Reporting Status: Success

2. Backup Successful – This rule checks for successful completion. A ticket is not generated, however the event is recorded for reporting.

Add a new event rule, and configure it as follows:

Event Source: Veeam Agent or Veeam Backup as applicable

Event Type: Information

Event ID: 190

SLA Class: Backup

SLA Status: Information

Reporting Status: Success

3. Backup Failed – This rule checks for failed backups and generates a ticket. The event is also recorded for reporting.

Add a new event rule as follows:

Event Source: Veeam Agent or Veeam Backup as applicable

Event Type: Error

Event ID: 190

SLA Class: Backup

SLA Status: Failure

Ticket Trigger Text: Backup Failed, or similar, to your preference.

Reporting Status: Failure

Save the Device Role, and copy if necessary to your clients. Add the role to the Device Profiles or individual devices as required.

With the monitoring in place, the following results will occur:

Monitoring backups that are taking too long

In some cases it is useful to know if a backup has not completed within the desired timeframe – for example a backup still running when business hours start could impact system performance. If required, an additional event rule can be added to generate a ticket if the backup has not completed within a specified period.

Add a new event rule as follows:

Event Source: Veeam Agent or Veeam Backup as applicable

Event Type: Information

Event ID: 190

SLA Class: Backup

SLA Status: Failure

Reporting Status: None

Select Timed Event and set start time to the scheduled start, and end time to the end of the backup window.

This rule will create a ticket if the backup is still running at the end of the backup window. No ticket is created if the backup completes within the window. The rule does not have any effect on the backup report.

Backup Reports

The rules configured above will result in a backup report showing the backup status for each day as follows:

Success – backup completed successfully

Failure – backup completed with errors

Warning – no backup ran.

Automate your service delivery with Naverisk:

Naverisk is an all-in-one RMM, Service Desk & PSA solution for MSPs and IT Professionals.

From monitoring and device management to ticketing and billing, Naverisk removes the need for running multiple programs.

Take advantage of Naverisk’s powerful automation features with a FREE demo today!

You will love the Naverisk experience. Try us today!

Deploy & Monitor Webroot from Naverisk

Deploy & Monitor Webroot from Naverisk

This article covers how to deploy the Webroot application to devices using Naverisk, monitor that the Webroot service is running, and configure alerts to be sent from the Webroot console to generate tickets in Naverisk.

Deploying Webroot to Devices

A script pack is available that will check a device to see if Webroot is currently installed, and will install it if not present. This script can be run on demand, or triggered using a scheduled task.

If not already available in your Naverisk console, download the Webroot Auto Installer script pack from the Routine Store. In Naverisk, go to Settings > Script Packs and click Upload Script Packs to import the Webroot script pack. This would normally be imported to the top level of your Client Tree, so that it is available to devices at all your clients.

Before deploying the script pack, you must update it with your Webroot license key. The deployment will fail if the license key is not set in the script pack.

Obtain your Webroot license key. It will be in the form XXXX-XXXX-XXXX-XXXX-XXXX

Edit the script pack, enter your license key under Parameters

Save the script pack. It is now ready for use. Should your license key change, you will need to update the script pack accordingly.

Monitoring the Webroot Service

A Device Role is available on the routine store that checks that the Webroot service is running. Should it stop for any reason, an alert will be raised in Naverisk.

Download the Device Role from the routine store, and import it into Settings > Device Roles. Copy the device role to all clients that require Webroot service monitoring.

Add the device role to the desired devices either by adding it to the applicable Device Types, or individually to each device under the Monitoring tab.

Configuring Alerts

Webroot endpoints communicate directly to the Webroot console when events such as threats being detected occur. It is easy to configure the console to send these alerts to Naverisk so that your AV monitoring/alerting can be consolidated in one location.

In the Webroot console, click on the Alerts tab and create a new alert.

Name the alert, and select the required alert type. This would typically be Threat Detected, however you can also configure alerts for other events such as Endpoint Installed.

Under Recipients, enter the email address you are using for incoming support emails in Naverisk.

Select the desired Sites. This allows you to create separate alerts for different sites/clients if required.

You can customise the template used for the email by adding attributes from the list at the bottom of the window.

These could be used in conjunction with the Naverisk Automation Rules by testing on the values populated by these attributes – for example, test for site name to assign the client in Naverisk.

Once configured, whenever an event is received by the Webroot console, an email will be sent to Naverisk that will raise a support ticket. This frees your engineers from having to monitor the Webroot console as well as Naverisk for AV alerts.

Automate your service delivery with Naverisk:

Naverisk is an all-in-one RMM, Service Desk & PSA solution for MSPs and IT Professionals.

From monitoring and device management to ticketing and billing, Naverisk removes the need for running multiple programs.

Take advantage of Naverisk’s powerful automation features with a FREE demo today!

You will love the Naverisk experience. Try us today!

5 Things You Didn’t Know Naverisk Could Do

5 Things You Didn’t Know Naverisk Could Do

We can’t tell you how often our clients say to us, “I didn’t know Naverisk could do that!”.

Naverisk is built with the aim to help MSPs and IT Professionals save costs and increase their efficiency. It does this through powerful automation.

With that in mind, here are 5 amazing features that will help your team save time. These can be especially useful if your techs are regularly on the road!

 

 

Trigger device actions with an email

 

This one is perfect for those technicians who are regularly on the road. Within Naverisk, automation rules work by processing emails using certain criteria from tickets, such as Trigger, Description, Ticket Status, SLA Status, etc.

Email integration creates tickets from emails. So it’s only natural that you can also trigger automation rules with an email.

Using these automation rules, you could trigger the restart of a device, send an email or even run a script. This means that your techs can deliver fast and efficient remote service, simply via the email on their phone.

 

 

Manage your Hyper-V environment

 

Whether you are familiar with Hyper-V servers or not, you may be surprised to find out that you can manage the environment from within Naverisk.

Managing your Hyper-V environment through Naverisk opens up a TON of automation opportunities. These range from creating a checkpoint for your Hyper-V through to configuring the memory of a VM. If you can do it in PowerShell, you can do it in Naverisk.

 

 

Remotely notify users to reboot their PC

 

One of the built-in features of Naverisk is that IT Administrators can inform users to reboot their device post-update. 

This feature is very handy on its own, but it can be taken to the next level with scripting. Utilizing a basic script, you can automate the notification process with a dialog box on a users desktop. If you want to be a bit fancy, you can even set it to use the Windows 10 notification styling. Therefore you can save valuable time previously spent on manual notifications.

 

 

Utilise wmic to remove applications in bulk

 

One of the basic functions of Naverisk is the ability to remotely remove applications from a device via the software tab. The limitation of this is that you can only remove apps from one device at a time. This is where the wmic command line comes in handy.

The wmic command line tool allows you to manage a number of actions for Windows computers. One of these actions is uninstalling select programs on a PC. Utilizing the wmic command, you can remove applications on devices in bulk. As a result, you won’t be wasting time editing each device individually.

 

 

Deploy fonts to Windows PCs

 

Naverisk can be used to deploy fonts across both Windows 7 and Windows 10 devices. Using a simple script, you can quickly and easily deploy as many fonts as you want, across an endless number of devices!

This is especially handy for major deployments where you suddenly have a request to install a new font across an entire organization.

 

 

 

Automate your service delivery with Naverisk:

Naverisk is an all-in-one RMM, Service Desk & PSA solution for MSPs and IT Professionals.

From monitoring and device management to ticketing and billing, Naverisk removes the need for running multiple programs.

Take advantage of Naverisk’s powerful automation features with a FREE demo today!

 

You will love the Naverisk experience. Try us today!