Chat now with support
Chat with Support

On Demand Global Settings Current - User Guide

Adding users to an organization

Adding users to an organization

Once you have created an organization, you can add additional users and determine what tasks each user can perform.

For a list of access control procedures, see the task flow Adding a user and assigning a role.

Users and roles

When you add a user to an organization, you also assign one or more roles. The role assignment determines what permission level a user has and ultimately, what tasks the user can perform. Assigning roles and setting user permissions is referred to as access control.

Access control is a process by which users are granted access and certain privileges to systems, resources, or information. In Quest On Demand, you can grant authenticated users access to specific resources based on your company policies and the permission level assigned to the user.

On Demand comes configured with a number of default roles. The default role permissions settings cannot be changed, but you can create custom roles with specific permission settings to align with your company policies. You can assign multiple roles to each user in order to combine permission sets.

NOTE: Every user must be assigned to at least one role. You cannot remove all roles from a user.

Default roles and their permission settings are described below.

The On Demand access control interface is comprised of two pages.

Default roles

Quest On Demand is configured with default roles that cannot be edited or deleted. You can duplicate default roles to create custom roles. The default roles are listed below.

On Demand administrator

On Demand administrators have full access to global settings and all modules. The user who signed up for On Demand and created the organization is automatically assigned the On Demand Administrator role.

Module administrator

Module administrators only have access to the specific module where they have been added as an administrator. Module administrators do not have access to global settings or tenants.

Default role permissions

Role Permissions

On Demand Administrator

(also has all module permissions)

  • Can rename the organization
  • Can read access control roles
  • Can create, delete, and assign access control roles
  • Can add and remove tenants
  • Can read Activity Trail
    • Specific services can be selected for this permission.
Recovery Administrator
  • Can manage backup settings
  • Can download hybrid credentials
  • Can run backup manually
  • Can unpack backups
  • Can run difference Report
  • Can restore from objects
  • Can restore from differences
  • Can read backup history
  • Can read unpacked objects
  • Can read differences
  • Can read task history
  • Can read events
  • Can read restore attributes
  • Can read UI projects
  • Can read UI collections
  • Can manage events
  • Can manage project settings
Audit Administrator

Can configure auditing and manage searches

Specific services can be selected for this permission.

Group Management Administrator
  • Can configure and manage group management
  • Can approve ,reject, or cancel a request
Migration Administrator Can configure and execute migrations
License Management Administrator Can read licenses

 

Adding a user and assigning a role

The flow chart below shows the process for adding users and assigning a role. The first step is to view the default role permissions settings. If required, you can create custom roles with specific permission settings to align with your company policies.

Once you have added a user, you must invite the user to sign in to the organization.

Viewing role permissions
Creating a custom role
Adding a user and assigning a role
Inviting new users

 

Access Control: Roles

Each access control role has a specific set of permissions that determines what tasks a user assigned to the role can perform . Your Quest On Demand organization comes configured with a number of default roles. The default role permissions settings cannot be changed, but you can create custom roles with specific permission settings to align with your company policies.

 

NOTE: To manage access control roles, you must have the permission "Can create, delete, and assign access control roles".

Perform the following tasks from the access control Roles page:

 

Viewing role permissions

Use the Roles page to view the list of roles defined for your organization. You can also view the users assigned to each role.

To view roles and permissions:

  1. In the side navigation panel, expand the Access Control item and select Roles.
  2. Click on a role name to open a read only page that displays the Role Permissions.

    The panel on the right is a list of users assigned to the role.
  3. To add users to the role, see Access Control: Users.

 

Creating a custom role

You can create roles with a custom set of permissions. Default roles cannot be edited. You must create a custom role to enable editing.

