Most modern Windows applications require .NET Framework to work properly. The roles and features setup wizard Server Manager in Windows Server 2012 R2 allows to install two different versions of .NET Framework at a time – 3.5 and 4.5. The installation of .NET Framework 4.5 doesn’t usually cause any problems – it’s very simple, however, you can’t say exactly the same about the installation of .NET Framework 3.5.
Actually, when trying to install .NET Framework 3.5 in Windows Server 2012 R2 with the standard settings, the following error message appears: «Installation of one of more roles, role services or features failed. The source files could not be found…».
The reason behind this behavior is that .NET Framework 3.5 binary files are not a part of the local cache of the binary files that are saved on the server’s system disk when the operating system is being installed. This is done under the concept of Features on Demand in Windows Server 2012 to reduce the amount of disk space occupied by the OS for its own needs.
Check if .NET Framework 3.5 is in the local repository using the Powershell command:

With the Release of Server 2012 R2 Microsoft completely changed how Remote Desktop Services are deployed and managed. This change tossed many like myself for a loop as I could not find any documentation on how to do what was once a 5 minute task. I could already install 3 updates one by one, these are also showing up in installed updates. Will continue the procedure this way. Today Jan 21.2017 i tried to install (as single update) Update for Windows Server 2012 R2 (KB2967917) only this one failed, maybe you see this in the log. It fails even if I install it manually.

• The Microsoft Evaluation Center brings you full-featured Microsoft product evaluation software available for download or trial on Microsoft Azure.
• Feb 07, 2017 I could already install 3 updates one by one, these are also showing up in installed updates. Will continue the procedure this way. Today Jan 21.2017 i tried to install (as single update) Update for Windows Server 2012 R2 (KB2967917) only this one failed, maybe you see this in the log. It fails even if I install it manually.

/Online means that you need to upgrade your current OS, and not the wim image
/enable-feature/featurename: NetFX3/all means that it is necessary to install .NET Framework 3.5 with all its features
/Source is the path to the directory with Windows distribution, which contains the necessary components
/LimitAccess prevents accessing Windows Update
The same operation in PowerShell for installing .Net 3.5 looks like this:
Add-WindowsFeature NET-Framework-Core -Source d:sourcessxs
Path to the original Windows distribution can be set in the system on a regular basis using:

• the registry parameter RepairContentServerSource that is located in the HKLMSOFTWAREMicrosoftWindowsCurrentVersionPoliciesServicing branch
• oragrouppolicy Specify settings for optional component installation and component repair (the policychangesthissettingintheregistry)

To fix the problem try to install .Net online through from Microsoft servers:

• Save the current Windows Update settings to the reg file (key HKLMSoftwarePoliciesMicrosoftWindowsWindowsUpdate)
• Delete this key and restart the WU service: net stop wuauserv & net start wuauserv
• Run the .Net5 online installation: DISM /Online /Enable-Feature /FeatureName:NetFx3 /All
• After the installation is complete, return the WU settings by importing the reg file and restart the WindowsUpdate service again

Uninstall this updates and after the reboot, try installing .NET 3.5.

This document describes how to install Internet Information Services (IIS) 8.5 on Windows Server® 2012 R2. IIS is the Web server role in Windows Server 2012 R2. The Windows Server 2012 R2 operating system has all the IIS features needed to support the hosting of Web content in production environments. Windows 8 also includes IIS features, but feature availability depends on the operating system version.

Note

You can use the procedures in this document to install IIS 8.0 or IIS 8.5.

The Web server has a modular design that enables you to customize a server by adding or removing modules to meet your specific needs. The Install IIS 8.5 on Windows Server 2012 R2 section describes how to install modules, and the Modules in IIS 8.5 section below describes the functionality that each module provides and which modules are installed by default.

New in IIS 8.5

IIS 8.5 includes several new features not found in IIS 8.0 or lower:

