Install or uninstall roles, role services or features (2023)

Dorado para: Windows Server 2022, Windows Server 2019, Windows Server 2016, Windows Server 2012 R2, Windows Server 2012

In Windows Server, the Server Manager console and the Windows PowerShell cmdlets for Server Manager enable roles and features to be installed on local or remote servers or offline virtual hard disks (VHDs). You can install multiple roles and features on a single remote server or offline VHD in a single Add Roles and Features wizard or Windows PowerShell session.

You must log in to a server as an administrator to install or uninstall roles, role services, and features. If you are logged in to the local computer with an account that does not have administrative privileges on your destination server, right-click the destination server in theserverTile, and then clickmanage asto provide an account with administrator privileges. The server on which you want to mount an offline VHD must be added to Server Manager and you must have administrator rights on that server.

For more information about roles, role services, and features, seeRoles, role services, and functions.

This topic contains the following sections.

• Install roles, role services, and roles using the Add Roles and Features Wizard

• Install roles, role services, and features by using Windows PowerShell cmdlets

• Remove roles, role services, and features using the Remove Roles and Features Wizard

• Remove roles, role services, and features by using Windows PowerShell cmdlets

• Install features and functions on multiple servers by running a Windows PowerShell script

• Install the .NET Framework 3.5 and other features as needed

Install roles, role services, and roles using the Add Roles and Features Wizard

In a single session in the Add Roles and Features Wizard, you can install roles, role and features services on the local server, a remote server added to Server Manager, or an offline VHD. For more information on how to add a server to Server Manager for administration, seeAdd servers to Server Manager.

How to install features and functions using the Add Features and Features Wizard

1. If Server Manager is already open, continue to the next step. If Server Manager is not already open, open it by doing one of the following.

   • On the Windows desktop, start Server Manager by clickingserver administratoron the Windows taskbar.

   • in the windowsBeginningscreen clickserver administratortile.

2. About himManagemenu clickAdd roles and features.

3. About himbefore you startVerify that your target server and network environment are ready for the role and feature you want to install. clickNext.

4. About himSelect the type of installationpage, selectRole or feature based installationto install all parts of roles or functions on a single server orRemotedesktopdienste-Installationto install a virtual machine-based desktop infrastructure or a session-based desktop infrastructure for Remote Desktop Services. theRemotedesktopdienste-InstallationThe option distributes logical parts of the Remote Desktop Services role to different servers based on the administrators' needs. clickNext.

5. About himSelect destination serverpage, select a server from the pool or an offline VHD. To select an offline VHD as the destination server, first select the server to mount the VHD to, and then select the VHD file. For information on adding servers to your server group, seeAdd servers to Server Manager. After selecting the destination server, clickNext.

   Use

   (Video) Uninstall roles,role services,feature p.2

   To install roles and features on offline VHDs, the target VHDs must meet the following requirements.

   • The VHDs must be running the version of Windows Server that matches the version of Server Manager that you are running. See note at the beginningInstall roles, role services, and roles using the Add Roles and Features Wizard.

   • VHDs cannot have more than one system volume or partition.

   • The shared network folder where the VHD file is stored must grant the following access rights to the computer account (or local system account) of the server you chose to mount the VHD on. Just access to the user account is not enough. Participation can be grantedfileyWritepermissions for theaGroup to allow access to the VHD, but for security reasons it is not recommended.

     • Read writeaccess todata sharingdialog box.
     • control totalaccess tosecuritytab, file or folderfeaturesdialog box.

6. Select Roles, select Role Services for the role if necessary, and then clickNextselect functions.

   As you progress, the Add Roles and Features Wizard automatically notifies you if any conflicts are found on the target server that might prevent the installation or normal operation of the selected roles or features. You will also be prompted to add roles, role services, or features required by the roles or features you selected.

   If you intend to manage the feature remotely, either from another server or from a client-based Windows computer running remote server administration tools, you can choose not to install feature management tools and plugins on the destination server. By default, administrative tools are selected for installation in the Add Roles and Features Wizard.