To create a role:

  1. In the side navigation panel, expand the Access Control item and select Roles.
  2. At the top right of the Roles page, click Create Role.

    Note that you can define a role based on an existing role. In the Roles list, click on the Action menu for a role and select Duplicate.
  3. On the Create Role page, enter a Role Name and Description.
  4. Under Role Permissions, select the check boxes for the permissions you want to assign to the role.
    Some role permissions are partitioned into services. If available, you can configure access to a service using the Selected Services field.
  5. At the top right of the page, click Create Role.

    You are returned to the Roles page and there is a prompt to Assign Users.
  6. To add a user to the role, click Assign Users.
  7. In the Add User to <custom_role> field, enter the email address of the user you want to add.
  8. Click Add User.
    Note that if the user is not currently a member, they are added to the organization.

 

Editing a custom role

Note that you cannot edit a default role. You can duplicate a default role and edit it to create a custom role.

To edit a role:

  1. In the side navigation panel, expand the Access Control item and select Roles.
  2. In the Roles list, click on the Action menu for a role and select Edit.
  3. On the Edit Role page. you can edit:
    - Name
    - Description
    - Role Permissions.
    Some role permissions are partitioned into services. If available, you can configure access to a service using the Selected Services field.
  4. Click Save.

    You are returned to the Roles page and there is a prompt to Assign Users.
  5. To add a user to the role, click Assign Users.
  6. In the Add User to <custom_role> field, enter the email address of the user you want to add.
  7. Click Add User.
    Note that if the user is not currently a member, they are added to the organization.

 

Adding a user to a role

NOTE:Email notification

When a user is added to a role, the user receives an email informing them of the action.

To add a user to a role:

  1. In the side navigation panel, expand the Access Control item and select Roles.
  2. In the Roles list, click on the Action menu for a role and select Assign Users.

    The Assign Role page opens.
  3. In the Add a user to this role field, enter the email address of the user you want to add.

    The user name must use the email address format <local_part>@<domain>
  4. Click Add User.
    The user is assigned to the role and has the permission set defined by the role.

 

Deleting a custom role

You cannot delete a default role.

Before deleting a role, you must remove all users from the role and either assign them a new role or remove them from the organization.

To delete a role:

  1. In the side navigation panel, expand the Access Control item and select Roles.
  2. In the Roles list, click on the Action menu for a role and select Delete.
  3. In the confirmation window, click Delete.
    You are returned to the Roles page.

 

Access Control: Users

Organization user credentials are based on email addresses. To log in to Quest On Demand using the email address, the user must create a Quest On Demand account with the email address. To create an Quest On Demand account, see Signing up and creating an organization.

Perform the following tasks on the access control Users page:

Once you have added a user, inform them that they have been added to an organization and specify the email address or Azure AD account used. Direct the new users to sign in to the organization using the procedures under Inviting new users.

 

Adding a user to your organization and assigning a role

Quest On Demand is configured with default roles. To create a custom role, see Access Control: Roles.

NOTE:Email notification

When a user is added to a role, the user receives an email informing them of the action.

To add a user:

  1. In the side navigation panel, expand the Access Control item and select Users.
  2. In the User Name field, enter the email address of the user you want to add.

    The user name must use the email address format <local_part>@<domain> .
  3. In the Assigned Role field, enter the role name. An auto-complete list offers suggestions based on your input.

    You must select a role to enable the Add button.
  4. Click Add.

 

Editing user roles

Quest On Demand is configured with default roles. To create a custom role, see Access Control: Roles.

NOTE: Email notification

When a role is added to or removed from a user, the user receives an email informing them of the change.

To assign a new role:

  1. In the side navigation panel, expand the Access Control item and select Users.
  2. In the list of users, locate the user you want to edit in the User Name column.
  3. On the right side of the Role field for the user, click the edit icon to make the Role field editable.
  4. Click inside the editable Role field and begin typing the name of the role you want to add. An auto-complete list offers suggestions based on your input.
  5. Enter the role name you want to add. An auto-complete list offers suggestions based on your input.
  6. Select the role from the list.
  7. Add additional roles or remove assigned roles as required.
  8. Click the check mark to confirm the role assignment.

 

