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

Similar Messages

Issues trying to recover failed Exchange Server 2013 in a DAG

Having several issues attempting to recover a failed Exchange Server 2013. To start out, the failed server was mounted on a virtual server using hyper-v. The virtual server failed due to some hard drive partition issues and would no longer boot. As there
really was no purpose to having Exchange on a Virtual Server I decided to rename the host to the same name as the virtual server. I reset the name in AD and proceeded to rename the server. Then made sure all the necessary things were installed and proceeded
to do a recovery installation. I neglected to properly delete the old databases belonging to that server. I simply deleted the files off the hard drive instead of doing it properly. I should mention this is a two node plus witness server installation.Now,
it seems I cannot delete the former server in either ECP or command line. I have attempted to clean up the mess with the old databases but there is one that was mounted only on the failed server that I cannot remove. It seems until I can remove that, I cannot
remove the failed server from the DAG and do a recovery install. The steps shown in the tech net articles to remove a failed database have also failed. At this point I am wondering if I should just give up on the server name and do an install on a new server
name or if someone can give me some information on how to clean up the mess, that would be better I am sure. Here is a list of the things I have tried.
https://technet.microsoft.com/en-us/library/dd876880(v=exchg.150).aspx and in this article, the item mentioned is not in ADSIedit.
http://exchangeserverpro.com/unable-remove-failed-server-dag-exchange-server-2010/
http://exchangeserverpro.com/exchange-2013-how-to-remove-dag-member/ This
article describes one of the problems I am having but the solution is not there.
Thanks to any and all who can offer advice.
Ronald C. Pope

Thank you for your answer. Running that command results in the following:
[PS] C:\Windows\system32>Remove-MailboxDatabase "Mailbox Database 0939719168"
This mailbox database contains one or more mailboxes, mailbox plans, archive mailboxes, public folder mailboxes or
arbitration mailboxes. To get a list of all mailboxes in this database, run the command Get-Mailbox -Database"Mailbox Database 0939719168". To get a list of all mailbox plans in this database, run the command Get-MailboxPlan. To get a list of
archive mailboxes in this database, run the command Get-Mailbox -Database "Mailbox Database 0939719168" -Archive. To get a list of all
public folder mailboxes in this database, run the command Get-Mailbox -Database "Mailbox Database 0939719168" -PublicFolder. To get a
list of all arbitration mailboxes in this database, run the command Get-Mailbox -Database "Mailbox Database 0939719168" -Arbitration.
To disable a non-arbitration mailbox so that you can delete the mailbox database, run the command Disable-Mailbox
<Mailbox ID>. To disable an archive mailbox so you can delete the mailbox database, run the command Disable-Mailbox
<Mailbox ID> -Archive. To disable a public folder mailbox so that you can delete the mailbox database, run the command
Disable-Mailbox <Mailbox ID> -PublicFolder. Arbitration mailboxes should be moved to another server; to do this, run
the command New-MoveRequest <parameters>. If this is the last server in the organization, run the command
Disable-Mailbox <Mailbox ID> -Arbitration -DisableLastArbitrationMailboxAllowed to disable the arbitration mailbox.
Mailbox plans should be moved to another server; to do this, run the command Set-MailboxPlan <MailboxPlan ID>
-Database "Mailbox Database 0939719168".
    + CategoryInfo          : InvalidOperation: (Mailbox Database 0939719168:DatabaseIdParameter) [Remove-MailboxDatab
   ase], AssociatedUserMailboxExistException
    + FullyQualifiedErrorId : [Server=EX01,RequestId=69b60793-fc4f-4dac-beb9-8c9afe381a36,TimeStamp=1/26/2015 6:28:34
   PM] 2BA41E0C,Microsoft.Exchange.Management.SystemConfigurationTasks.RemoveMailboxDatabase
    + PSComputerName        : ex01.<domain>com