7. About himConfirm installation selectionpage, review your role, role, and server options. When you are ready to install, clickinstall.

   You can also export your selections to an XML-based configuration file that you can use for unattended installations with Windows PowerShell. To export the settings that you specified in this session of the Add Roles and Features Wizard, clickExport configuration settingsand then save the XML file to a convenient location.

   DiePlease provide an alternate source pathcommand in theConfirm installation selectionThe page allows you to specify an alternate source path for the files required to install features and functions on the selected server. On Windows Server 2012 and later versions of Windows Serverfunctions on demandYou can reduce the disk space occupied by the operating system by removing functions and feature files from servers that are managed exclusively remotely. If you removed roles and features files from a server using theUninstall-WindowsFeature-deletecmdlet, you can install future features and functions on the server by specifying an alternate source path or share where the required features and functions files are stored. The source path or file share must allowfilepermissions for theagroup (not recommended for security reasons) or to the computer account (DOMAIN\server name$) from the destination server; Granting access to the user account is not enough. For more information on Features on Demand, seeWindows Server installation options.

   You can specify a .wim file as an alternate role file source when installing roles, role services, and roles on a running physical server. The source path of a WIM file must have the following format, withWIMas a prefix and the index where the feature files are located as a suffix:WIM:e:\sources\install.wim:4. However, you cannot use a .wim file directly as a source to install roles, role services, and features on an offline VHD. You must mount the VHD offline and point it to the mount path of your source files, or it must point to a folder that contains a copy of the .wim file contents.

8. After clickinginstall, theInstallation in progressThe page displays the installation progress, results, and messages such as warnings, errors, or post-installation configuration steps required by the features or features you installed. In Windows Server 2012 and later versions of Windows Server, you can close the Add Roles and Features Wizard while the installation is still in progress and view the installation results or other messages in thenotificationsArea at the top of the Server Manager console. press thenotificationsFlag icon to show more details about installations or other tasks you perform in Server Manager.

Install roles, role services, and features by using Windows PowerShell cmdlets

The Server Manager deployment cmdlets for Windows PowerShell work similarly to the GUI-based Add Roles and Features Wizard and the Remove Roles and Features Wizard, with one IMPORTANT difference. Unlike the Add Roles and Features Wizard, Windows PowerShell does not include management tools or snap-ins for a role by default. To include management tools as part of a role installation, add theInclude administration tools- Parameters for the cmdlet. When you install roles and features on a server running the Server Core installation option of Windows Server 2012 or later versions, you can add the management tools of a role to an installation, but the GUI-based management tools and snap-ins are not added. they can be installed on servers running the Server Core installation option of Windows Server. The Server Core installation option only installs the Windows PowerShell command line and management tools.

To install features and features by using the Install-WindowsFeature cmdlet

1. Do one of the following to open an elevated Windows PowerShell session.

   Use

   If you are installing roles and features on a remote server, you do not need to run Windows PowerShell with elevated user rights.

   • Right click on the Windows desktopWindows PowerShellon the taskbar, and then clickExecute as an administrator.

   • in the windowsBeginningRight-click the Windows PowerShell tile, and then click the app barExecute as an administrator.

2. untilGet-WindowsFeatureand then pressGet intoto view a list of roles and features available and installed on the local server. If the local computer is not a server or you want information about a remote server, run itGet-WindowsFeature-nombreDeEquipo <computer name>, in whichcomputer namerepresents the name of a remote computer running Windows Server 2016. The cmdlet output includes the command names of the functions and features that you add to your cmdlet in step 4.

   Use

   In Windows PowerShell 3.0 and later versions of Windows PowerShell, it is not necessary to import the Server Manager cmdlet module into the Windows PowerShell session before running the cmdlets that are part of the module. A module is automatically imported the first time you run a cmdlet that is part of the module. Also, Windows PowerShell cmdlets and the function names that are used with the cmdlets are not case-sensitive.

