The Acumen IT Support blog provides you with helpful articles about Microsoft Exchange management and troubleshooting.

Several web sites provide good overviews.

Microsoft Exchange Server Overview

Microsoft Exchange Server Wikipedia


HOWTO Send Email from an Additional Exchange Address


One of our technicians was having trouble sending an email from an additional Exchange address. Acumen Consulting owns the domain but didn’t have it in the Exchange Server.

Our Acumen technician found this solution to the problem.

Exchange Solution:

The solution that will solve the problem permanently is to setup an authoritative domain in the server, create a mailbox for that domain, and then delegate send-as permissions for the mailbox.

You will have to change the SMTP address for this to apply to that domain and this becomes the default reply-to address. The only address that you can send from is the default reply-to address.  You cannot send from an alias.


By default, Exchange applies the address policy based on the recipient (address).

Thus, you need to uncheck the box before making changes to or removing any default SMTP addresses.

Keep in Mind:

You can only SEND from the default reply-to address listed on the mailbox. No exceptions.

You can have other addresses listed as aliases, but when you set send-as permissions to the mailbox or distribution lists, you can only send from the default reply-to address or it’ll bounce back.

For more information about this mail server, visit the link below:

Email Management

Exchange Server Consulting

An error caused a change in the current set of domain controllers


An error caused a change in the current set of domain controllers

In a Windows Domain with Exchange, it is possible that after demoting a domain controller Exchange 2010 Management console will not open properly.

You may see repeated error messages similar to “An error caused a change in the current set of domain controllers.

It was running the command…”. The error repeats regardless of opening and closing the MMC, logging off and on, or restarting the server.

Resetting the configuration domain controller is still possible within the MMC.

But be aware that does not fix the problem.

Domain Controllers Solution:

A solution that has worked to solve this problem is to delete the file “Exchange Management Console” in C:\users\[user]\AppData\Roaming\Microsoft\MMC

After deleting this file, reopen the Exchange Management Console and the file will be recreated.

If you found this useful please visit our IT Support Home Page at Acumen and see other ways we can help you!

Outlook Autodiscover vs Internal DNS – Exchange 2010


Hosting email for multiple domains can be complicated. Especially when all the hosted companies have their own internal DNS servers. This morning we had a customer who was getting a certificate error complaining that the cert did not match the name it was looking for. After using the Exchange connectivity tool (Test Exchange) We verified that from the outside everythi looked good. Once we got into the customers’ internal DNS we found a wildcard record for their outside domain (, not domain.local) that pointed to their webserver. Once we deleted this and created a SRV record that pointed them in the right direction for _autodisover, Outlook ceased to complain about the certificate because everything matched.

These sorts of issues can be the source of much wasted time and effort for an IT staff already overburdened with internal problems. At Acumen we deal with IT issues of this nature all the time and our technicians are available for consultation. Just give us a call at 314.333.3330 or check out our Contact Us Page. See our Exchange Hosting page for detailed information on our services.

Give us a call and hopefully we can help solve your problem quickly and easily.