I was able to disable the one mailbox that was listed for the database. I got the following error when attempting the command Get-Mailbox -Database"Mailbox Database 0939719168"
[PS] C:\Windows\system32>Get-MailboxPlan Database "Mailbox Database 0939719168"
Get-MailboxPlan : The term 'Get-MailboxPlan' is not recognized as the name of a cmdlet, function, script file, or
operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try
again.
At line:1 char:1
+ Get-MailboxPlan Database "Mailbox Database 0939719168"
+ ~~~~~~~~~~~~~~~
    + CategoryInfo          : ObjectNotFound: (Get-MailboxPlan:String) [], CommandNotFoundException
    + FullyQualifiedErrorId : CommandNotFoundException
the public folder and archive switch simply return a command prompt leading me to believe that there are no public or archive boxes on that database.
Ron

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

Exchange Server 2013 - DAG Failure

Exchange server 2013 with two Mailbox server role and One CAS server role with DAG Enabled on it.
Exchange server went live with 150 Mailbox on both the server distributed evenly.
Both mailbox server lost connectivity and unable to communicate with CAS server.
Outlook and OWA user unable to connected to their mailboxes.
Both the Mailbox server went down disrupting the mailflow.
Later found that Cluster Node wasnt responding in timely fashion. Had to remove the Mailboxes from the DAG and later remove the DAG configuration.
Disable Replication network on each of the mailbox server and rebooted it.
Re gain network connectivity to the Mailboxes and they are back on online.
What could be the issue.
Both mailbox server are rich in resources which can be ruled here

Hello,
According to your description, your network configure may be issue.
We recommend you assign static IP address for cluster server to check the result.
Cara Chen
TechNet Community Support

Writing client app to connect to Exchange Server 2013 and set OOF for users on vacation

I am coding an C# app that should connect to Exchange Server 2013 on-premise (Servers Location is not in our Company). I`ve got an account (User and Pass) with readonly admin-rights for now and want to read and set OutOfOffice Objects for other users. I
decide to use EWS Managed API over Autodiscovery but I am bit confuse how
I tried to connect with "service.UseDefaultCredentials = true" and read contacts -> this code works:
try
            ExchangeService _service
= new ExchangeService(ExchangeVersion.Exchange2013_SP1);
            _service.Credentials
= new WebCredentials("service.exchange",
"1234", "domain");
            _service.TraceEnabled
= true;
            _service.TraceFlags
= TraceFlags.All; _service.UseDefaultCredentials
= true;
            _service.AutodiscoverUrl("[email protected]",
RedirectionUrlValidationCallback);
            foreach
(Contact contact in _service.FindItems(WellKnownFolderName.Contacts,
new ItemView(2)))
var test = contact;
        catch
(Exception exception)
            Console.WriteLine(exception);
After that I tried the same with _service.UseDefaultCredentials = false; got error -> "The Autodiscover service couldn't be located." I am not shure if this "direct log on" is the right way, On msdn I've read about "delegate access"
and "Impersonation" (NTLM and Basic Authentication) I'am a bit confused. Can anybody help me?

hi,
when you set a credential, you don't have to set the UseDefaultCredentials property (it is already updated).
For autodiscover, you should try to set the property EnableScpLookup to True if you are in the Exchange domain or it is known by the current domain.
Autodiscover uses a domain query (through Active Directory) and/or a dns query (this requires a DNS register for autodiscover.domain.net) to determine the access to the autodiscover service URI.
Regards,
Désiré GOVIN Refresh IT Solutions

Issues with setting up Exchange Server 2013