3. untilGet help Install-WindowsFeatureand then pressGet intoto see the syntax and accepted parameters for theInstall-WindowsFeaturecmdlet.

4. Enter the following and then pressGet into, isfunction namerepresents the command name of a function or feature that you want to install (obtained in step 2), andcomputer namerepresents a remote computer on which you want to install features and functions. Separate multiple values ​​forfunction nameby using commas. theStart againThe parameter automatically reboots the target server if necessary for feature or feature installation.

   Install-WindowsFeature -Name <feature_name> -computerName <computer_name> -Restart

   To install features and functions on an offline virtual hard disk, attach both thecomputer nameparameters and theVHDParameter. if you don't add themcomputer nameparameter, the cmdlet assumes that the local machine is mounted to access the VHD. thecomputer nameThe parameter contains the name of the server on which to mount the VHD and theVHD-The parameter contains the path to the VHD file on the specified server.

   Use

   You have to add thosecomputer nameparameter when you run the cmdlet on a computer running a Windows client operating system.

   To install roles and features on offline VHDs, the target VHDs must meet the following requirements.

   • The VHDs must be running the version of Windows Server that matches the version of Server Manager that you are running. See note at the beginningInstall roles, role services, and roles using the Add Roles and Features Wizard.

   • VHDs cannot have more than one system volume or partition.

   • The shared network folder where the VHD file is stored must grant the following access rights to the computer account (or local system account) of the server you chose to mount the VHD on. Just access to the user account is not enough. Participation can be grantedfileyWritepermissions for theaGroup to allow access to the VHD, but for security reasons it is not recommended.

     • Read writeaccess todata exchangedialog box.
     • control totalaccess tosecuritytab, file or folderfeaturesdialog box.

   Install-WindowsFeature -Name <feature_name> -VHD <ruta> -computerName <computer_name> -Restart

   Example:The following cmdlet installs the Active Directory Domain Services role and the Group Policy Management role on a remote server, ContosoDC1. Management tools and plugins are added usingInclude administration toolsand the destination server should be automatically restarted if the installation requires restarting the servers.

   Install-WindowsFeature -Name AD-Domain-Services, GPMC -Computername ContosoDC1 -IncludeManagementTools -Restart

5. When the installation is complete, verify the installation by checking theall serversServer Administrator, select a server on which you have installed roles and features, and view theroles and functionsTile on the selected server page. You can also run theGet-WindowsFeatureCmdlet for the selected server (Get-WindowsFeature -computerName <computer name>) to display a list of roles and features installed on the server.

Remove roles, role services, and features using the Remove Roles and Features Wizard

You must log in to a server as an administrator to uninstall roles, role services, and features. If you are logged in to the local computer with an account that does not have administrative privileges on your target uninstall server, right-click the target server in theserverTile, and then clickmanage asto provide an account with administrator privileges. The server on which you want to mount an offline VHD must be added to Server Manager and you must have administrator rights on that server.

How to remove features and features using the Remove Features and Features Wizard

1. If Server Manager is already open, continue to the next step. If Server Manager is not already open, open it by doing one of the following.

   • On the Windows desktop, start Server Manager by clickingserver administratoron the Windows taskbar.

     (Video) How to remove server roles or features from Windows Server 2012

   • in the windowsBeginningscreen clickserver administratortile.

2. About himManagemenu clickDelete roles and functions.

3. About himbefore you startOn the page, make sure you're ready to remove roles or functions from a server. clickNext.

