Quick Fix: Register ASP.net 4.0 With IIS Windows Server 2012

Issue
Bumped into an issue where ASP.net 4.0 wasn’t registered with IIS running on Windows Server 2012. Before that Server OS the solution was an easy one: simply follow this posting of mine and all is fine again.

HOWEVER, Windows Server 2012 and later don’t support that anymore and the ONLY fix is removing IIS and reinstalling it with ASP.net 4.0. But that’s way too much and takes too much time, effort and resources.

Quick Fix
Thanks to Google I found two articles about how to fix this WITHOUT removing and reinstalling IIS:

1. Open IIS Manager and select the webserver and select Modules (found under header IIS);
2. Double click on it, so you open Modules, and remove the module ServiceModel;
3. Go back to IIS Manager, select the webserver again in IIS, and select Handler Mappings (found under header IIS);
4. Remove the handler svc-Integrated;.
5. Restart IIS by using an elevated cmd prompt and issue this command: IISRESET <enter>;
6. When IIS is running again add WCF by going to "Turn Windows Features On and Off" and enable .NET Framework 4.5 Features > WCF Services > HTTP Activation;
7. Restart IIS by using an elevated cmd prompt and issue this command: IISRESET <enter>.

Now the SCOM 2012 Web Console will be fully functional WITHOUT reinstalling IIS .

A big word of thanks to the authors of these two articles I used for this solution:

1. http://stackoverflow.com/questions/15278027/cant-register-net-4-0-in-iis-on-windows-8
2. http://www.codeproject.com/Articles/613812/Solve-IIS-8-Error-Could-not-load-type-System-Servi