Exchange 2013 Site Resilient / DR setup; remove DR CAS server from serving DR-local users
we got exchange 2013 deployment in our primary data center with AD Domain = domain1.com and AD site= primary-Site and with two exchange 2013 servers each with CAS+mailbox roles (srv1.domain1.com + srv2.domain1.com) setup as DAG and file-share witness server in same data center filesrv.domain1.com. each mailbox database has 2 copies one active and one passive. both CAS servers are load-balanced by a separate dedicated load balancer for all exch services like OWA, ECP, EWS,MAPI,... in this office the owa namespace is = https://owa.domain1.com, where all users Outlook clients connect and discovers to their mailboxes using MAPI/HTTP to https://owa.domain1.com/... which is fine since the outlook clients are in the same LAN of the exchange servers data center 1 and belonging to domain1.com AD domain. We wanted to achieve Site Resiliency (a.k.a DR) to our exchange setup. we have already a working data center 2 in another country with: AD Domain = domain2.com and AD site= Branch-Site and with two exchange 2013 servers each with CAS+mailbox roles (srv1.domain2.com + srv2.domain2.com) setup as DAG and fileshare witness server in same data center filesrv.domain2.com. each mailbox database has 2 copies one active and one passive. both CAS servers are load balanced by a separate dedicated load balancer for all exch services like OWA, ECP, EWS,MAPI,... similar to the primary office, this branch office has local LAN Outlook users (belonging to domain2.com AD) connects to their mailboxes which are hosted on the domain2 Exchange owa/DAG this office owa namespace is = https://owa.domain1.com, where all users Outlook clients connect and discovers to their mailboxes using MAPI/HTTP to https://owa.domain1.com/... which is fine since the outlook clients are in the same LAN of the exchange servers data center 2 and belonging to domain2.com AD domain. Notes: both domains domain1.com and domain2.com have full trust and belong to same AD forest. VPN links exist between both offices and functional. both domains are at the same level/ no child domains exist. all users primary SMTP domain is unified = mailto:name@email.com internal DNS autodiscover.email.com ==> owa.domain1.com thru Outlook connection status we can identify which CAS the user is connecting to. Case Scenario: We wanted to achieve Site Resiliency (a.k.a DR) to our exchange setup in the Primary Office. we choose the branch office to be this DR site for our Exchange services in the primary office. We prepared a new AD DC + DNS + GC (srv3.domain1.com) in branch office in AD site Branch-Site with dedicated IP of branch office range along. We prepared a new Exchange 2013 server (srv3.domain1.com) in Branch-Site with branch site IP range to be CAS+MBX roles. we joined the srv3.domain1.com to DAG of the primary office. we added 3rd copy of the databases existing in primary office and got replicated successfully to srv3.domain1.com. also same virtual directory names we configured on srv3.domain1.com similar to what is configured for srv1/2.domain1.com Issue: the strange behavior after deploying the 3rd exchange server srv3.domain1.com in the branch office site, here is that the local LAN users of branch office (whose user accounts belong to AD domain domain2.com and have mailboxes under branch exchange setup DAB of srv1/2.domain2.com with https://owa.domain2.com), now these outlook LAN clients connect to https://owa.domain1.com (which is hosted over WAN on primary DC) which is hosted in the primary office data center. we don't want our branch users outlook clients to connect over Internet WAN link to the primary exchange CAS (https://owa.domain1.com). these outlook clients used normally to connect to the branch exchange CAS owa.domain2.com. Required to achieve: We want srv3.domain1.com CAS+MBX as DR server to switch over to it from primary office to it in case of primary DC is down and to keep the existing branch users connecting normally to their exchange setup owa.domain2.com and NOT to use the owa.domain1.com by any means
User removed from AD remains in the GAL
Good morning, I removed a user from our Server 2016 domain because I was given the wrong spelling of her first name (I tried to change the display name, since both names start with "C", but the server wouldn't allow it). I recreated the user's account using the correct information and then saw that the original mailbox was still there so I removed it. Now I have the new, corrected name with a mailbox under that new name, but when I go to Outlook, click on To... , and scroll down (my Address Book is the GAL), the new name doesn't show up but the old name does. AND, that old name has an External Contacts icon. I've done AD searches, ADSIedit searches, and my mailbox search only brings up the new, correct mailbox. I have no idea on where to go from here. I'm not an Exchange guy so if I'm missing something simple I'll be ok with someone pointing it out. Thanks, Joe B
Mails not able to send not
Hi, I getting an error in the payslip application. While sending the payslip through the software to the 100 employees in our organization it is sending only 5 mails all other mails are rejecting. I am unable to find whether the issue with the payslip software or in exchange server having any limitation from the sender email.
Migrating Exchange 2013 from On Premise to Azure
Hello Experts! I am looking to migrate Exchange 2013 running on Onpremise to migrate on Azure or new different datacenter. 2 VMs for CAS+Mbx (DAG1), 2 VMs for Mbx(DAG2), 2 VMs for SMTP, 2 VMs for Edge Transport running on esx host. I will have express route VPN and requirement infrastructure deployed. I have below 2 queries- Once co existence configured and Exchange 2013 Infrastructure running on IaaS promoted as Internet facing CAS, will there by any redirection required to legacy on-premise Exchange 2013 infrastructure will this work smooth or any issues are expected? If I deploy 2 Servers (CAS/MBX) having both the roles, can I use DAG for mailbox server high availability and Azure LB for CAS Load balancing. I know Exchange running on Azure IaaS is less recommended due to cost and other factors and O365 is recommended solution but this is one of requirement hence please suggest if we have any other solution. I went thru this article and we don't have hyper v as of now: https://docs.microsoft.com/en-us/exchange/exchange-2013-virtualization-exchange-2013-help?redirectedfrom=MSDN#bkmk_prereq Thank you.
IMCEAEX NDRs 50% solved - Exchange 2013
Hello, After DB corruption and re-creating two mailbox accounts, adding new X500 email address entries (based on email NDRs "mailto:" fields) and deleting cached contact information in outlook clients, I've ended up with a functional account and the other account (let's say ABC@smoothe.com) not being able to receive emails. The weird thing is, outlook clients are caching the contact with a typo from somewere I'm not being able to find nor fix. Even weirder, users are able to send emails for a first time if they delete cached contact information and then type the email address manually, but on a second attempt they receive a NDR message with the wrong X500 email address. Exchange side X500 entry: /o=corp123/ou=Exchange Administrative Group (FYDIBOHF4141415)/cn=Recipients /cn=ABC@smooth.com Outlook NDR: /o=corp123/ou=Exchange Administrative Group (FYDIBOHF4141415)/cn=Recipients /cn=ABzC@smooth.com I've restarted several services and tried restarting the server. No luck. Did I missed something when re-creating the mailboxes in the Exchange Server? Thanks in advance! Max
Exchange Server 2013
I know I am using an outdated version of Exchange given 2019 is current but I can't upgrade yet. We are currently using Exchange CU14 on Windows 2008 and I'd like to get a fresh install of Exchange on 2012 R2. Since CU14 is no longer available, I was looking to upgrade to CU23 ... at least I would be on a supported version of 2013 on a supported server OS. So far, I have a new VM that is patched up to date. I've run repadmin /syncall on by DCs and they are error free I've run dcdiag on my DCs and they are in synch I ran setup /PrepareSchema /IAcceptExchangeServerLicenseTerms successfully. I reran the two utilities above as well as repadmin /showreps ... everything cleared. When I try to run setup with the /PrepareAD parameter, it errors out. ----------------------------- D:\Exchange Install\Exchange2>setup /PrepareAD /IAcceptExchangeServerLicenseTerms Microsoft Exchange Server 2013 Cumulative Update 23 Unattended Setup Copying Files... File copy complete. Setup will now collect additional information needed for installation. Performing Microsoft Exchange Server Prerequisite Check Prerequisite Analysis COMPLETED Configuring Microsoft Exchange Server Organization Preparation FAILED The following error was generated when "$error.Clear(); initialize-ExchangeUniversalGroups -DomainController $RoleDomainControll er -ActiveDirectorySplitPermissions $RoleActiveDirectorySplitPermissions " was run: "System.NullReferenceException: Object reference not set to an instan ce of an object. at Microsoft.Exchange.Management.Tasks.InitializeExchangeUniversalGroups.Crea teOrMoveEWPGroup(ADGroup ewp, ADOrganizationalUnit usgContainer) at Microsoft.Exchange.Management.Tasks.InitializeExchangeUniversalGroups.Inte rnalProcessRecord() at Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__b() at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String fun cName, Action func, Boolean terminatePipelineIfFailed) at Microsoft.Exchange.Configuration.Tasks.Task.ProcessTaskStage(TaskStage tas kStage, Action initFunc, Action mainFunc, Action completeFunc) at Microsoft.Exchange.Configuration.Tasks.Task.ProcessRecord() at System.Management.Automation.CommandProcessor.ProcessRecord()". The Exchange Server setup operation didn't complete. More details can be found in ExchangeSetup.log located in the <SystemDrive>:\ExchangeSetupLogs folder. ---------------------- When I go into ADSI Edit and look at Configuration, Services, Microsoft Exchange properties and drill down to the contents of the OtherWellKnownObjects attribute, I can see the full path of where it is currently set. When I look in AD, I can drill down into the OU and see the Managed Availability Servers group. In the properties, I can see our existing Exchange server. Since the OtherWellKnownObjects attribute can't be edited, how can I resolve the issue to get AD Prep'd and Exchange installed? Am I going about this the wrong way? My thoughts were to bring up a second exchange server, migrate the mailboxes and other settings and then make the necessary DNS modifications. Thoughts?
