Potential Downtime or Damage to Exchange if I remove a second domain controller??

We have a single instance of Exchange 2010 with all roles (minus lync, communications, etc..) on a Server 2008 Standard server.
We also have a primary domain controller and a second domain controller that offers DNS and would be used in case of disaster to the primary controller.
I've noticed in the past that if the secondary domain controller is down for maintenance that the Exchange server starts having problems. A major example of this would be last year the virtual instance of the second domain controller failed and when we rebooted
the exchange server, it lost its association with the domain even though the primary domain controller was readily accessible.
We are in a spot now that we no longer need the secondary domain controller and want to decommission it. I obviously want that to go as smoothly as possible. Is there anything I should do to prevent any unwanted damages to the exchange environment?
Jonathan Strader

It doesn't seem that anyone has responded to this. The short answer is turning off the secondary server will NOT have an effect on the exchange server. HOWEVER, that is the short answer.
It WILL have an effect if:
1) the secondary server is the ONLY DNS server and the exchange server is using the secondary server for DNS queries.
2) The FSMO Roles are on the secondary server
3) The Secondary server is the only global catalog.
I know this is a lot to take in.. but it really isn't that hard. FSMO Roles and global catalog are just a piece of active directory that keeps track of users, rights, settings, that sort of thing. You need to make sure that you seize the FSMO
roles on the first domain controller.
One command you can do on the first server to check fsmo roles is:
netdom query fsmo
On a side note. This is what you can do as well to see if the secondary server has any effect on exchange. Ready? Turn off the secondary server and see if anything bad happens (People don't get their emails..) if something stops working
after you turn off the second server then turn it back again. Everything should be back to normal.
Jerry Suner

Similar Messages

Exchange server-Removing a Domain Controller from the forest

Hi Guys,
I need some help on removing a faulty domain controller from the AD forest. Here is the scenario:
1. The FSMO roles have been seized to a new domain controller already.
2. The old one is non-functional and is down for ever.
I know the steps would be doing a meta-data cleanup And then remove some of the DNS entries related to the old server. But the real issue is:
> I have Exchange 2013 running in one of the machines configured in the Forest, which was migrated from the old Domain controller. I then set Exchange listening to the new domain controller.
So, my doubt is, if I delete the old domain controller and do a metadata cleanup, would it have any effect on the exchange server? The Exchange machine acts as an additional domain controller as well. Its a production environment and any
change that affects Exchange would cause a big loss. Looking forward for your valuable suggestions..
Regards,
Nash

Hi Ed,
I don't have issues with the AD on the Exchange server. Eventhough it is configured as an AD, Exchange is pointed to the main working domain controller, which is a different machine. I just want to remove the traces of an old domain controller from which
I transferred the FSMO roles to the new domain controller. The old domain controller is completely down and hence I can't do a conventional 'dcpromo' on it. So just planning to do a 'metadata clean up' for removing the non-working DC from the forest.
So, In essence, I just want to know that, if I do a metadata cleanup, would it affect the Exchange server in any way?
Regards,
Nash

Domain controller upgrade in Exchange Environment

We have an existing 2003 Server Environment and Exchange server 2003 coexistence with Exchange server 2010 with DAG setup. We have recently decided to move to a windows server 2012 standard Environment. How do I promote the new windows Server 2012 std
to DC and remove the 2003 Server from the Environment. My users are currently using the old 2003 DC to logon.
in brief
We have windows 2003 enterprise + sp2 Domain controller (holding DNS as well) and Exchange server 2003 Entp + Exchange server 2010 running in Coexistence with DAG.
We have decided to remove the 2003 Server from the Environment and go with Windows 2012 Standard OS. I would know to know the what will be the impact on Exchange server environment if any ?
please suggest right path with less downtime.Mailing service should not be affected.
TheAtulA

Simply migrate the remaining mailboxes to your Exchange Server 2010 and then you can decommission your Exchange Server 2003. More if you ask them here: https://social.technet.microsoft.com/Forums/exchange/en-US/home?forum=exchangesvrgenerallegacy
Once done, you can upgrade to ADDS 2012 and introduce your first DC running Windows Server 2012. Please note that your Exchange Servers should be SP2 or later to support your new DC. More details here: http://blogs.technet.com/b/rmilne/archive/2013/09/17/exchange-support-for-windows-server-2012-r2.aspx
This posting is provided AS IS with no warranties or guarantees , and confers no rights.
Ahmed MALEK
My Website Link
My Linkedin Profile
My MVP Profile

When exchange Domain Controller or Global Catalog servers?

I have a few questions want to get your help.
1,which situation exchange would contact with the Domain Controller, and which situation exchange would contact with the Global Catalog servers?what's the difference?
2,for the mailbox replication service, besides moving the mailbox ,and DAD relevant operations, which situation mailbox replication service also contact with Dc?
Please click the Mark as Answer button if a post solves your problem!

Hi,
About Question 1:
For Exchange, GC is mainly for Address Book lookups. Exchange server access to the global catalog for address information.
About DC, every domain controller contains the following three directory partitions.
1. Configuration: Contains the Configuration container, which stores configuration objects for the entire forest in cn=configuration,dc= forestRootDomain.
2. Schema: Contains the Schema container, which stores class and attribute definitions for all existing and possible Active Directory objects in cn=schema,cn=configuration,dc= forestRootDomain.
3. Domain: Contains a < domain > container, which stores users, computers, groups, and other objects for a specific domain.
For example, each Exchange Server object has the attribute Boolean messageTrackingEnabled. The Exchange server processes will turn on or off message tracking depending on the value of this attribute in the directory. This is an example of configuration data.
Configuration data is stored in the Configuration partition of Active Directory, and this partition is replicated to every DC in the Forest. Therefore Exchange can potentially go to any DC to access this information.
About Question 2:
The Mailbox Replication Service is responsible for moving mailboxes, importing and exporting .pst files, and restoring disabled and soft-deleted mailboxes. All these options need to contact with DC.
Best regards,
Belinda
Belinda Ma
TechNet Community Support
Thank you so much
Please click the Mark as Answer button if a post solves your problem!

Migrate Domain Controller include Exchange Server

Beside the above suggestions, you may also walk through this informative technet article that covers almost all the required steps and provides step-wise instructions to accomplish this task in simple way : http://blogs.technet.com/b/chrisavis/archive/2013/10/01/performing-an-in-place-upgrade-of-server-200... When you will be migrating users mailboxes from old server to upgraded server, you can have a look on Lepide exchange manager that would be a suitable approach to get this job done in flawless manner without having downtime.

Hi everybody !
My company bought a new server and I have schedule to migrate current domain controller ( 2008 R2 ) to new server ( 2012 R2 )
My system has 1 Exchange server which I'm not familiar with. I have experience with migrating DC ( transfer roles / DNS ) but I'm worry about Exchange server. What should I prepare for this case ?
This topic first appeared in the Spiceworks Community

Migration from Exchange 2007 to 2013 between different domain

Hi,
Our company have two domains controller (AD1 and AD2) but it is not trusted. Due to company change, we need to plan merge two domains to new domain (AD3). Under the plan, we will user ADMT for user object migration and password.
For Exchange, we will plan to use Exchange 2013 on new domain. I want to know that what is the best way to migrate all mailboxes from AD1 and AD2 to AD3's new exchange server. We need to migrate over 500+ mailboxes.
Please anyone to suggest what is the best way to do it ?
thanks

Hello,
You can use the New-MigrationBatch cmdlet to move more than one mailbox at a time. When you create a migration batch, I recommend you use the LargeItemLimit parameter specifies the number of large items to skip if the move request encounters such items
in the mailbox.
If you have any feedback on our support, please click
here
Cara Chen
TechNet Community Support

A problem with Win 7 Pro, Outlook Web Access based on Exchange Server 2003, and two different domains

Dear Microsoft Support,
As mentioned in the title,
I have two domains. One is Domain A at HQ. The other one is Domain A at branch office. A laptop having Win 7 Pro OS is a client of Domain A. The Domain A has Exchange Server 2003. Users of Domain B get connected to Exchange Server for email services. In
all clients of the Domain B, IP address of the email server added in C:\Windows\System 32\drivers\etc\host file.
Whereas in the clients of Domain A it was not done, because all the servers including the email server belong to the Domain A.
Now, a user with Domain A's client (it is a laptop) came to Branch office and wanted to access the Outlook (using Outlook Web Access). since there is no IP address added in the Host file of the laptop, connectivity to email is not possible. When I try to
add the IP address, I was not able to do so due to Domain A's security reasons.
So, let me know, is there a way out to add the IP address in the host file of the Domain A's client.
Thanks in advance.
Ravi Sekhar Modukuru

I would suggest adding the mailserver address in Domain B's DNS. Would that be possible?
I agree. The correct solution in this case (since it appears you already have a two-way Domain Trust in place) is to properly configure DNS in Domain 'B' to be a secondary of Domain 'A' and completely eliminate the need to maintain the HOSTS file.
Lawrence Garvin, M.S., MCSA, MCITP:EA, MCDBA
SolarWinds Head Geek
Microsoft MVP - Software Packaging, Deployment & Servicing (2005-2014)
My MVP Profile: http://mvp.microsoft.com/en-us/mvp/Lawrence%20R%20Garvin-32101
http://www.solarwinds.com/gotmicrosoft
The views expressed on this post are mine and do not necessarily reflect the views of SolarWinds.

How to install Exchange Server 2010 with the name of my existing Domain Controller.

I have my Primary domain Controller as abc.com in 2008 r2 standard. abc.com is registered. I want to set up Fresh Exchange Server 2010 sp2 with the name of the same
abc.com domain name. Please guide me the steps how to do that. Waiting for your kind response. :)

