# Migration of Ignition and MES module (OEE\_Downtime\_V2) from Windows Server 2016 to Windows Server 2022 without license loss

**URL:** <https://forum.inductiveautomation.com/t/migration-of-ignition-and-mes-module-oee-downtime-v2-from-windows-server-2016-to-windows-server-2022-without-license-loss/114135>\
**Category:** Ignition\
**Created:** [February 24, 2026, 3:32am UTC](https://forum.inductiveautomation.com/t/migration-of-ignition-and-mes-module-oee-downtime-v2-from-windows-server-2016-to-windows-server-2022-without-license-loss/114135 "2026-02-24T03:32:09Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![sergey.netu.90](https://avatars.discourse-cdn.com/v4/letter/s/6bbea6/32.png) [@sergey.netu.90](https://forum.inductiveautomation.com/u/sergey.netu.90)\
**Post date:** [February 24, 2026, 3:32am UTC](https://forum.inductiveautomation.com/t/migration-of-ignition-and-mes-module-oee-downtime-v2-from-windows-server-2016-to-windows-server-2022-without-license-loss/114135/1 "2026-02-24T03:32:09Z")

</div>

We need to migrate the existing Ignition installation together with the MES module (OEE\_Downtime\_V2) from Windows Server 2016 to Windows Server 2022.

The Ignition version will remain the same.

Please advise on the correct procedure to perform this migration without losing or invalidating the current license.

---

<div class="post-metadata">

**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\
**Post date:** [February 24, 2026, 1:15pm UTC](https://forum.inductiveautomation.com/t/migration-of-ignition-and-mes-module-oee-downtime-v2-from-windows-server-2016-to-windows-server-2022-without-license-loss/114135/2 "2026-02-24T13:15:54Z")

</div>

Deactivate the license before you start. (That makes it available for re-use.) Reactivate after the upgrade.