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
Overview—Installing the Dragon client with initial settings
You can use command line options to copy your initial Dragon settings to all your Dragon client installations.
Prerequisites
Before installing the Dragon client, do the following:
l Have the Dragon serial number available. If you are installing or upgrading Dragon on multiple networked
computers, have the group serial number available.
l Ensure all mapped drives you plan to use are mapped on each client computer where you are distributing the
installation.
l Install any pending Windows updates on clients and restart as needed.
l Copy any .ini files you want apply to your installation to a central location so you can access them later.
Notes:
l If you chose Enable Desktop Search Commands on the Commands tab during the initial installation, you must
also install Microsoft Search before installing Dragon.
l Enclose long path names containing spaces in quotation marks. Be sure to escape the each quotation mark with a
backslash: \" .
l You can use the /qn option to install the product in Quiet mode, where there is no user interface, and no
messages appear. To use the /qn option, add it to the end of the command line. Another option, the /passive
mode, runs the entire installation unattended, but displays a progress bar.
l The first time you run an installation from the command line, you should use the /qf option rather than /qn. This
allows you to see prompts that help you determine any problems with the command line.
l To ensure that you receive messages about any errors that occur during the installation, pass /L and one or more
sub-options, followed by a log file name. The installer then creates a file containing any installation log errors and
other messages related to the process. You can send the log file to technical support, should any issues arise.
l For more information on MSI options, see the Microsoft website: http://msdn.microsoft.com/en-
us/library/aa367988(v=vs.85).aspx.
Push installations
Dragon includes a native Windows Installer (MSI) that allows you to install across a network to multiple client
computers and customize your installations. You can use the included Dragon 14.msi (see “Command Line
installation with msiexec.exe” on page 71) or admininstall.bat file (see “Performing an administrative installation
with a batch file” on page 70).
Several servers support this type of network installation:
l Windows Server 2008 R2 and 2012 x64
l System Management Server (SMS)
l Active Directory
For an administrative installation, the administrator creates an image of the installation program on the server and then
configures the server to automatically push the application onto the client systems. You can also configure network
installations to modify, repair, or remove an existing installation.
67










