Skip to main content
Get-ExchangeServer

Remove Exchange Server From Active Directory Domain

Remove Exchange Server From Active Directory Domain

At times you may have to remove exchange server from Active Directory domain because the Server is dead and there is no possibility to recover it. In such situations, we can use Adsiedit.msc to remove the dead server entries from active directory domain. The procedure is same for Exchange 2007, 2010 and 2013

I came across a situation where the exchange 2010 environment was running smoothly, except there was a dead Exchange 2007 Server that was still showing in the settings.

So to list all the Exchange servers we have in the environment, open the Exchange Powershell and run Get-ExchangeServer:

Get-ExchangeServer

As we can see, the dead server “Mail” is a standard edition server with version 8.3 (Exchange 2007 Sp3). While the other functioning servers are 14.3 (Exchange 2010 Sp3).

Before removing the dead Server, we need to remember the following:

  • Ideally we should remove the exchange server by uninstalling from Add/Remove Programs.
  • It should be our last method to remove the server, when we are 100% sure that the server is unrecoverable.
  • Send/Receive connectors or any other configuration may still have the server in the settings, you should remove them manually.
  • AdsiEdit is very sensitive thing, only make changes when you know what you are doing.
  • It is good practice to take System State backup before making changes in the Adsiedit.

If you confirm all the above points, you can proceed to the removal step, otherwise leave it and ask for help from some senior systems engineer.

Procedure:

To remove the dead server, open Adsiedit.msc and connect to Configuration:

ADSIEDIT Configuration

Then go to the following path:

Configuration, CN=Configuration, CN=Services, CN=Microsoft Exchange, CN=<OrganizationName>, CN=Administrative Groups, CN=Exchange Administrative Group (FYDIBOH…, CN=Servers

Remove Exchange Server From Active Directory

Select the dead server from right pane, right click and delete.

ADSIEDIT Configuration exchange server delete

Finally, go again to Exchange Powershell and run the Get-ExchangeServer command to confirm the server is deleted from the list.

Get-ExchangeServer after

You may also like to check the Technet article “Remove the last legacy exchange Server”.

Allow This Website To Configure Server Settings

Fix: Allow This Website To Configure Server Settings

Allow This Website To Configure Server Settings

If we use DNS SRV record for Autodiscover, you may get the message “Allow This Website To Configure Server Settings” while opening the Outlook. The detail mentions:

https://Mail.Domain.com/Autodiscover/Autodiscover.xml

“Your account was redirected to this website for settings. You should only allow settings from sources you know and trust.”

Allow This Website To Configure Server Settings

It appears because Outlook has found the SRV record for Autodiscover that is configured for mail.domain.com. The complete SRV record is _Autodiscover._tcp.domain.com. The complete URL for Autodiscover also appears in this notification. This warning message is  expected and we can ignore it by clicking Allow.

Fix for a Single User:

To automatically ignore this warning message for a user, we need to add a registry entry on the User’s PC depending on the Outlook version.

Outlook 2007:

HKEY_CURRENT_USER\Software\Microsoft\Office\12.0\Outlook\AutoDiscover\RedirectServers

Outlook 2010:

HKEY_CURRENT_USER\Software\Microsoft\Office\14.0\Outlook\AutoDiscover\RedirectServers

Outlook 2013:

HKEY_CURRENT_USER\Software\Microsoft\Office\15.0\Outlook\AutoDiscover\RedirectServers

Outlook 2016:

HKEY_CURRENT_USER\Software\Microsoft\Office\16.0\Outlook\AutoDiscover\RedirectServers

RediretServers

Go to the related path and create new string value with the name of the Server we are redirecting in SRV record, for example mail.domain.com.

RediretServers mail.domain.com entry

Close the registry and you will no longer get this prompt again for this user.

 

Fix for multiple users through Group Policy:

If you want to push this registry entry through group policy, you can create a new group policy object and link it to the Users OU. Browse to “User Configuration\Preferences\Windows Settings\Registry” and create new registry item with the following settings:

Action: Update
Hive: HKEY_CURRENT_USER
Key Path: Software\Microsoft\Office\15.0\Outlook\AutoDiscover\RedirectServers
Value name: mail.domain.com
Value type: REG_SZ

Registry entry mail.domain.com

If users have different Outlook versions, then you have to create Registry key for each Outlook version. By just changing the path.

For example for Outlook “Software\Microsoft\Office\15.0\Outlook\AutoDiscover\RedirectServers” for Outlook 2013 and “Software\Microsoft\Office\16.0\Outlook\AutoDiscover\RedirectServers” for Outlook 2016 and so on.

The Connection to Microsoft Exchange is Unavailable

The Connection to Microsoft Exchange is Unavailable

The Connection to Microsoft Exchange is Unavailable

The Connection to Microsoft Exchange is Unavailable in Outlook 2010 appears some times while opening Outlook or setting up a new Outlook profile gives error . Similar issue is experienced with Outlook 2013 and Outlook 2016.

The Connection to Microsoft Exchange is Unavailable

No Connection Issues? Try these:

But most of the times, it is neither related to Outlook’s connectivity to the network nor Exchange Server is down. The problem is caused because of the Autodiscover process faced some issue during the profile setup. For that, you can try the following:

  • Use the manual setup process and provide the Server details, make sure to configure the Exchange Proxy settings.
  • Configure the outlook with caching turned off, you can turn it on later if needed.

May be there are Connection issues, Try these:

Some times you may have some connection issues between Outlook client and Exchange Server, then you can try the following things:

  • If the error comes for an existing profile, try to create a new Outlook Profile.
  • Flush DNS (To clear the DNS cache, in case there were some IP/Name related changes).
  • Disable the Antivirus Software and try again(Many Antivirus have builtin firewall these days).
  • In case you are using proxy Server for Internet, Add Proxy exception for mail.domain.com, to redirect traffic to the local server.