Removing a user from the organization

NOTE: Email notification

When a user is removed from the organization, they receive an email informing them that they no longer have access to the organization.

  1. In the side navigation panel, expand the Access Control item and select Users.
  2. In the list of users, locate the user you want to delete in the User Name column.
  3. In the Action field for the user, click the delete icon.
  4. In the confirmation window, click Remove.

 

Inviting new users

Once you have added a user, inform them that they have been added to an organization and specify the email address or Azure AD account used. Direct the new users to the following procedures to sign in to the organization.

Creating a Quest account and joining an existing On Demand organization
Joining an existing On Demand organization
Joining an existing On Demand organization with an Azure AD account

 

Creating a Quest account and joining an existing On Demand organization

This procedure is for new On Demand users. You do not need to create a Quest account to join an existing On Demand organization. However, creating a Quest account allows you to access On Demand resources such as the support site.

If do not want to create a Quest account or you already have an On Demand account and an administrator has added you to their organization, see Joining an existing On Demand organization.

Prerequisites
  • You must have a valid email account where you can receive a verification email from support.quest.com.
  • An On Demand administrator for the organization must have added you to the organization by adding your email address on the "Permissions" page. See Permissions.

To join an organization:

  1. Go to the web page quest-on-demand.com and under Create a Quest account click Sign Up.

    The "Create a Quest Account" page opens.

  2. Enter your credentials for your new Quest account.

    Note that the email and password entered here wil. be the credentials you use to sign to On Demand.

  3. Click the check box to agree to Quest’s privacy policy and terms of use.

  4. Click Sign Up.

    The “We’ve sent you an email” page opens.

  5. Go to your email account and open the email from support.quest.com.

  6. Click on the Verify email address link.

    The On Demand home page opens. You are signed in to the organization that your were added to.

 

Joining an existing On Demand organization

This procedure is for users that want to join an existing organization.

Prerequisites
  • An On Demand administrator for the organization must have added you to the organization by adding your email address on the "Permissions" page. See Permissions on page 16.

NOTE: An administrator can add you to an organization by specifying your Azure AD account. See Joining an existing On Demand organization with an Azure AD account.

  • If multiple On Demand organizations are associated with your email account, you must know the name of the organization you want to sign in to. After sign in, the "Select Organization" page is displayed where you must select the organization where you want to sign in to.

To join an organization:

  1. Go to the web page quest-on-demand.com.

    The "Welcome to Quest On Demand " page opens.

  2. Under Already have an account, click Sign In.

    The "Sign in" page opens.

  3. Enter your email account credentials.
  4. Click Sign In
    • If only one organization is associated with your email account, the On Demand home page opens. You are signed in to the organization that your were added to.
    • If there are multiple organizations associated with your email account, the “Multiple Organizations Found” page opens with a list of organizations. Click the organization you want to sign in to and then click Select Organization.

 

Joining an existing On Demand organization with an Azure AD account

You can use your Azure AD account to join an existing On Demand organization. Using your Azure AD account is referred to as federated identity management.

Federated identity management can increase security and lower risk by enabling an organization to identify and authenticate a user once, and then use that identity information across multiple systems, including external partner websites such as On Demand.

Prerequisites
  • An On Demand administrator for the organization must have added you to the organization by adding your Azure AD account on the "Permissions" page. See Permissions on page 16.
  • If multiple On Demand organizations are associated with your Azure AD account, you must know the name of the organization you want to sign in to. After sign in, the "Select Organization" page is displayed where you must select the organization where you want to sign in to.

To join an organization with an Azure AD account:

  1. Go to theweb page quest-on-demand.com.

    The "Welcome to Quest On Demand " page opens.

  2. Under Already have an account, click Sign In.

    The "Sign in" page opens.
  3. At the bottom of the page, click Sign in with Microsoft.
    • If only one organization is associated with your Azure AD account, the On Demand home page opens. You are signed in to the organization that your were added to.
    • If there are multiple organizations associated with your Azure AD account, the “Multiple Organizations Found” page opens with a list of organizations. Click the organization you want to sign in to and then click Select Organization

