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
Chapter 13: Working with Custom Commands
Using the MyCommands Protection Utility
In Dragon Group, you can protect custom Text-and-Graphics, Step-by-Step, Macro Recorder, and Advanced Scripting
commands by exporting them into a .dat file, and then running the MyCommands Protection Utility included in your
Dragon installation. After they are imported to the Dragon client, users can use the commands, but cannot view or edit
their source code or re-export the commands. As a result, the integrity of the commands remains intact.
To protect the commands in a .dat file:
1. Make a backup copy of the unprotected .dat file and store it in a secure location.
When you protect the .dat file that you are distributing, you cannot make the file available for editing again.
2. Open a command prompt.
3. Change directories to the Program folder inside your installation directory. By default:
C:\Program Files\Nuance\NaturallySpeaking14\Program
4. Enter the following on the command line:
protectcmds.exe <dat-file-path> <vendor-name> [<vendor-contact-info>]
If a user attempts to view, copy, or edit commands from a protected file, the following message appears:
The command was protected by <vendor-name>.
Please contact <vendor-contact-info> for more information.
In the Command Browser, the same message appears as the Preview Content in Script mode.
When you have protected the file, you can place it in the Data Distribution directory for distribution to multiple user
profiles, and then use the nsadmin command line tool. For more information, see the nsadmin Help file available in
the Help folder of your installation directory (by default, C:\Program Files\Nuance\Nat-
urallySpeaking14\Help).
To distribute commands in the NMC console, see “Working with Command Sets” in the Nuance Management Server
Administrator Guide.
80










