Forum Discussion

GabeCz's avatar
GabeCz
Copper Contributor
Jun 05, 2026

Moving from Windows Server 2022 to 2025

And by moving I mean stand up a completely fresh Windows Server 2025 as the old server was patched for one too many times. (painfully slow and stuffy) What I figured out so far, is to install Wind...
CM2012
MECM
MECM Migration
mertefekanlikilic's avatar
mertefekanlikilic
MCT
Jun 24, 2026

Hi GabeCz​ 

Your recovery plan is generally sound and I don't see any major issues with it.

The only thing I would challenge is the assumption that the old OS is the root cause of the performance issue. A 7.9 GB ConfigMgr database is very small, so I would normally investigate SQL performance, disk latency, inbox processing and provider performance before assuming the repeated upgrade path is responsible.

Regarding rollback, there isn't really a hard point of no return as long as you have good backups of both the site database and the original server. However, once the recovered site is online and actively processing data, rolling back becomes increasingly complicated.

I would strongly recommend taking:

  • A ConfigMgr site backup
  • A SQL backup
  • A VM snapshot/full backup of the existing site server

before beginning the recovery.

Also make sure both servers are never online simultaneously with the same site identity.

If this is a standalone site used primarily for OSD/PXE, the migration itself should be relatively straightforward.