Tenant Management

Tenant Management

A tenant is a dedicated instance of Azure Active Directory (Azure AD) that your Microsoft organization receives and owns when it signs up for a Microsoft cloud service such as Azure or Office 365. For more information, see this Microsoft help page.

This section contains information on adding and removing tenants.

Tenant overview

Number of users in the tenant

On the Tenants page, each tenant tile lists the number of Users in the tenant. The user count is divided into Cloud only and Hybrid users. Hybrid users are Microsoft identities that can access both on-premises and cloud based resources.

Azure AD tenant

A tenant houses the users in a company and the information about them. You must add a tenant in order to manage the tenant properties using an On Demand module.

Applications used to manage Azure AD tenant properties must participate in the consent flow provided by Azure AD. This means an Azure Global Administrator must provide admin consent when adding a tenant to On Demand. Admin consent is granted on behalf of the Microsoft Azure organization.

B2C tenants

In addition to the standard Azure AD tenant, you can also add an Azure AD B2C tenant. On the Tenant page, Azure AD B2C tenants can be distinguished by the following icon next to the tenant name:

For more information on B2C tenants, see this Microsoft help page.

Azure Global administrator

The Azure Global Administrator role is the top level administrator role and has access to all features. By default, the person who signs up for an Azure subscription is assigned the Global Administrator role for the tenant. Additional users can be assigned to the Global administrator role.

In On Demand, once you select Add tenant, you are redirected to the Microsoft tenant administration login page where you must log in with the Global Administrator credentials for the tenant. Then, you are redirected to a page that lists the permissions that will be granted. You must click Accept and provide admin consent for the On Demand application. Once the Global Administrator adds a tenant to On Demand, an application record is created in the tenant indicating that admin consent has been provided.

NOTE: Global Admin credentials are only required to grant admin consent for the minimal list of permissions required by On Demand. Global Admin credentials are not stored, share, or used for any other purpose.

Admin consent permission levels

For security, when you first add a tenant, only the minimum permission settings are granted. Some modules require additional permissions. Once a tenant has been added to On Demand, you can grant additional permissions on the Admin consent status page.

Adding a tenant

Prerequisites

Admin consent is required to add a tenant to On Demand. Since only an Azure Global administrator can grant admin consent, you must be able to provide Azure Global administrator credentials for the tenant you are adding.

To add a tenant:

  1. Log in to On Demand using the credentials you used to sign up for On Demand.

  2. In the navigation panel on the left, click Tenant.

  3. On the Tenant page, click Add tenant.

    You are redirected to the Microsoft login page.

  4. Enter the Azure AD Global Administrator credentials and click Next.

    A page opens with the list of permissions settings you are granting.

  5. Click Accept.

    You return to the On Demand Tenants page.

  6. On the Tenant page, at the bottom of the tile for the newly added tenant, click Go.

    The admin consent status page opens.

  7. If the minimum permission settings granted when the tenant was added are sufficient for a module, the Status for the module is Uses Base. If the module requires additional permissions, the Status is Not Granted.

    If required, to accept additional permissions for a module, click Grant Consent.

    You are redirected to the Microsoft login page.

  8. Enter the Azure AD Global Administrator credentials and click Next.

    A page opens with the list of permissions settings you are granting.

  9. Click Accept.

    You return to the On Demand Tenants page.

 

Admin consent

 

Admin consent status

To open the Admin Consent status page, click Tenants in the navigation page and then click Go on the tenant tile.

On the Admin Consent status page, you can view the module admin consent status for each tenant you have added. The process of approving the use of an application for the whole Microsoft Azure AD organization by the Microsoft Global administrator is referred to as admin consent. The Microsoft Global administrator must provide admin consent when adding a tenant to On Demand. When a tenant is first added, On Demand requests base admin consent permissions. Some modules can function using the base permission set while other require a higher level of admin consent permissions.

