You need to ensure that the feature can be installed on Server1

You have a server named Server1 that runs Windows Server 2012 R2.
You try to install the Microsoft .NET Framework 3.5 Features feature on Server1, but the
installation fails repeatedly.
You need to ensure that the feature can be installed on Server1.
What should you do?

You have a server named Server1 that runs Windows Server 2012 R2.
You try to install the Microsoft .NET Framework 3.5 Features feature on Server1, but the
installation fails repeatedly.
You need to ensure that the feature can be installed on Server1.
What should you do?

A.
Install Windows Identity Foundation (WIF) 3.5.

B.
Install the Web Server (IIS) server role.

C.
Connect Server1 to the Internet.

D.
Run the Add-AppxProvisionedPackagecmdlet.

Explanation:
The files needed are no longer available on the local Hard drive. We need to connect the
server to the Internet.
Important to note that when starting with Windows Server 2012 R2 and Windows 8, the
feature files for .NET Framework 3.5 (which includes .NET Framework 2.0 and .NET
Framework 3.0) are not available on the local computer by default. The files have been
removed. Files for features that have been removed in a Features on Demand configuration,
along with feature files for .NET Framework 3.5, are available through Windows Update. By
default, if feature files are not available on the destination server that is running Windows
Server 2012 R2 Preview or Windows Server 2012 R2, the installation process searches for
the missing files by connecting to Windows Update. You can override the default behavior by
configuring a Group Policy setting or specifying an alternate source path during installation,
whether you are installing by using the Add Roles and Features Wizard GUI or a command
line.

Show Hint

Leave a Reply 5

Your email address will not be published. Required fields are marked *

David

David

DISM /Online /Enable-Feature /FeatureName:NetFx3 /All /LimitAccess /Source:D:\sources\sxs

Where d:\ is the Windows Server 2012 ISO.

Reply

JonBan

JonBan

I don’t see how connecting to the Internet resolves the issue.

On Windows 2012R2, even if you download the full, redistributable dotnetfx35.exe package from http://microsoft.com/downloads, Windows will force you to activate the .Net 3.5 Framework feature and miserably fail, unless you select an alernate path pointing to your installation media.

Reply

gbj

gbj

I’ve had failures as well with adding features and not specifying the path to an iso and the servers did have internet access. The add roles wizard does however pop a message saying it will try and get the files from windows update or from a location specified in gpo. Connecting to the internet seems incorrect, but perhaps the least incorrect out of the 4 available?

Reply

robber

robber

C is correct. Dism can do the trick as well (actualy that will download the sourcefiles into a diskimage) or like the explaination says specify the source during installation.
Hence, this is not the same as downloading the dotnetfx35 package. It’s just a windowsfeature which gets it’s files from internet or a source u specify.

Reply