I've posted this question here as well; Exchange Server Forums > Exchange Software Updates > not sure were it's beloning <mod?>
I've updated a perfectly good working Exchange 2010 server with KB982639 Rollup 4 today, only to find disaster. The update completed, but after the restart all Exchange services and W3SVC/IISADMIN were disabled. Starting them manually did no good. I then rolled back (deinstall) the rollup4, restarted and made all exchange services start again by hand (delayed restart). This, thank God, helped.
Now I wanted to connect to EMC, only to find more sjit. When searching for the on-premises exchange server first the W3SVC wasn't started, after I did that the WinRM client failed. I've searched here and followed some related cases, like reinstalling (or installing acually) WinRM. Now it's running, but WinRM cannot process the request; it cannot determine the content type of the http response etc. etc. Powershell has (of course) the same problem. Exchange runs, but unmanaged.
So, of to IIS... but the /PowerShell virtual has errors; the filename \\?\C:\Program Files\Exchange Server\v14\CleintAccess\PowerShell\web.config has error: blank.... yes, no error for the error .
Kinda lost here, any any any help appreciated.