So I really screwed the pooch on this one. I have a new exchange 2010 server and I was working on the coexistence portion of the server migration. While trying to get the redirection for my users to be nice and smooth something got corrupted in IIS and now I get a series of errors. This is when trying to do something from the EMS: Starting a command on remote server failed with the following error message : The WinRM client cannot process the reque st. It cannot determine the content type of the HTTP response from the destination computer. The content type is absent or invalid. For more information, see the about_Remote_Troubleshooting Help topic. + CategoryInfo : OperationStopped: (System.Manageme...pressionSyncJob:PSInvokeExpressionSyncJob) [], PSRe motingTransportException + FullyQualifiedErrorId : JobFailure Now when I try to open the EMC I get the same basic message: Starting a command on remote server failed with the following error message : The WinRM client cannot process the reque st. It cannot determine the content type of the HTTP response from the destination computer. The content type is absent or invalid. For more information, see the about_Remote_Troubleshooting Help topic. When I try to open the error pages on the default website in IIS Manager: There was an error while performing this operation. Details: Filename:\\?\C:\inetpub\wwwroot\web.config Line number: 5 Error: Lock violation I have run the EMTshooter and it worked fine. I have been through so many pages and help documents and nothing has worked at this point.

So got back to google and tried again. found this page: http://forums.msexchange.org/m_1800535775/mpage_1/key_/tm.htm#1800544044 Which linked to this page: http://stackoverflow.com/questions/2472818/500-19-error-in-iis7-when-an-error-occurs deleted web.config(renamed actually) ran iisreset and I am back into the EMC/EMS :) --Doug

I know this thread appears to be solved, but I had chased the same symptoms for weeks trying to recover EMC/EMS on my Exchange 2010 SP1 Server, and none of the published suggestions got me any closer to a fix. What did work for me in the end was the result of an accidental examination of some of the settings in IIS. I discovered what appeared to be an incorrect setting for the 'Application Pool' in the 'advanced settings' for a virtual directory. I googled for a listing the would confirm this, http://technet.microsoft.com/en-us/library/dd577064(EXCHG.80).aspx Using this publication I reset all virtual directories to reflect the suggested application pool, and the suggested identity for each. Issued an 'iisreset', and I was back in business. I have no idea how those settings got out of step, although I had done some preliminary work with the installation of Sharepoint at about the time the errors appeared. regards Graham