Hybrid Configuration Wizard: Exchange server “” was not found. Please make sure you typed the name correctly.

NOTE: This post – drafted, composed, written, and published by me – originally appeared on https://blogs.technet.microsoft.com/johnbai and is potentially (c) Microsoft.

When you decommission an Exchange Server in your Organization and have a Hybrid Configuration, one of the things that does not occur is that the server is not removed from the Hybrid Configuration (msExchCoexistenceRelationship) to reflect this. When you run the Hybrid Configuration Wizard, after the decommission, you’ll see the following error:

The wizard did not complete successfully. Please see the list below for error details.
Exchange server “<Server>” was not found. Please make sure you typed the name correctly.


Given the above, you’ll see something similar to the following in Exchange Management Shell for the Hybrid Configuration:

SendingTransportServers   : {UNDERJORDISKE
                            DEL:416ba20c-62c1-4a28-95e5-8dbb6430dc96, LJUSALFER


One method to resolve this issue is to do a modification of the object in Active Directory. Using ADSIEdit, browse to the configuration container and either go to the object’s path (Config container > Services > Microsoft Exchange > Organization Name > Hybrid Configuration) or just create a new query (objectClass=msExchCoexistenceRelationship). Once you have the object, look for the property you want to fix (in this case, it was ‘msExchCoexistenceTransportServers’). I removed the two defunct values.

I, then, used Exchange Management Shell to get the DistinguishedName of the current Transport Servers in the Organization:

Get-TransportService | FL DistinguishedName

DistinguishedName : CN=HYLDA,CN=Servers,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=minvan,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=minvan,DC=se
DistinguishedName : CN=STROMKARLEN,CN=Servers,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=minvan,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=minvan,DC=se

I copied these values into the same property I removed the defunct values, previously. After doing so, I re-ran the Hybrid Configuration Wizard.

One thought on “Hybrid Configuration Wizard: Exchange server “” was not found. Please make sure you typed the name correctly.

  1. John – thank you! I found this really helpful, and it solved my issue. I had an Exchange 2013 sever bite the dust and it wasn’t uninstalled cleanly. I removed it from the organization using ADSIEdit a while back, but had not had to do anything with the
    hybrid wizard in a while….but when I launched it the other day, I got the same error you did.

    To be honest, I don’t go into ADSIEdit very often, so I was at a loss for how to get to the Config container (Mike, who asked you about this yesterday was working with me). In hind sight, this is REALLY simple, but if you have not used ADSIEdit, it isn’t necessarily

    For anyone who runs into this same issue, and is unfamiliar with ADSIEdit, here are the steps:

    Launch ADSIEdt from a Domain Controller in the same site as the Exchange Server from where you are trying to launch the Hybrid wizard. when it opens up, it will likely say, in the left hand pane:

    ADSI Edit
    –> Default Naming Context
    ——> DC=[your internal domain name], DC=[your internal domain suffix]

    Instead of "Default Naming Context" you want it to simply say, "configuration". Right click on "Default naming context" and then left click on "Settings…" This will open a "Connection Settings" dialogue box. under the "Connection Point" section, specifically
    under "Select a well know Naming Context", choose "configuration", then click Ok. That’s all there is to it. Then just drill down as guided by John’s post above.

    Side note – in my instance, I needed to edit two attributes:


    As soon as I made the change, I logged into my Exchange server and was able to launch the Hybrid wizard without issue!



Comments are closed.