4. About himSelect destination serverpage, select a server from the pool or an offline VHD. To select an offline VHD, first select the server to mount the VHD to, and then select the VHD file.

   Use

   The shared network folder where the VHD file is stored must grant the following access rights to the computer account (or local system account) of the server you chose to mount the VHD on. Just access to the user account is not enough. Participation can be grantedfileyWritepermissions for theaGroup to allow access to the VHD, but for security reasons it is not recommended.

   • Read writeaccess todata sharingdialog box.
   • control totalaccess tosecuritytab, file or folderfeaturesdialog box.

   For information on adding servers to your server group, seeAdd servers to Server Manager. After selecting the destination server, clickNext.

   Use

   You can use the Remove Roles and Features Wizard to remove roles and features from servers that are running the same version of Windows Server that supports the version of Server Manager that you are using. You cannot remove roles, role services, or roles from servers running Windows Server 2016 if you are running Server Manager on Windows Server 2012 R2, Windows Server 2012, or Windows 8. You cannot use the Remove Roles and Features Wizard to remove roles and features of servers running Windows Server 2008 or Windows Server 2008 R2.

5. Select Roles, select Role Services for the role if necessary, and then clickNextselect functions.

   As you progress, the Remove Features and Features Wizard automatically prompts you to remove any features, role services, or features that cannot run without the features or features you are removing.

   Additionally, you can remove management tools and plugins for roles on the target server. By default, the Remove Roles and Features Wizard has management tools selected for removal. You can keep the administration tools and plugins if you plan to use the selected server to manage the role on other remote servers.

6. About himConfirm distance selectionpage, review your role, role, and server options. When you're ready to remove the features or features, clickextinguish.

7. After clickingextinguish, theremoval progressThe page shows the progress, results and messages about the removal, e.g. B. Warnings, errors, or configuration steps required after removal, e.g. B. Target server reboot. In Windows Server 2012 and later versions of Windows Server, you can close the Remove Roles and Features Wizard while the removal is still in progress and view the removal results or other messages in thenotificationsArea at the top of the Server Manager console. press thenotificationscheckmark to display more details about distances or other tasks you are performing in Server Manager.

Remove roles, role services, and features by using Windows PowerShell cmdlets

The Server Manager deployment cmdlets for Windows PowerShell work similarly to the GUI-based Remove Roles and Features Wizard, with one IMPORTANT difference. Unlike the Remove Roles and Features Wizard, Windows PowerShell does not remove the management tools or snap-ins for a role by default. To remove management tools as part of removing a role, add theInclude administration tools- Parameters for the cmdlet. When you uninstall roles and roles from a server that is running the Server Core installation option of Windows Server 2012 or a later version of Windows Server, this parameter removes the Windows PowerShell and command-line management tools for the specified roles and roles.

How to remove features and features using the Uninstall-WindowsFeature cmdlet

1. Do one of the following to open an elevated Windows PowerShell session.

   Use

   If you are uninstalling roles and features from a remote server, you do not need to run Windows PowerShell with elevated user rights.

   • Right click on the Windows desktopWindows PowerShellon the taskbar, and then clickExecute as an administrator.

   • in the windowsBeginningRight-click the Windows PowerShell tile on the screen, and then click the app barExecute as an administrator.

2. untilGet-WindowsFeatureand then pressGet intoto view a list of roles and features available and installed on the local server. If the local computer is not a server or you want information about a remote server, run itGet-WindowsFeature-nombreDeEquipo <computer name>, in whichcomputer namerepresents the name of a remote computer running Windows Server 2016. The cmdlet output includes the command names of the functions and features that you add to your cmdlet in step 4.

   Use

   In Windows PowerShell 3.0 and later versions of Windows PowerShell, it is not necessary to import the Server Manager cmdlet module into the Windows PowerShell session before running the cmdlets that are part of the module. A module is automatically imported the first time you run a cmdlet that is part of the module. Also, Windows PowerShell cmdlets and the function names that are used with the cmdlets are not case-sensitive.

3. untilGet Help Uninstall-WindowsFeatureand then pressGet intoto see the syntax and accepted parameters for theDesinstalar-WindowsFeaturecmdlet.

