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. As was discussed in...
Updated Apr 22, 2020
Version 3.0
Blog Post
6 MIN READ
Resolving WinRM errors and Exchange 2010 Management tools startup failures
I have an interesting issue. We installed a secondary NIC on a server running Windows 2008 R2 and Exchange 2010. After installing the second NIC, there are WinRM issues and EMC and Powershell will not connect up. EMC gets an Initialization Failed: The Client Could not connect to the destination specified in the request.
Upon running this EMTshooter tool, I keep getting prompted that Port 80 is not bound. Of course, when I check the bindings for the Default Web Site, it is. If I change the port to something like 81, run EMTshooter, get the error and choose yes to update the bindings, it does add the Port 80 entry back in. So, it does exist. The problem I have is this Second NIC seems to have messed everything up. I found another forum that discusses it. Their only solution seems to be to format and start over. Surely, there has to be another option. We've tried removing the second NIC and reverting back to the way things were, but the problems still persist. Here is a link to the other forum: http://social.technet.microsoft.com/Forums/en-US/exchangesvradmin/thread/89b34787-321d-4657-9ffb-80889d65b7cd/
Any suggestions?
Upon running this EMTshooter tool, I keep getting prompted that Port 80 is not bound. Of course, when I check the bindings for the Default Web Site, it is. If I change the port to something like 81, run EMTshooter, get the error and choose yes to update the bindings, it does add the Port 80 entry back in. So, it does exist. The problem I have is this Second NIC seems to have messed everything up. I found another forum that discusses it. Their only solution seems to be to format and start over. Surely, there has to be another option. We've tried removing the second NIC and reverting back to the way things were, but the problems still persist. Here is a link to the other forum: http://social.technet.microsoft.com/Forums/en-US/exchangesvradmin/thread/89b34787-321d-4657-9ffb-80889d65b7cd/
Any suggestions?