...
| Markdown |
|---|
- [Prerequisites](#prerequisites)
- [Migration Procedure](#migration-procedure)
# Prerequisites
- The migration from a server with Windows Server 2019 to a server with Windows Server 2022 requires that the former is already upgraded to Saga 6.3.0 or higher.
- A server with the Windows Server 2022 operating system. A server with the Windows Server 2022 operating system. The server must have a hardware specification identical to that of the Windows Server 2019 server from which one is migrating. The same applies to anti-virus software, host server port, firewall rules and IP blocking prerequisites, which all should be the same to match the migrated configuration. See the *Prerequisites* section of the [Installation Guide](https://ayfie-dev.atlassian.net/wiki/spaces/SAGA/pages/2400714758/Ayfie+Locator+Installation+Guide) for details.
- A new license for the new Windows Server 2022 server
- If the current installation is set up with a gMSA account, then add the new server to the gMSA security group. See section *Add the Saga Host to the Security Group* of the [Create gMSA Account](https://ayfie-dev.atlassian.net/wiki/spaces/SAGA/pages/3343745025/Create+gMSA+Account).
- Determine the server's Gateway Hostname (reusing the current Gateway Hostname is the standard practice)
- If one is to change the Gateway Hostname the following additional prerequisites apply:
- An SSL certificate for the new Gateway Hostname if one is using Certificate Authority provided SSL certificate files. See the *HTTPS* section of the [Installation Guide](https://ayfie-dev.atlassian.net/wiki/spaces/SAGA/pages/2400714758/Ayfie+Locator+Installation+Guide) for more information.
- An updated *Redirect URI* in the Azure Application, if the Authority Service is set up with Azure AD. See the *Azure Active Directory* section of the [Installation Guide](https://ayfie-dev.atlassian.net/wiki/spaces/SAGA/pages/2400714758/Ayfie+Locator+Installation+Guide) for more information.
# Migration Procedure
To migrate a Saga instance from Windows Server 2019 to Windows Server 2022, perform these steps:
- From within an elevated PowerShell shell on the Windows Server 2019 server, do the following to stop Saga:
- Change directory to *D:\Program Files\ayfie\saga* (the path assumes the recommended Saga install directory).
- Stop Saga by running `.\stop-saga.ps1`.
- Copy the folder *D:\Program Files\ayfie\saga* to the same location on the Windows Server 2022 server.
- If one is reusing the current Gateway Hostname, perform these steps on the Windows Server 2022 server:
- From within an elevated PowerShell shell, do the following to start Saga:
- Change directory to *D:\Program Files\ayfie\saga* (the path assumes the recommended Saga install directory).
- Run `.\saga.ps1`
- Update DNS to now instead refer to the new server with Windows Server 2022
- If the new instance has a new Gateway Hostname, perform these steps on the Windows Server 2022 server:
- If one is using Certificate Authority provided SSL certificate files, replace the SSL certificate files in _D:\Program Files\ayfie\saga\volumes\Traefik\certs_ on the Windows Server 2022 server. See the *HTTPS* section of the [Installation Guide](https://ayfie-dev.atlassian.net/wiki/spaces/SAGA/pages/2400714758/Ayfie+Locator+Installation+Guide) for more information.
- If the Authority Service is set up with Azure AD, update the *Redirect URI* of the Azure AD application.
- From within an elevated PowerShell shell, do the following to start Saga:
- Change directory to *D:\Program Files\ayfie\saga* (the path assumes the recommended Saga install directory).
- Run `.\saga.ps1 -configure` and change the Gateway Hostname.
- Start the Management Console and replace the license. See [Add or Replace a License](https://ayfie-dev.atlassian.net/wiki/spaces/SAGA/pages/3390013467/Add+or+Replace+a+License) for more information.
|