Nuance Management Center
Table Of Contents
- Configuration and client installation guide
- About this guide
- Chapter 1: Introduction
- Chapter 2: Installation checklists
- Chapter 3: Preparing for your server installation
- Chapter 4: Installing the servers
- Chapter 5: Post-installation tasks
- Chapter 6: Preparing for your Active Directory single sign-on configuration
- Chapter 7: Installing the Local Authenticator
- Chapter 8: Preparing for your Dragon Group client installation
- Chapter 9: Installing the Dragon Group client
- Chapter 10: Installing the Dragon client with Settings
- Chapter 11: Configuring the Dragon client for NMS
- Chapter 12: Scheduling Optimization Tasks
- Chapter 13: Working with Custom Commands
- Chapter 14: Upgrading the Dragon client
- Chapter 15: Managing Logs and Errors
- 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
- Appendix B: Stand-Alone Mode Installation Options
- Appendix C: Database backups
Dragon Installation Guide
Installing and binding the SSL certificate
About signed certificates
Using SSL requires that you obtain a signed SSL certificate from a certificate authority, such as GoDaddy or Verisign.
The certificate authority must be a trusted authority known to both the client computer and the server. Nuance
Management Center does not support internally generated (self-signed) certificates.
To obtain a signed certificate, you'll need to provide information to the certificate authority about your organization and
the server on which you are installing the certificate in the Certificate Signing Request (CSR). Each certificate
authority may require different information. Typically, the information can include the following:
l Organization name
l Organization location information, such as town and state
l Computer name for the server on which you are installing the certificate
l Extended Key Usage value, such as 2.5.29.37. Extended key usage further refines key usage extensions, which
define the purpose of the public key contained in the certificate.
l Key Size, such as 2048 bits or 4096 bits. Determines the length of the public key in the certificate. A longer key
provides stronger security. You determine the level of security that is appropriate for your environment.
You obtain this information from your IT department, or from the person who installed and configured your server.
For more detailed information on installing SSL certificates, see:
http://msdn.microsoft.com/en-us/library/ms733791.aspx
About ports
Clients contact the Local Authenticator on the standard HTTP ports 80 and 443.
To install and bind the certificate:
1. Ensure that an SSL certificate is installed in the Personal store of the local computer for the user that the NMS
service is running as.
To add the Certificates Snap-in and view the certificates installed on the local computer, see https://tech-
net.microsoft.com/en-us/library/cc754431(v=ws.11).aspx.
43










