Client Environment:

• Server: 41.204.7.26:4433
• Usernames: (aon1, aon2, aon3, aon4, aon5)
• Domain: SZ.EIB.BZ
• VPN: https://www.sonicwall.com/products/remote-access/vpn-clients/
• VPN Password (Protected): EB Sphere (Pty) Ltd\EB Sphere (Pty) Ltd Team Site - Documents\Clients\Eswatini Insurance Brokers (former Aon Swaziland)\AON Swaziland (Eswatini Insurance Brokers)\Docs\EIB VPN Remote Access.docx
• Everest.NET Version: 29
• Azure Blob Storage Explorer - NB! The latest version of this application does NOT run on the client's own environment. Please use the version specified here: Github - Azure Storage Explorer v1.28.1

Managed Instance:

• Database Server: sqlmi-ebs-prod.public.2a5fe6cde9a7.database.windows.net,3342
• Databases: (EIB_Staging_Everest, EIB_Live_Everest, EIB_Staging_Everest_Documents, EIB_Live_Everest_Documents)
• Server address: 172.30.0.7
• File Storage Directory (Root): D:\EIB_Staging_Everest\
• Domain: africa.ebsphere.eib_staging_everest

Migration Observations:

• Updating the license requires that we uncomment the security check in the following trigger:
  • Table: prgSystemSettings > Trigger: tr_prgSystemSettings
• Staging documents database was restored from another client and required the truncation of the document table.
• Staging database was restored from the live database at the client's environment.
• Passwords for the various users were generated using: https://www.useapassphrase.com/ (Replace the spaces with dots). The password which we generated for this client can be found on Azure. 
• DB Scrub - The following database alterations were required once we restored the database to the managed instance:
  • Local path references must be directed to the (D:\) drive. Values may include C:\, C:\Temp etc...
  • GRANT statements removed
  • Connection strings must point to the new environment
  • Reference to IP address to be resolved
• STP file was created for the client using an existing file. 
• Used the following stored procedure to assist with finding potential data changes: [dbo].[sp_scan_db]