Hi,
From you description, you want to install an Exchange server 2010 in the abc.com. When you set up your Exchange, Exchange need to join in a domain. You just need to specify the domain to abc.com.
What's more, here is a helpful blog about Exchange 2010 installation for your reference.
HOWTO Install Exchange 2010 - Step by Step
http://blogs.technet.com/b/ferris/archive/2010/03/05/howto-install-exchange-2010-step-by-step.aspx
Hope it helps.
Best regards,
Amy
Amy Wang
TechNet Community Support

Upgrading domain controller from Server 2003 to Server 2012 R2, how will this affect Exchange 2010?

Hi All,
Below is an AD and Server related post that I had submitted last week. While I did receive valid responses for the post, I was advised to check with the Exchange forums for the Exchange related question in
bold. All responses are welcomed, thank you!
===========================================================
Hi All,
I am hoping that someone could perhaps provide some insight on this topic as I apparently can't seem to google the best answer.
I have recently acquired an AD domain that is running on a 2003 domain controller. I have been tasked with upgrading our existing domain structure with 2012 R2 domain controllers for our main office and remote offices.
The domain name is company.mynetwork.com, and it is the default first site name. We have multiple offices throughout the US with their own domain controllers (i.e. FL.mynetwork.com, NY.mynetwork.com, DC.mynetwork.com, etc.).
Our main office, and default first site has one domain controller (mynetdc1) running Server 2003 R2. It is also our only DNS server for the main office. It also has an additional domain controller called mynetmaster3 which is running Server 2003.
Both mynetdc1 & mynetmaster3 NTDS settings show them as global catalogs under AD Sites & Services. Both servers are also in the AD Domain Controllers OU, along with all of the other satellite office domain controllers.
Additionally, our main office is running Exchange 2010 with the latest service pack. My questions are:
Can we demote and retire mynetmaster3, then replace mynetdc1 with a newly promoted 2012 R2 global catalog domain controller without harming anything in the domain tree and interrupting connectivity to the other offices (this of course goes without saying
after a 4 hour maintenance window to get the task completed has passed)?
Should we upgrade the satellite offices first after raising the functional level for mynetdc1, or should we do the opposite (upgrade main office, then satellite offices)?
MS Exchange 2010 is heavily dependent on AD, what effect will this entire project have on our email server? What steps should we take beforehand to ensure email continuity?
Finally, is there any shame for a Net Admin to suggest that we hire an implementation specialist for this task? :)
Any advice would be greatly appreciated!