4. Enter the following and then pressGet into, isfunction namerepresents the command name of a function or feature that you want to remove (obtained in step 2), andcomputer namerepresents a remote computer from which you want to remove roles and functions. Separate multiple values ​​forfunction nameby using commas. theStart againThe parameter automatically restarts the target servers if necessary for role or role removal.

   Desinstalar-WindowsFeature -Name <feature_name> -computerName <computer_name> -Restart

   To remove features and features from an offline VHD, add both thecomputer nameparameters and theVHDParameter. if you don't add themcomputer nameparameter, the cmdlet assumes that the local machine is mounted to access the VHD. thecomputer nameThe parameter contains the name of the server on which to mount the VHD and theVHD-The parameter contains the path to the VHD file on the specified server.

   Use

   You have to add thosecomputer nameparameter when you run the cmdlet on a computer running a Windows client operating system.

   The shared network folder where the VHD file is stored must grant the following access rights to the computer account (or local system account) of the server you chose to mount the VHD on. Just access to the user account is not enough. Participation can be grantedfileyWritepermissions for theaGroup to allow access to the VHD, but for security reasons it is not recommended.

   • Read writeaccess todata sharingdialog box.
   • control totalaccess tosecuritytab, file or folderfeaturesdialog box.

   Uninstall-WindowsFeature -Name <feature_name> -VHD <path> -computerName <computer_name> -Restart

   Example:The following cmdlet removes the Active Directory Domain Services role and the Group Policy Management role from a remote server, ContosoDC1. Management tools and plugins are also removed, and the destination server should be automatically restarted if removal requires a restart of the servers.

   Desinstalar-WindowsFeature -Nombre AD-Domain-Services, GPMC -computerName ContosoDC1 -IncludeManagementTools -Reiniciar

5. After the removal is complete, verify that the features and functions have been removed using theall serversIn Server Manager, select the server from which you removed roles and features and view theroles and functionsTile on the selected server page. You can also run theGet-WindowsFeatureCmdlet for the selected server (Get-WindowsFeature -computerName <computer name>) to display a list of roles and features installed on the server.

Install features and functions on multiple servers by running a Windows PowerShell script

Although you cannot use the Add Roles and Features wizard to install roles, role services, and features on more than one target server in a single wizard session, you can use a Windows PowerShell script to add roles, role services, and features to various destinations. to install servers that you manage with Server Manager. The script you use to perform the batch deployment, as this process is called, references an XML configuration file that you can easily create by using the Add Roles and Features Wizard and clickingExport configuration settingsafter going through the wizardConfirm installation selectionAdd Features and Features Wizard page.

How to install roles and features on multiple servers

1. If you haven't already done so, create an XML configuration file that contains the roles, role services, and roles that you want to install on multiple servers. You can create this configuration file by running the Add Roles and Roles Wizard, selecting the roles, role services, and roles you want, and clickingExport configuration settingsafter going through the wizardConfirm installation selectionPage. Save the configuration file in a suitable location. You don't have to clickinstallor complete the wizard if you are only running it to create a configuration file.

2. Do one of the following to open an elevated Windows PowerShell session.

   • Right click on the Windows desktopWindows PowerShellon the taskbar, and then clickExecute as an administrator.

   • in the windowsBeginningRight-click the Windows PowerShell tile on the screen, and then click the app barExecute as an administrator.