• Enhanced logging. An administrator can enable the logging of additional custom fields from request or response headers, or from server variables.
• Logging to event tracing for Windows. An administrator can enable the sending of logging information to Event Tracing for Windows (ETW).
• Dynamic Website activation. If there are a large number of configured sites (100 or greater, by default), the service will not activate any of the sites when the service is started.
• Idle Worker Process Page-Out. An administrator can enable an idle worker process to be suspended rather than terminated.

For more information on these features, see What's New in IIS 8.5.

For information on new features in IIS 8.0, see What's New in IIS 8.0.

Before You Begin

Ensure that you have administrative user rights on the computer on which you plan to install IIS 8.5. Note that by default, you do not have administrative user rights if you are logged on as a user other than as the built-in administrator, even if you were added to the local Administrators group on the computer.

Log on either to the built-in administrator account, or explicitly invoke applications as the built-in administrator by using the runas command-line tool.

Note

You can run runas /user:administrator cmd.exe so that every application you run from that command line will be elevated, eliminating the need to use the runas syntax from that command line.

If you are logged on to an account other than the built-in local administrator account, you may see the following security alert dialog box.

Install IIS 8.5 on Windows Server 2012 R2

IIS is one of the server roles on Windows Server 2012 R2, named Web Server (IIS). You can use the following to install IIS:

• The Server Manager user interface in Windows Server 2012 R2
• A command-line installation using DISM (Deployment Image Servicing and Management)
• A command-line installation using PowerShell cmdlets

Note

IIS can also be installed on Windows 8 through the Turn Windows features on or off dialog box from the Programs and Features settings of the Control Panel.

Install IIS 8.5 using the Server Manager

Server Manager provides a single dashboard to install or uninstall server roles, role services, and features. Server Manager also gives an overview of all currently installed roles and features.

When you install IIS 8.5 using the Windows Server 2012 R2 Server Manager, the steps you perform are different when you install IIS for the first time, as opposed to when you add roles, services, or features to an existing IIS installation. The two procedures are provided below. Different procedures are also used to add and remove roles, role services, and features. You cannot add and remove from the same UI

For more information on how to run the installation wizards in Server Manager, see Install or Uninstall Roles, Role Services, or Features.

Install IIS 8.5 for the first time in the Server Manager

When the Web Server (UI) role is chosen for the first time in the Add Roles and Features Wizard in Server Manager, the basic components and services needed for IIS are automatically selected. The following procedure will install Internet Information Services on a running physical server when IIS has not already been installed. To change an existing installation of IIS, perform the next procedure, Install additional role services for IIS. These two procedures involve different steps.

1. Open Server Manager by clicking the Server Manager icon on the desktop.

2. In the Server Manager window, with the Dashboard and Quick Start selected, click Add roles and features, or click the Manage menu, and then click Add Roles and Features. The Add Roles and Features Wizard will start with a Before You Begin page. The wizard asks for verification of the following:

   • The administrator account has a strong password.
   • The network settings, such as IP addresses, are configured.
   • The most current security updates from Windows® Update are installed.

3. On the Before You Begin page, click Next.

4. On the Installation Type page, select Role-based or feature-based installation to configure a single server. Click Next.

5. On the Server Selection page, select Select a server from the server pool, and then select a server; or select Select a virtual hard disk server, select a server to mount the VHD on, and then select a VHD file. Click Next.

   Note

   To connect to the virtual hard disk, the virtual machine must be turned off and disconnected. If you select a VHD file from a network share, that share must grant Read and Write permissions to the computer (local system) account of the server that you selected to mount the VHD (user-only account access is not sufficient).

   Note

   Servers in a server pool will be available only if they have been added by the Add other servers to manage command in Server Manager.

6. On the Server Roles page, select Web Server (IIS).

7. In the Add Roles and Features wizard, click Add Features if you want to install the IIS Management Console. If you do not want to install the Management Console, uncheck Include management tools (if applicable), and then click Continue.

8. On the Server Roles page, click Next.

   Note

   The features required for the default role services of Management Tools and IIS Management Console will be preselected in the Features page.

9. On the Features page, select any features that you would like to install, and then click Next. Note that you do not need to select any features on this page to install IIS. IIS setup will select the features that are required.