As long as the operating system on your Exchange servers isn't upgraded, and as long as you do the Active Directory domain and forest updates in the supported manner (the following link is a good example -
http://blogs.msmvps.com/mweber/2012/07/30/upgrading-an-active-directory-domain-from-windows-server-2003-or-windows-server-2003-r2-to-windows-server-2012/), Exchange will happily operate behind the scenes. Exchange 2010 is supported in the Windows
forests (domain controllers, domain functional level and forest functional level) mentioned in the following TechNet article, which includes both Windows 2003 and Windows 2012.
http://technet.microsoft.com/en-us/library/ff728623(v=exchg.150).aspx
Due to this, you should be good as long as you do the domain controller, domain, and forest upgrades carefully. Oh, and before you start each step, get a nice backup.

Remove Domain Controller role from Exchange 2010 Server

Hi team,
There is a client with Domain Controller (2008 R2) running together with Exchange Server 2010 SP3. However there were some huge problems with Exchange and DC therefore since the best practice is to keep those roles seperately, they are in need of doing so.
Can someone please suggest me the best approach? The server they use right now is with 16GB therefore whatever done, Exchange should be on that machine and DC on the other 6GB.
Option 01.
Both Exchange and DC are together
Install new Exchange on a temporary Server and move everything make that Exchange server the only working primary
Remove exchange from the DC server
Promote new Additional DC and promote it with FSMO and make primary
Demote the old DC from the 16GB server
Install Exchange again on the 16GB server and move everything from the temporary server
Or Option 02
Add new additionall Domain Controller server and make it primary with GC and FSMO
Run dcpromo to demote the old Domain controller role from where the Exchange Server too is installed
Once DC role is removed from the exchange server, set up DNS and perform a restart, so Exchange will identify the new GC and domain controller
Live happily ever after
Thank You,
Cheers!!