To view admin consent status:

  1. Click Tenants in the navigation panel on the left.
  2. At the bottom of a tenant tile, click Go.

    The admin consent status page for the tenant opens.

The Status column indicates if admin consent has been granted for a module. If the current status is Not Granted, enable a module for this tenant by clicking Grant Consent in the Actions column.

NOTE: If additional admin consent permission is required to perform specific tasks within a module, these items are listed beneath the main admin consent item for the module.

Granting consent

For the following scenarios, click Grant Consent in the Actions column.

  • Admin consent has been revoked in the Azure AD portal, resulting in a status of Revoked.
  • The admin consent token for the module has expired, resulting is a status of Token Expired. This can occur if the Azure Global Administrator account used to grant consent has changed (deleted, role change, password change).
    Note that a Token Expired status is not serious and has a limited impact on Quest On Demand operation.

 

Revoking admin consent

Completely revoking admin consent removes all permissions granted for the On Demand application. This action is usually performed as part of the process of removing a tenant. Revoking admin consent is a manual process that must be performed in the Azure portal.

Revoking admin consent in the Azure Portal

Revoking admin consent removes all permissions granted for the On Demand application.

To revoke admin consent:

  1. Log in to the Azure Resource Manager with the credentials for the tenant Active Directory.
  2. Click on the Azure Active Directory icon in the left menu.
  3. In the Active Directory panel, select Enterprise applications.
  4. In the Enterprise applications panel, select All applications.
  5. Select the Quest On Demand application.

    The On Demand application Overview displays in the main panel.

  6. At the top of the main panel, click Delete.

 

Removing a tenant

You can remove a tenant from On Demand. Removing a tenant disables all module functions related to the tenant. Active backups and provisioning actions are canceled.

NOTE: To restore a tenant and all the associated On Demand configuration, contact Quest Technical support.

Tenant restore is possible for up to 30 days after it has been removed. You must provide the tenant name and your organization ID. See Displaying the organization ID.

To remove a tenant:

  1. Click Tenants in the navigation panel on the left.
  2. On the tenant tile for the tenant you want to remove, click the menu icon on the right side of the title bar.
  3. Click Remove.

Once you add a tenant to On Demand, an application record is created in your tenant indicating that you have agreed to admin consent. When you remove a tenant from On Demand, this record is not removed and admin consent access remains. You must log in to Azure and manage access to the application.

 

On Demand Home page

On Demand Home page

The Home page contains the following components.

Masthead The masthead displays your current user ID and provides information about your organization.
Side navigation panel The side navigation panel is always available as you move through the On Demand site.
Dashboard In addition to a tile for each module, the Dashboard displays statistics and operational data for your tenant.

Masthead

The masthead displays the Quest On Demand name on the right and on the left:

  • Your user ID with a drop down menu arrow.
  • An information icon (i) that opens the On Demand information window.

Masthead drop-down menu

Clicking anywhere on your user ID opens the drop-down menu to perform the following tasks:

  • View your current Region Name and Organization Name.
  • Perform organization management (see Managing organizations and regions).
  • Configure your user settings by clicking My Account.
    • Use of Cookies: You can enable or disable the use of a cookie for session monitoring. The initial state of this setting is determined by your response to the cookie notice when you join an organization. Note that this setting is by region. If you join an organization in a different region, you receive the cookie notice again.
  • Sign Out from your current session. Note that you are automatically logged out after 30 minutes of inactivity.

Information window

The On Demand information window contains the following tabs:

  • About: Version numbers and copyright information.
  • Third Party: The list of third party components used in the product. This information is also contained in the Release Notes.
  • Contact: Information on how to contact Quest Technical support.

Side navigation panel

Minimize the panel

Click on the arrow at the top to minimize the side navigation panel.

My Dashboard

Click to return to the Home page.

Tenants

