I got into a bit of a freak out the other day.I wanted to install SharePoint 2013 on a new server, but I couldn't because of .NET incompatibility. After some research I found that the problem was the same one that I had earlier had to unravel for my Exchange Server. It seems that unfortunately, the .NET Framework 4.6.1 is not compatible with many relatively recent Microsoft server products. If you are building images you'll want to make sure that you include images that do not include this component as it is not supported and may block new installations of products like these:
- Exchange 2013, 2015
- SharePoint 2013
- Office Web Apps Server 2013
- Skype for Business Server 2015
Block it before it gets there!You want to stick with .NET 4.5.2, so here's how to prevent the installation of 4.6.1
Method 2: Method 3:
But wait! .NET 4.6.1 is already installed!
If the .NET 4.6.1 update is already installed and you have not yet installed a server product (perhaps it is already in a baseline image) then you simply need to uninstall the update and run the repair tool
But wait! .NET 4.6.1 is already installed AND I've already installed Exchange or SharePoint or Skype Server!
Don't Panic! The above steps still apply with just a few caveats
Is this forever?
Of course not. Eventually you will be using products that are compliant with .NET 4.6.1 because you are working with the next generation product or because Microsoft has updated the previous generation product to be supported by .NET 4.6.1. Then you can remove the GPO preference or reg hack and allow your systems to update normally.