Link to home
Start Free TrialLog in
Avatar of Brandon Miller
Brandon MillerFlag for United States of America

asked on

Exchange 2013 Cumulative Update 15 Issue

I am getting the following error when attempting to install CU15 on one of our exchange servers.

Error:
Setup can't use the domain controller 'Site' because it belongs to Active Directory site 'Main Site'. Setup Must use a domain controller in the same site as the computer (other mail server).


The server that is getting the error is setup as our other sites mail server. All of the mail accounts are linked from the other sites DC. I cannot move the server to the main site.
2017-11-28-08_02_40-SJSOMAIL---Remot.png
ASKER CERTIFIED SOLUTION
Avatar of Scott C
Scott C
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of Brandon Miller

ASKER

Im not sure I can change it to the main site without causing isues with the trust we have with the other domain?
You may have to.  Setup need to use a DC that's in the same site as your Exchange server you're trying to update.
Oh gotcha once the update is complete I just need to move it back to the other site for normal operation? Basically move the server site over to the mail domain and perform the update then change it back?
That should work. Or just make the change, do the update, leave it and see how things work.  If everything works as it should, just leave it, if you have any interruption, then change it back to the way it was.
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Ronin,

The mail server that I am updating is for the specific site where their DC resides, the main site does not have any of their user accounts that access it.  However, since they are simply linked accounts within the mail domain I guess it would make sense that the Exchange server would need to be on the same site as the MAIL DC's since we have an trust between the mail domain and the external site.

here is a cut from the results:
Get-ExchangeServer -Identity (Problem Server)
(MAIN SITE FQDN)/Configuration/Sites/External Site

Get-ExchangeServer -Identity (Server that update worked on)
(MAIN SITE FQDN)/Configuration/Sites/MainSite
I'm not sure if I understand your explanation.
How many domains/forests do you have? You can substitute the real names with domain.com, domain1.com, etc.
Also, indicate how many physical sites there are as well as what is located in those sites.
Specifically, provide example of the name for the DCs as well as the FQDN for the Exchange.
We have several sites

MainSite/Campus: co.main-site.st.com (5 domains within forest)
mail domain: mail.co.main-site.st.com (Contains mail servers with trusts between sites)

external site/domain: external1.org (Trust between mail domain and external site) linked accounts.

Im not entirley sure how its setup because I started working here after everything was setup. Some of it just leaves me scratching my head as to why it was setup that way. The odd thing to me is when I look in sites and services the MailServer that wont update is not showing up in the main sites and services even though the site results from the powershell show it in there.
MAIL  domain.com/Configuration/Sites/MainSite
OtherMAIL domain.com/Configuration/Sites/ExternalSite  (Problem Server)      
MAIL2 domain.com/Configuration/Sites/MainSite
MAIL3 domain.com/Configuration/Sites/MainSite
MAIL4 domain.com/Configuration/Sites/MainSite

Not sure if this helps clear it up at all.
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
I was able to update the server without changing the Site assignment. I simply added the site in the registry. The update pushed through without any issues.
Enough information provided