This README provides a step-by-step guide on performing an in-place migration of a Windows instance on Oracle Cloud Infrastructure using an OCI-Included license.
Windows In-Place Migration on OCI
This migration guide demonstrates the process of upgrading an existing Windows instance in OCI through in-place migration techniques. The focus is to ensure a smooth transition with minimum downtime and maximal compatibility with the new environment. The final step involves reactivating the Windows License Key.
- For BYOL instances: Simply verify the activation status and if necessary, re-enter your product key.
- For OCI-Provided license instances: You must reset the activation and reapply the product key using OCI’s KMS. This step is described later in this document.
Execute the following command in PowerShell prompt:
Get-ComputerInfo -Property WindowsProductNameApply the latest updates to your Windows instance.
Create a full backup of the boot volume and attached block volumes.
Download the proper Windows Server ISO locally.
If you don’t have an attached block volume yet, it's advisable to attach one to store the installation media efficiently.
Mount the ISO locally on the instance.
Run setup.exe from the mounted ISO.
If prompted for a product key, enter it.
Note: The product key will be removed during KMS activation.
You should be able to use a Volume Key provided by Microsoft
A Volume key is a product key that can be used during setup but can't be activated without KMS.
Choose the correct image, for example, "Windows Server 2022 Standard with Desktop Experience"
Select what to keep.
If "Keep files, settings and apps" option is greyed out, immediately abort the upgrade to prevent data loss.
Before starting the upgrade:
- Go to your OCI Console,
- Instance Details
- Create a Console Connection
This will allow continuous access and monitoring without RDP.
Connect via VNC to the Console connection.
Click Install to start the upgrade.
Use a VNC connection for Linux, MAc or Windows
Connect via VNC to :
127.0.0.1:5900When the installation has completed, check the Activation state
slmgr /xprIf you must reset the Windows Activation for an OCI-Provided License:
Open a PowerShell Prompt with Admin Rights and verify the upgraded Windows version using:
Get-ComputerInfo -Property WindowsProductNameslmgr /upkslmgr /cpky shutdown /r /t 0slmgr /skms 169.254.169.253:1688slmgr /rearmshutdown /r /t 0Key Management Services (KMS) client activation and product keys
Example using GVL key for Windows 2022 Standard:
slmgr /ipk VDYBN-27WPP-V4HQT-9VMD4-VMK7H### FORCE ACTIVATION
slmgr /atoslmgr /dlvUsing a Key Management Service (KMS) allows assigning a temporary key that is periodically renewed, rather than a permanent key.
This activation model is dynamic and designed to support enterprises managing a large number of licenses across multiple servers and client computers in an internal network environment.
How KMS Works:
- Temporary Key:
- The key used for activation via KMS is not permanent and is regularly reactivated by an internal KMS server.
- This key must be renewed at regular intervals to ensure that the operating system remains activated without interruption.
- Renewal Period:
- By default, a machine activated via KMS must "renew" or "revalidate" its activation on a regular basis. (Default: 6 months)
- However, the attempts to reactivate are much more frequent.
- Renewal Tolerance:
- While the activation interval is set at 180 days, systems attempt to reactivate every 7 days.
- This helps prevent service interruptions in case of KMS server issues or other network errors that could impede activation during this time.
- Why a Renewal Model?
- Using KMS as an activation method is particularly beneficial for large organizations for several reasons:
- CENTRALIZED MANAGEMENT: KMS allows administrators to manage activations through an internal network, centralizing license administration without requiring an external connection for each activation.
- LICENSE COMPLIANCE: This model helps businesses stay compliant with Microsoft licensing agreements, as it ensures only verified and approved machines are activated.
- FLEXIBILITY: It provides flexibility in license management, particularly useful in cases of frequent hardware or software configuration changes, common in large IT environments.
This repeated temporary approach ensures that any machine no longer part of the network or organization loses its activation, thereby helping to secure and regulate the use of software licenses.