Hi All
Not sure what im doing wrong yet i am having issues with exchange server 2013.
Currently I have got general SMTP Mail flow working. as long as i log onto the local servers OWA (https://10.x.x.x/owa) i can log into a users mailbox. i have tested sending and recieving mail using this and it works.
My main issue now is with accessing the OWA externally via our website. (owa.xx.xx.au/owa) or connecting ANY Outlook to the server.
When i connect to the exchange server via outlook it asks for the password again multiple times never authenticating it then time's out and says:
" the action cannot be completed. the connection to microsoft exchange is unavailable, outlook must be online or
connected to complete this action "
then when i click on OK it goes to the General Tab and under microsoft exchange server: the name for it appears as
[email protected]
with mailbox set as:
=SMTP:[email protected]
Currantly on our DNS i have
mx= 10 mail.xx.xx.au
CNAME= autodiscover = mail.xx.xx.au
CNAME= OWA = mail.xx.xx.au
A = mail = 12.34.56.78
On our modem/router i have set one-to-one nat to our firewall IP
On our firewall i have
SMTP SAT and NAT to Exchange server
HTTPS Sat and NAT to exchange Server
HTTP Sat and Nat to exchange Server
Port 587 SAT and Nat to exchange server
pop SAT and NAt to exchange server
Im willing to bet its something stupid i have overlooked but i was wondering if anyone would be able to help me out
Regards
Sibsy

Hello,
Firstly, please follow the Shadab's suggestion to check related virtual directory settings.
Please make sure you use certificate that's created by a CA that's trusted by the client computer's operating system.
Please use get-outlookanywhere | fl cmdlet to check ExternalClientAuthenticationMethod. By default, the authentication is Negotiate.
Cara Chen
TechNet Community Support

Exchange Server 2013 - Sizing

Can some please provide me Exchange server 2013 sizing for 180 Mailbox users with mailbox profile size 10 GB With 1 DAG with two mailbox servers.
Please provide for Exchange Server in Virtual environment.
I have already created a setup on Environment going through test mode.
Existing Environment
2 X CAS servers - 2 Core - 4 GB Memory - 500 GB Hard disk space
2 X Mailbox Server - 2 Core - 12 GB Memory - 1.5 TB disk space
Theses servers are build on VMWare hosted on ESX server
Please provide your feedback for best practice and solution to support 180 Mailbox profile with Mailbox size limit 10 GB
Thanks in adavance
Benhur
benhur007

Hi Benhur,
we have over one thousand mailboxes ( inc. room,shared,calendar and so on).We only have 2 servers With Mailbox and CAS role.No need to seperate those roles if you really dont have to.2013 CAs only Proxy/redirect requests and nothing is stored (other that
daily performance log and iis log).C: drive for Exchange install i recomend 70gb on each server.
When it comes to mailbox database,are you planning to use Public folders?In 2013 Public folders can be stored on seperate databases.
Also it is not recomended to have Exchange and mailbox database on same physical disk,so you should seperate those out and expand over time without taking Down the server.
In easy sample the server can look like this:
C: Install Exchange 70GB
D: Database files 1GB ( here you map multiple databases in different folders,so it look like D:\DB01,D:\DB02,D:\DB03 and so on.And each folder is an own 300 gb disk that you Mount into one of these folders at time.Path and name have to be identical on both
servers when setting up DAG.)
E: Log files 1GB ( here you map multiple databases in different folders,so it look like E:\LOG01,E:\LOG02,E:\LOG03 and so on.And each folder is its own 70 gb disk that you Mount into one of these folders at time.Path and name have to be identical on
both servers when setting up DAG.)
Approx 300GB each database and 70 gb each log(for each database) should be fine.
10gb database pr user can cause performance issue if they are working online (Citrix or other apps),if cache locally it might take time if they are not inside worknetwork.
Dont forget that you should also have your own replication network or it will consume bandwidth when you move over multiple users to different databases.
Hope this helps!
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. Thank you! Off2work

SOFS support for Exchange Server 2013

Hi all,
I am aware of the following factors:
1. Exchange only supports block-level storage
2. Using SoFS as DAG FSW is not supported.
But may I confirm whether Microsoft supports the scenario below?
==============================================
My client has one set of Windows 2012 R2 Scale-Out File Servers to support their hyper-V farm. Storage is Dell MD3000 with Windows 2012 R2 Storage Space. Is it supported by Microsoft to run Exchange Server 2013 and Exchange Server 2010 in the virtual machines
which are running on SoFS? Assume IOPS has been properly sized.
==============================================
Regards,
William
William Yang

Hi,
There is no official documents talked about whether the Windows server 2012
Scale-Out File Server is supported for Exchange 2013 and Exchange 2010.
Generally, the supported storage configuration in Exchange 2013 is listed in the article below:
https://technet.microsoft.com/en-us/library/ee832792(v=exchg.150).aspx
Hope it helps.
Regards,
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]
Winnie Liang
TechNet Community Support

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

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.

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 setup / coexistance Exchange 2010