Adding/Removing the DC-Role while Exchange is installed, is not supported so forget about your Option 2.
Here's what I would do:
1. Install a new GC/DC (move FSMO etc)
2. Install a new temporary server for Exchange and move everthing over
3. Decomission the old Exchange Server
4. Demote the old Domain Controller
5. Install Exchange on a newly freshly installed OS and move everything over from your temp server
Martina Miskovic

Installing a Windows 2012 Domain Controller into a 2000/2003 domain with Exchange 2003

Hello,
    I have a client that we are planning to migrate to 2012 over time. They currently have a Windows 200 DC and 2 member servers running Windows 2003, one of which is running Exchange 2003.
    We first are going to introduce a 2012 server into the domain and my plan was to DCPromo the 2003 server that isn't running Exchange and raise domain level to 2003 and then demote the 2000 server. I was then going to install the
2012 server into the domain and make it a backup Domain Controller for the time being and leave the newly promoted Windows 2003 server as the primary Domain Controller with all the roles and global catalog. My question is will Exchange 2003 still function
normally in this scenario?
   I've been doing research and read some things about Exchange 2003 not working with 2012 Domain Controllers, but I was thinking if the 2003 is still the primary, it might work. We will eventually migrate to 2003, they just don't want to
do it all at once, due to costs and other issues.
Thanks.

I didn't ask if it was supported, I just wanted to know if Exchange 2003 would continue
to function if the Windows 2003 DC still held all the FSMO roles and Global Catalog.
A not supported situation means that it is a situation where Microsoft made no testing or do not guarantee that you can operate with no problems. Following a not supported scenario could be done but is on your own risk.
If it won't, can the 2012 server be a member server in the 2003 AD? The 2000
DC it is replacing, just shares files on the network in addition to being the lone AD server
Yes, it can be a member server.
This posting is provided AS IS with no warranties or guarantees , and confers no rights.
Ahmed MALEK
My Website Link
My Linkedin Profile
My MVP Profile

Installing Exchange on a domain controller?

We are very small business firm like less than 10 people. I planning to setup new server. Initially I thought install AD, DNS, DHCP, DC and Exchange on same server. Microsoft not recommending all in my server
Installing Exchange on a domain controller is not recommended.
So give me suggestion, Is it OK install everything on server for small company like us? or
create 1 virtual and install Exchange on that server and rest will be on base?.
ItsMeSri SP 2013 Foundation

