Cloud Migration Training

1. Cloud MigrationTraining

2. NMS Cloud Migration Introduction • Customers can now store speech recognition and other data objects in the Nuance data center, rather than in an on premise NMS server. • Customers that have more than one Nuance product will be able to share data across multiple Nuance applications. • A customer creating an auto-text or word in the Nuance Management Console will see that object available with both products, DMNE and DM360 Direct. • Objects created in one client can be seen by other clients. • What should a current on premise customer expect when moving to the cloud configuration?

3. What will remain on premise? • NMS will be removed from on premise • PO Server will be removed from on premise • Speechnodeswill remain on premise. • Speech profiles will remain on premise • In some cases, an NMS “call forwarder” will be required to install and configure. • Specifically, the call forwarder will be required when on-premise (LDAP / AD) configuration is required. • Old on premise NMS server could be used • Customers will access the cloud Nuance Management Console once migrated.

4. Preconditions • NMS on premise server is running NMS 2.0 or later (DMNE 1.0 SP3). 4.x or later • If the customer is on DMNE 1.x, they should use the voc removal tool on user profiles before migrating to the cloud. If currently on DMNE 2.x, the customer should consolidate words and ATs before migrating, especially if the customer has large number of words ie. via DDT. • A “Call Forwarder” server may be required if the customer is using LDAP/AD/Trusted mode of authentication. Customer can use existing NMS server for CF so NMS server address remains the same for Dragon client login. • If not using call forwarder/old NMS server, Dragon client will need to point to new NMS server location. Note: If customer is using the old method of adding the LDAP server address to the NMS config file for DMNE authentication, users will need NTLM credentials added to their user accounts to use “Call Forwarder” post migration. Future - Add a button to NMC to create NTLM credentials using native NMC login IDs. NMC Site setting “LDAP authentication” must also be set to use single or multi domains.

5. Preconditions – cont’d In order for Dragon to get this setting from NMS, user has to first log into Dragon with native credentials.

6. Cloud Organization Creation (Nuance) A Nuance employee (Bob Harris) will need to create a new org in the cloud if one does not already exist for this customer with the following: • Same organization ID as customer’s on premise org with one userin administrator group. This user will run the Cloud Migration Tool. • Modify that user’s group to include the following rights: • Product - Manage DM360 Network Edition • Dragon – Allowed to run DM360 Network Edition tools • Create and import a single NMC license for this Organization, and assign it to the user • Create organization tokens for PO and Call Forwarder installation. If cloud organization already exists, Nuance employee should make sure Org IDs match between cloud and on premise servers and add rights above to administrator running Cloud Migration tool. Also create org tokens for SN and CF.

7. What the customer needs prior to migration Nuance Service should be there to guide customer through the process. The customer will need: • A computer where: • The customer has rights to install an application. • The computer is on the same network with the Nuance Management Server. • The computer is on the same network with the NMS SQL Server • Their source (on premise) NMS server address, NMC administrator login id/password and SQL server address and credentials. • The target (cloud) NMS server address (nms.nuancehdp.com) & credentials of administrator user account created by Nuance • A prefix and/or suffix to be used in the event of login id conflicts during migration

8. Running the migration Start the migration from the cloud NMC -> Utilities -> Tools Prompt to install the tool After installation launch the tool

9. Running the migration – on premise server/credentials Enter on premise server name and administrator credentials for NMC

10. Running the migration – on premise SQL server/creds Enter on premise SQL server name and credentials

11. Running the migration – cloud server/credentials Enter cloud server name and administrator credentials for NMC

12. Running the migration – login IDs must be unique Admin must enter either a prefix or suffix or both that would be added to any user’s login ID from the on premise system that already exists in another organization in the cloud. NMS will add it to the user’s login ID before migrating it to the cloud.

13. Running the migration – confirmation Confirm info and hit Migrate!

14. Running the migration – packaging the data • Could take some time depending on # of users/auto-texts, words, etc • Administrator does not have to be in attendance during this time

15. What data is migrated? • Organization details including domains and tokens • Sites including Master User Profile locations (including HTTP and SSL Settings) and all DMNE settings • Groups including all DMNE settings • Users including all DMNE settings and user NTLM credentials • Licenses (and assignments) • Speech node collections • Auto-texts, commands and speech words (not from command sets) • Command sets along with auto-texts and commands that were imported from command sets are not migrated

16. Running the migration – Summary Data is packaged then zipped and to sent to NMS in the cloud

17. Monitoring progress on NMC • Cloud Migration Tool delivers the packaged data to NMS in the cloud where it is merged into the cloud DB • This process could take some time • NMC->Messages reports on progress every 15 minutes followed by a summary • Login ID conflicts are listed in summary message and can be copied/pasted into MS Word or Excel

