Nuance Management Center

ManualsBrandsNuance ScanSoft ManualsApplicationsDragon Professional Group

Table Of Contents

Configuration and client installation guide
About this guide
- Guide overview
  - Audience
- Additional resources
Chapter 1: Introduction
- About Nuance Management Center
- Physical architecture
Chapter 2: Installation checklists
- Checklist—Planning the server installation
- Checklist—Planning the client installation
Chapter 3: Preparing for your server installation
- Software requirements—Server
  - Application server and database server
  - NMC console
- Hardware requirements—Server
- Server installation prerequisites
  - Application server and database server
- NMC console
- Other considerations
- Obtaining required server software
- Opening required ports
- Installing the SSL certificate
Chapter 4: Installing the servers
- Installing SQL Server
- Installing Nuance Management Center
  - Install
Chapter 5: Post-installation tasks
- Configuring your network switch
- Verifying the NMS Platform service is running
  - Starting the NMS Platform service manually
- Logging in to the Nuance Management Center (NMC) console
- Determining your database backup method
Chapter 6: Preparing for your Active Directory single sign-on configuration
- Single sign-on overview
- Before you begin
- Creating an NMC console Administrator user for Active Directory
- Setting the Active Directory connection string
- Creating and configuring user accounts for single sign-on
  - Creating user accounts
  - Configuring user accounts
Chapter 7: Installing the Local Authenticator
- About the Local Authenticator
  - Local Authenticator logs
- Creating organization tokens
- Installing and binding the SSL certificate
- Installing the Local Authenticator
- Editing the configuration file
- Starting the Local Authenticator service
Chapter 8: Preparing for your Dragon Group client installation
- Software and hardware requirements—Client
  - Dragon Group hardware recommendations
  - Supported Virtual Desktop infrastructure applications
- Required skills for installing Dragon Group
- Dragon File Structure
  - Windows 7, Windows 8.x, and Windows 10
  - Accessing program files
- Assigning access
  - Assigning permissions
    - Clients
    - Roaming user profiles
- Configuring client workstations
Chapter 9: Installing the Dragon Group client
- Install Dragon and choose the default settings
Chapter 10: Installing the Dragon client with Settings
- Overview—Installing the Dragon client with initial settings
  - Prerequisites
- Push installations
  - Support for SMS and Windows Server with Active Directory
- Installing the same Dragon configuration on multiple computers
- Performing an administrative installation with a batch file
  - Understanding the script in admininstall.bat
  - Modifying admininstall.bat
- Command Line installation with msiexec.exe
  - Installing the same configuration on additional computer(s)
Chapter 11: Configuring the Dragon client for NMS
- Associating Dragon clients with the Nuance Management Center (NMC) server or ...
Chapter 12: Scheduling Optimization Tasks
- Using Acoustic and Language Model Optimizer and Scheduler tools
Chapter 13: Working with Custom Commands
- Using the Convert XML to DAT Tool
- Using the MyCommands Protection Utility
Chapter 14: Upgrading the Dragon client
- Preparing to upgrade Dragon
- Upgrading Roaming User Profiles
  - Before you upgrade
  - After upgrading Roaming user profiles
- Upgrading Your Dragon installation from the Command Line
- Upgrading with msiexec.exe
- Upgrading user profiles
  - Running the Upgrade User Profiles Wizard
  - Importing custom words and commands
Chapter 15: Managing Logs and Errors
- Dragon logs
  - Dragon client logs
  - Usability logs (Stand-Alone mode only)
- Handling Dragon error messages
- Accessing the Dragon Knowledge Database
Chapter 16: Using Dragon over a remote desktop connection
- Use Dragon through a remote desktop connection
- Remote desktop connection support
- Support for dictation sources over a remote desktop connection
- System Requirements for using Dragon through a remote desktop connection
- Installing Dragon on the server and the client
- Configuring the Windows server
- Configuring Windows Server 2008 R2
- Configuring Windows Server 2012 R2 Part 1
- Configuring Windows 7 Ultimate Server
- Configuring the Dragon clients
- User Profiles and using Dragon through a Remote Desktop session
Appendix A: Options for MSI Installations
- MSI options for Dragon installations
  - Sample command lines
- Feature variables to set through the ADDLOCAL or ADVERTISE properties
- Speech options
- MSI options for scheduled tasks
- Editing Miscellaneous and Scheduled Task settings in nsdefaults.ini
- Extracting MSI/MST Files from the Dragon setup.exe
Appendix B: Stand-Alone Mode Installation Options
- Setting Roaming user profile options
- Understanding Roaming user settings in nsdefaults.ini and roamingdef.ini
  - nsdefaults.ini settings
  - roamingdef.ini options
- Installing a Roaming user profile configuration on additional computers
Appendix C: Database backups
- About database backups
- Disabling automatic database backups

Dragon Installation Guide

Configuring your network switch

If you have multiple NMC servers in your environment, you can use a network traffic switch to balance the incoming

client activity among your servers. You can configure the switch to make an API call periodically to your servers to

ensure they are operational.

Configure the switch to make the following API call:

http://<NMS-Server-Name>:443/Nuance.NMS.Services/

__NMSServiceStatus/Rest/Status

If operational, the NMC servers return the following XML response:

<ServiceStatusResponse xmlns=

"http://schemas.datacontract.org/2004/07/Nuance.NAS.Connector.

DictationTranscription" xmlns:i="http://www.w3.org/2001/

XMLSchema-instance">

__<Status>Running</Status>

__<ServerDateTimeUTC>2010-12-13T20:50:13.0969590Z

____</ServerDateTimeUTC>

__<InterfaceType>basicHttpTransport</InterfaceType>

</ServiceStatusResponse>

If the servers are down, the switch receives an error. If the switch receives anything other than the expected response,

the switch can tag a specific server as down and reroute network traffic.