Installs one or more roles, role services, or features on either the local or a specified remote server that is running Windows Server 2012 R2.
Windows Server · Risk: High · Documentation Verified
Last verified: 2026-10-26
Microsoft Microsoft.Windows.ServerManager.Migration reference: Installs one or more roles, role services, or features on either the local or a specified remote server that is running Windows Server 2012 R2. The syntax and selected example below are adapted from the pinned Windows Server 2025 reference. Module availability, target configuration and delegated permissions determine whether it can run in your environment. Documentation and parameter text: Microsoft, CC BY 4.0; formatting adapted by Cmdlet World. No execution testing is claimed.
Use an account with the target resource permissions documented for Install-WindowsFeature. Modifying administrative cmdlets may require elevation or delegated administration. This catalog does not assert that ordinary users can execute the command.
Supported environments
Windows / Microsoft.Windows.ServerManager.Migration · Windows Server 2025 documentation; feature/module prerequisites apply
Parameters
-ComputerName
Specifies a remote computer for which this cmdlet installs one or more available rrsandf_plural. This parameter accepts only one computer name. If this parameter is not added, or no computer name is specified, the default target is the local computer. Valid values for the parameter include a NetBIOS name, an IP address, or a fully qualified domain name of a remote computer that is running Windows Server To use an IP address of a remote computer as the value of this parameter, your command must include the *Credential* parameter. The computer must either be configured for HTTPS transport, or the IP address of the remote computer must be included in the WinRM TrustedHosts list on the local computer. For information about adding a computer name to the WinRM TrustedHosts list, see How to Add a Computer to the Trusted Host List in about_Remote_Troubleshooting.
-ConfigurationFilePath (required)
Specifies a single path to a configuration file which specifies roles and features to be installed, and any configuration parameters needed. The path can be specified by using a local relative path or by using built-in environment variables prefixed with the $env tag (such as $env:systemdrive\filename). A configuration file can be generated by running the arfw in Server Manager. If this parameter is specified, then the *Name* parameter cannot be used.
-Confirm
Prompts you for confirmation before running the cmdlet.
-Credential
Specifies a user account that has access rights to perform this action. If the parameter is not added, or no value is specified, the default value of this parameter is the current user. Enter a user name in one of the following formats. Quotation marks are optional. - UserName - Domain\User - User@Domain.com - A Credential object returned by the Get-Credential cmdlet. If a user name is entered, then a prompt for a password is displayed.
-IncludeAllSubFeature
Indicates that the cmdlet installs all subordinate role services, and all subfeatures of parent roles, role services, or features specified by the *Name* parameter.
-IncludeManagementTools
Indicates that the cmdlet installs all applicable management tools of the roles, role services, or features specified by the *Name* parameter. Although management tools are installed by default when you are installing features by using the arfw, management tools are not installed by default when you install features by using the Install-WindowsFeature cmdlet; this parameter must be added to install management tools.
-LogPath
Specifies a name and path to a log file. Add this parameter if the results of your command must be stored in a log.
-Name (required)
Specifies a list of features to install. This parameter does not support wildcard characters. If this parameter is specified, then the *ConfigurationFilePath* parameter cannot be used.
-Restart
Indicates that cmdlet automatically restarts the target computer if a restart is required by the installation process for the specified roles or features. This parameter cannot be used with the *Vhd* parameter.
-Source
Specifies the path to feature files, if the files are not available in the local feature store of the target computer or VHD. Valid values for this parameter are either a network path or the path to a Windows image file (WIM). If you are installing roles or features on an offline VHD, you must use a mounted WIM. It is not necessary to mount the WIM file for installing on a running physical computer, because a WIM is mounted internally for deployments to a physical computer. Specify the path by using a local relative path, or by using built-in environment variables that are prefixed with the $env tag as shown in the following examples. The path specified in this parameter is only used if the command cannot find feature files in the local side-by-side store of the specified target computer or VHD. The command searches for feature files in the following order: - On the target computer or offline VHD. - Path specified as the value of this parameter. If you add a Universal Naming Convention (UNC) path, verify that the computer account of the target server has Read permissions on the share. The computer account should be in one of the following formats: DOMAIN\SERVERNAME$ or SERVER$ - Repository path specified by the Group Policy Object (GPO), Specify settings for optional component installation and component repair, located in Computer Configuration/Administrative Templates/System in Local Group Policy Editor. This Group Policy setting controls the following Windows Registry setting: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Policies\Servicing\LocalSourcePath. - Windows Update.
-Vhd (required)
Specifies the path to an offline VHD. The path can either point to a VHD file, or to a location on which the VHD is already mounted by using Deployment Image Servicing and Management (DISM) tools. The VHD can be on a local disk on the target computer, or on a network shared folder. If the VHD is in a network shared folder, then the value of this parameter is a UNC path to the VHD. In this case, the computer account of the computer that you are using to mount the VHD must have read and write permissions (Read/Write permissions in the File Sharing dialog box, or Full Control on the Security tab of the folder Properties dialog box) on the shared folder, or the VHD will not be accessible. Local loopback UNC paths are not supported. Use either of the following formats for the computer account: DOMAIN\SERVERNAME$ or SERVERNAME$. Add the *ComputerName* parameter to specify the target computer you want to use to mount the VHD. If the *ComputerName* parameter is not specified, then the local computer is used. The computer that you are using to mount the VHD must be running Windows Server 2012 R2. Any local path, such as D:\myFolder, that is specified by using this parameter is always relative to the target computer.
-WhatIf
Shows what would happen if the cmdlet runs. The cmdlet is not run.
Prerequisites
Windows with the Microsoft.Windows.ServerManager.Migration module and the Windows feature or management tools that provide it. Confirm target connectivity and version compatibility using the linked Microsoft reference.
Security considerations
This cmdlet changes system state. Review every target and parameter in the official reference, test outside production, and prepare an appropriate backup or rollback. Do not execute the example automatically.
Examples
Example 1: Install IIS, including all role services and applicable management tools on the specified computer
This command installs Web Server (IIS), including all role services and applicable management tools, on a computer named Server1, by using the credentials of a user account named contoso.com\PattiFul. Source: Microsoft, CC BY 4.0; transcript prompt/output removed. This example was not executed.