18. Identical Sites, Groups and User Accounts • If customers are migrating to an existing organization, they should decide how they want to handle identical sites, groups and users that exist in both organizations. • If no action is taken, identical sites, groups and users will be merged. • If customers wish to keep sites and groups separate, they may need to rename these objects on either side prior to migration. • Most customers will want their users to be merged into one in the cloud. If the user’s login ID is identical, the users on both orgs will be merged.

19. Identical Sites, Groups and User Accounts – cont’d Identical Sites • If an on premise and a cloud site both have the same site name, the sites are considered identical. (The tool will no longer check for Site ID when deciding if sites are identical.) Identical Groups • If an on premise and a cloud group both have the same group name, the same role  and are both members of the same named site, the groups are considered identical. • If the group’s roles or sites are different, the groups are not considered identical and will not be merged into one group. • If the groups are named the same, in the same site but have different roles, the on premise group will have the word “conflict” added to the group name when it is migrated. Identical User Accounts • If an on premise and a cloud user account both have the same login ID and both belong to the same organization, the user accounts are considered identical. The tool will no longer check for first name or last name when deciding if user accounts are identical. Domain names • If the on premise and any cloud organization have the same domain name, the on premise domain name will have the word “conflict” added to it when it is migrated. The NMC summary message will display that.

20. Merging Identical Sites, Groups and User Accounts Identical Sites • All DMNE Network Edition site settings will be migrated from the on premise site to the cloud site. All site level speech recognition objectswill be merged. Identical Groups • All DMNE Network Edition (US and UK) group settings will be migrated from the on premise group to the cloud group. All group level speech recognition objects will be merged. • Primary group on premise will become primary group in cloud. • Group security rights and access rules will remain as they are in the cloud. (Open issue- Jira NCMT-4 On cloud migration security rights/privileges are not merged with identical group in cloud) User Accounts • All DMNE Network Edition (US and UK) user account settings will be migrated from the on premise user account to the cloud user account. All user level speech recognition objects will be merged. Dragon Profile Folder Name and NTLM credentials are also migrated. System and Token credentials are not migrated. • All licenses granted to the on premise user account will be granted to the identical user account in the cloud.

21. Challenges seen with migrations • User Login ID conflicts • Time to migrate (resolved with latest changes) • Merging vs. migrating data (also resolved in latest release) • One customer migrated from a test system where they imported users because they didn’t want to disturb their live system. (Doesn’t disturb live system.) • If customer is using LDAP/AD/Trusted authentication, they will need a Call Forwarder to use the same login credentials. If using old config file method, need to add NTLM creds to user accounts. • Customers should look at both systems before migrating to make sure same named sites, groups and user accounts will merge as desired and resolve any conflicts if not desirable. • Customers should consolidate words and ATs before migrating. Issues with large number of users/words. Not just a cloud migrating issue. • Time between migration and then using DMNE in cloud. Can re-run migration and additional speech rec objects, setting changes will be migrated.

22. Sharing objects between DMNE and other cloud products • Speech Recognition objects that are shared • Auto-texts (DMNE <->Direct) • Words (DMNE <-> Direct) • Commands from Command Sets (DMNE->Direct) • Speech Recognition objects not shared • Speech Lists

23. DMNE/NMS/Direct behavior with respect to Auto-texts • Auto-texts will upload from NMS to DMNE on login. • Auto-texts (text & graphic commands) will upload from DMNE to NMS the next time the user logs into DMNE (after creating AT). • A text and graphic command created in DMNE will appear in NMC at the user level and it will also appear in Direct under Manage Auto-texts. • Auto-texts will upload from Direct to NMS when created/edited. They will appear in NMC at the user level.Auto-texts created in Direct areuploaded to DMNE.

24. DMNE/NMS/Direct behavior with respect to Commands/Command Sets • Commands are not uploaded or downloaded to/from NMS or DMNE. (Something to look into for future.) • Commands can be exported from DMNE and imported into NMC as part of a command set at the site or group level only. • Commands (from a command set) can be copied and pasted to the user level in NMC. These commands are then available in Direct under Manage Commands. • Commands will upload from Direct to NMS when created/edited. They will appear in NMC as a user level Command. These commands are not available in DMNE.

25. DMNE/NMS/Direct behavior with respect to Words • Words will upload from NMS to DMNE on login. User should see all Words from groups that the user account is a member of. (Open issue– Jira NG-52 Group level Speech Words/Auto-texts not seen in Dragon client for the newly associated group ) • Words will upload from DMNE to NMS as words are added in DMNE. Words from DMNE are applied to the user profile when BatchWordUpdate runs in approximately 1 hour. • Words will upload from Direct to NMS (at the user level) as words are added in Direct (via Manage Vocabulary). • All words are seen in both clients

26. Importing objects from DMNE to NMS Auto-texts –> to all levels • XML only (can select site, group, user) Words –> to all levels • .txt file only (can select site, group, user) • Words that exist at the site or group level cannot be imported at the user level Command Sets (Power Packs) -> to site and group levels only • XML and .DAT (select site or group) • Can copy/paste from site or group to user level

27. Questions? • Content would go here • And here…