

- NETFRAMEWORK 4.6.1 FOR WINDOWS SERVER 2012 R2 DOWNLOAD INSTALL
- NETFRAMEWORK 4.6.1 FOR WINDOWS SERVER 2012 R2 DOWNLOAD UPDATE
- NETFRAMEWORK 4.6.1 FOR WINDOWS SERVER 2012 R2 DOWNLOAD REGISTRATION
- NETFRAMEWORK 4.6.1 FOR WINDOWS SERVER 2012 R2 DOWNLOAD PRO
So the 2 big lessons I learnt from this areġ.Net Framework 4.6.1 has problems which can cause issues with SCCM (who knows, it could be affecting many other products, as we already know Exchange is one of them).Ģ. So, overall, it was really an interesting day for me. It's working ok for now but I am keeping an eye on it. There was another issue that I faced with where WSUS app pool was entering into stopped state. net versions to 4.0 all the 3 components started working again. Option would have been to reinstall those 3 roles which wasn't an ideal option. I have to thank the Microsoft engineer for identifying this. IIS itself seemed to be working fine (as SCCM MP was working ok). It, and as a result, all the IIS web applications associated with. It took us some time to realise that while removing 4.6.1 above, it took the whole of.
NETFRAMEWORK 4.6.1 FOR WINDOWS SERVER 2012 R2 DOWNLOAD REGISTRATION
net 4.0.Īfter this, the above WSUS installation problem disappeared, completed the wizard and the SUP successfully synchronised with WSUS and everything started working again.Īfter sometime however I noticed that 3 other SCCM components (Application Catalog, App Catalog Service and Certificate Registration points) stopped working. So I told this to the Microsoft engineer and we decided to remove 4.6.1 from the server.
NETFRAMEWORK 4.6.1 FOR WINDOWS SERVER 2012 R2 DOWNLOAD UPDATE
Net 4.6.1 update causing problems in the Exchange world.
NETFRAMEWORK 4.6.1 FOR WINDOWS SERVER 2012 R2 DOWNLOAD PRO
Which resolved that Admin console problem later on).Ĭoming back to the WSUS/4.6.1 issue, I also remembered from a recent Windows IT Pro article about. net framwork updates (including 4.6.1) though those updates did not resolve the problem, they did not seem to cause any harm to the server so we left them as they were (By the way it was only the R2 SP1 CU2

This issue we had installed all the latest. When we manually browsed to that location, that folder C:\Windows\Microsoft.Net\Framework64\v did not exist on the system.Īnd then I suddenly remembered that last month while troubleshooting As you can see in the below screenshot, the WSUS installer attempts to run a MSI custom action in the middle of the wizard which makes use of InstallUtil.exe which is present under. We continued trawling through the enormous WSUS installation logs.ĭuring this stage one particular entry in the log caught my eyes. So he suggested moving the WSUS/SUP role to another server which wasn't an ideal option for us.

The engineer initially tried various dcom/iis permissions and coudn't find anything obvious. Repeated installation attempts of WSUS (even with reboots) did not make the situation any better. The log file had errors discussed in this threadīut it wasn't specifically related to that problem. Threw an error with no specific useful error message. After selecting all the appropriate options (WSUS location, backend server, port/url selection etc.) during the middle of installation, the wizard Role (with the intention of reinstalling it) and it is during this time things started to take interesting turn. It was throwing error when launching the WSUS console, at the same time there were Site Status error messages on SCCM console monitoring tab. It was much later that I realised that WSUS had gone belly up. It looks like something went wrong with that hotfix installation which I did not notice at that time and hence I continued As part of the wizard I was asked to install KB2530678.
NETFRAMEWORK 4.6.1 FOR WINDOWS SERVER 2012 R2 DOWNLOAD INSTALL
Yesterday I was trying to install SCUP 2011 on the above SCCM server. We have a standalone primary SCCM 2012 R2 SP1 running on Windows server 2008 R2 with a dedicated SQL Server 2008 R2 back end. I had an interesting 24 hours with SCCM in our organisation.
