Version 1.26 by Phillip Swanepoel on 2024/10/10 07:53
Show last authors
1 (All scripts used are stored on the managed instance under "D:\SKL_Staging_Everest\~_~_skl\scripts" - To be moved to source control)
2 Create Files and Folders using current standards (Currently copied from working copy).
3 - Rename folder in inetpub/wwwroot to new domain
4
5 Rename all references using a search and replace to the new environment.
6 - "Client_ENV_Everest"
7 - Passwords
8 - Application name
9
10 Create new AD groups using the script "ad_create.ps1" 
11 - Separate user groups need to be created for live and staging
12 - Update admin and support email addresses in script to be added to the groups upon creation
13
14 Create Local Users using "env_create.ps1" (this script is also used to create services and can be done at this point).
15 - Generate passwords using [[Use a Passphrase>>url:https://www.useapassphrase.com/]] in the format xxx.xxx.xxx.xxx#33
16 - Update admin and support email addresses in script to be added to the groups upon creation
17
18 Create database using current naming scheme in azure (currently by copying a current working database, with the data removed in a later step).
19 - User Groups are added automatically through a job within 5 minutes.
20
21 Setup SVC users and delete base database users using "SKL_sqlmi_accesss_SKL.sql" 
22 - Enable SQLCMD mode under Query > SQLCMD Mode
23 - Client Code: Three Letter Acronym
24 - TargetEnv: Live | Staging
25 - ClearLogins: 2
26 - Passwords in script to be updated to the ones used above
27
28 Update Synonyms for Documents and Audit if relevant
29
30 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"
31 - Ensure that you DO NOT run this on the wrong database 
32 \\Run dba.dbo.sp_scan_db '%HLL[_]%','HLM_Staging_Everest'
33
34