Chapter 2: Overview of NMS in the cloud

This chapter discusses NMS in the cloud; how it works, how it differs from hosting an on-premise NMS, and how to upgrade to NMS in the cloud.

Overview of NMS in the cloud

Nuance Management Server (NMS) in the Cloud stores data objects on the cloud server in the

Nuance data center. These objects include the following profile customizations: n

User account n

Text and Graphics/auto-texts n

Custom words n

Custom Command Sets

Storing objects in NMS in the cloud allows organizations that have more than one Nuance product to share data across multiple Nuance applications. For example, if an administrator at an organization creates an auto-text in the Nuance Management Console, that organization's users can see and use that object with Dragon NaturallySpeaking Professional as well as any application that uses Speech Anywhere Services.

What will be different when you migrate to NMS in the cloud?

This section describes what you can expect when moving or upgrading to the NMS in the cloud configuration.

Note: Text and Graphics and DragonTemplates are supported. Text and Graphics with Lists are not supported.

n

NMS is hosted in the Nuance Data Center instead of being hosted in your organization.

n

The cloud NMS stores all the Dragon user settings. n

Management - Your administrators access the cloud Nuance Management Console to configure and manage users. This provides the administrators with one place where they can view and manage all product licenses for NMS supported products.

25

Dragon NaturallySpeaking 13 Administrator Guide n

Shared content (profile sharing) with other Nuance products. Text and Graphics/autotexts and custom words can be shared between DNS Professional and

SpeechAnywhere Services powered third party applications.

n

Single and centralized cloud management of products.

n

Management of cloud Text and Graphics/auto-texts using the cloud Nuance

Management Console.

n

Management of Dragon and NMS settings that was previously accomplished using the on-premise Nuance Management Console is now done using the cloud/hosted

Nuance Management Console.

n

User profiles are enhanced with customizations; auto-texts and custom words that are defined at the Site or Group level.

n

Importing, exporting, and deletion of user profiles is not available in the cloud NMS.

These features have been moved to the Dragon client for Dragon NaturallySpeaking

Professional.

n

An administrator can back up and restore a user account from the User Accounts screen.

n

In some cases, you may need to install and configure an NMS “Local Authenticator” when on-premise LDAP or Active Directory support is required.

n

Speech node collections are defined at the organization level. n

NMS download packages are distributed to individual organizations instead of to everyone on the system.

n

You can add comments to organization tokens n

The Organization Tokens tab and Credentials tab are visible to all administrators.

Managing user logins

User logins in the cloud must be unique. If a user’s login is being used by a user in another organization in the cloud NMS, this is a user login conflict that needs to be resolved before the user can be migrated to the cloud NMS. For example, if you are upgrading "Bob" to NMS in the cloud, and user login "Bob" already exists in the cloud NMS, this is a naming conflict. For more details, see Move data from an existing user to the cloud NMS server.

Organizations using LDAP/AD

If you are using LDAP or Active Directory to authenticate users, there should be no conflicts when moving to the cloud. The NMS uses a “domain” along with the login which maps to a unique organization.

1. Install and configure the NMS Local Authenticator.

2. Minor configuration of the NMS Local Authenticator is required which basically consists of setting a domain name and the LDAP address where non-trusted LDAP/AD functionality

is required. For details, see Install the Local Authenticator .

Organizations using NMS native credentials

If you are using NMS native logins to authenticate users, when you move to the cloud, the

NMS native logins may conflict with existing user accounts. For example, if your organization has a user login called “bob” and a user login called “bob” is already in use in the cloud system, you must change the user login before you can move that user account to NMS in the cloud. The Local Authenticator is not required.

26

Chapter 2: Overview of NMS in the cloud

The Cloud Migration tool considers a user account on an on-premise NMS and a user account on the cloud NMS to be the same if their user logins are the same and both accounts belong to the same organization.

Using the Profile Association Tool

The Profile Association tool is only required for US customers that are upgrading from a version of DNS Professional that does not support NMS in the cloud.

Administrators install the Profile Association Tool in a location that: n

Has access to the profile store n

Communicates with the NMS in the cloud

The workflow for using the profile association tool is: n

Nuance sets up an Organization for your organization in the cloud NMS.

n

Your administrator uses the cloud Nuance Management Console to create user accounts n

Your administrator runs the standalone Profile Association Tool to:

n

Search the user profile store for available user profiles that require user accounts n

Search the cloud NMS server for user accounts that need user profiles n

Allows the administrator to map the user profiles to the user accounts.

Authentication

After you upgrade a user account or a Dragon client to Nuance Management Server (NMS) in the cloud, users must log into the system using the Dragon client in connected mode. This action authenticates the user with the NMS and allows them to later use Dragon in disconnected mode.

The user cannot use Dragon in disconnected mode until they first login to Dragon in connected mode.

The following only applies to organizations that are using LDAP/Active Directory SSO for authentication. NMS native credential users do not require the Local Authenticator.