Hi,
It is not recommended to install Exchange server on a domain controller. You can create a virtual Exchange server, there is a lot of planning that goes into constructing a virtualized Exchange infrastructure, with the primary consideration being hardware
allocation and fault tolerance. Concerning these factors will guide you to a solid and reliable infrastructure.
For more information, here is a blog for your reference.
Microsoft Exchange 2010: Establishing a Virtual Exchange 2010 Datacenter (Note: Though it is Exchange 2010, it is also helpful to Exchange 2013 about this issue)
https://technet.microsoft.com/en-us/magazine/hh641416.aspx
Hope this can be helpful to you.
Best regards,
If you have feedback for TechNet Subscriber Support, contact
[email protected]
Amy Wang
TechNet Community Support

Exchange Server 2013 and Domain Controller

Hello,
I am planning to install domain controller and exchange server 2013 in same server hardware. Is that not recommended? If not, why is it no recommended?
Thank you in advance,

thanks for such a quick response.
Just a small question about the link that you put. Does member server mean other server other than domain controller?
Regards,
Yes, Also the server on which you are installing Exchange should have exchange installed.
Cheers,
Gulab Prasad
Technology Consultant
Blog:
http://www.exchangeranger.com    Twitter:
  LinkedIn:
   Check out CodeTwo’s tools for Exchange admins
Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.

Proxyaddresses in a domain where Exchange has been removed

Scenario - two companies merge, both have on-premises Exchange orgs. Mailboxes are moved to CompanyA's domain, and Exchange is completely removed from CompanyB's domain. Now, several years later, CompanyA is configuring dirsync (AADSync, actually) to sync
both domains to Office 365, and I just noticed that the accounts in CompanyB still have remnants of Exchange attributes, such as the proxyAddresses. Some of these addresses may conflict with the mail-enabled objects in CompanyA, so my question is - should
we make an effort to clear all the proxyAddresses from the accounts in CompanyB prior to the dirsync? If so, what other attributes do I need to be concerned with? Also, do proxyAddresses have any use other than Exchange? I don't want to clear them if it might
cause problems elsewhere.

You're asking what attributes need to be "cleaned up" after a cross-forest migration? There is no single answer here, as it depends on how the migration was done, but generally speaking the proxyAddresses attribute does a lot of the legwork.
You should have an accepted domain defined for each of your mailboxes' proxyAddresses.
I've not seen proxyAddresses used outside of Exchange.
This is an approach that might get you started
http://theessentialexchange.com/blogs/michael/archive/2009/07/07/removing-old-emailaddresses-proxyaddresses-in-exchange-2007.aspx
Mike Crowley | MVP
My Blog --
Planet Technologies

Preparing new Certificate for Exchange - how to cover the .local domain names

I need to plan out our new certificate for our CAS servers. Exchange 2010 SP3. Our current SAN certificate has several names including our Exchange FQDN's which are exserver.domain.local. I know our CA will not let me generate SAN's with a .local anymore
so how do I cover the Exchange internal FQDN's in the certificate?
I did a get-exchangecertificate and the only certificates I have are the public CA with all the SAN's and Services are IP.WS. The other two Exchange certificates are self signed but only for SMTP "S".
You can only have one certificate for web services "W" so how do you get around the Exchange FQDN? Our internal autodiscover, availability and OOF etc....that Outlook uses all use the Exchange internal FQDN of servername.domain.local.
Even if I generate another Exchange certificate for the server FQDN and submit it to our internal CA, I cannot enable web services on this certificate because my public certificate is already enabled for web services.
Need some help here. I am really stumped on this one.

Hi Shadowtuck,
It is suggested to post in the Exchange forum:
https://social.technet.microsoft.com/Forums/en-US/home?category=exchangeserver
In addition, hope the link below could be helpful for you:
Global changes in legislation regarding SAN SSL Certificates
http://www.networking4all.com/en/ssl+certificates/faq/change+san+issue/
Regards,
Yan Li
Please remember to mark the replies as answers if they help and unmark them if they provide no help.

Potential Downtime or Damage to Exchange if I remove a second domain controller??

Similar Messages

Maybe you are looking for