2021 R2 Release Notes

2021 R2 Release Notes

2021 R2 Release Notes

Refined UI for more speed and precision

The latest release of Naverisk continues to make the application more intuitive with greater control over the devices and clients you manage. The aim here is to provide faster access to the tools you use most, for a better user experience.

Below we highlight some key features of this update, click here for the full release notes.

Devices Tab Upgrade

The devices section is one of the most active areas in Naverisk so we have given it an upgrade, with two new tabs to help bridge some of the functionality gaps of the past.

A new Software tab gives an overview of all applications installed at the device or client level. This section will make it easier to locate a specific version of software and make changes to any devices with it installed.

For example, a faulty version of a software has been exposed with vulnerabilities. Do a query with the new Quick Search bar to locate and update all workstations with the rogue version.

Winget for Updates

Naverisk is now using Microsoft Winget to manage software installed on Windows 10 and 11 Devices. If the Windows 10 device does not have the Winget already, Naverisk will install it to the selected device first.

Patching has a new home!

The Patching tab has been moved from the menu to a handy tab in the Devices section. This change was based on user data and feedback as devices and patching are normally used in succession, so it is more intuitive to have them in the same location with many tasks interconnected.

The new tab has all the same functions a before, but now in a more readily accessible location.

Global Quick Search

We’ve expanded the Ticket and Device quick search bar to include Software which will take you straight to the new tab in devices. This new search will allow you to quickly type a name and/or version of an application to check the status and make changes to clients devices where required.

You will find it now located in the top left of Naverisk, which should help speed up your workflow.

Device Statuses

In keeping with usability refinements, the 3 active device statuses have been renamed, to make things clearer for the technician.

Online: Agent is Connected and up to date

Maintenance Mode: Agent is in Maintenance Mode

Offline: Agent is Disconnected

Find a full list of agent statuses in the release notes below.

Custom Reports

We added an RTF output to all Custom Reports which will improve the compatibility and editing options. New custom reports created after the release of R2 will automatically be available as RTF documents also.

This is a quality-of-life upgrade requested by users.

Task Manager UI

The size of the task manager dialogue box has been increased for easier handling. We also added a restart services option to the services dropdown menu and a new view to let users filter on all running services, stopped services and stopped automatic services.

Other improvements

Outside of the features listed above, there are a raft of improvements across the entire application:

  1. OS Device Types for Windows 11 and Server 2022
  2. Dashboard added to the NEW button
  3. Classic theme removed, all user to standard UI
  4. Description field of grid character count increased
  5. Breadcrumb display for SNMP devices
  6. Reformat time lapse in Devices page

For a full list of new features and changes, you can download the full release notes from the link below.

Deliver world-class IT services with Naverisk.

We’re constantly striving to provide a better RMM, Service Desk & PSA platform for MSPs and IT service professionals. Our aim is to provide deep features at the best price. If you’re not already on the platform, get a demo of Naverisk today.

You will love the Naverisk experience. Try us today!

2020 R3 Release Notes

2020 R3 Release Notes

2020 R3 Release Notes

Hot on the heels of our 2020 R2 release comes R3!

We are proud and excited to announce the 2020 R3 release!
Due to overwhelming demand the decision was made to primarily focus 2020 R3 on completing Naverisk’s PSA billing automation capabilities.

(Note: Naverisk 2021 R1 will, in turn, be primarily focused RMM updates and improvements).

With the introduction of an Invoicing Report, Service Catalogue and a Recurring Service Agreement, Naverisk now offers a complete MSP billing automation platform for not only MSP services, but 3rd party products as well (such as M365, or managed AV).

MSP billing agreements now supported:

  • AYCE User
  • AYCE Device
  • Block Time
  • Term
  • Time and Materials
  • Recurring Service (new)
We have a large number of MSP partners running PSA tools integrated with Naverisk. The completion of our MSP billing automation capabilities will allow these partners to realize the cost savings and efficiencies of running a single all-in-one RMM, Service Desk and PSA platform.

Service catalogue

Addition of a master catalogue of all services supplied by your MSP business. Use these services in recurring agreements to automate billing for such. Each service will have the following attributes:

  • Service name
  • Service description
  • Type – five options: Hardware, Software, SaaS, HaaS or IT Service
  • Vendor – Customizable list of suppliers (see Settings section)
  • Buy price – cost of service (used to calculate agreement profitability)
  • Payment term – Frequency of payment to vendor (used to calculate agreement profitability).

New agreement – recurring service

Ability to automate invoicing for recurring services (e.g. fixed fee services, 3rd party services, M365 licenses, etc). Including auto calculation of profitability on a per agreement basis. Note that recurring service agreements can only be associated to one type of service.

Ticket and note billing statuses, queues & workflows

Introduction of ticket and note billing statuses and ticket billing queues. Easily review, update and approve billable time or expense notes in tickets. Tickets listed in the billing queue will automatically clear as billable notes are invoiced in Xero, QuickBooks or marked as invoiced in Naverisk.

Note billing statuses, set manually, as follows:

  1. Billable or Non-Billable
  2. Ready to Invoice or Not Ready to Invoice
  3. Invoiced or Not Invoiced
Ticket billing statuses are automatically set by note billing statuses, as follows:
  1. Non-billable – ticket only includes non-billable notes
  2. Reviewable – ticket includes billable notes which have not been set as ready to invoice
  3. Ready to invoice – ticket includes billable notes which have all been set to ready to invoice
  4. Partially invoiced – ticket includes a mix of already invoiced billable notes and billable notes marked as ready to invoice
  5. Invoiced – ticket includes billable notes which have all been invoiced
Tickets marked as non-billable, or invoiced, will not show in the new billing queue.

Invoice report

Consolidate all your client agreements into one invoice report view for export into Xero or Quickbooks, via existing integrations. Includes the ability to include billing information for 3rd party services, including the upcomming Naverisk data protection platform. Invoice reports will display the following note and agreement attributes:

AYCE per User
Description – Agreement’s Description
Quantity – Agreement’s user count
Unit Price – Agreement’s sell price
AYCE per Device
Description – Agreement’s description
Quantity – Agreement’s device count
Unit Price – Agreement’s sell price
Recurring Service
Description – Agreement’s description
Quantity – Agreement’s quantity
Unit Price – Agreement’s sell price
Description – Agreement’s description
Quantity – Agreement’s purchased hours
Unit Price – Agreement’s cost per hour
Description – Agreement’s description
Quantity – Agreement’s purchased hours
per selected frequency
Unit Price – Agreement’s cost per hour
Time & Material
Description – Ticket ID, note type, note
Quantity – Notes quantity (time or
Unit Price – Notes cost per hour
AYCE per user, AYCE per device and recurring service agreements will be included in an invoice report when the report’s date range coincides with the agreement start and end date. Whenever one of the above agreements is active within a report’s date range that agreement will be included in the invoice report in one of the following ways:
  • Whole month will be included in full
  • Days will be counted separately as Pro Rata

Ticket activity interface improvements


(i) Agreement description into the note UI to ensure technicians select the right agreement
(ii) Checkboxes in notes allowing technicians to mark time and expense notes as ready to invoice
(iii) Select / clear all and billing related filters to the notes filter drop down.

Agreement financial information & profitability reporting

Added a financial details section to all agreements. This includes the fields required to calculate the agreement value and profitability.

Agreement financial information – role based access controls

Added a new user group and role based rights to limit specific users from editing/viewing client and agreement financial Information.

Warranty and lease expiry date views

Added warranty and lease expiry date column’s to the device grid, allowing easy viewing and sorting of devices by warranty and lease expiry dates.

Performance, stability & quality improvements

On top of the features in 2020 R3 we have focused on fixing bugs and improving the general performance of Naverisk. Including, but not limited to:

  • Improved: Ticket queues. Ability to save column selections on a per queue basis
  • Improved: Proxy server support. Ability to use remote control methods behind proxy servers
  • Improved: Updated the client page to show the sum of AYCE per device agreements’ device count
  • Improved: Added support for special characters in script file names: +#&
  • Fixed: Raising a ticket from the user chat dialog box
  • Fixed: Client’s primary point of contact information to be copied to the client’s secondary point of contact
  • Fixed: Passive device names not showing correctly in breadcrumbs
  • Fixed: Removing fully consumed block agreements from the list of agreement available in time and expense notes
  • Fixed: Removed inactive term agreements from the list of agreement available in time and expense notes
  • Fixed: Scheduling page’s jump to week button is not correctly advancing the calendar, in some cases
  • Fixed: Scheduling page’s calendar was not showing the corresponding day of the week, in some cases
  • Fixed: Saving a ticket without job estimate
  • Fixed: Changes to contact name were not reflected correctly in time notes, in some cases
  • Fixed: Restored the email detachment link
  • Fixed: Linux advanced agents creating large HistoricalDataStore directories, in some cases
  • Fixed: Linux drives displayed as C:\, instead of the actual name of drive, in some cases

You will love the Naverisk experience. Try us today!

2020 R2 Release Notes

2020 R2 Release Notes

2020 R2 Release Notes

Naverisk RMM & PSA rapid release program now in play.

We are proud and excited to announce the 2020 R2 release!
Background – we made a significant development commitment in our 2020 R1 release to refactor backend services and components to:

  • Improve overall platform quality.
  • Allow us to ship faster, more agile, releases.

We will now be shipping major releases approximately every two months, with minor releases and hot fixes shipping as required.

We value feedback on our roadmap! Our Forum (https://forum.naverisk.com) is the place to share feature requests, or usability comments, for roadmap consideration.

Authentication / 2FA security improvements

The following authentication methods are now supported:

  1. Username + password.
  2. Username + 2FA.
  3. Username + 2FA + pin.
  4. Username + password + 2FA.

Script pack editor – in app

Scripting is a strength of Naverisk and is one of the key tools to deliver IT services automation. 2020 R2 adds the ability to easily (and quickly) edit and save script packs “in app”.

Multiple technicians / users on a ticket

2020 R2 allows the addition of secondary user(s) to tickets. Naverisk Users can now add other technicians to tickets and create ticket views showing tickets they are assigned to, or marked as secondary users.

Naverisk administrators can choose to activate this feature from the settings page. It can be configured to allow one, or multiple, secondary users as needed.

Key benefits:

  • Team based management of tickets.
  • Ability to “follow” a ticket by adding yourself as a secondary user.

Ticket due date

Control delivery dates for key tickets and tasks with due dates. Tickets can be sorted and filtered by due date in the ticket grid. Sets the platform for agreement based SLA’s, where ticket response and completion SLA’s drive ticket due dates.

Other improvements

You asked, we listened.

On top of the new headline features in 2020 R2 we have delivered a significant number of quality and performance improvements across the Naverisk platform.

  1. User interface improvements.
  2. Creating a ticket creates a new ticket for the client selected/open in the “client tree”.
  3. Exiting a ticket will prompt the user to save any entered text.
  4. Client deletion process, added extra validation, requiring the user to type the name of the client to be deleted.
  5. Removing the Assigned User in a ticket will now automatically change the ticket status to Unassigned.
  6. Changing a ticket status to Unassigned will now automatically remove the Assigned User.
  7. File explorer performance and stability.
  8. Scheduling a device restart will now write an event to the device audit log.
  9. Remote Control will now always return the correct status after a new agent install.
  10. Antivirus, Firewall and Antispyware columns will now be sorted by status first and then alphabetically.
  11. Uploading files larger than the configured upload limit will now show an error message.
  12. Security centre monitoring, addressed reporting issues on Windows 10 build 2004.
  13. Service desk and device table/grid sort performance and stability.
  14. Documents, addition of metadata (document creation date, last saved date, etc).
  15. Various performance and quality improvements across the platform.

Deliver world-class service with Naverisk:

We’re constantly striving to provide a better RMM, Service Desk & PSA platform for MSPs and IT service professionals. Our aim is to provide deep features at the best price. If you’re not already on the platform, get a demo of Naverisk today.

You will love the Naverisk experience. Try us today!

Deploying and Monitoring ESET Security from Naverisk

Deploying and Monitoring ESET Security from Naverisk

Deploying and Monitoring ESET Security from Naverisk

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


Note that this guide is only applicable to enterprise and MSP versions of ESET products managed from ESET Security Management Center or ESET Cloud Administrator. Stand alone or consumer versions cannot be deployed or monitored by Naverisk.

Deploying ESET to devices

Deploying ESET security applications in a managed environment requires installing both the ESET management agent and the desired endpoint application. You can either install the ESET management agent, then deploy the endpoint application from the ESET console, or you can install them both together.

A script pack is available that will deploy both the ESET management agent and endpoint application to any compatible Naverisk device. The script pack will check a device to see if ESET 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 ESET Installer Kit script pack from the Routine Store. In Naverisk, go to Settings > Script Packs and click Upload Script Packs to import the ESET 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 create a deployment package from the ESET management console, and add the deployment link to the script pack parameters. The deployment will fail if the link is not set in the script pack.

  1. Log into the ESET Security Management Center or ESET Cloud Administrator console.
  2. From the left-hand panel, select Installers.
  3. Click on Create Installer, then select Live Installer
4. Select your package contents, ensuring Security Product is ticked.
5. Select your License
6. Select Product version
7. Accept the EULA (steps may differ based on product).

You may also tick Use AV Remover under Advanced, if you wish to automatically remove a previous AV product. Click Finish.

8. Select the “Show Download Link” option and copy the link to the notepad, using the Copy button.
9. In Naverisk, edit the script pack, and paste the download link under Parameters
Save the script pack. It is now ready for use.

Monitoring the ESET Service

A Device Role may be used to monitor the endpoint application service to raise an alert should the service stop running. Because a number of different ESET endpoint applications are available for use, you will need to create a specific Device Role for each application that you have deployed, and assign this to the appropriate devices.

To create a Device Role to monitor the ESET application service, under: Settings > Device Roles select New Role. Under Monitored Services click Add.

Select a device that has the required ESET endpoint application installed. Browse through the list of services to find the ESET application service, and set Notify When to Stopped.
Save the Device Role and apply it to the required devices.

Configuring Alerts

ESET endpoints applications communicate directly to the ESET 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 ESET console, click on the Notifications tab. This will display a list of available alert notifications.

Edit each notification as required, and add your Naverisk support email address to the list of configured email addresses. Click Save when finished.
Once configured, whenever an event is received by the ESET console, an email will be sent to Naverisk that will raise a support ticket. This frees your engineers from having to monitor the ESET 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!

Deploying & Monitoring Bitdefender

Deploying & Monitoring Bitdefender

Deploying & Monitoring Bitdefender


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


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.


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: 


  • 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.


  • 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.


  • 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 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!