10. On the Web Server Role (IIS) page, click Next.

11. On the Role Services page, select any additional role services that you want to install.

    Note

    When you install IIS for the first time by selecting Web Server (IIS), you will get at least the default installation that includes a minimum set of role services. You can see at this point that those default services are preselected on the Server Roles page. For a list of the server roles available, and which roles are installed by default, see Modules in IIS 8.5. You will have the chance to select more role services later in this procedure.

    Note

    You can also deselect role services that were selected by default when you selected Web Server. However, at least one role service must be selected for Web Server to be selected and installed.

12. If you selected a role service that requires other role services or features to be installed, a page will be opened indicating the role services or features to be installed. Leave Include management tools (if applicable) selected to select the install management tools associated with the server role. You may not need the management tools on the destination server if you plan to manage the role remotely. Click Add Features to add the required role services or features.

13. After you have added the role services that you need on the Role Services page, click Next.

14. On the Confirmation page, verify the role services and features that are selected. Select Restart the destination server automatically if required to restart the destination server if the settings need to take immediate effect. To save the configuration information to an XML-based file that you can use for unattended installations with Windows PowerShell, select Export configuration settings, move to the appropriate path in the Save As dialog box, enter a file name, and then click Save.

    When you are ready to start the installation process on the Confirmation page, click Install.

15. The Installation Progress page is displayed. You can close the wizard without interrupting running tasks. You can view task progress or open the page again by clicking Notifications in the notification area, and then clicking Task Details.

16. On the Results page, verify that the installation succeeds, and then click Close.

17. Confirm that the Web server works by opening a Web browser, and verifying that the following default Web page is displayed when you use the http://localhost address.

Install additional IIS 8.5 role services in the Server Manager

After you have installed the Web Server role on a running physical server for the first time, you can run through the installation process again to install additional roles, role services, and features.

1. Open Server Manager by clicking the Server Manager icon on the desktop.

2. In the Server Manager window, with the Dashboard and Quick Start selected, click Add roles and features, or click the Manage menu, and then click Add Roles and Features. The Add Roles and Features wizard will start with a Before You Begin page. The wizard asks for verification of the following:

   • The administrator account has a strong password.
   • The network settings, such as IP addresses, are configured.
   • The most current security updates from Windows® Update are installed.

3. On the Before You Begin page, click Next.

4. On the Installation Type page, select Role-based or feature-based installation to configure a single server. Click Next.

5. On the Server Selection page, select Select a server from the server pool, and then select a server; or select Select a virtual hard disk server, select the server to mount the VHD on, and then select the VHD file. Click Next.

   Note

   To connect to the virtual hard disk, the virtual machine must be turned off and disconnected. If you select a VHD file from a network share, that share must grant Read and Write permissions to the computer (local system) account of the server that you selected to mount the VHD (user-only account access is not sufficient).

   Note

   Servers in a server pool will be available only if they have been added by the Add other servers to manage command in the Server Manager.

   Note

   On the Server Roles page, Web Server (IIS) will be selected when IIS 8.0 has already been installed. If Web server (IIS) is not selected, perform the procedure in Install IIS 8.5 for the first time in the Server Manager.

6. On the Server Roles page, open the Web Server (IIS) tree until you see a role service that you want to install. Select the role service.

   Note

   Those roles, services, and features that have already been installed will be identified by 'Installed' in parentheses after the name, and the name will be grayed out. To remove a role, service, or feature, see Uninstall IIS 8.5 Using the Server Manager. Note, however, that you can expand the lower-level entries under a node even when the node is grayed out.

   Note

   For a list of the server roles that are available, and which roles are installed by default, see Modules in IIS 8.5 below.

7. If the role service that you selected requires other role services or features to be installed, an Add Features page will be opened listing those required role services or features. Leave Include management tools (if applicable) selected to select the install management tools associated with the server role. You may not need the management tools on the destination server if you plan to manage the role remotely. Click Add Features to add the required role services or features to the installation.

