Exchange DAG member

I have joined 2012 R2 to a domain and installed Exchange 2013. Is it safe to do NIC teaming after all the changes or NIC teaming would break exchange and domain authentication due to change of MAC address?
pchettriIT DirectorAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Rodney BarnhardtServer AdministratorCommented:
NIC teaming is not recommended on Exchange. Part of it is due to the what it handles the DAG failovers. The system, in a multi-DAG environment, would not be aware there is a failure and move the DAG to the unimpaired server. It seems you may just be using one server, so you may be able to do it, but I have never seen any indication that Microsoft supports this configuration. That is probably due to the fact they would prefer a multi-DAG configuration for failover.

Also, NIC teaming is still not supported on a domain controller. There can be issues there as well. I have tried it in a test environment and DCDIAG fails when it is ran.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Rodney BarnhardtServer AdministratorCommented:
I did find a reference for server 2008. It is supported in one and only one configuration.

"Active Directory Domain Controllers only support teamed network cards in a “Fail on Fault” configuration and not in a load balanced configuration."

"At this time, Microsoft does not support load balanced network teams on domain controllers due to potential data corruption issues."
pchettriIT DirectorAuthor Commented:
I remember having issue on test DC where I had to reinstall server after binding which is why I wanted consult before trying on production Exchange.

Thanks for sharing your inputs appreciate you help
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2012

From novice to tech pro — start learning today.