Opens the Tenants page. For information, see Tenant Management.

Module links

Use the module links to quickly open a module page.

Access Control

Manage users and their assigned roles. See Adding users to an organization.

Services

Provides information on all available modules and provides a link to the Quest product page for the module.

Help and Release Notes
  • Help opens a User Guide
  • Release Notes opens a document with information on the currently deployed software version and technical support information.

When you are on the Home page, the Global Settings documents open. When you are on a module page, these links open the documentation for the module.

Settings

 

 

Dashboard

The Quest On Demand dashboard is shown below. The dashboard contains the following components:

Tenant filter

Located in the top right of the dashboard, the tenant filter determines what data is displayed on the dashboard. You can choose to display all tenants, a subset, or a single tenant.

Tenant summary

The tenant summary indicates which teants are currently selected and provides a summary of licenses, users and groups in the selected tenant.

 

Needs your attention!

The Needs your attention! tile displays a summary of alerts and cautions from all of the modules you are currenlty subscribed to. It also displays information on the status of your subscription or trial if it is close to expiry.

Module tiles

If you have a subscription to a module, the module tile displays status information for your tenant.

 

Settings

Settings

 

Activity trail

An activity trail is a set of records that provide documentary evidence of the sequence of activities that have affected at any time a specific operation, procedure, or event. The information recorded includes date and time, user name, and a description of the event.

On Demand retains the complete activity trail history for an organization. You can specify the start and end dates for an activity trail log download.

The following activity trail logs are available:

  • Global Settings: Records information for:

    • add and remove tenant events
    • granting of admin consent for a tenant
    • assigning and unassigning a user to be an On Demand Administrator
    • notification events
  • Recovery: Records information on backup enable and disable events.

 

Downloading activity trail logs

To download activity trail logs:

  1. In the side navigation panel, click Settings.

  2. In the main panel, under Modules, select Global Settings or a module type.

    By default, the date fields are configured to download logs from the last seven days.

  3. To change the start or end dates, click on the date fields and select a date from the calendar window.
  4. Click Download.

    A zip file containing a comma separated values (.csv) file is downloaded.

 

Agents

A local agent is required to query and perform management actions on on-premise Active Directory objects. Agents run as a service on a machine in the local network. The machine must have sufficient privileges to perform the actions required. You must install the agent on the local machine.

This section contains information on installing and configuring an agent.

NOTE: For more information on an agent for a specific module, see the module User Guide.

 

Installing an agent

  1. On your local machine, create a folder to store the agent install file and installation key.
  2. In the On Demand navigation panel, click Settings.
  3. In the main panel menu bar, click Agents.
  4. Under Download Agent, click Download and save the file in the folder you created.
    If your browser automatically saves the file in a default folder, locate the file and copy it into the folder you created.
  5. Go to the folder you created and extract the contents of the zip file into the folder. An Agent folder is created.
  6. Return to the On DemandSettings > Agents page and under Generate Installation Key, click Generate and save the generated file in the Agent folder. If your browser automatically saves the file in a default folder, locate the installation key file and copy it into the Agent folder.

    NOTE: If you do not copy the key file into the Agent folder, you will be prompted for the path to the file during the installation.
  7. In the Agent folder, double click Setup.exe.
    A console window opens.
  8. In the console window, you are prompted to confirm the installation. Type y and press Enter.
  9. You are prompted to enter the Agent name. Press Enter to accept the default or type a name and press Enter .
    The agent is installed and the console window closes.
  10. Return to the On DemandSettings > Agents page and click Refresh.
    In the Modules pane, the agent name is listed under the Group Management module.
  11. Click on the agent name to display the Agent Information.

 

Adding domains to the agent

For modules that support on premises Active Directory domains, the domain name must be added to the domain list. The agent validates the domain name when it is added. For example, if you add domain xyz.corp and it does not exist or cannot be connected to, you receive an error.

