windows, vmware, linux and whatever else confuses me…

Archive for April 2013

How to: Remove Legacy Exchange Servers using ADSIEdit tool

leave a comment »

Why would you need to remove legacy exchange servers via adsiedit.msc ? A few reasons:

  • The servers are permanently offline due to bad hardware/operating system
  • An installation/uninstall of Exchange failed

The following steps must be completed via ADSIEdit tool in order to remove legacy Exchange Servers from your environment

To enable this tool in Windows 2008R2/Windows 7:

Start –> Run and type “regsvr32 adsiedit.dll” (without the quotes) –> “Ok” key.  A dialogue screen will appear with an successful message. Click “Ok”. Then go to Start –> Run and type “adsiedit.msc”. This command will open the adsiedit tool

Select the correct Naming Context:

By default “Configuration” should be listed.  If it is not right-click on ADSI Edit and select “Connect to”. Under “Connection Point” make sure “Configuration” is selected under the drop down menu of “Select a well known Naming Context:”. Click “Ok”

Perform the removal: (Exchange 2007/2010)

Navigate to the following path –> Configuration –> Services –> Microsoft Exchange –> First Organization –> Administrative Groups –> Exchange Administrative Group –> Servers

Once you are in the “Servers” container you can simply right-click the server and select “Delete”

For Exchange 2003 the path is very similar except for one container name:

Configuration –> Services –> Microsoft Exchange –> First Organization –> Administrative Groups –> First Administrative Group –> Servers

Refresh the server list in Server Manager/EMC and those old legacy servers should now be gone

Written by thlnk3r

April 17, 2013 at 08:13

Posted in Uncategorized

Exchange 2010: Edge Transport versions not updating after SP3

leave a comment »

After updating to Exchange 2010 SP3 x64 I noticed my Edge Transport server version did not update. It was still displaying version 14.2 (should say 14.3).

Solution: Delete and re-create the Edge Transport subscription

Steps I took:

In the Edge Transport Server, Open the Exchange Management Shell –> Type following

New-EdgeSubscription –FileName “C:\EdgeSubscription.xml” (or whatever file name you prefer to have)

Copy the Edge subscription file to the Hub Transport server (which in my case was my multi-role exchange server) into C:\

In Hub Transport Server –> Open Exchange Management Console –> Organization Configuration –> Hub Transport section

In the action pane, click New Edge Subscription –> New Edge Subscription Wizard

Click Browse –> select Active Directory site –> Select Default First Site

Browse to the location of the Edge subscription file that was copied over from the Edge Transport server and click Next –> Finish

Verify synchronization to the Edge Transport server’s AD LDS via Event Viewer. Also verify and make sure the NEW version number reads correctly (in my case it now says 14.3)

Written by thlnk3r

April 6, 2013 at 08:45

Posted in Uncategorized

Exchange 2010 Error: MapiExceptionNotFound: Unable to mount database (hr=0x8004010f, ec=-2147221233)

leave a comment »

When attempting to create a few databases in my Exchange 2010 environment I received the below error:


MapiExceptionNotFound: Unable to mount database (hr=0x8004010f, ec=-2147221233)

The cause is described in this Microsoft KB:

This issue occurs when the value of the ConfigurationDomainController parameter and the value of the PreferredGlobalCatalog parameter are different. In this scenario, the Mailbox database operation fails because of the replication latency that occurs between the configured domain controllers and the preferred global catalog.


To resolve this issue, set the preferred Active Directory server in Exchange Management Shell to the following cmdlet: 

Set-ADServerSettings –PreferredServer <DC FQDN>

I’m guessing this error appeared AFTER I promoted two more domain controllers to my lab environment. After updating the preferred server name (FQDN) I was able to successfully add new databases. Also if the error above occurs more than once AFTER doing the PS command (Set-ADServerSettings), I recommend restarting the AD Topology service and Information Store service.

Written by thlnk3r

April 6, 2013 at 07:16

Posted in Uncategorized