Exchange 2010 remote PowerShell breaks after add/remove/change of IP Address

Something that occurs in a lab situation quite frequently and less in real life is changing IP addresses on your Exchange server. Some of my lab servers frequently undergo a scenario change where I’ll add or remove them from specific Hyper-V networks or subnets.

 

Then one day everything broke. EMS reported :

Connecting to remote server failed with the following error message : The WinRM client sent a request to an HTTP server and got a response saying the requested HTTP URL was not available. This is usually returned by a HTTP server that does not support the WS-Management protocol. For more information, see the about_Remote_Troubleshooting Help topic.

image

 

EMC reported a slightly different error:

The attempt to connect using “Kerberos” authentication failed, etc, etc however the message points to the fact that the WinRM URL isn’t where it’s expected to be.

image

 

Bearing in mind that we know that the machines IP addresses have changed a little, it makes sense to have a look at the IIS configuration.

Looking at the bindings of the default web site I can see that something is amiss, since the IP address reflected is the new IPadress of the new subnet I connected to, as opposed to the expect machine address, or even All Unassigned on the Default Site as I would expect.

image

I changed the bindings back to All Unassigned, and restarted the web site

image

 

EMS and EMC are back in business.

image

Nicolas Blank

Nicolas is an Architect, author, and speaker focused on all things Exchange and Cloud at NBConsult. With over 16 years of experience on Exchange, Nicolas consults to customers globally on cloud based and on-premises Exchange as well as ISVs building Exchange focused products. Nicolas has extensive experience using Azure to create public and private Azure based offerings leveraging cloud based principles and common sense. Nicolas currently holds status of MCM Exchange 2010, Office 365 (Microsoft Certified Master), MCSM Exchange 2013, and has been awarded Microsoft MVP (Most Valuable Professional) for Microsoft Exchange since March 2007. Nicolas has co-authored "Microsoft Exchange Server 2013: Design, Deploy and Deliver an Enterprise Messaging Solution," published by Sybex. Nicolas blogs regularly on Exchange and messaging topics at blankmanblog.com, tweets at @nicolasblank, and is the founder of and a contributor to IT Pro Africa itproafrica.com and @itproafrica

nicolasblank has 99 posts and counting.See all posts by nicolasblank

  • Álvaro Vieira

    Hi,

    I have the same problem, when I change the IP address, the EPS doesn´t work, the message error is: permission denied.

    How can I resolve this problem?

    Regards,

    Álvaro

  • roys

    check your clock. in my case the hyper-v host was off –> the VMs were off

    problem resolved by setting time sync to work properly

  • Thanks for sharing your info. I really appreciate your efforts and I am waiting
    for your next post thanks once again.

X

Pin It on Pinterest

X