(All scripts used are stored on the managed instance under "D:\SKL_Staging_Everest\__skl\scripts" - To be moved to source control)
Create Files and Folders using current standards (Currently copied from working copy).
       - Rename folder in inetpub/wwwroot to new domain

Rename all references using a search and replace to the new environment.
       - "Client_ENV_Everest"
       - Passwords
       - Application name

Create new AD groups using the script "ad_create.ps1" 
       - Separate user groups need to be created for live and staging
       - Update admin and support email addresses in script to be added to the groups upon creation

Create Local Users using "env_create.ps1" (this script is also used to create services and can be done at this point).
       - Generate passwords using Use a Passphrase in the format xxx.xxx.xxx.xxx#33
       - Update admin and support email addresses in script to be added to the groups upon creation

Create database using current naming scheme in azure (currently by copying a current working database, with the data removed in a later step).
      - User Groups are added automatically through a job within 5 minutes.

Setup SVC users and delete base database users using "SKL_sqlmi_accesss_SKL.sql" 
      - Enable SQLCMD mode under Query > SQLCMD Mode
      - Client Code: Three Letter Acronym
      - TargetEnv: Live | Staging
      - ClearLogins: 2
      - Passwords in script to be updated to the ones used above

Update Synonyms for Documents and Audit if relevant

Remove old data using the script "\Dropbox\EBSphere\Everest SQL\Special Scripts\_Debug Scripts [DO NOT RUN]\Script for new Database [DO NOT RUN]\Clear Data [DO NOT RUN].sql"
      - Ensure that you DO NOT run this on the wrong database 

Truncate the documents db

Run dba.dbo.sp_scan_db '%CLIENT[_]%','CLIENT_ENV_Everest' to identify any scripts or tables with old references and update them to reference the new database and client

Create STP using Everest Administrator

Create license using new STP 

Test new STP