Wiki source code of Add New Client to managed instance
Version 1.43 by Phillip Swanepoel on 2024/10/10 09:08
Hide last authors
| author | version | line-number | content |
|---|---|---|---|
 |
1.11 | 1 | (All scripts used are stored on the managed instance under "D:\SKL_Staging_Everest\~_~_skl\scripts" - To be moved to source control) |
| |
1.9 | 2 | Create Files and Folders using current standards (Currently copied from working copy). |
| 3 | - Rename folder in inetpub/wwwroot to new domain | ||
| |
1.7 | 4 | |
| |
1.8 | 5 | Rename all references using a search and replace to the new environment. |
| |
1.9 | 6 | - "Client_ENV_Everest" |
| |
1.8 | 7 | - Passwords |
| 8 | - Application name | ||
| |
1.9 | 9 | |
| 10 | Create new AD groups using the script "ad_create.ps1" | ||
| |
1.3 | 11 | - Separate user groups need to be created for live and staging |
| |
1.10 | 12 | - Update admin and support email addresses in script to be added to the groups upon creation |
| 13 | |||
| |
1.5 | 14 | Create Local Users using "env_create.ps1" (this script is also used to create services and can be done at this point). |
| |
1.4 | 15 | - Generate passwords using [[Use a Passphrase>>url:https://www.useapassphrase.com/]] in the format xxx.xxx.xxx.xxx#33 |
| |
1.10 | 16 | - Update admin and support email addresses in script to be added to the groups upon creation |
| 17 | |||
| |
1.3 | 18 | Create database using current naming scheme in azure (currently by copying a current working database, with the data removed in a later step). |
| |
1.6 | 19 | - User Groups are added automatically through a job within 5 minutes. |
| |
1.1 | 20 | |
| |
1.12 | 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 | ||
| |
1.19 | 26 | - Passwords in script to be updated to the ones used above |
| |
1.11 | 27 | |
| |
1.20 | 28 | Update Synonyms for Documents and Audit if relevant |
| 29 | |||
| |
1.21 | 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" |
| |
1.27 | 31 | - Ensure that you DO NOT run this on the wrong database |
| |
1.20 | 32 | |
| |
1.27 | 33 | Truncate the documents db |
| 34 | |||
| 35 | 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 | ||
| 36 | |||
| |
1.31 | 37 | Create STP using Everest Administrator |
| 38 | |||
| 39 | Create license using new STP | ||
| 40 | |||
| 41 | Test new STP |