I want to migrate Azure Vm from 2012 to Azure vm 2019 , I dont want to do in place upgrade

Question

Hello Team , I want to migrate Azure Vm from 2012 to Azure 2019 , I dont want to do in place upgrade , because based on our company policy we are supposed to use our hardening OS images only , In this case I dont want to do in place upgrade

Answer 1

Hi @murugan here is a brief summary of what can be done,

1 - Prepare the New VM on Azure

2 - Data Transfer Tools: Robocopy, or PowerShell scripts to transfer data. Azure File Sync can also be a good option for syncing data if it's constantly changing.

3 - File Server:

When migrating files between Windows Server VMs in Azure, using Distributed File System (DFS) can significantly streamline the process. DFS offers two core components beneficial for migration: DFS Namespaces (DFS-N) and DFS Replication (DFS-R).

DFS Namespaces allow you to create a virtual directory structure that can hide the physical network location of the files. This is particularly useful during migration because it provides a consistent point of access for users, regardless of where the data physically resides

DFS Replication (DFS-R) DFS Replication is a multi-master replication engine that synchronizes folders between servers across local or wide area network connections. It ensures that your files are replicated and up-to-date across your Windows Server VMs.

Reference: https://learn.microsoft.com/en-us/windows-server/storage/dfs-replication/dfsr-overview

4 - Applications and Network

After completing the synchronization of files and databases, it's essential to transition towards the final migration stages to ensure minimal disruption and a transparent changeover for users. Database Read-Only Mode: Once the base data synchronization is complete, set the database on the old VM to read-only mode. This step prevents any new changes from occurring in the database, ensuring that no data is lost or modified during the final stages of migration. Shut Down Old VM: After ensuring all data has been synchronized and the database is set to read-only, shut down the old Windows Server 2012 VM. This action prevents any access to the old system and ensures that all traffic will be directed to the new system once the DNS and IP changes are made. Migrate IP Addresses and DNS Pointers: To minimize impact and ensure a seamless transition for users, migrate the IP addresses and update the DNS pointers from the old VM to the new Windows Server 2019 VM. This step ensures that users can continue accessing services and applications without any change in their access patterns or the need for reconfiguration on their end.

5 - Active Directory
If your environment uses Active Directory (AD) for user and resource management, additional steps should be taken to ensure the AD infrastructure is updated and remains functional post-migration.

Add New Server as Secondary Domain Controller

Migrate FSMO Roles: Transfer the Flexible Single Master Operations (FSMO) roles from the old domain controller to the new one. This transfer is a critical step in ensuring that the new server takes over the primary operational roles within the AD environment

Demote Old Domain Controller

Get in touch if you need more help with this issue.

--please don't forget to "[Accept the answer]" if the reply is helpful--

Answer 2

Thanks for your reply Jackson.

Windows machine 2012 is already running in the Azure, we want to migrate this Azure windows VM 2012 to 2019 by using our OS hardening images in Azure only. 2012 machines are already in Azure.

In this Case what are the steps document that we need to follow ?

Answer 3

Murugan, Balaganesh You can do it in several ways, prepare your image in the on-premise environment and migrate with the settings in Azure.

You can also provision a new VM and apply security settings, and use a standard image: You'll need to follow a structured process that ensures the new environment is secure, compliant, and incorporates all required configurations. Here’s a step-by-step guide tailored to your requirements only on Azure:

Step 1: Create the New VM with Windows Server 2019

Provision a Temporary VM: Start by creating a new, temporary VM in Azure using the standard Windows Server 2019 image from the Azure Marketplace. This VM will be used to apply your hardened settings.

Step 2: Apply Your Hardened Settings

Apply Hardening: Log into the temporary Windows Server 2019 VM and manually apply all your organization's hardening settings. This may include configurations related to security policies, user account controls, network configurations, and installed security software or patches.

Step 3: Create a Custom Image

Capture the Image: Capture the image using the Azure portal or Azure CLI. This custom image will include all your hardened settings. Reference: https://learn.microsoft.com/en-us/azure/virtual-desktop/create-custom-image-templates

Step 4: Provision Your New VM from the Custom Image

Create New VM from Custom Image: Now that you have a custom image with all your hardening applied, use this image to create a new VM in Azure. This can be done through the Azure portal, PowerShell, or Azure CLI.
https://learn.microsoft.com/en-us/partner-center/marketplace/azure-vm-use-own-image --

--please don't forget to "[Accept the answer]" if the reply is helpful--

Answer 4

We already have hardening Image it is available in our Azure Marketplace.

1. Create new VM by using 2019 hardening image.
2. After creating the new VM 2019,,,how to migrate 2012 to 2019 ? What are the things we need to check ? what is the checklist that we need to follow before and after ?