Note that the agent must be enabled and online to add a domain name to the list. Check the Enabled and Online icons at the top left of the Agent Information fields.

To add a domain:

  1. In the On Demand navigation panel, click Settings.
  2. In the main panel menu bar, click Agents.
  3. In the Modules panel, select the module name for the agent.
  4. The Domains field is below the Agent Information. Enter a domain name in the text box and click Add.
    If the operation is successful, the domain is added to the domain list.

 

Enabling and disabling the agent

If an agent is enabled it is returned in a request for available agents within the organization. For example, a service may request an agent for domain xyz.corp in organization A. The agent management service looks for all enabled agents that support domain xyz.corp for organization A. Any agents that have been disabled are ignored. If the agent has been disabled it is not used.

To enable or disable an agent

  1. In the On Demand navigation panel, click Settings.
  2. In the main panel menu bar, click Agents.
  3. In the Modules panel, select the module name for the agent.
  4. The Enabled / Disabled toggle is at the top left of the Agent Information fields.
  5. Click on the toggle to change the state of the agent.

Note that you can start and stop the agent from a console window. See Additional agent commands.

 

Uninstalling the agent

Prerequisites

You must know the location of the agent setup.exe file. See Installing an agent

To uninstall an agent:

  1. Open a console window and navigate to the folder where the agent setup.exe file is located.
  2. Type setup.exe uninstall and press Enter.
  3. You are prompted to confirm the uninstall. Type y and press Enter.

 

Additional agent commands

The following commands and switches can be used from the Windows console command line. To use a command or switch, you must first navigate to the folder where the agent setup.exe file is located or provide the path to the file as part of the command syntax.

Prefix each command or switch with setup.exe. For example setup.exe install.

Type Syntax Description
Command

install

or

i

Installs the agent.
Command

uninstall

or

u

Uninstalls the agent.
Switch -q Do not ask for install or uninstall confirmation.
Switch

-keyfile

or

-kf

The full path to the agent installation key file.
Switch -key A string representation of the installation key.
Switch

-name

or

-n

The name of the agent.
Switch -user The username to run the Windows service under.
Switch -password The password for the username of the Windows service account.
Command start Starts the agent.
Command stop Stops the agent.
Command restart Restarts the agent.
Command status Gets the status of the agent. Status can be Running or Stopped.
Switch

-h

or

-?

Displays the help screen.

 

Notifications

A Quest On Demand notification is an email sent to one or more recipients following an event. For example, after a backup failure event, specified recipients receive a notification email.

Table 1: Supported notifications
Module Event
Recovery Backup failure

Configuring notification recipients

To add notification recipients for an event:

  1. In the side navigation panel, click Settings.

  2. In the main panel, click Notifications in the menu bar.
  3. Under Modules, select a module type and then, an event type.

  4. In the Set the recipients text box, enter the email address for a recipient and click Add.
    The recipient is listed below the text box.
  5. Repeat step 4 to add more recipients.
  6. Click Save.
    The next time the event occurs, all the listed recipients receive a notification email.

 

Subscriptions

This section contains the following topics.

Subscription details The Subscriptions page contains the details of your current subscriptions.
Managing subscriptions Quest On Demand subscriptions are associated with an email address. In order to activate a subscription, the email address of the subscription owner must be added to the Subscription Owner list.
Subscription expiry To prevent loss of data, subscription expiry takes place in stages.

 

Subscription details

Click the module name to get information on product subscription details and pricing as well as links to Quest sales support.

Table 2:

Subscription field descriptions

Field Values Description
Modules Module Name

The module name.

Modules may offer separate licenses for specific features.

Features Feature Name A feature is the smallest subscription unit. Features can be bundled into Standard, Premium, and Enterprise offerings.
Subscription Type Standard, Premium, or Enterprise The organization has purchased a subscription to features offered by this module. The specific subscription type depends on the number of features purchased.
Trial

The organization has subscribed to a trial license. Module features may be limited.