So started setting up Exchange 2013 and ran into a random issue regarding the OAB. Resolved by deleting/recreating the OAB in Exchange 2010.
My issue now is setup will not complete, just tells me an "Incomplete Installation Detected" starts to resume the installation. Upon "next" I receive just a hanging screen of "Setup Progress" which goes no where.
[06/12/2014 20:05:19.0860] [0] **********************************************
[06/12/2014 20:05:19.0876] [0] Starting Microsoft Exchange Server 2013 Setup
[06/12/2014 20:05:19.0876] [0] **********************************************
[06/12/2014 20:05:19.0876] [0] Local time zone: (UTC-05:00) Eastern Time (US & Canada).
[06/12/2014 20:05:19.0876] [0] Operating system version: Microsoft Windows NT 6.2.9200.0.
[06/12/2014 20:05:19.0876] [0] Setup version: 15.0.516.32.
[06/12/2014 20:05:19.0876] [0] Logged on user: DOMAIN\Admin.
[06/12/2014 20:05:19.0954] [0] Command Line Parameter Name='sourcedir', Value='F:\'.
[06/12/2014 20:05:19.0954] [0] Command Line Parameter Name='mode', Value='Install'.
[06/12/2014 20:05:19.0969] [0] RuntimeAssembly was started with the following command: '/sourcedir:F: /mode:Install'.
[06/12/2014 20:05:20.0344] [0] The following roles are installed: BridgeheadRole ClientAccessRole MailboxRole UnifiedMessagingRole AdminToolsRole
[06/12/2014 20:05:21.0391] [0] Setup is choosing the domain controller to use
[06/12/2014 20:05:21.0595] [0] The MSExchangeADTopology has a persisted domain controller: DOMAIN CONTROLLER
[06/12/2014 20:05:22.0485] [0] PrepareAD has been run, and has replicated to this domain controller; so setup will use DOMAIN CONTROLLER
[06/12/2014 20:05:22.0485] [0] Setup is choosing a global catalog...
[06/12/2014 20:05:22.0516] [0] Setup has chosen the global catalog server DOMAIN CONTROLLER.
[06/12/2014 20:05:22.0516] [0] Setup will use the domain controller 'DOMAIN CONTROLLER'.
[06/12/2014 20:05:22.0516] [0] Setup will use the global catalog 'DOMAIN CONTROLLER'.
[06/12/2014 20:05:22.0516] [0] Exchange configuration container for the organization is 'CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=DOMAIN,DC=LOCAL'.
[06/12/2014 20:05:22.0532] [0] Exchange organization container for the organization is 'CN=DOMAIN,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=DOMAIN,DC=LOCAL'.
[06/12/2014 20:05:22.0579] [0] Setup will search for an Exchange Server object for the local machine with name 'LOCALHOST'.
[06/12/2014 20:05:22.0751] [0] Exchange Server object found : 'CN=LOCALHOST,CN=Servers,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=DOMAIN,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=DOMAIN,DC=LOCAL'.
[06/12/2014 20:05:22.0751] [0] The following roles have been unpacked: BridgeheadRole ClientAccessRole MailboxRole UnifiedMessagingRole FrontendTransportRole AdminToolsRole CafeRole
[06/12/2014 20:05:22.0751] [0] The following datacenter roles are unpacked:
[06/12/2014 20:05:22.0751] [0] The following roles are installed: BridgeheadRole ClientAccessRole MailboxRole UnifiedMessagingRole AdminToolsRole
[06/12/2014 20:05:22.0766] [0] The local server has some Exchange files installed.
[06/12/2014 20:05:22.0798] [0] Server Name=LOCALHOST
[06/12/2014 20:05:22.0829] [0] Setup will use the path 'F:\' for installing Exchange.
[06/12/2014 20:05:22.0829] [0] Setup will discover the installed roles from server object 'CN=LOCALHOST,CN=Servers,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=DOMAIN,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=DOMAIN,DC=LOCAL'.
[06/12/2014 20:05:22.0829] [0] 'BridgeheadRole' is installed on the server object.
[06/12/2014 20:05:22.0829] [0] 'ClientAccessRole' is installed on the server object.
[06/12/2014 20:05:22.0829] [0] 'MailboxRole' is installed on the server object.
[06/12/2014 20:05:22.0829] [0] 'UnifiedMessagingRole' is installed on the server object.
[06/12/2014 20:05:22.0845] [0] The installation mode is set to: 'Install'.
[06/12/2014 20:05:44.0768] [0] An Exchange organization with name 'DOMAIN' was found in this forest.
[06/12/2014 20:05:44.0768] [0] Active Directory Initialization status : 'True'.
[06/12/2014 20:05:44.0768] [0] Schema Update Required Status : 'False'.
[06/12/2014 20:05:44.0768] [0] Organization Configuration Update Required Status : 'False'.
[06/12/2014 20:05:44.0768] [0] Domain Configuration Update Required Status : 'False'.
[06/12/2014 20:05:44.0768] [0] The locally installed version is 15.0.516.32.
[06/12/2014 20:05:44.0768] [0] Exchange Installation Directory : 'C:\Program Files\Microsoft\Exchange Server\V15'.
[06/12/2014 20:05:44.0830] [0] Applying default role selection state
[06/12/2014 20:05:44.0877] [0] Setup is determining what organization-level operations to perform.
[06/12/2014 20:05:44.0877] [0] Because the value was specified, setup is setting the argument OrganizationName to the value DOMAIN-NAME.
[06/12/2014 20:05:44.0877] [0] Setup will run from path 'C:\Program Files\Microsoft\Exchange Server\V15\'.
[06/12/2014 20:05:44.0893] [0] InstallModeDataHandler has 0 DataHandlers
[06/12/2014 20:05:44.0893] [0] RootDataHandler has 1 DataHandlers
[06/12/2014 20:05:45.0737] [0] Finished loading screen IncompleteInstallationDetectedPage.
[06/12/2014 20:05:48.0518] [0] Setup is determining what organization-level operations to perform.
[06/12/2014 20:05:48.0518] [0] Because the value was specified, setup is setting the argument OrganizationName to the value DOMAIN-NAME.
[06/12/2014 20:05:48.0518] [0] Setup will run from path 'C:\Program Files\Microsoft\Exchange Server\V15\'.
[06/12/2014 20:05:48.0518] [0] InstallModeDataHandler has 0 DataHandlers
[06/12/2014 20:05:48.0518] [0] RootDataHandler has 1 DataHandlers
[06/12/2014 20:05:48.0737] [0] Finished loading screen SetupProgressPage.