3. Copy and paste the following script into your Windows PowerShell session.

   function Invoke-WindowsFeatureBatchDeployment { param ( [parameter (required)] [string []] $computerNames, [parameter (required)] [string] $ConfigurationFilepath ) # Deploy features to multiple computers at the same time. $jobs = @() foreach($computerName in $computerNames) { $jobs += start-Job -Command { Install-WindowsFeature -ConfigurationFilepath $using:ConfigurationFilepath -computerName $using:computerName -Restart } } Receive-Job -Job $ Jobs -Waiting | select-Object Success, RestartNeeded, ExitCode, FeatureResult}

   The destination servers are automatically restarted if necessary for the roles and functions you have selected.

4. Execute the function as follows.

   1. Create a variable to store the names of your target computers separated by commas. In the following example, the variable is$ServerNamessaves destination server namesContoso_01yContoso_02. PressGet into.

      # Beispielaufruf $ServerNames = 'Contoso_01','Contoso_02'Invoke-WindowsFeatureBatchDeployment -computerNames $ServerNames -ConfigurationFilepath C:\Users\sampleuser\Desktop\DeploymentConfigTemplate.xml

   2. To run the function, enter the following and then pressGet into, is$ServerNamesis an example of the variable you created in the previous step andC:\Users\Sample User\Desktop\DeploymentConfigTemplate.xmlis an example of a path to the configuration file that you created in step 1.

      Invoke-WindowsFeatureBatchDeployment -computerNames $ServerNames -ConfigurationFilepath C:\Users\Sampleuser\Desktop\DeploymentConfigTemplate.xml

5. When the installation is complete, verify the installation by checking theall serversServer Administrator, select a server on which you have installed roles and features, and view theroles and functionsTile on the selected server page. You can also run theGet-WindowsFeatureCmdlet directed to a specific server (Get-WindowsFeature -nombreDeEquipo<computer name>) to display a list of roles and features installed on the server.

Install the .NET Framework 3.5 and other features as needed

Starting with Windows Server 2012 and Windows 8, the .NET Framework 3.5 feature files (including the .NET Framework 2.0 and .NET Framework 3.0) are not available on the local computer by default. The files have been deleted. Feature files that have been removed in a Features on Demand configuration are available through Windows Update along with feature files for the .NET Framework 3.5. By default, if the role files are not available on the destination server that is running Windows Server 2012 or later, the installation process checks for the missing files by connecting to Windows Update. You can override the default behavior by configuring a Group Policy setting or by specifying an alternate source path during installation, whether you are installing from the Add Roles and Features Wizard GUI or from a command line.

You can install the .NET Framework 3.5 by doing one of the following steps.

• UseHow to install the .NET Framework 3.5 by running the Install-WindowsFeature cmdletto add thoseThoseand specify a source from which to get the .NET Framework 3.5 function files. if you don't add themThose, the installation process first determines whether a path to the feature files has been specified through Group Policy settings, and if no such path is found, it checks for the missing feature files using Windows Update.

• UseHow to install the .NET Framework 3.5 by using the Add Roles and Features Wizardto specify an alternate source file location in theConfirm installation optionsAdd Features and Features Wizard page.

• UseHow to install the .NET Framework 3.5 using DISMto get files from Windows Update by default or by specifying a source path to the installation media.

Configure alternate sources for feature files in Group Policyfor the .NET Framework 3.5 or other functions if no function files are found on the local computer.

How to install the .NET Framework 3.5 by running the Install-WindowsFeature cmdlet

1. Do one of the following to open an elevated Windows PowerShell session.

   Use

   If you are installing roles and features from a remote server, you do not need to run Windows PowerShell with elevated user rights.

   • Right click on the Windows desktopWindows PowerShellon the taskbar, and then clickExecute as an administrator.

   • in the windowsBeginningRight-click the Windows PowerShell tile on the screen, and then click the app barExecute as an administrator.

   • On a server that runs the Server Core installation option for Windows Server 2012 R2 or Windows Server 2012, enterPower Shellat a command prompt, and then pressGet into.

2. Enter the following command and then pressGet into. In the following example, the source files are in parallel storage (abbreviated asSxS) on the installation media on drive D.

   Install-WindowsFeature NET-Framework-Core -Source D:\Sources\SxS

   If you want the command to use Windows Update as the source for missing feature files, or if a default source has already been set through Group Policy, you don't need to add the file.Thoseparameters, unless you want to specify a different font.

How to install the .NET Framework 3.5 by using the Add Roles and Features Wizard

1. About himManagemenu in Server Manager, clickAdd roles and features.

2. Select a destination server running Windows Server 2016.

3. About himselect functionsAdd Roles and Features Wizard Page.NET Framework 3.5.

4. If the local computer allows it through Group Policy settings, the installation process tries to use Windows Update to recover the missing feature files. clickinstall; You do not need to continue to the next step.

   (Video) The request to add or remove features on the specified server failed Installtion...Error: 0x8024402c

   If your group policy settings do not allow this, or if you want to use a different source for the .NET Framework 3.5 function files in whichConfirm installation selectionWizard page, clickPlease provide an alternate source path.

5. Provide a path to a side-by-side store (such asSxS) on installation media or in a WIM file. In the following example, the installation media is in drive D.

   D:\Sources\SxS\

   To specify a WIM file, add aWIM:Prefix and add the index of the image to be used as a suffix in the WIM file, as shown in the following example.

   WIM:\\server name\share\install.wim:3

6. clickOKand then clickinstall.

How to install the .NET Framework 3.5 using DISM

1. Do one of the following to open an elevated Windows PowerShell session.

   Use

   If you are installing roles and features from a remote server, you do not need to run Windows PowerShell with elevated user rights.

   • Right click on the Windows desktopWindows PowerShellon the taskbar, and then clickExecute as an administrator.

   • in the windowsBeginningRight-click the Windows PowerShell tile on the screen, and then click the app barExecute as an administrator.

   • On a server running the Server Core installation option, enterPower Shellat a command prompt, and then pressGet into.

2. Run one of the following DISM commands.

   • If the computer has access to Windows Update or a default source file location has already been configured in Group Policy, run the following command.

     DISM /online /Enable function /Function name:NetFx3 /All

   • If the computer has access to the installation media, run a command similar to the following. In the following example, the operating system installation media is in drive D. Therestricted accessThe parameter prevents the command from trying to contact Windows Update or a server running WSUS.

     DISM /online /Enable-Feature /Featurename:NetFx3 /All /LimitAccess /Source:d:\sources\sxs

   Use

   The DISM command is case sensitive.

Configure alternate sources for feature files in Group Policy

The Group Policy settings described in this section specify the authorized source locations for .NET Framework 3.5 files and other feature files removed as part of a feature-on-demand configuration. Policy settingsSpecify settings for installing and repairing optional componentsis found inComputer Configuration\Administrative Templates\SystemFolders in the Group Policy Management Console or in the Local Group Policy Editor.

How to configure a default alternate source path in Group Policy

1. In the Local Group Policy Editor or Group Policy Management Console, open the following policy settings.

   Computer Configuration\Administrative Templates\System\Optional component installation and repair settings

2. ChoosePermittedto enable the policy setting if it is not already enabled.

3. I amAlternate source file pathtext field in theoptionsIn the panel, provide a full path to a shared folder or a .wim file. To specify a .wim file as an alternate source file location, add the prefixWIM:to the path and add the index of the image to be used in the WIM file as a suffix. The following are examples of values ​​that you can specify.

   • Path to a shared folder:\\server name\Pull apart\folder names

   • Path to a WIM file in which3represents the index of the image where the feature files are located:WIM:\\server name\share\install.wim:3

4. If you do not want computers controlled by this policy setting to check Windows Update for missing feature files, select this optionNever try to download Payload from Windows Update.

5. If computers controlled by this policy setting normally receive updates through WSUS, but you prefer to use Windows Update instead of WSUS to find missing feature files, selectContact Windows Update directly to download repair content instead of Windows Server Update Services (WSUS)..

6. clickOKwhen you have finished changing these policy settings, and then close Group Policy Editor.

See also

Windows Server installation optionsMicrosoft .NET Framework 3.5 Deployment ConsiderationsHow to enable or disable Windows features