WinRM redirect error when trying to open EMC in Exchange 2010
Recently installed an Exchange 2010 to upgrade from Exchange 2003. We host multiple domains for many small school districts so we run a single server environment and have for many years on 2003. After following the TechNet article to Configure Outlook Anywhere to Use and SSL Certificate with Redirection I am no longer able to open my Exchange Management Console. It gives me an error that the WinRM Service cannot process the request because the request needs to be sent to a different machine. Use the redirect information to send request to a different machine. where do I set this redirect? I know it is related to the redirect the article made me set up for the autodiscover service, but I am not sure where the change needs to be made in IIS. The services seem to be running fine, but I cannot access the management console. I am afraid to change anything else for fear of making it worse. Anyone know where the redirect needs to be done?
July 5th, 2010 3:37pm
Hi , According for the Error it seems more of a DNS issue than Anything. You Must have Assigned a certificate on the Exchnage machine. I Suggest Adding that Cert o IIS Virtual Directory and Making it IIS Enabled. Can you Close the Windows Firewall for sometime and Check if the error persist. When you Open the Powershell Are you opening it from EXMR001 ? Can you go in cmd and ping exmr001 ?[Do you get the correct Reply with the firewall off now] If yes than Try creating a session again and Note that it is connecting to EXMR001 and does the error persist. If not done than try this Fix the Name Resolution for the server, try to resolve the name of your DCs / other Exchange boxes. Open IIS and check the authentication providers, make sure that the following Authentication providers must be configured on Exchange boxes for IIS: Integrated Windows Authentication (Enabled) Anyoumus Authentication (Enabled) Basic Authentication (Enabled) Diegest Authentication (Enabled) You can also try to fix this problem by doing the following: Login to the Exchagne Server on which you are facing this problem, go to Server Manager and Remove the WINRM feature Restart the Server After Restarting the server go to Server Manager, install the WINRM again After installing the WINRM feature to the Exchange Server Open CMD as RUN as Administrator run the command "winrm -quickconfig" - when you will execute this command, it will ask for creating the firewall execptions, say YES I hope this should resolve your problem Regards. Shafaquat Ali.M.C.I.T.P Exchange 2007/2010, M.C.I.T.P Windows Server 2008, M.C.T.S OCS Server 2007 R2
July 6th, 2010 2:40am
I am running this on a Windows 2008 server if that makes a difference. The server is available in DNS. OWA works just fine. Also, after installing the RPC over HTTP on this server, it shut down the Microsoft Exchange Server Host. Mail is working, but no I seem to have two problems. Are they related? Does anyone have experience with setting up an Exchange 2010 server on Windows 2008 with a single SSL Certificate? I followed all of the steps that Microsoft suggested and now the management functionality of this all is broken, but the mail is still flowing.....It seems to be related to IIS and powershell, which I have little experience in.
July 6th, 2010 4:09pm
Please check the “HTTP Redirect” setting in the /PowerShell virtual directory Where is the management tools located? Please verify if you can launch the EMC directly on the server, which will also use remote powershell feature to connect What’s the full error information? Is there a redirect location URL reported?James Luo TechNet Subscriber Support (http://technet.microsoft.com/en-us/subscriptions/ms788697.aspx) If you have any feedback on our support, please contact email@example.com
July 7th, 2010 6:16am
I am trying to open the EMC directly on the server. I am unable to open Exchange PowerShell either. I get this message: VERBOSE: Connecting to mydomain.com [mydomain.com] The WinRM service cannot process the request because the request needs to be sent to a diffe rent machine. Use the redirect information to send the request to a new machine. Redirect location reported: https://m ail.mydomain.com/powershell . To automatically connect to the redirected URI, verify "MaximumConnectionRedirectionCount" p roperty of session preference variable "PSSessionOption" and use "AllowRedirection" parameter on the cmdlet. + CategoryInfo : OpenError: (System.Manageme....RemoteRunspace:RemoteRunspace) , PSRemotingTransportRed irectException + FullyQualifiedErrorId : PSSessionOpenFailed There is no redirect on the PowerShell virtual directory, but I have tried manually entering my server name with no luck.
July 7th, 2010 12:59pm
I went through this whole post and everything appears to be correct. It fail on the Exchange server itself - it is unable to locate an on-premises exchange server. This only started to happen after I setup a redirect for the autodiscover service according to Technet articles that seemed to meet my needs: http://technet.microsoft.com/en-us/library/bb201695.aspx http://technet.microsoft.com/en-us/library/bb310764.aspx When I did this everything seemed to work fine, but now the EMC does not load. I am trying to set up RPC over HTTP for Exchange 2010. I also get an error in my event log that the Microsoft Exchange Server Host terminated unexpectedly. Hope that clarifies things a little.
July 7th, 2010 3:14pm
Quote: “I have tried manually entering my server name with no luck” Where do you enter? Please check the “Exchange service host” service, see if it’s running correctly Please use the “Test-PowerShellConnectivity” cmdlet for testing, and then check the output and the event in the application log Do you have workstation that installed management tools? Please go to /bin folder, and backup the original ConnectionFunctions.ps1 file to another location, open the ConnectionFunctions.ps1 file in the /bin folder, and then add “AllowRedirection” after all New-PSSession cmdlet for testing Resources: Connect Remote Exchange Management Shell to an Exchange ServerJames Luo TechNet Subscriber Support (http://technet.microsoft.com/en-us/subscriptions/ms788697.aspx) If you have any feedback on our support, please contact firstname.lastname@example.org
July 8th, 2010 3:07am
The error was caused by changing the bindings on the Default Web Site as per step 4 in this article: http://technet.microsoft.com/en-us/library/bb310764.aspx Of course changing the bindings back breaks the initial problem I was trying to fix by configuring Outlook Anywhere to Use an SSL Certificate with Redirection. Also, my RPC over HTTP still causes Microsoft Exchange Service Host to fail. That appears to be an unrelated problem.
July 8th, 2010 12:30pm
Thanks for the sharing. So, the cause is the wrong bindings on the IISJames Luo TechNet Subscriber Support (http://technet.microsoft.com/en-us/subscriptions/ms788697.aspx) If you have any feedback on our support, please contact email@example.com
July 8th, 2010 9:26pm
Shafaquat, Several of the authentication providers in IIS had changed states to disabled and I was unable to use EMT. After changing the authentication providers to enabled I was back up and running. I can only suspect an update caused the change. Thank you for taking the time to share your knowleged. Thomas Lansford
March 23rd, 2012 1:44pm