Hi,
Let's try the following resolutions:
1. Check if the discovery SearchMailbox is present on Exchange 2010 when you run the Exchange 2013 Install.
2. Reinstall your Exchange 2013 server:
Open ADSIEDIT, CN=Configuration, DC=your domain ->CN=Services ->CN=Microsoft Exchange ->CN=First Organization ->CN=Administrative Groups ->Cn=Exchange Administrative Group ->CN=Servers ->CN=Server name
After remove the exchange server, please reinstall your exchange server to test the result.
Thanks,
Angela Shi
TechNet Community Support

Exchange Server 2013 Update from to CU3 to CU8 stuck, Exchange completely down

Hello,
We tried to update a Exchange 2013 server to CU8 because we needed support from Microsoft (certificate revoked, so OWA not working anymore) and they could only help us after updating to CU8 first. The problem is that the update got stuck and now Exchange
is not working at all anymore. Since it is a production enviroment and there is mail in all outboxes we do not want to turn back to a snapshot but solve the problem and continue the update. Any help is welcome because all mail is down now :-(
The error we received at the Exchange Server is:
C:\Users\administrator.DOMAINNAME\Downloads\Exchange-cu8>setup.exe /m:upgrade /In
stallWindowsComponents /IAcceptExchangeServerLicenseTerms
Welcome to Microsoft Exchange Server 2013 Cumulative Update 8 Unattended Setup
Copying Files...
File copy complete. Setup will now collect additional information needed for
installation.
Languages
Mailbox role: Transport service
Client Access role: Front End Transport service
Mailbox role: Client Access service
Mailbox role: Unified Messaging service
Mailbox role: Mailbox service
Management tools
Client Access role: Client Access Front End service
Performing Microsoft Exchange Server Prerequisite Check
Configuring Prerequisites COMPLETED
Prerequisite Analysis COMPLETED
Configuring Microsoft Exchange Server
Preparing Setup
COMPLETED
Stopping Services COMPLETED
Language Files COMPLETED
Removing Exchange Files COMPLETED
Preparing Files
COMPLETED
Copying Exchange Files COMPLETED
Language Files COMPLETED
Restoring Services COMPLETED
Language Configuration COMPLETED
Mailbox role: Transport service FAILED
The following error was generated when "$error.Clear();
$connectors = Get-ReceiveConnector -Server $RoleFqdnOrName;
foreach($connector in $connectors) { if($connector.MaxLocalHopCount -g
t 1) { Set-ReceiveConnector -Identity $connector.Identity -MaxLocalHopCount 5 }
" was run: "Microsoft.Exchange.Management.SystemConfigurationTasks.Recei
veConnectorRoleConflictException: The values that you specified for the Bindings
and RemoteIPRanges parameters conflict with the settings on Receive connector "
SERVER-EXCHANGE\Externe POP3 mailboxen". Receive connectors assigned to differen
t Transport roles on a single server must listen on unique local IP address & po
rt bindings.
bij Microsoft.Exchange.Configuration.Tasks.Task.ThrowError(Exception exceptio
n, ErrorCategory errorCategory, Object target, String helpUrl)
bij Microsoft.Exchange.Configuration.Tasks.Task.WriteError(Exception exceptio
n, ErrorCategory category, Object target)
bij Microsoft.Exchange.Management.SystemConfigurationTasks.SetReceiveConnecto
r.InternalValidate()
bij Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__b()
bij Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String fu
ncName, Action func, Boolean terminatePipelineIfFailed)".
The following error was generated when "$error.Clear();
$connectors = Get-ReceiveConnector -Server $RoleFqdnOrName;
foreach($connector in $connectors) { if($connector.MaxLocalHopCount -g
t 1) { Set-ReceiveConnector -Identity $connector.Identity -MaxLocalHopCount 5 }
" was run: "Microsoft.Exchange.Management.SystemConfigurationTasks.Recei
veConnectorRoleConflictException: The values that you specified for the Bindings
and RemoteIPRanges parameters conflict with the settings on Receive connector "
SERVER-EXCHANGE\Default Frontend SERVER-EXCHANGE". Receive connectors assigned t
o different Transport roles on a single server must listen on unique local IP ad
dress & port bindings.
bij Microsoft.Exchange.Configuration.Tasks.Task.ThrowError(Exception exceptio
n, ErrorCategory errorCategory, Object target, String helpUrl)
bij Microsoft.Exchange.Configuration.Tasks.Task.WriteError(Exception exceptio
n, ErrorCategory category, Object target)
bij Microsoft.Exchange.Management.SystemConfigurationTasks.SetReceiveConnecto
r.InternalValidate()
bij Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__b()
bij Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String fu
ncName, Action func, Boolean terminatePipelineIfFailed)".
The Exchange Server setup operation didn't complete. More details can be found
in ExchangeSetup.log located in the <SystemDrive>:\ExchangeSetupLogs folder.

Hello Gadget,
Please find the solution as follows
This error is concern about WMSVC certificate which was deleted, we could refer to the following steps:
1- Go to IIS Manager and select server certificate,
2- Select “Create Self-Signed Certificate”,
3- For Server 2012 in the Friendly Name Field type: WMSVC and select the personal (certificate Store),
4- Now go to ” Management Service”,
5- From SSL Certificate choose the newly create “WMSVC” Self-Signed Certificate,
6- Apply,
7- Now start service of “Web Management service”.
https://social.technet.microsoft.com/Forums/office/en-US/eac00dc2-6e43-45ae-939c-aad82a144908/cu8-install-fails?forum=exchangesvrgeneral
Exchange Queries

Exchange Server 2013 - Lab setup with internal emails only

Hi,
I'm new to Exchange Server 2013. I've started a POC on the product by setting up a Lab environment with one 1 AD server and 1 Exchange server (Both Windows 2012 R2). As this is a POC I just need the internal email communication. I don't want the mails to
go over the internet.
I've completed the installation part and just started to configure Send/Receive connectors and got stuck with the question whether the connectors are required or not.
Could someone please help me out in configuring internal email setup for Exchange 2013 lab setup.
Regards,
Nithin

Hi,
You need not to configure send/receive connectors for internal email.
The following article for your reference:
http://technet.microsoft.com/en-us//library/aa996395(v=exchg.150).aspx
Default Receive connectors created during setup
Certain Receive connectors are created by default when you install the Mailbox server role.
Default Receive connectors created on a Mailbox server running the Transport service
When you install a Mailbox server running the Transport service, two Receive connectors are created. No additional Receive connectors are needed for typical operation, and in most cases the default Receive connectors don't require a configuration change.
These connectors are the following:
Default <server name>   Accepts connections from Mailbox servers running the Transport service and from Edge servers.
Client Proxy <server name>   Accepts connections from front-end servers. Typically, messages are sent to a front-end server over SMTP.
Each connector is assigned a TransportRole value. You can use it to determine the role the connector is running in. This can be helpful in cases where you are running multiple roles on a single server. In the case of each Receive connector previously
mentioned, their TransportRole value is HubTransport.
To view the default Receive connectors and their parameter values, you can use the
Get-ReceiveConnector cmdlet.
Default Receive connectors created on a Front End Transport server
During installation, three Receive connectors are created on the Front End transport, or Client Access server. The default Front End Receive connector is configured to accept SMTP communications from all IP address ranges. Additionally, there is a Receive
connector that can act as an outbound proxy for messages sent to the front-end server from Mailbox servers. Finally, there is a secure Receive connector configured to accept messages encrypted with Transport Layer Security (TLS). These connectors are the following:
Default FrontEnd <server name>   Accepts connections from SMTP senders over port 25. This is the common messaging entry point into your organization.
Outbound Proxy Frontend <server name>   Accepts messages from a Send Connector on a back-end server, with front-end proxy enabled.
Client Frontend <server name>   Accepts secure connections, with Transport Layer Security (TLS) applied.
In a typical installation, no additional Receive connectors are required.
Niko Cheng
TechNet Community Support

Exchange Server 2013 // MFCMAPI could connect with errors

While connecting with Exchange Server 2013 I have started facing problem with my application.
My application fails to connect to Exchange with below parameters, then i have tried using MFCMAPI to if everything is okay. MFCMAPI could connect with above errors.
And I have tried with program using below parameters, i still get network error from MAPI call. Can you kindly help, I can provide any additional
details needed.
___ props[prop_count].ulPropTag = PR_PROFILE_UNRESOLVED_NAME;
    props[prop_count].Value.lpszA   = <ProfileUnresolvedName>;
    prop_count++;
    props[prop_count].ulPropTag     = PR_PROFILE_UNRESOLVED_SERVER;
    props[prop_count].Value.lpszA   = <[email protected]>;
    prop_count++;
    // Setting this to TRUE causes OpenMsgStore() to fail with MAPI_E_UNCONFIGURED
    props[prop_count].ulPropTag      = PR_CONVERSION_PROHIBITED;
    props[prop_count].Value.b        = FALSE;
    prop_count++;
    props[prop_count].ulPropTag     = PR_PROFILE_CONFIG_FLAGS;
    props[prop_count].Value.l       = CONFIG_SERVICE /*| CONFIG_PROMPT_FOR_CREDENTIALS
| CONFIG_SHOW_CONNECT_UI */;
    prop_count++;
    props[prop_count].ulPropTag     = PR_DISPLAY_NAME;
    props[prop_count].Value.lpszA   = <Mailbox Profile Name>;
    prop_count++;
    //Above setting used to be sufficient to connect using RPC
    //Below parameters added to connect via HTTPS
    LPSTR pwszUser = "domain\\username"; //also tried
[email protected] AND username
    LPWSTR pwszPassword = L"paswword"; // Password has been encrypted using CryptProtectData
    props[prop_count].ulPropTag = PR_PROFILE_RPC_PROXY_SERVER_W;
   props[prop_count].Value.lpszW = L"https://ProxyHostname.domain";
    prop_count++;
    props[prop_count].ulPropTag = PR_PROFILE_RPC_PROXY_SERVER_AUTH_PACKAGE;
    props[prop_count].Value.l = RPC_C_AUTHN_NONE;      // RPC_C_HTTP_AUTHN_SCHEME_NTLM,
RPC_C_HTTP_AUTHN_SCHEME_BASIC
    prop_count++;
    props[prop_count].ulPropTag = PR_PROFILE_RPC_PROXY_SERVER_FLAGS;
    props[prop_count].Value.l = PRXF_ENABLED | PRXF_SSL;// | PRXF_IGNORE_SEC_WARNING; // | PRXF_IGNORE_SEC_WARNING;
    prop_count++;
    props[prop_count].ulPropTag = PR_PROFILE_RPC_PROXY_SERVER_PRINCIPAL_W;
    props[prop_count].Value.lpszW = L"msstd:certificateserverhostname.domain";
    prop_count++;
    props[prop_count].ulPropTag = PR_PROFILE_AUTH_PACKAGE;
    props[prop_count].Value.l = RPC_C_AUTHN_GSS_NEGOTIATE;
// RPC_C_AUTHN_WINNT, RPC_C_AUTHN_GSS_NEGOTIATE, RPC_C_AUTHN_NONE
    prop_count++;
    props[prop_count].ulPropTag = PR_PROFILE_AUTH_USER_W;
    props[prop_count].Value.lpszA = pwszUser;
    prop_count++;
    props[prop_count].ulPropTag = PR_PROFILE_AUTH_PASSWORD;
    props[prop_count].Value.bin.lpb = dataBlobOut.pbData;
    props[prop_count].Value.bin.cb = dataBlobOut.cbData;
    prop_count++;
    DB( (DB_PR _T("ConfigureExchangeService() About to configureMsgService\r\n"),
this ) );
    hres = lpServiceAdmin->ConfigureMsgService( exchUID, 0, config_flags, prop_count, props
    I still get MAPI_E_NETWORK not found
Are there any configuration changes need to be done on Exchange Server?
Is there any mistake in above parameters?
Kindly suggest.

You can refer Dave's blog post @
http://blogs.msdn.com/b/dvespa/archive/2013/05/21/how-to-mfcmapi-create-mapi-profile-exchange-2013.aspx
DeVa, M.S., {MSFT} Please remember to mark the replies as answers if they help

Exchange server 2013 - Setting up DAG

Similar Messages

Maybe you are looking for