Chat now with support
Chat with Support

Nova Current - User Guide

Delegation & Policy Control Reporting Tenant Management System Settings About

Deprovision data collection

Users can stop the collection of data for a tenant by doing the following:

1.In TMS, click the 'Data Collection' tab.

2.Next to 'Data Collection Enabled', click 'Deprovision'.


NOTE: This can only be completed by a user with either a 'System Administrator' or 'Quest TMS Admin' role.

Invitation to access Nova

This section describes what a user sees when they are invited to access Nova.


First, the user receives an email invitation that looks similar to this:



When they click the link in the email, they are prompted to create a user account:



Here is more about the options to create a user account:

·Creating a Quest Authentication Account: Create credentials that are unique to their Nova/Quest account.

·Leveraging Microsoft Entra ID to sign in: Use Microsoft Entra ID credentials to access Nova.

Finally, the user might be asked to enter/confirm their name:


License types

There are several types of license that can be added to give access to features and services within the product. The Nova System Administrator for your tenant can see the licenses which are assigned, as well as the roles relating to individual users.


This is an example of a screenshot of what the Nova System Administrator might see:

Types of license

The available licenses are as follows:
Delegation and Policy Control

This gives access to the Delegation & Policy Control areas of Nova. It allows administrators to create and manage policies, as well as delegated administrators to perform actions according to those policies, such as changing an end-user password, adding an out-of-office message and so on


Reporting and Audit

This gives access to the reporting areas of Nova including pre-built reports and the Report Center.

On-premises agent


The following are the requirements for the Nova on-premises agent:

·The Azure Active Directory module for Windows PowerShell must be installed on the machine where you will install the on-premises agent.  This can be done via PowerShell with Install-WindowsFeature -Name RSAT-AD-PowerShell

·It must have 443 access to the Nova URL for the tenant. (This is called the endpoint address)

·It must be installed on a domain joined server. The server will need to have outbound ports 443 and 44388 open to the Autopilot application IP.

·It must have a service account that has Domain Admin rights in Azure Active Directory for each domain in the forest that the agent will manage. This is used for proxied administration.

·Service Account must be member of following groups in domain:

CN=Domain Admins,CN=Users
CN=Enterprise Admins,CN=Users

·The service account must have logon as service rights on the server.

·The agent must have a current .Net framework installed, as well as PowerShell 5.1 or above.

To obtain and install the agent:

1.Go to the On premises agent page.


2.Ensure that the web services URL is copied and saved, it will be used during the installation:


3.Download the agent

4.Run the installation, and follow the prompts.


NOTE: During the installation you will request a token on the following screen:


When prompted for an account to connect with, use the same Global Admin account which was used for the Service Account.


Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating