Would upgrading Windows Server 2008 R2 Standard to Enterprise on an Exchange Server stop Exchange from working?
We found out we need to have Windows Server 2008 R2 ENTERPRISE in order to get the Failover Cluster feature, so we upgraded the OS and now when we go to launch the Exchange Management Console we get Initialization failed The following error occurred when searching for On-Premises Exchange server: [OurServerName.something.something] Connecting to remote server failed with the following error message: The WinRM client received an HTTP server error status (500), but the remote service did not include any other information about the cause of the failure. For more information, see the about_Remote_Troubleshooting Help topic. It was running the command 'Discover-ExchangeServer -UseWIA $true -SuppressError $true'. just so you don't think we are complete dweebs this is in the lab on a test server at this juncture
December 29th, 2011 1:20pm

found the following thread it is a bit lengthy so I will poor myself some tea and muddle through it: The WinRM client received an HTTP server error status (500) http://social.technet.microsoft.com/Forums/en-US/exchange2010/thread/5b82f131-b469-4661-9d6c-1c1c7939b73a
Free Windows Admin Tool Kit Click here and download it now
December 29th, 2011 2:22pm

found the following thread it is a bit lengthy so I will poor myself some tea and muddle through it: The WinRM client received an HTTP server error status (500) http://social.technet.microsoft.com/Forums/en-US/exchange2010/thread/5b82f131-b469-4661-9d6c-1c1c7939b73a
December 29th, 2011 2:22pm

The following worked for us, and by the way you can upgrade the OS to Enterprise while Exchange is already installed: I had the same problem (Management Console and Management Shell could not connect to server). After configuring a second Exchange Server 2010 on a virtual machine, I was able to run the Exchange Best Practices Analyzer. ExPBA reported the wrong accounts were configured on the IIS Application Pools for Exchange. The Exchange application pools are supposed to run on the LocalSystem account, but mine were configured with the ApplicationPoolIdentity for each of the Exchange application pools. To correct, open IIS Manager and expand the Application Pools node. In each of the Exchange application pools, click Advanced Settings, and change the account to LocalSystem (be sure not to select LocalService by mistake). Click Ok when done. Restart IIS (at a command prompt, type IISRESTART /NOFORCE). Hope this helps others who have been confounded by the generic "Error 500" message from WinRM.
Free Windows Admin Tool Kit Click here and download it now
December 29th, 2011 4:00pm

The following worked for us, and by the way you can upgrade the OS to Enterprise while Exchange is already installed: I had the same problem (Management Console and Management Shell could not connect to server). After configuring a second Exchange Server 2010 on a virtual machine, I was able to run the Exchange Best Practices Analyzer. ExPBA reported the wrong accounts were configured on the IIS Application Pools for Exchange. The Exchange application pools are supposed to run on the LocalSystem account, but mine were configured with the ApplicationPoolIdentity for each of the Exchange application pools. To correct, open IIS Manager and expand the Application Pools node. In each of the Exchange application pools, click Advanced Settings, and change the account to LocalSystem (be sure not to select LocalService by mistake). Click Ok when done. Restart IIS (at a command prompt, type IISRESTART /NOFORCE). Hope this helps others who have been confounded by the generic "Error 500" message from WinRM.
December 29th, 2011 4:00pm

Note that you may have put the server that you upgraded out of a supported configuration. http://technet.microsoft.com/en-us/library/bb691354.aspx "If you're installing the Mailbox server role and you intend the server to be a member of a database availability group (DAG), you must be running the Enterprise Edition of Windows Server 2008 or Windows Server 2008 R2. The Standard Edition doesn't support the features needed for DAGs. You can't upgrade Windows when Exchange is installed on the server."Tim Harrington | MVP: Exchange | MCITP: EMA 2007/2010, MCITP: Lync 2010, MCITP: Server 2008, MCTS: OCS | Blog: http://HowDoUC.blogspot.com | Twitter: @twharrington
Free Windows Admin Tool Kit Click here and download it now
December 29th, 2011 5:10pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics