Exchange Server 2013 failover design

Hello:
I'm designing a failover Exchange Server 2013 solution. I only need mail and calendar services.
I'm planning to put two physical servers with Windows Server 2012 R2 with (or without) Hyper-V to run one virtual machine in
each physical server.
I don’t have external storage device, I like to use database replication
Also, I have a physical third party anti-spam firewall
The questions:
I need one VM for Mailboxes and a separate one for CAS (4 VMs in total) or I can install 2 VMs with MBX+CAS in each VM server?
I need a third server to avoid brain duplication, or isn’t needed?
Exchange Server 2013 supports POP3 connections?
Thanks for your time, and sorry for my bad English!
Un saludo! Juan Segura

The questions:
I need one VM for Mailboxes and a separate one for CAS (4 VMs in total) or I can install 2 VMs with MBX+CAS in each VM server? - Definitely you can go for multi-role servers
to combine MBX+CAS and in fact that's
recommended except couple scenarios.
I need a third server to avoid brain duplication, or isn’t needed? You need a witness server but that can be non-Exchange server too. You need to add Exchange trusted subsystem
in Local Admin group of that server
Exchange Server 2013 supports POP3 connections? - Yes, you can have POP3 connections
Blog |
Get Your Exchange Powershell Tip of the Day from here

Similar Messages

Exchange server 2013 - Setting up DAG

