Migrating Notification Services

Systems that are not configured to use TLS 1.2 would need the following registry entries for the new Notification Hub to work:

• [HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\.NETFramework\v4.0.30319]

"SystemDefaultTlsVersions"=dword:00000001

"SchUseStrongCrypto"=dword:00000001

• [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework\v4.0.30319]

"SystemDefaultTlsVersions"=dword:00000001

"SchUseStrongCrypto"=dword:00000001

Note:
- Before you run the AVEVA Work Tasks Notification Migration Wizard, unregister from the existing Mobile Notification services. For information on unregistering, see Unregistering from the Mobile Notification Service.
- After unregistering the Mobile Notification services, close the Farm Configuration Wizard and then run the AVEVA Work Tasks Notification Migration Wizard.

To migrate Notification Services

To migrate the mobile notification service from earlier versions of the product, follow the steps given below:

1. Run the AVEVA Work Tasks Notification Migration Wizard.

2. Provide the Database Server name, Farm Database name, Authentication Mode, and the Database credentials.

3. Click Migrate to migrate the Notification details.

4. Run the Farm Configuration Wizard, and click Next.

5. In the Edit Farm Settings window, select Service Settings.

6. Click Next.

   The Services/Global Settings window appears.

7. Click the edit button near the Mobile Notification Service.

   The Mobile Notification Service Settings window appears.

8. Click Test Connection to verify the connection. Make sure the URL is mobilenotification.worktasks.connect.aveva.com, and then click OK.

9. Click Register.