8. If you need any additional role services, repeat steps 6 and 7.

   Note

   Add only the modules that are necessary to minimize the IIS installation footprint and the attack surface.

   When you have selected all required role services, and their dependencies, on the Server Roles page, click Next.

9. On the Features page, select any features that you need to be installed. Any features required to be installed for role services that you selected in step 6 will already be selected. Click Next.

10. On the Confirmation page, verify the role services and features that are selected. Select Restart the destination server automatically if required to restart the destination server if the settings need to take immediate effect. To save the configuration information to an XML-based file that you can use for unattended installations with Windows PowerShell, select Export configuration settings, move to the appropriate path in the Save As dialog box, enter a file name, and then click Save.

    When you are ready to start the installation process on the Confirmation page, click Install.

11. The Installation Progress page is displayed. You can close the wizard without interrupting running tasks. You can view task progress or open the page again by clicking Notifications in the notification area, and then clicking Task Details.

12. On the Results page, verify that the installation succeeds, and then click Close.

13. Confirm that the Web server works by opening a Web browser, and verifying that the following default Web page when you use the http://localhost address.

Uninstall IIS 8.5 using the Server Manager

In the Add Roles and Features wizard of Server Manager, you cannot delete existing features that have already been installed. To delete roles and features, use the Remove Roles and Features wizard of Server Manager. You can remove an individual role, role service, or feature by unchecking it in the wizard, or you can uninstall all of IIS by unchecking the IIS Web Server Role.

Windows 2012 R2 Install-module

1. Open Server Manager by clicking the Server Manager icon on the desktop.

2. Click Manage at the top of the Server Manager, and then click Remove Roles and Features.

3. On the Before you begin page, click Next.

4. On the Server Selection page, select the server from the server pool, and then click Next.

5. On the Remove Server Roles page, clear the check box of any server role or role service that you would like to remove.

6. If you uncheck a role service that has feature dependencies, the Remove Features dialog box will be displayed showing the dependencies. Click Remove Features to remove them. You can remove all of IIS by unchecking Web Server (IIS).

7. On the Remove Server Roles page, select any other role or role service that you want to remove, and then click Next.

8. On the Features page, uncheck any feature that you would like to remove. If you uncheck a feature that has feature dependencies, a dialog box will be displayed showing the dependencies. Click Remove Features to remove them. On the Features page, click Next.

9. On the Confirmation page, verify that the roles, role services, and features to be removed are correct, and then click Remove.

   Note

   It is recommended that you do a restart if you are prompted to do so, unless you have other activities that you want to do before the restart takes place. A restart is especially important when you remove roles, role services, or features.

10. The Removal Progress page is displayed. You can close the wizard without interrupting running tasks. You can view task progress or open the page again by clicking Notifications in the notification area, and then clicking Task Details.

11. On the Results page, click Close.

12. Restart the destination server to finish removing features.

Install IIS 8.5 from the Command Line

You can install IIS 8.5 from the command line using DISM or PowerShell. Note that DISM and PowerShell have different namespaces for installation parameters, so the parameter names used in their commands will be different. For more information, see Modules in IIS 8.5.

Note

Pkgmgr.exe has been deprecated. Use DISM instead for scripts installing IIS 8.5.

Install IIS 8.5 using DISM

Automating the installation of IIS by using unattended scripts is very useful if you need to deploy multiple Web servers and want to ensure that each of the Web servers is set up with identical components and services. In Windows Server 2012 R2, DISM is used for unattended scripts, letting you install or uninstall optional features from a command prompt or scripts. To use DISM, you must make sure you have administrative user rights on the computer. For more information about DISM, see DISM Overview

If you do not explicitly include in the DISM code a feature that the IIS installation has a dependency on, the installation will fail, and will not generate an error message. For a list of dependencies required, see Feature Dependencies.

For a full list of the DISM parameters corresponding to IIS roles, services, and features, see Modules in IIS 8.5.

The following script will install all roles, role services, and features of IIS 8.5, getting the full IIS installation that includes all available feature packages. If there are roles, role services, or features that you do not need, you should edit the script to include only those that you require. The order of the commands in the DISM script does not matter. The entire script will be handed off to the engine and treated as one transaction. To install IIS 8.5 with a script, type the following on one line in an elevated command prompt.

