![]() I was approached by a good friend of mine and he asked what I thought we could do to make these errors a little easier to troubleshoot. In other words, depending on how knowledgeable you are with these errors, troubleshooting them is all around. ![]() The situation is further complicated by the fact that some of the errors presented have similar wording most seem to originate with WinRM (Windows Remote Management), and in some cases different root problems can produce the exact same error message. We have seen that these changes are usually done when the IIS administrator is attempting to "tighten up" IIS security by editing the Default Web Site or PowerShell vdir settings. ![]() This generally (but not always) happens when Exchange 2010 is installed on an IIS server that is already in service, or when changes are made to the IIS server settings post Exchange Install. ![]() As was discussed in that blog, we have seen situations where the management tool connection to the target Exchange server can fail, and the error that is returned can be difficult to troubleshoot. As was discussed in the previous (related) blog post " Troubleshooting Exchange 2010 Management Tools startup issues", in Exchange 2010 the Management tools are dependent on IIS.
0 Comments
Leave a Reply. |