This post was authored by Vivek Mishra on behalf of the .NET Framework team.
Hi WSUS Admins,
The Microsoft .NET Framework 4.5.1 will be made available via Windows Server Update Services on 26 Nov 2013 and this blog highlights some of the key aspects.
The .NET Framework is a development platform for building apps for Windows, Windows Phone, Windows Server, and Windows Azure. The .NET Framework 4.5.1 is a highly compatible, in-place update to the .NET Framework 4 and 4.5. The .NET Framework 4.5.1 can be installed fresh on any supported platform or can be used to upgrade your previous .NET 4 or 4.5 installation. The .NET Framework 4.5.1 also works side by side with older Framework versions lower than .NET 4.0. Applications that are based on earlier versions of the Framework will continue to run on the version targeted by default, after .NET Framework 4.5.1 is installed.
You can learn more about .NET Framework 4.5.1 here.
Useful information about this release:
The .NET Framework 4.5.1 and its corresponding language packs are being released for following supported platforms:
Windows Vista SP2, Windows 7 SP1, Windows Server 2008 SP2, Windows Server 2008 R2 SP1, and Windows Server 2012.
The .NET Framework 4.5.1 Language Packs will also be available via WSUS, both to support the upgrade of previous language packs for .NET Framework 4 or 4.5 and for computers, that either have the localized version of the base operating system or have one or more Multilingual User Interface (MUI) packs installed.
On Windows 8.1, Windows RT 8.1 and Windows Server 2012 R2, .NET Framework 4.5.1 is available in-box, so you do not need to deploy or install the product separately.
On Windows 8 and Windows RT, customers can get the .NET Framework 4.5.1 by upgrading their computer to Windows 8.1 and Windows RT 8.1 respectively. There is currently no .NET Framework 4.5.1 Windows Update offering for these 2 platforms.
Enterprises, that have a specific need to block offering .NET Framework 4.5.1, on computers which can directly connect to Microsoft Update servers, can do so by deploying the blocker registry key as described in following Microsoft Knowledge Base:
KB2721187: How to temporarily block the installation of the .NET Framework 4.5.1 and its corresponding language packs
Good to hear that.
Why not for Windows 7? See support.microsoft.com/.../en-us
IE11 was rolled out on WSUS on Nov 22 but announced for Nov 14th there. WTH are you doing!?
.NET 4.5.1 on WU is being released for supported versions of Windows 7, i.e. Windows 7 SP1.
This is similar to what you might have seen for IE11 here: support.microsoft.com/.../en-us
Acceleration is a fast growing start-up which is having their ERP Web solutions for Education, Finance & Hospitality domain. Recently they have started with training modules for Dot Net / JAVA / PHP technologies & Android / Windows 8 Framework application development. Good opportunity for 6 Week / Internship program for all Engineering & MCA.
They are Industry professionals to train & get you prepared for IT Job Interviews. The Good part is they have seperately added a interview preparatory technical programs to get you qualify in any IT interview.
Add-Ones for training profile: -
--> Technical Leaders & Managers from Industry to train
--> Live project development Exposure
--> Valid Pvt ltd company experience
--> 100% Job Assistance
--> Personality Development Sessions + Resume Writing Tips
--> Free Mock Tests for written exams for Interview Cracking
So, since this has been released... Where is the update for Windows Vista/7, Server 2008/2008R2? I see the Server 2012 update in WSUS, but all the other update appear to be missing...
@Curious WSUS AdminHere are three KB numbers associated with .NET Framework 4.5.1 on Windows Update:http://support.microsoft.com/kb/2858725 - Vista/Windows 7/Server 2008/Server 2008 R2 - MSI Product & Lang Packshttp://support.microsoft.com/kb/2881468 - Server 2012 - MSU Product http://support.microsoft.com/kb/2858726 - Server 2012 - MSU Lang Packs
On a Windows Server 2012 R2 server, I was unable to complete the install of the WSUS role after installing the .NET 4.5.1 update. The server failed to finish the post-deployment configuration steps. (This was a clean installation of Windows Server 2012 R2 and WSUS was the first thing to be installed. But I made the mistake of running Windows Update first.)
Followup: On a second try on a clean install of Windows Server 2012 R2 without the .NET 4.5.1 update, the post-deployment configuration task still failed. The Hyper-V virtual machine in which I was installing WSUS had dynamic memory enabled; disabling dynamic memory allowed the task to proceed successfully.I cannot verify whether .NET 4.5.1 update is in conflict with installing WSUS or not, though I have found some online knowledge that indicates that it is.
so what should I be looking for within cm12 software updates so that I can deploy this instead of using an application based deployment? Thanks in advance.
I have everything enabled except for tools and feature packs, is it in one of those classes?