How to Install a Windows Feature That Requires a Restart in Azure DevOps

Описание: Learn how to install `Windows features` that require a `restart` in Azure DevOps Pipelines. This guide walks you through using a self-hosted agent for seamless integration.
---
This video is based on the question https://stackoverflow.com/q/73586385/ asked by the user 'Casper' ( https://stackoverflow.com/u/1492315/ ) and on the answer https://stackoverflow.com/a/73618821/ provided by the user 'Bowman Zhu-MSFT' ( https://stackoverflow.com/u/6261890/ ) at 'Stack Overflow' website. Thanks to these great users and Stackexchange community for their contributions.

Visit these links for original content and any more details, such as alternate solutions, latest updates/developments on topic, comments, revision history etc. For example, the original title of the Question was: Azure DevOps: how to install a windows feature which requires a restart?

Also, Content (except music) licensed under CC BY-SA https://meta.stackexchange.com/help/l...
The original Question post is licensed under the 'CC BY-SA 4.0' ( https://creativecommons.org/licenses/... ) license, and the original Answer post is licensed under the 'CC BY-SA 4.0' ( https://creativecommons.org/licenses/... ) license.

If anything seems off to you, please feel free to write me at vlogize [AT] gmail [DOT] com.
---
Managing Windows Features in Azure DevOps: A Practical Guide

When working with Azure DevOps, one may encounter the challenge of installing Windows features that require a restart. This situation can be particularly tricky when utilizing Azure Pipelines since typical agents may not allow for operational restarts. In this post, we will address how to overcome this hurdle with a clear and structured solution.

The Problem: Installing a Windows Feature That Requires a Restart

Imagine you need to install a specific Windows feature. For example, you want to execute the following command to install the WebDAV Redirector feature:

[[See Video to Reveal this Text or Code Snippet]]

However, executing this command will require a restart of the server. The challenge arises when you’re working within an Azure DevOps pipeline, where initiating a restart is not a feasible option on a typical pipeline agent. Additionally, you may want to ensure services like the WebClient are automatically set to start upon boot, using a command like:

[[See Video to Reveal this Text or Code Snippet]]

The Solution: Utilizing Self-Hosted Agents

To properly install Windows features that demand a restart, the most effective solution is to use a self-hosted agent. This approach provides you with better control over the environment and allows you to manage the server as needed.

Steps to Using a Self-Hosted Agent

Set Up a Self-Hosted Agent:

Install the Azure DevOps agent on your own Windows Server (preferably the same version you intend to work with, such as Windows Server 2019).

Follow the instructions provided in the Azure DevOps documentation for setting up self-hosted agents.

Configure Your Pipeline:

Once your self-hosted agent is up and running, you can configure your pipeline to use this agent.

In your pipeline YAML or interface settings, specify the self-hosted agent pool:

[[See Video to Reveal this Text or Code Snippet]]

Install the Required Feature:

In your pipeline script, use the Install-WindowsFeature command to install the desired feature:

[[See Video to Reveal this Text or Code Snippet]]

Restart the Agent (if necessary):

Depending on the server setup, you may need to restart the server after installation. Since this is a self-hosted agent, you can manually trigger the restart or set it up through your pipeline scripts, knowing it won’t affect hosted pipelines.

Set Service Startup Type:

Following the restart (if required), run the command to set the WebClient service to start automatically:

[[See Video to Reveal this Text or Code Snippet]]

Conclusion

Navigating the installation of Windows features that necessitate a restart in Azure DevOps pipelines can initially seem daunting, but using a self-hosted agent simplifies this process significantly. By setting up an environment you control, you can proceed with installations and restarts without the limitations of standard pipeline agents.

Feel free to reach out if you have more questions or need further assistance with your Azure DevOps journey. Happy coding!