<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[Topics tagged with activation]]></title><description><![CDATA[A list of topics that have been tagged with activation]]></description><link>https://xcp-ng.org/forum/tags/activation</link><generator>RSS for Node</generator><lastBuildDate>Thu, 14 May 2026 02:27:43 GMT</lastBuildDate><atom:link href="https://xcp-ng.org/forum/tags/activation.rss" rel="self" type="application/rss+xml"/><pubDate>Thu, 04 Apr 2024 01:22:55 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Losing Windows Activation when migrating VM from ESXi 6.7]]></title><description><![CDATA[Since you're changing all of the underlying hardware that the guest has, Microsoft is going to force you to reactive.
You could look at setting up a licensing server to manage these systems and then feed them that information so they can validate and then license.
This isn't an issue presented by XCP-ng (or literally any other hypervisor), its a Microsoft restriction to ensure you aren't stealing their software.
]]></description><link>https://xcp-ng.org/forum/topic/8763/losing-windows-activation-when-migrating-vm-from-esxi-6-7</link><guid isPermaLink="true">https://xcp-ng.org/forum/topic/8763/losing-windows-activation-when-migrating-vm-from-esxi-6-7</guid><dc:creator><![CDATA[DustinB]]></dc:creator><pubDate>Thu, 04 Apr 2024 01:22:55 GMT</pubDate></item></channel></rss>