SharePoint 2013 on Azure–Solving “Error while enabling Windows feature : NetFx3” in Windows Server 2012 R2

When we deploy SharePoint 2013 in Windows Azure, there are few obstacles we need to tackle. I had following conditions in my environment

• Windows Server 2012 R2 Datacenter image as the VM image
• Virtual machines are located in Azure Virtual Network

In this article series I will discuss some issues we faced and solutions we used to overcome them
In this post I will explain the first issue we came across.
The issue occurred while we installing SQL Server, where the installation process failed to install dot net framework 3.5. The actual error message was as below

“Error while enabling Windows feature : NetFx3, Error Code : -2146498298 , Please try enabling Windows feature : NetFx3 from Windows management tools and then run setup again. For more information on how to enable Windows features , see http://go.microsoft.com/fwlink/?linkid=227143”

As certain sources mentioned, I used “Add Roles and Features Wizard” and specified alternate source path to pic relevant files from Windows image. But it still prompted me following error.

I tried the same task using command line, but the operation failed after 62% or 66%
After hours of struggling, following are the remedies I used to arrive at a solution

Remedy 1 : Disable IP6, and Provide Google DNS as an alternative DNS
  

Remedy 2 : Download the latest Windows Server 2012 R2 Data Center Image
From this link you can download the trial image.

Remedy 3 : Configure group policy “Specify settings for optional component installation and component repair”
When this policy is enabled, a network location (for example, a file server) can be specified for both repair of the feature file store, and to enable features that have their payload removed. The Alternate source file path can point to a \sources\sxs folder or a Windows image (WIM) file using the WIM: prefix
To enable the policy, navigate to Computer Configuration\Administrative Templates\System in Group Policy Editor


After enabling the policy, run “gpupdate” to refresh the policy

Remedy 4 : Execute following command to Activate dot net 3.5
Open a PowerShell windows as the administrator and execute following command to install dot net 3.5 with required prerequisites. I extracted the downloaded image in a drive so I provided that location as the source

1. Dism /online /enable-feature /featurename:NetFx3 /All /Source:E:\sources\sxs /LimitAccess

Above remedies allowed me to install dot net 3.5 and continue the SQL Server installation without further issues.