Hello,
The short answer: The specific step of activating the key does not require downtime, but the preparation steps before it and the updates after it do require a reboot.
Here is the breakdown of the process so you can plan your maintenance window accordingly:
- Prerequisites (Requires Downtime): Before you can activate the ESU key, you must install the ESU Licensing Preparation Package and the latest Servicing Stack Update (SSU). Installing these packages generally requires a restart of the server.
- Activation (No Downtime): Once the server is back online, applying the product key using the command line (Software Licensing Management Tool) does not require a reboot.
- Install Key:
slmgr /ipk <ESU-Product-Key>
- Activate Key:
slmgr /ato <ESU-Activation-ID>
- Installing Updates (Requires Downtime): After successful activation, your server will begin downloading the actual security updates. Installing these monthly security updates will require a reboot, just like standard Windows updates.
Recommendation: Plan for a maintenance window to install the prerequisites and the first round of updates. You can perform the activation step (slmgr) casually between these reboots without impacting users.
Please let me know if you run into any errors during the activation commands, and I will happily follow up to help you resolve them.
If this answer solves your issue, please click "Accept Answer" so other users can find this solution more easily.