Install IIS 8.5 using PowerShell

You can use the following PowerShell cmdlets to install all of IIS 8.5:

To install only specific features, list them in the PowerShell cmdlet, as in the following example:

The following points apply to running the PowerShell cmdlets:

• The cmdlet requires elevation. You must be running a Windows PowerShell session as an administrator to run the cmdlet.
• The cmdlet does not install management tools for roles, role services, and features by default. You must add the IncludeManagementTools parameter to the cmdlet to do so.

For a full list of the PowerShell parameters corresponding to IIS 8.5 roles, services, and features, with more information, see Modules in IIS 8.5. The following lists all these parameters.

• Web-Server
• Web-WebServer
• Web-Security
• Web-Filtering
• Web-Cert-Auth
• Web-IP-Security
• Web-Url-Auth
• Web-Windows-Auth
• Web-Basic-Auth
• Web-Client-Auth
• Web-Digest-Auth
• Web-CertProvider
• Web-Common-Http
• Web-Http-Errors
• Web-Dir-Browsing
• Web-Static-Content
• Web-Default-Doc
• Web-Http-Redirect
• Web-DAV-Publishing
• Web-Performance
• Web-Stat-Compression
• Web-Dyn-Compression
• Web-Health
• Web-Http-Logging
• Web-ODBC-Logging
• Web-Log-Libraries
• Web-Custom-Logging
• Web-Request-Monitor
• Web-Http-Tracing
• Web-App-Dev
• Web-Net-Ext
• Web-Net-Ext45
• Web-ASP
• Web-Asp-Net
• Web-Asp-Net45
• Web-CGI
• Web-ISAPI-Ext
• Web-ISAPI-Filter
• Web-WebSockets
• Web-AppInit
• Web-Includes
• Web-Ftp-Server
• Web-Ftp-Service
• Web-Ftp-Ext
• Web-Mgmt-Tools
• Web-Mgmt-Console
• Web-Mgmt-Compat
• Web-Metabase
• Web-WMI
• Web-Lgcy-Mgmt-Console
• Web-Lgcy-Scripting
• Web-Scripting-Tools
• Web-Mgmt-Service

Uninstall IIS 8.5 using PowerShell

You can use the PowerShell cmdlet UnInstall-WindowsFeature to uninstall IIS 8.5. Run get-help Install-WindowsFeature at a PowerShell command line to see the syntax of the cmdlet. The following points apply to running the cmdlet:

• The cmdlet requires elevation. You must be running a Windows PowerShell session as an administrator to run the cmdlet.
• The cmdlet does not uninstall management tools for roles, role services, and features by default. You must add the IncludeManagementTools parameter to the cmdlet to do so.

Windows 2012 R2 Install-module Not Found

Modules in IIS 8.5

IIS modules are individual role services that the server uses to process requests. The following table shows which modules are available to be installed in the Web server, which are installed by default, which role the role service is included in, the parameter used in DISM or PowerShell to install them, and a brief description of the functionality that they provide.

Note

An asterisk (*) in the table below denotes a role or role service that is installed by default when the Web Server (IIS) role is installed.

Feature Dependencies

The following table shows which role services and features must be installed for the role service or features in the table row to be installed.

The Add Roles and Features Wizard and Remove Roles and Features Wizard of Server Manager take care of dependencies by prompting you to add dependencies when adding a role service or feature, or to remove dependencies when removing a role service or feature. However, when you install IIS using DISM, you need to include in the DISM code any dependency that a role service or feature being installed has, or the installation will fail, and you may not receive an indication why it failed.

When you remove a role service or feature, make sure that you do not remove a service or feature that another service or feature has a dependency on. There can be an intersection of dependencies, for example between ASP and ASP.NET. So if you were to remove ASP, and remove its feature dependencies, you could remove dependencies for ASP.NET, as well.

Windows 2012 R2 Install Iis

See also