Since the NMS is no longer on-premise, you must install and configure the “NMS Local

Authenticator” to query your LDAP/Active Directory store and validate user credentials. You install the “NMS Local Authenticator” at your site and configure your Dragon Clients to point to the Local Authenticator. The Local Authenticator tests the user credentials and sends authentication requests to the cloud NMS to retrieve data.

Profile importing, exporting, and deleting

Since the NMS in the cloud does not have access to the profile store, this functionality is no longer available in the Nuance Management Console. Instead, it is available and performed through the Dragon Client.

If an administrative task requires the importing, exporting, or deletion of user profile(s), someone must perform these actions on the Dragon workstations. For details, see the

Dragon Help.

27

Dragon NaturallySpeaking 13 Administrator Guide

Overview of Installing and Configuring NMS in the Cloud

This section provides an overview of how to install and configure Dragon NaturallySpeaking

Professional with the Nuance Management Server (NMS) in the cloud. For a detailed list of steps and prerequisites, see Dragon in the Cloud Installation Checklist in the Dragon

NaturallySpeaking Professional Installation Guide.

Overview of Installing and Configuring NMS in the Cloud

You will complete the following steps to install and configure Dragon NaturallySpeaking

Professional with the Nuance Management Server (NMS) in the cloud:

1.

Before You Begin

2.

Set Up Your roaming user profile Host Machine

3.

Install the Local Authenticator (Optional)

4.

Install and Configure Dragon clients

Before You Begin

Before you begin, Nuance will send you a welcome email containing the information that you need to install and configure NMS in the cloud, including: n

The URL for NMS in the cloud.

n

Your Organization ID.

n

Your administrator user name and password.

n

An alphanumeric token that you will need to install the Local Authenticator.

Keep this information on hand; you will need it as you install and configure DNS Professional with NMS in the cloud.

Install the Local Authenticator

If you want to use LDAP or Active Directory Single Sign On for your authentication, and are using NMS in the cloud, you must install the NMS Local Authenticator.

The cloud NMS cannot test LDAP credentials inside your organization. The NMS Local

Authenticator fills this gap by testing LDAP credentials. If they pass verification, the Local

Authenticator sends the credentials to NMS in the cloud for processing.

You install the Local Authenticator on a local server that is accessible to both the cloud NMS and your Dragon Clients. Once a client authenticates with the Local Authenticator, the cloud

NMS server is used for all other client requests; using the session the client was granted during authentication.

If you want to use Dragon's native authentication, you do not need to install the Local

Authenticator.

See Installing the Dragon Client in the Dragon NaturallySpeaking Professional Installation

Guide for instructions on how to install the Local Authenticator.

Set Up Your roaming user profile Host Machine

Set up the machine that will host your roaming user profiles. For more information, see

Setting up the roaming user profiles machine and Checklists for Setting up a file server for

roaming user profiles in the Dragon NaturallySpeaking Professional Installation Guide.

28

Chapter 2: Overview of NMS in the cloud

Install and Configure Dragon NaturallySpeaking Professional Clients

Follow the instructions in the "Installing the Dragon Client" chapter of the DNS Professional

Installation Guide to install the latest Dragon Professional clients and configure them to use either NMS in the cloud or the Local Authenticator.

Setting the NMS download location

1. In the Nuance Management Console, in the Organizations section, click Organization

Overview.

2. In the Organizations section of the ribbon, click Details.

3. On the Products tab, expand the DNS Professional section.

4. In the Downloads section, select Download from cloud.

5. Click OK.

Logging existing and new users into NMS in the cloud

When a user logs into the Dragon client, Dragon queries NMS to get the user login information for the user. Dragon uses the login to find the user profile folder for the user.

In all versions of NMS, user logins must be unique.

NMS introduces changes that make it easier to move users to NMS in the cloud. When you move a user to NMS in the cloud, and the user login already exists in the cloud, that user login will have to be changed as a part of the migration process. To avoid having to rename the user profile folder, NMS provides Dragon with the user profile folder name (instead of the user login). Dragon uses this information to find the profile folder for the user and log them into the system.

For a new user, the NMS generates a folder name using the format login_GUID and returns this to Dragon. Dragon uses this value to create the profile folder for the new user. NMS only appends the GUID to the profile folder name, not to the user profile.

For example, for a new user profile "bob", the NMS generates the folder name: “bob_

35B5CB9B-922B-47FB-AA20-AE2E515D9802”.

"bob' is the name of the profile and is stored in the folder “bob_ 35B5CB9B-922B-47FB-

AA20-AE2E515D9802”.

When the user logs into Dragon, NMS authenticates the user’s credentials and returns a unique name for Dragon to use to create the user’s profile location.

After you upgrade a user account or a Dragon client to Nuance Management Server

(NMS) in the cloud, users must log into the system using the Dragon client in connected mode. This action authenticates the user with the NMS and allows them to later use

Dragon in disconnected mode.

The user cannot use Dragon in disconnected mode until they first login to Dragon in connected mode.

29