Microsoft .NET Framework version 4.5.2 is installed on ConfigMgr 1511 clients


Hi everyone, Eric Ellis here again with a quick note about Microsoft .NET Framework and the Configuration Manager build 1511 (and later) client that I want to be doubly sure you’re aware of. If you’re running Configuration Manager 1511 or newer, when you go to upgrade or install your clients, Microsoft .NET Framework version 4.5.2 will be installed at the same time if the client is running a version of Microsoft .NET Framework prior to 4.5. This is by design as noted in the documentation here:

Prerequisites for deploying clients to Windows computers in System Center Configuration Manager

You can find it under the section titled Dependencies External to Configuration Manager and Automatically Downloaded During Installation.

On a related note, remember that as of January 12th of 2016, support for Microsoft .NET 4.0, 4.5, and 4.5.1 expired. There will be no new security updates, non-security updates, free or paid assisted support options or online technical content updates. For more information see Microsoft .NET Framework Support Lifecycle Policy FAQ (click on Announcements, then Products Reaching End of Support in the First Half of 2016. You’ll find it under Products Moving to End of Support).

I’m sure you’re probably already aware of this but I wanted to take a minute to point it out just so that there are no surprises when you go to install the new client.

Eric Ellis, Senior Support Escalation Engineer

Microsoft Enterprise Cloud Group


Comments (9)
  1. Vegard Alsli says:

    Found out several weeks back when suddenly .net 4.5 installations started failing in the task sequence. I wish we had this information then 🙂

  2. sbrown515 says:

    Is ConfigMgr 1511 written in VS 2013 then? what about support for .net 4.6.1? Can/should it be deployed to site servers and clients? I’d rather future-proof my environment than stick on an old .net at the rate these are being deprecated…

    1. Matt Wreede says:

      .NET 4.5.2 follows the OS end of life, so it’ll be supported until the end of the OS you’re installing it on.

      https://support.microsoft.com/en-us/lifecycle?C2=548

      That said, we’re running 4.6.1 without issue on V1511.

  3. sbrown515 says:

    Also, when will .net 4.6.1 be available as a software update in ConfigMgr 4.6.1?

    1. sbrown515 says:

      that is, when will .net 4.6.1 be available as a software update in ConfigMgr 2012 R2

      1. Matt Wreede says:

        It should be showing up for you now. It was released to WSUS a month or so ago.

        https://blogs.msdn.microsoft.com/dotnet/2016/01/26/microsoft-net-framework-4-6-1-is-available-on-windows-update-and-wsus/

        It’s only showing up for certain OSes, though; 2008R2 is notably absent from the list.

  4. hakkon8 says:

    How about Visual C++2005 Redistributable?

    EOS at 2016/04/12.

    https://support.microsoft.com/us-ua/lifecycle/search?sort=PN&alpha=Visual%20Studio%202005%20Professional%20Edition

    Products Released
    Lifecycle Start Date
    Mainstream Support End Date
    Extended Support End Date
    Service Pack Support End Date
    Notes
    Microsoft Visual Studio 2005 Professional Edition 1/27/2006 4/12/2011 4/12/2016 1/8/2008

    SCCM2012R2 Client need VC++ 2005 and VC++ 2010,
    SCCM1511 Client : VC++ 2005 and VC++2013.

    https://technet.microsoft.com/en-us/library/gg682042.aspx

    Microsoft Visual C++ 2005 Redistributable version 8.0.50727.42 Required to support Microsoft SQL Server Compact operations.

  5. Taarun says:

    is anything will affect application level which are running while migration SCCM agent to CB 1511 or newer

  6. Pallavi says:

    Hi Eric,

    I just wanted to know what will happen when we try to uninstall SCCM CB client from client machine. Will it uninstall Dot net framework too from the client machine? If not then how can we achieve this ? I want to uninstall SCCM CB client from selected client machine as well as i want to uninstall .NET 4.5.2.

    Regards
    Pallavi

Comments are closed.

Skip to main content