Note: When moving from Trial to Paid, the user associated with the paid subscription must be an organization administrator. See Managing organizations and regions.

Technical Preview

The organization has subscribed to a technical preview license. Module features may be limited.

Not subscribed The organization is not subscribed to this module.
Expiry Date mm/dd/yyyy The date on which the subscription will expire. See Subscription expiry
Rate Plan Prepaid A set number of licenses have been purchased.
Overage The organization is billed for licenses as they are consumed.
Licenses #### The number of licenses purchased ( if the Rate Plan is Overage).
Used #### The number of licenses currently consumed.

 

Managing subscriptions

Quest On Demand subscriptions are associated with an email address that was used to purchase the subscription. All valid email address formats are supported. The email address does not need to be associated with a Quest account.

In order to activate a subscription, the email address of the subscription owner must be added to the Subscription Owners list on the Settings > Subscriptions > Shared Subscriptions page. A subscription owner can share subscriptions with multiple organizations.

Adding a subscription owner to the Subscription Owners list does not add the user to the organization. A subscription owner does not have sign in capability or any other permission settings. To add a user to an organization, see Adding users to an organization.

Sharing a subscription

To share a subscription with the organization, request permission from the subscription owner to add their email address to the Subscription Owners list. If the request is accepted, all subscriptions associated with the email address are assigned to the organization. A subscription owner can share subscriptions with multiple organizations.

Note that a Subscription sharing status of Active indicates that the user has consented to share subscriptions. It does not indicate that a valid subscription is associated with the email address.

  1. In the side navigation panel, click Settings.
  2. On the Settings page, click Subscriptions in the top menu.
  3. At the top right, click Shared Subscriptions.
  4. On the Shared Subscriptions page, enter the email address of the subscription owner and click Request.
    The email address is added to the Subscription Owners lists with a Subscription sharing status of Pending.
  5. The subscription owner receives an email with a request to share the subscriptions associated with the email address.
    If the subscription owner accepts the request, the Subscription sharing status changes to Active and any subscriptions associated with the email address are added to the Subscriptions page.
  6. If Subscription sharing remains in the Pending state, you can choose to select Cancel Request from the Action menu.

Stop using a subscription

You can stop subscription sharing by removing the subscription owner's email address from the Subscription Owners list.

  1. In the side navigation panel, click Settings.
  2. On the Settings page, click Subscriptions in the top menu.
  3. At the top left, click Shared Subscriptions.
  4. In the Subscription Owners list, locate the email address of the subscription owner that will no longer share subscriptions with the organization.
  5. In the Action column for the subscription, select Stop Using Subscription.
  6. The confirmation window lists the subscriptions that will be removed from the organization. Click Stop Using Subscription.
    The subscription owner receives an email informing them that the subscription is no longer assigned to the organization. All subscriptions associated with the email address are removed from the Subscriptions page.

 

Subscription Owner when Moving from a Trial to a Paid subscription

The user that signed up for a trial subscription is automatically an administrator for the organization. If a different user email address is used for purchasing a paid subscription, this user address must be added to the Subscription Owners list before the subscription status displays as Paid.

If you need assistance determining the email address used to purchase the subscription or, if you want to change the address associated with the subscription, contact Technical support.

 

Subscription expiry

To prevent loss of data, subscription expiry takes place in stages.

Stage 1: Your subscription expires in X days

Thirty days prior to expiry, the On Demand organization administrator receives an email notification. From this time on, the module tile on the On Demand home page displays the number of days before the subscription expires.

Stage 2: Subscription expired. Access denied.

Once the subscription expires, members of the organization can no longer access the On Demand module. The configuration settings have been preserved and module services continue for the next 30 days.

Stage 3: Subscription expired. Service disabled.

After 30 days, module services are no longer operational for the tenants in the organization. Data is preserved for 30 days and then, it is permanently deleted.

Stage 4: Subscription expired. Data deleted.

Your data has been deleted and cannot be restored.

Related Documents