I recently ran into an issue with Windows Server 2012 R2 and was able to resolve it despite a good deal of misinformation that I found out on the Internet. It all started when I needed to install a proprietary application on one of my client’s production servers; the application in question required Microsoft .NET Framework 3.5. No biggie, I thought, remembering that this could be enabled as a “feature” through Server Manager. So I loaded it up and attempted installation only to watch it crash and burn (see image below).
Read More…
Brian Dunham is a Cisco and Microsoft certified network and systems engineer with over a decade of experience in the Information Technology field. When he is not in front of a computer he can be found out in the wilderness canoing, hiking, fishing, or camping.
Contact: brian.dunham@netris.us