HOWTO: Install the DotNET Framework on Windows Server 2012 v3.5

Microsoft has been releasing Windows Server RTM for some time after Microsoft has provided RTM to msdn&technet subscribers as well as MPN and MVL users, a large-scale deployment and upgrade began! I believe that we will encounter some problems more or less, and today to share with you is how to install the DotNET Framework v3.5 (including v2.0 and v3.0) on Windows Server 2012.

The first thing to say about this is to review the previous situation-earlier on Windows Server R2, if you want to install the DotNET Framework v3.5 (hereinafter referred to as:. NET v3.5) simply through the "Add and remove" feature, without having to go through the Internet The relevant components are downloaded. However, there have been some subtle changes in this step on Windows Server 2012.

Goxia A recent batch deployment test for Windows 8, Windows ADK needs to be installed in the environment, and because the VAMT 3.0 in the ADK component requires SQL Server, the default component installation option is maintained during the installation of ADK, and the process is smooth, but the installation After discovering that the automatic installation of SQL Server 2012 does not contain administrative tools, but also the English version, so reset the virtual environment, intended to reinstall. The first thing to do before reinstalling ADK is to manually install the SQL Server 2012 Express with Tools Simplified Chinese version, and the installation readiness test for SQL Server is smooth but when the installation is nearing the end, the. NET v3.5 is not valid, although the progress is still can continue, but then prompted an error (PS: Then also did not screenshot, the specific error message forgot!) ), helpless cancel installation! At this time the system is suspended, a cruel and reset the virtual environment. Didn't think twists, re-dated first install. NET v3.5, as always, by adding and removing, the wizard prompts you to specify an alternate source path for the installation of. NET v3.5, but it is too simple to notice. Think as Windows 8 needs to be installed via the Internet from Microsoft download. Did not expect the next problem, the installation failed to prompt! As shown in the following:

Okay, so let's take a look at this. "Specify alternate source path", look at the detailed introduction the general meaning can be understood as such, Windows Server 2012 continues to support. NET v3.5, but the current system file library (WinSxS) does not contain. NET v3.5 , so installing. NET v3.5 requires you to specify an installation source for the installation wizard, which is different from Windows 8 because Windows 8 automatically downloads the installation from the Web when this feature is installed by default. To specify an alternate source path, you must have the installation source for Windows Server 2012, because the related components of. NET v3.5 are contained in the "SxS" subdirectory of the installation disk "Sources" root directory. To do this, simply click on "Specify alternate source path" on the "Determine Installation Selection" page and type the specified path in the pop-up box to see:

In addition to being able to operate the installation in a GUI manner, we are able to use the DISM command, which applies to both Windows 8 and Windows Server 2012 (with the "/all" parameter), as follows:

Dism/online/enable-feature/featurename:netfx3/source:x:\sources\sxs

Of course, Microsoft is strongly recommending that administrators use powerful Powershell to manage their systems, and in Windows Server 2012 's Server Manager cmdlets, "install-windowsfeature" can be used to Command, refer to the following commands:

Install-windowsfeature–name Net-framework-core–source X:\sources\sxs

Note: The above command only applies to Windows Server 2012! If you want Powershell cmdlets to be suitable for client systems such as Windows 8, refer to the following command:

Enable-windowsoptionalfeature–online–featurename Netfx3–source X:\sources\sxs

For more detailed information, read Microsoft Windows Server Core Team blog:http://blogs.technet.com/b/askcore/archive/2012/05/14/ Windows-8-and-net-framework-3-5.aspx