Installing SQL Server 2012 on Server 2012 R2 Info

As you all should know, .NET Framework 3.5.1 is required for SQL Server 2012. In Server 2012 R2 (I don't know about 2012) SQL Server will pass all of the requirement checks for .NET 3.5.1 because version 4 or 4.5 is installed by default on Server 2012 R2. Even though you get all green check marks, the SQL Server installation will crap out complaining that 3.5.1 can't be enabled.

To install 3.5.1 on Server 2012 R2 (This assumes you have your Server 2012 R2 installation media mounted as d)
The easiest way: open PowerShell as admin and type the following - dism /online /enable-feature /featurename:netfx3 /all /source:d:\sources\sxs

Or you could go through Add Roles and Features wizard, select the .NET 3.5 feature and then supply d:\sources\sxs as the source if it complains.

Just a heads up. Being that MS revised this exam to include SQL Server 2014 material, they may ask about installing SQL 2012 on Server 2012 and 2012 R2. I wouldn't put it past them.

Find more posts tagged with

Comments

greg9891

Thanks for the update! might come in handy.

ektorakos

how do you run powershell from the command prompt if you are in core ?

AvgITGeek

By default it should run as administrator being you log in as administrator. In windows core, type powershell and hit enter. you should enter PS

ektorakos

i cannot enter as administrator . only option is kim_akers or other.

I succeeded the powershell command so now i am in
PS C:\users\kim_akers\> and i type

PS C:\users\kim_akers\> dism /online /enable-feature /featurename:netfx3 /all /source:d:\sources\sxs

and of course i get error that the command is wrong or the path is incorrect.
the cd is mounted in d.

nothing works for me. i guess i am too nube for this

ektorakos

oh wait it worked now that i tried again.

i wander if this space before every slash is required " /" , or i was just spelling it wrongly before

AvgITGeek

Yes. The spaces are required as it separates the switches. You can run command prompt in powershell but you can't run powershell cmdlets in the command prompt. While in powershell "ipconfig" will still work.

AvgITGeek

Cool trick if you don't know. If you add your remote servers to server manager, you can install Roles and Features on those remote servers without touching them.

And you will probably need to follow this when installing SQL Server 2014 on Server 2012 R2 as well. I haven't gotten to installing SQL Server 2014 yet.

Oh ektorakos, we all started out as noobs. Don't give up, it can be frustrating but do not give up!