Hi Guys,
I have an Exchange 2013 server(a single dedicated box with all the roles(MailBox and Client Access) configured in it. Now I want to enable data redundancy and Failover. So, I want to setup a DAG and my idea is given below.
I Want to setup a 2 node DAG. The first node is my current working box and the second node is another box at a different location. I would then Install Exchange on the 2nd node with mailbox role on it. As it is a 2 node DAG, I would require another box as
a witness server.
Please let me know if there is any flaws with the above setup. Also, let me know if I require a different Exchange server license for the second installation.
Thanks and Regards,
Nash Burns

Hi,
From the article blow, we know a license must be assigned for each instance of the server software that is being run. The second Exchange server need a license.
Exchange Server 2013 licensing
http://office.microsoft.com/en-us/exchange/microsoft-exchange-server-licensing-licensing-overview-FX103746915.aspx
And the type of license is based on the number of mailbox databases.
Standard: designed for the mailbox needs of small to midsize organizations. Also appropriate for non-mailbox roles in a larger Exchange deployment. This edition supports 1 to 5 mailbox databases.
Enterprise: designed for larger organizations that may require a greater number of mailbox databases. This edition supports 1 to 100 mailbox databases.
Best regards,
Belinda
Belinda Ma
TechNet Community Support

Exchange 2010 /2013 DAG Design

Hi All,
I Have Gone through some Articles and Blogs where i read about the DAG Design and Member server placement in Site Resiliency Scenarios..
I just want to know what and how many DAG Designs we can propose to Customers.
As per my knowledge and study i came across -
(A) Active/Passive Model with Shared Namespace (Single DAG)
(B) Active/Passive model with different namespaces (Single DAG)
(C) Active/Active Model with Different Namespaces (2 DAGs).
I am Just Curious to know is there any other model DAG that can be proposed apart from above mentioned Designs in terms of both Namespace and Database Active copy Location.
Also can you also put some light and clarify whether we can have
Active/Active Model with Shared Namespace (Single DAG). I have read it is supported in exchange 2013, if so can we do the same in Exchange 2010 as well. If not what makes this design different in exchange 2010 v/s exchange 2013. How can we
achieve this design in exchange 2013?
I got a good article on above scenarios
here but I have some terms or paragraphs bit
confusing. Please help me to understand the bold lines in below paragraph.
Since we typically only have active users connecting to the primary datacenter (at least the majority of the users connect to this datacenter unless a site failover occurs),
the autodiscover record (autodiscover.exchangelabs.dk) in external DNS points to the load balancer in the primary datacenter. The internal “AutoDiscoverServiceInternalUri” on the CAS servers in the primary datacenter has been configured with a value of https://mail.exchangelabs.dk/autodiscover/autodiscover.xml,
and the same goes for the CAS servers in the failover datacenter. Now you could choose to point the AutoDiscoverInternalUri on CAS servers in the failover datacenter at “https://failover.exchangelabs.dk/autodiscover/autodiscover.xml” but
you can easily up on in a situation where SCP’s aren’t reachable during a site failover. Also, cross-site traffic caused by Autodiscover have a minor impact on the WAN link since autodiscover requests consists of small XML based text files.
Also in
Active/Passive model with different namespaces (Single DAG) or Active/Active Model with Different Namespaces (2 DAGs) model do we still repoint EWS,OA,EAS
etc. web service records in public DNS. If yes what should be their value (please refer
Complete Site failover Segment in Above URL)
it would be very helpful if you could provide any detailed Design diagram as mentioned in URL to understand the things better. or any Technet Articled with well
description
Thanks in advance
Regards
Aanand Singh
Regards, Aanand Singh

Hello,
The sentence " you
can easily up on in a situation where SCP’s aren’t reachable during a site failover. Also, cross-site traffic caused by Autodiscover have a minor impact on the WAN link since autodiscover requests consists of small XML based text files." I
understand that if site failover occurs,as long as the CAS servers are available in the primary datacenter, clients will continue to connect to the CAS servers in this datacenter. The CAS servers will not be used in the failover datacenter.
Consider WAN outage, we recommend you deploy Active/Active Model with Different Namespaces (2 DAGs).
Besides, I recommend you configure DNS to round-robin between the VIPs of the load balancers in each datacenter to realize single namespace.
Here are some articles for your reference.
http://technet.microsoft.com/en-us/library/dd979781(v=exchg.141).aspx
http://blogs.technet.com/b/scottschnoll/archive/2012/11/01/storage-high-availability-and-site-resilience-in-exchange-server-2013-part-3.aspx
http://blogs.technet.com/b/exchange/archive/2013/01/25/exchange-2013-client-access-server-role.aspx
Cara Chen
TechNet Community Support

Mail Delivery betweek Exchange Server 2013 co-existance with Exchange server 2010

Hello Guys
I have a mailflow issue, hoping someone can help with detail description, below is the setup
Exchange server 2010 SP3 with all roles in one server
Exchange server 2013 SP1 with CU6 with all roles in one server - this server is in a different subnet to the 2010 server. I am able to see exchange 2010 databases and mailboxes from Exchange 2013. For testing purposes, I have moved 3 mailbox from 2010
to 2013. These 3 mailbox, is able to send and receive email from Internet but to each other via OWA or Outlook. These 3 mailbox also not able to send to receive email from any mailbox that is still in 2010 server via OWA or Outlook. I am not planning the whole
server cutover in a go and planning to do state by stage mailbox migration so I need mailflow working properly. When I send an email from one of the migrated mailbox that is in 2013 server, I can see that the email leaves the mailbox outbox and sits in the
queue ..
Can someone please provide detailed solution what needs to be configured?
MCITP, MCSA, MCSE,VCP - Consultant, Solution Design, Implementation

Hi,
1.please check the mailbox send and receive quota for exchange 2013 migrated mailbox.
2.Please check the email attributes of the exchange 2013 migrated mailbox because it seems to be a problem with that particular mailbox.
3.Then do the message tracking and that would be the only way to find the where the send messages has gone.
4.Please check and confirm you have an enough space on the disk where exchange queue database is residing.
I think I need to create a receive connector in the 2013 to receive from 2010 ?
No need ,by design exchange 2013 cas server default frontend receive connector will be having an
entire ipv4 and ipv6 segment and anonymous connection is checked by default.
I think I also need to create a send and receive connector for 2013 users to each other?
No need , an intra organisation send connector and the default receive connectors in exchange will be used
for internal mail flow between the exchange 2013 users.
Please reply me if you have any queries .
Regards
S.Nithyanandham
Thanks S.Nithyanandham

Deploying 2x Exchange Server 2013 CAS server email traffic high availability during patching & reboot

Hi people,
What is the best way to utilize VMware technology to host 2x the Exchange Server 2013 CAS role VM in my production VM to ensure that the email traffic is not halted during server patching ?
Previously in Exchange Server 2007 I am using Windows NLB (IGMP Multicast) on my ESXi 4.1, now with ESXi 5.1 and 2013 I wonder if there is any better way to make sure that the server failover does not disrupt the mail flow between the Smarthost and the CAS server role.
Thanks

Hey AlbertWT,
Can you clarify exactly what you mean when you say "server patching?" Do you mean patching at the ESXi host level or something within the guest?
As you probably know Exchange 2013 CAS no longer needs NLB or even a hardware load balancer. Due to changes in the architecture, even simple DNS round robin is "enough" to load balance the CAS role. NLB has its own set of headaches which you are probably all too familiar with so getting rid of that can help remove a lot of complexity from the situation.
If you can clarify what you mean by "server patching" and "server failover" in your post I think that would be helpful for me to give you a more definitive answer.
Matt
http://www.thelowercasew.com

Exchange Server 2013 architecture

Hi
We are planning to migrate Exchange server 2010 to 2013 with DR.
Could anybody please tell me the recommended design for this..
I am planning to put two CAS Server, two mbx server in production site and one CAS server , one MBX server in DR site.
Enabling DAC in DR site.
This design is ok or else i need to put all roles in two server in production and one in dr..
Please advise...

Either option would leave you with at least one available server per role in the main site, except that with two servers, you would have two servers holding the role not affected by the failure of a given server.
For example, you have CAS1, CAS2, MBX1, MBX2.
If MBX1 fails, you still have two CAS.
If CAS1 fails you still have two MBX.
What's generally more of a problem is quorum for the DAG cluster.
If you loose the main site, the database mailboxes cannot mount in the DR because they would not "have quorum".
This is adressed at the bottom of this article:
http://technet.microsoft.com/en-us/library/dd979799(v=exchg.150).aspx
This also addresses the notion of "quorum":
http://www.msexchange.org/articles-tutorials/exchange-server-2013/high-availability-recovery/exchange-2013-dag-dynamic-quorum-part1.html
You might address this (at a greater cost) with two DAG nodes in each site and with a FSW and alternate FSW.
Just a note: if you want all-around high availability, you would want to consider the CAS role as well (perhaps you have) which usually involves use of some form of load-balancing (or DNS round robin in a worse case scenario - not optimal).
Load-balancing between distant sites can be more of a challenge. If you have more questions, ask away.
Please mark as helpful if you find my contribution useful or as an answer if it does answer your question. That will encourage me - and others - to take time out to help you.

Pull POP client web to Exchange Server 2013

Hi, i am new in Microsoft Exchange Server and Email Server Administrator. At present, my company planed to have a Microsoft Exchange Server 2013 and my scope will pull data from the web-client using POP3 to the Exchange. Would you guys give me any solution
and advice for this? Thanks a ton
Sorry for my bad English.

Hi,
What’s the exact mean of “pull data from the web-client using POP3 to the Exchange”? Do you mean the Outlook client connects to Exchange 2013 with POP protocol?
If that is the case, please enable and configure the POP in your Exchange server by the following article:
https://technet.microsoft.com/en-us/library/bb124934(v=exchg.150).aspx
Generally, POP3 was designed to support offline mail processing. With POP3, email messages are removed from the server and stored on the local POP3 client unless the client has been set to leave mail on the server. For more information
about POP3 in Exchange 2013, please refer to:
https://technet.microsoft.com/en-us/library/jj657728(v=exchg.150).aspx
Regards,
Winnie Liang
TechNet Community Support

How to clone Microsoft Exchange Server 2013 configurations from one server to another server?

Hi! I need help of cloning Microsoft Exchange Server 2013 configurations from my first Server to the second Server. By doing this, the second Server will replace and run as per normal as the first Server is. How can this be done?
Thanks!

Cloning an Exchange Server is a very bad idea. Exchange is very heavily intergrated into Active Directory and this can (and honestly not to sound scary probably will) cause major issues in your environment.
Also, since you cannot have 2 servers with the same name in the same domain/network running at the same time you'll need to change the name of one of the servers. That is a huge no-no with Exchange and requires a complete uninstall/reinstall of the
product.
Now requirements differ between environments, but if you are in a scenario where you want to move from 1 Exchange 2013 (or 2010 for that matter) Server to another machine running the same version of Exchange AND (this is a big requirement for the failover
cluster piece) the Operating Systems of the machines are the same (i.e going 2012r1 to 2012r1 or 2012r2 to 2012r2 and not 2012r1 to 2012r2) you can do what Brenle suggested with the DAG and DB copies. If the Operating System of the new machine is different
(2012r1 to 2012r2) then you will will not be able to use a DAG, and will need to perform mailbox moves to move between servers.
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread

Error in Installing Exchange Server 2013 (w SP1) Mailbox Role on Windows Server 2012 R2

Hi Team,
Need urgent help in resolution of following error:
Environment Details: VMware ESXi 5.5 (vMotion)
Migration from Exchange Server 2007 (SP3 + RU13) to Exchange Server 2013
Exchange Server: Exchange Server 2013 with SP1 (Latest Installation Media)
OS: Windows Server 2012 R2 - Standard (Latest Installation Media)
Exchange 2013 Roles: Seprated (Mailbox and CAS on Different VMs)
Prerequisites: Installed
Error: Installation gives Error at Step 10 during installation of Mailbox Service
Error Details Below:
Error:
The following error was generated when "$error.Clear();
if ([Environment]::OSVersion.Version.Major -ge 6)
$WsbBinPath=$RoleInstallPath+"bin\wsbexchange.exe";
$reg= join-path (join-path $env:SystemRoot system32) reg.exe;
$servicecmd = join-path (join-path $env:SystemRoot system32) sc.exe;
if ((get-service wsbexchange* | where {$_.name -eq "wsbexchange"}))
if ((get-service wsbexchange).Status -eq "Running")
Start-SetupProcess -Name:"$servicecmd" -Args:"stop wsbexchange";
Start-SetupProcess -Name:"$servicecmd" -Args:"delete wsbexchange";
Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\CLSID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /t REG_SZ /d `"CExchangeHelper Class`" /f";
Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\CLSID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /v AppId /t REG_SZ /d `"{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /f";
Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\CLSID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}\LocalServer32`" /t REG_SZ /d `"$WsbBinPath`" /f";
Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\APPID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /t REG_SZ /d `"CExchangeHelper Class`" /f";
Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\APPID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /v LocalService /t REG_SZ /d `"wsbexchange`" /f";
Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\APPID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /v LaunchPermission /t REG_BINARY /d `"010004806000000070000000000000001400000002004c0003000000000014001f000000010100000000000512000000000018001f000000010200000000000520000000200200000000180003000000010200000000000520000000270200000102000000000005200000002002000001020000000000052000000020020000`"
/f";
Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\APPID\wsbexchange.exe`" /v AppId /t REG_SZ /d `"{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /f";
Start-SetupProcess -Name:"$reg" -Args:"add `"HKLM\Software\Microsoft\windows nt\currentversion\WindowsServerBackup\Application Support\{76fe1ac4-15f7-4bcd-987e-8e1acb462fb7}`" /v `"Application Identifier`" /t REG_SZ /d
Exchange /f";
Start-SetupProcess -Name:"$reg" -Args:"add `"HKLM\Software\Microsoft\windows nt\currentversion\WindowsServerBackup\Application Support\{76fe1ac4-15f7-4bcd-987e-8e1acb462fb7}`" /v CLSID /t REG_SZ /d `"{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`"
/f";
Start-SetupProcess -Name:"$reg" -Args:"add `"HKLM\Software\Microsoft\windows nt\currentversion\WSBAppExchangeHelper`" /v AutoMarkDbRecoverable /t REG_DWORD /d 1 /f";
Start-SetupProcess -Name:"$reg" -Args:"add `"HKLM\Software\Microsoft\windows nt\currentversion\WSBAppExchangeHelper`" /v AutoMountOnPITRecovery /t REG_DWORD /d 1 /f";
Start-SetupProcess -Name:"$servicecmd" -Args:"create wsbexchange binpath= `"$WsbBinPath`" type= own start= demand error= ignore obj= LocalSystem DisplayName= `"Microsoft Exchange Server Extension for Windows Server Backup`"";
Start-SetupProcess -Name:"$servicecmd" -Args:"description wsbexchange `"Enables Windows Server Backup users to back up and recover application data for Microsoft Exchange Server.`"";
" was run: "Process execution failed with exit code 1.".

Resolved ! :)
Root Cause: The user account I was using had all the required privileges for Exchange Installation but was not having access to edit the registry of the server. Enable access to registry edit tools and you are good to go.
As an alternate you can also try installing using Domain Administrator account if in case there is an IT Policy constraint in the former method.
Thanks to all.

Exchange Server 2013 Client Mail are Return.Error is [0x80040305-0x0004de-0x00054a]

Hi,
We are using Exchange Server 2013.we have Outlook 2007 SP3 and 2010 SP2 client .Some clients inform mails are return.
Return massage
"This message could not be sent. Try sending the message again later, or contact your network administrator. Your server administrator has limited the number of items you can open simultaneously.
Try closing messages you have opened or removing attachments and images from unsent messages you are composing. Error is [0x80040305-0x0004de-0x00054a]"
Thanks,
Gayan

1) Disable TCPChimney and RSS on CAS and Mailbox Servers by running below commands
netsh int tcp set global chimney=disabled
netsh int tcp set global rss=disabled
2) Disable unwanted Add-Ins in outlook that may open many sessions
3) If above steps doesnt resolve, you can delete existing outlook profile and create new Outlook online profile

How can I clone a completed Exchange Server 2013 in a Lab Enviroment?

I was having great time with my Exchange Server 2013 until I tried to clone it to avoid fresh installation of another Exchange 2013 server. Steps taken
(1)Clone the Exchange1 and turn it off
(2) Brought the Clone Exchange2, renamed it, change the IP configurations,
(3) Re-ran the ADprep/Doamin prep
(4) Checked the ASDIedit to verify the Schema/configuration in AD
(5) Restarted I and was able to logon to the Exchange2
(6) Brought up the Exchange1, but unable to logon because the name was no longer in AD database
What I did to fix this:
(7) Rejoin the Exchange1 to the domain - and was able to logon
(8) Unable to access ECP or OWA of any of the two servers.
(9) Errors received - Fix the configuration file of the application
My Question - How to I fix the configuration file as suggested (via powershell or GUI or ASDIedit.msc)?

Unless you are cloning an entire environment, and then bringing it up in a seperate isolated environment, it is not supported to simply clone an Exchange Server, and then bring it online in an existing environment and rename it to save on setup and configuration
time.
You can script the setup and configuration of Exchange through Powershell, either with scripts or with another product controlling it - something like
System Center Orchastrator.
From the script side of things there are many available on peoples blogs. Check
here.
Edit: and to be clear, there is no need to re-run any prep tasks against Active Directory when installing a new Exchange Server, unless you are installing into a new domain as part of your Forest.
Oliver
Oliver Moazzezi | Exchange MVP, MCSA:M, MCITP:Exchange 2010,Exchange 2013, BA (Hons) Anim | http://www.exchange2010.com | http://www.cobweb.com | http://twitter.com/OliverMoazzezi

Exchange Server 2013 and Remote Access VPN on a single server running Windows Server 2012?

Just by way of background, I have been installing and administering network servers, e-mail systems, VPN servers, and the like for many years. However, my involvement with Exchange and Windows Server has been mostly on the forensics and data recovery
level, or as a (sophisticated) user. I have never tried to deploy either from scratch before. My deployment experiences have been mostly with Linux in recent years, and with small private or personal "servers" running such cutting edge
software as Windows XP back when it was new. And even NetWare once.
When a client asked me if I could set up a server for his business, running Exchange Server (since they really want Outlook with all of its bells and whistles to work, particularly calendars) and providing VPN access for a shared file store, I figured it
could not be too difficult given that its a small business, with only a few users, and nothing sophisticated in the way of requirements. For reasons that don't bear explaining here, he was not willing to use a vendor hosting Exchange services or cloud
storage. There is no internal network behind the server; it is intended to be a stand-alone server, hanging off a static IP address on the Internet, providing the entirely mobile work-force of about 10 people with Exchange-hosted e-mail for their computers
and phones, a secure file store, and not much else. If Exchange didn't need it, I would not need to install Active Directory, for example. We have no direct need for its services.
So I did the research and it appears, more by implication than outright assertion, that I should be able to run Windows Server 2012 with Exchange Server 2013 on a server that also hosts Remote Access (VPN only) and does nothing else. And it appears
I ought to be able to do it without virtualizing any of it. However, I have spent the last three or four days fighting one mysterious issue after another. I had Remote Access VPN working and fairly stable very quickly (although it takes a very
long time to become available after the server boots), and it has mostly remained reliable throughout although at times while installing Exchange it seems to have dropped out on me. But I've always been able to get it back after scrounging through the
logs to find out what is bothering it. I have occasionally, for a few minutes at a time, had Exchange Server willing to do everything it should do (although not always everything at the same time). At one point I even received a number of e-mails
on my BlackBerry that had been sent to my test account on the Exchange Server, and was able to send an e-mail from my BlackBerry to an outside account.
But then Exchange Server just stopped. There are messages stuck in the queues, among other issues, but the Exchange Administration Center refuses now to display anything (after I enter my Administrator password, I just get a blank screen, whether on
the server or remotely).
So, I am trying to avoid bothering all of you any more than I have to, but let me just begin with the basic question posed in the title: Can I run Exchange Server (and therefore Active Directory and all of its components) and Remote Access (VPN only) on
a single Windows Server 2012 server? And if so, do I have to run virtual machines (which will require adding more memory to the server, since I did not plan for it when I purchased it)? If it can be done, can anyone provide any pointers on what
the pitfalls are that may be causing my problems? I am happy to provide whatever additional information anyone might like to help figure it out.
Thanks!

An old thread but I ran into this issue and thought I share my solution since I ran into the same issue. Configuring VPN removes the HTTPS 443 binding on the Default Site in IIS for some strange reason; just go and editing the bindings, add HTTPS and things
should be back to normal.

Error when try to install exchange Server 2013 in windows server 2008 R2 Sp1

Hi
I'm getting these errors while trying to install Microsoft Exchange Server 2013 on my Windows Server 2008 R2 SP1 the user i'm using is the Administrator and it is already a member of "Enterprise
Admins" and "Schema Admins"
in my organization there is 6 Exchange server 2013 in 3 site windows server 2012 in this case
I have to install exchange 2013 in windows Server 2008 r2 sp1
the functional level 2008 R2 I getting these errors please help.
Errors:
This computer doesn't belong to a valid Active Directory site. Check the site and subnet definitions.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.InvalidADSite.aspx
Error:
A reboot from a previous installation is pending. Please restart the system and then rerun Setup.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.RebootPending.aspx
Error:
There is a pending reboot from a previous installation of a Windows Server role or feature. Please restart the computer and then run Setup again.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.PendingRebootWindowsComponents.aspx
Error:
You must be a member of the 'Organization Management' role group or a member of the 'Enterprise Admins' group to continue.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.GlobalServerInstall.aspx
Error:
You must use an account that's a member of the Organization Management role group to install or upgrade the first Mailbox server role in the topology.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.DelegatedBridgeheadFirstInstall.aspx
Error:
You must use an account that's a member of the Organization Management role group to install the first Client Access server role in the topology.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.DelegatedCafeFirstInstall.aspx
Error:
You must use an account that's a member of the Organization Management role group to install the first Client Access server role in the topology.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.DelegatedFrontendTransportFirstInstall.aspx
Error:
You must use an account that's a member of the Organization Management role group to install or upgrade the first Mailbox server role in the topology.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.DelegatedMailboxFirstInstall.aspx
Error:
You must use an account that's a member of the Organization Management role group to install or upgrade the first Client Access server role in the topology.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.DelegatedClientAccessFirstInstall.aspx
Error:
You must use an account that's a member of the Organization Management role group to install the first Mailbox server role in the topology.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.DelegatedUnifiedMessagingFirstInstall.aspx
Error:
Setup encountered a problem while validating the state of Active Directory: Could not find information about the local site. This can be caused by incorrect configuration of subnets or sites or by replication latency. See the Exchange setup log for more
information on this error.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.AdInitErrorRule.aspx
Error:
Either Active Directory doesn't exist, or it can't be contacted.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.CannotAccessAD.aspx

I think it's from subnet in site and services
have 3 site A,B,C and new site is "D"I have problem in "D" site
A subnet is 10.33.50.0/24 AD 2012 ,exchange 2013
B subnet is 10.35.50.0/24 AD 2012 ,exchange 2013
C subnet is 10.36.50.0/24 AD 2012 ,exchange 2013
D subnet is 10.100.100.0/25 AD 2008 ,exchange 2013 error when install it
find event error
The description for Event ID 6 from source MSExchange CmdletLogs cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair
the component on the local computer.
If the event originated on another computer, the display information had to be saved with the event.
The following information was included with the event:
test-SetupPrerequisites
{Roles={LanguagePacks, Bridgehead, ClientAccess, UnifiedMessaging, Mailbox, FrontendTransport, Cafe}, LanguagesAvailableToInstall=True, DomainController=, CustomerFeedbackEnabled=True, ExchangeVersion=15.0.847.32, LanguagePackDir=D:\Exchange
Server Software, SufficientLanguagePackDiskSpace=True, ADInitError=Setup encountered a problem while validating the state of Active Directory: Could not find information about the local site. This can be caused by incorrect configuration of subnets or sites
or by rep, ScanType=PrecheckInstall, LanguagePackVersioning=True, HostingDeploymentEnabled=False, TargetDir=C:\Program Files\Microsoft\Exchange Server\V15, SetupRoles={LanguagePacks, AdminTools, Bridgehead, ClientAccess, UnifiedMessaging, Mailbox, FrontendTransport,
Cafe}}

Microsoft Exchange Server 2013 Cumulative Update 7 Setup - Active Directory Topology service on server 'TopologyClientTcpEndpoint (localhost)' returned an error - Set-SharedConfigDC

What am I trying to do?
I have tried installing Microsoft Exchange Server 2013 Cumulative Update 7 Setup on a fresh install of Windows Server 2012 R2 but it gets stuck when running the setup exe on Step 8 of 14 “Mailbox Transport Service” I have included full
error logs at the bottom of the page but the basics are in order it will throw which loop around are:
[01/20/2015 17:13:20.0084] [2] Beginning processing Set-SharedConfigDC
[01/20/2015 17:13:20.0178] [2] The call to Microsoft Exchange Active Directory Topology service on server 'TopologyClientTcpEndpoint (localhost)' returned an error. Error details No Minimal Required Number of Suitable Directory Servers
Found in Forest mydomain.com Site Default-First-Site and connected Sites..
[01/20/2015 17:13:20.0178] [2] No Minimal Required Number of Suitable Directory Servers Found in Forest mydomain.com Site Default-First-Site and connected Sites.
Exchange is currently running in the envirmonet on 2010 Sp3 I am installing 2013 CU7 fresh so I can migrate the databases over.
What am I running?
2 X DC on domain and forest functional level 2008R2 both writable
1 X fresh install of Windows 2012 R2 which is domain joined
What have I tried?
Checked Ipv6 is enabled on all DC NICS and Existing Exchange Servers
Rebooted every server
Run setup as Administrator
My account is part of the domain Enterprise Admin group
Tried adding "Exchange Server" or "Exchange Enterprise Servers" to the group policy and doing the relevant gpupdate /force and reboot :
Computer Configuration Windows Settings
Security Settings + Local Policies
User Rights Assignment Mange auditing and security log
Turned off firewall on DC and Exchange Server even stopped the service
Turned off all AV on the DC and Exchange Server
Checked I could telnet to global catalog servers on port 3268 which I can
Checked the global catalog records existed in DNS which they all do
Done the obvious ping tests all round which confirms connectivity
Schema has been prepared using appropriate commands before running the setup exe
setup.exe /PrepareSchema /IacceptExchangeServerLicenseTerms
Making sure the following path has full permissions:
EXCHANGE14:\Current\Release\Shared\Datacenter\Setup
Restarted Microsoft Exchange Active Directory Topology service
DcDiag all looks good
What have I noticed that is suspicious?
Microsoft Exchange Transport service will not start even though both of its dependences services have started:
Microsoft Filtering Management Service
Microsoft Exchange Active Directory Topology Service
It will eventually error with
“Windows could not start the Microsoft Exchange Transport Service on local computer
Error 1053: This Service did not respond to the start of control request in a timely fashion”
This error is from the GUI wizard itself:
Error:
The following error was generated when "$error.Clear();
$maxWait = New-TimeSpan -Minutes 8
$timeout = Get-Date;
$timeout = $timeout.Add($maxWait);
$currTime = Get-Date;
$successfullySetConfigDC = $false;
while($currTime -le $timeout)
$setSharedCDCErrors = @();
try
Set-SharedConfigDC -DomainController $RoleDomainController -ErrorVariable setSharedCDCErrors -ErrorAction SilentlyContinue;
$successfullySetConfigDC = ($setSharedCDCErrors.Count -eq 0);
if($successfullySetConfigDC)
break;
Write-ExchangeSetupLog -Info ("An error ocurred while setting shared config DC. Error: " + $setSharedCDCErrors[0]);
catch
Write-ExchangeSetupLog -Info ("An exception ocurred while setting shared config DC. Exception: " + $_.Exception.Message);
Write-ExchangeSetupLog -Info ("Waiting 30 seconds before attempting again.");
Start-Sleep -Seconds 30;
$currTime = Get-Date;
if( -not $successfullySetConfigDC)
Write-ExchangeSetupLog -Error "Unable to set shared config DC.";
" was run: "System.Exception: Unable to set shared config DC.
at Microsoft.Exchange.Configuration.Tasks.Task.WriteError(Exception exception, ErrorCategory category, Object target, Boolean reThrow, String helpUrl)
at Microsoft.Exchange.Configuration.Tasks.Task.WriteError(Exception exception, ErrorCategory category, Object target)
at Microsoft.Exchange.Management.Deployment.WriteExchangeSetupLog.InternalProcessRecord()
at Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__b()
at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePipelineIfFailed)".
Exchange logs which have been written:
**The error will loop around for 8 minutes on trying to set-sharedconfig DC whatever this is trying to do ??
[01/20/2015 17:13:20.0084] [2] Active Directory session settings for 'Set-SharedConfigDC' are: View Entire Forest: 'True', Configuration Domain Controller:mydomain.com', Preferred Global Catalog: 'mydomain.com', Preferred Domain Controllers:
'{ mydomain.com}'
[01/20/2015 17:13:20.0084] [2] User specified parameters:
-DomainController:mydomain.com' -ErrorVariable:'setSharedCDCErrors' -ErrorAction:'SilentlyContinue'
[01/20/2015 17:13:20.0084] [2] Beginning processing Set-SharedConfigDC
[01/20/2015 17:13:20.0178] [2] The call to Microsoft Exchange Active Directory Topology service on server 'TopologyClientTcpEndpoint (localhost)' returned an error. Error details No Minimal Required Number of Suitable Directory Servers
Found in Forest mydomain.com Site Default-First-Site and connected Sites..
[01/20/2015 17:13:20.0178] [2] No Minimal Required Number of Suitable Directory Servers Found in Forest mydomain.com Site Default-First-Site and connected Sites.
[01/20/2015 17:13:20.0178] [2] The call to Microsoft Exchange Active Directory Topology service on server 'TopologyClientTcpEndpoint (localhost)' returned an error. Error details No Minimal Required Number of Suitable Directory Servers
Found in Forest mydomain.com Site Default-First-Site and connected Sites..
[01/20/2015 17:13:20.0178] [2] No Minimal Required Number of Suitable Directory Servers Found in Forest mydomain.com Site Default-First-Site and connected Sites.
[01/20/2015 17:13:20.0178] [2] Ending processing Set-SharedConfigDC
[01/20/2015 17:13:20.0193] [2] Beginning processing Write-ExchangeSetupLog
[01/20/2015 17:13:20.0193] [2] An error ocurred while setting shared config DC. Error: The call to Microsoft Exchange Active Directory Topology service on server 'TopologyClientTcpEndpoint (localhost)' returned an error. Error details
No Minimal Required Number of Suitable Directory Servers Found in Forest mydomain.com Site Default-First-Site and connected Sites..
[01/20/2015 17:13:20.0193] [2] Ending processing Write-ExchangeSetupLog
[01/20/2015 17:13:20.0193] [2] Beginning processing Write-ExchangeSetupLog
[01/20/2015 17:13:20.0193] [2] Waiting 30 seconds before attempting again.
[01/20/2015 17:13:20.0193] [2] Ending processing Write-ExchangeSetupLog
[01/20/2015 17:13:50.0195] [2] Beginning processing Write-ExchangeSetupLog
[01/20/2015 17:13:50.0273] [2] [ERROR] Unable to set shared config DC.
[01/20/2015 17:13:50.0273] [2] [ERROR] Unable to set shared config DC.
[01/20/2015 17:13:50.0288] [2] Ending processing Write-ExchangeSetupLog
[01/20/2015 17:13:50.0288] [1] The following 1 error(s) occurred during task execution:
[01/20/2015 17:13:50.0288] [1] 0. ErrorRecord: Unable to set shared config DC.
[01/20/2015 17:13:50.0288] [1] 0. ErrorRecord: System.Exception: Unable to set shared config DC.
   at Microsoft.Exchange.Configuration.Tasks.Task.WriteError(Exception exception, ErrorCategory category, Object target, Boolean reThrow, String helpUrl)
   at Microsoft.Exchange.Configuration.Tasks.Task.WriteError(Exception exception, ErrorCategory category, Object target)
   at Microsoft.Exchange.Management.Deployment.WriteExchangeSetupLog.InternalProcessRecord()
   at Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__b()
   at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePipelineIfFailed)
[01/20/2015 17:13:50.0288] [1] [ERROR] The following error was generated when "$error.Clear();
$maxWait = New-TimeSpan -Minutes 8
$timeout = Get-Date;
$timeout = $timeout.Add($maxWait);
$currTime = Get-Date;
$successfullySetConfigDC = $false;
while($currTime -le $timeout)
$setSharedCDCErrors = @();
try
Set-SharedConfigDC -DomainController $RoleDomainController -ErrorVariable setSharedCDCErrors -ErrorAction SilentlyContinue;
$successfullySetConfigDC = ($setSharedCDCErrors.Count -eq 0);
if($successfullySetConfigDC)
break;
Write-ExchangeSetupLog -Info ("An error ocurred while setting shared config DC. Error: " + $setSharedCDCErrors[0]);
catch
Write-ExchangeSetupLog -Info ("An exception ocurred while setting shared config DC. Exception: " + $_.Exception.Message);
Write-ExchangeSetupLog -Info ("Waiting 30 seconds before attempting again.");
Start-Sleep -Seconds 30;
$currTime = Get-Date;
if( -not $successfullySetConfigDC)
Write-ExchangeSetupLog -Error "Unable to set shared config DC.";
        " was run: "System.Exception: Unable to set shared config DC.
   at Microsoft.Exchange.Configuration.Tasks.Task.WriteError(Exception exception, ErrorCategory category, Object target, Boolean reThrow, String helpUrl)
   at Microsoft.Exchange.Configuration.Tasks.Task.WriteError(Exception exception, ErrorCategory category, Object target)
   at Microsoft.Exchange.Management.Deployment.WriteExchangeSetupLog.InternalProcessRecord()
   at Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__b()
   at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePipelineIfFailed)".
[01/20/2015 17:13:50.0288] [1] [ERROR] Unable to set shared config DC.
[01/20/2015 17:13:50.0288] [1] [ERROR-REFERENCE] Id=AllADRolesCommonServiceControl___ee47ab1c06fb47919398e2e95ed99c6c Component=EXCHANGE14:\Current\Release\Shared\Datacenter\Setup
[01/20/2015 17:13:50.0288] [1] Setup is stopping now because of one or more critical errors.
[01/20/2015 17:13:50.0288] [1] Finished executing component tasks.
[01/20/2015 17:13:50.0304] [1] Ending processing Install-BridgeheadRole
Windows Event Viewer:
Process Microsoft.Exchange.Directory.TopologyService.exe (PID=5276) Forest mydomain.com. Exchange Active Directory Provider couldn't find minimal required number of suitable Global Catalog servers
in either the local site 'Default-First-Site' or the following sites:

Hi apl228,
1. Please make sure the IPv6 is enabled.
2. Please make sure the account that install Exchange server has Administrator permission.
3. Please make sure DNS has been configured correctly.
Thanks
Mavis Huang
TechNet Community Support

How can i get newly added contacts for a Mailbox User in Exchange Server 2013

Hi all,
I need to synchronize contacts in Exchange Server and Sugar CRM Application, for that
i need to get newly added contacts for a User in Exchange Server 2013 by using EWS Managed API.
I know how get the list of all contacts for a particular user , but in the list how i can find
new contacts ?

Hi Dora,
that's the fun thing:
You add your own property (and it'll be invisible to outlook users, not to worry).
Extended Properties allow you to define custom property on Exchange Items. And it has a
method for setting those too.
Here's a short post doing a very simple intro on using Extended Properties.
Glen's Exchange Blog is a generally useful resource when working with EWS, I'm confident you'll be able to find lots of tips there as well.
Cheers,
Fred
There's no place like 127.0.0.1

Exchange Server 2013 failover design

Similar Messages

Maybe you are looking for