Configuration Exchange 2013 DAG on two Server Data center 2012 with Hyper -V roles

Dears,
I try to planning and installation two hosts ( Data center 2012 servers) then install Hyper-V role on both this server, then create VM on each Data center server to be install Exchange 2013 on them.
After that I want to configure DAG between Exchanges servers, so what are the prerequisite to do that ?
Note: I use external IBM storage that will be located all VMs and DAG
Many thanks

Hi Moon,
In addition to Gulab's suggestion, I would like to clarify the following things:
1. Yes, we can use Standard or Datacenter version of the Windows Server 2012 operating system to configure Exchange 2013 DAG.
2. Each member of the DAG should be running the same operating system.
3. The DAG with an even number of members should have a witness server. A witness server is a server outside a DAG that's used to achieve and maintain quorum when the DAG has an even number of members.
What's more, here are some helpful articles for your reference.
Planning for High Availability and Site Resilience
http://technet.microsoft.com/en-us/library/dd638104(v=exchg.150).aspx#HR
High Availability and Site Resilience
http://technet.microsoft.com/en-us/library/dd638137(v=exchg.150).aspx
Hope it helps.
If there are any problems, please feel free to let me know.
Best regards,
Amy
Amy Wang
TechNet Community Support

Similar Messages

Single CAS NameSpace in Multi-Data Center Model With Exchange 2013

Hi
We are in process of transitioning from Exchange 2007 to Exchange 2013. Our Exchange 2007 infrastructure is as follows:
2 Data centers (DC 1 and DC 2). Both with active user population. Both have their own direct Internet Connectivity
Standalone Exchange 2007 mailbox servers in each data center
Load Balanced CAS (HT co-located) servers using Hardware Load Balancers in each data center. Load balancers are configured with VIP and FQDNs (LoadBalancer1.Com and LoadBalancer2.com)
Currently No access allowed from Internet except ActiveSync (No OWA or OA)
Outlook anywhere is disabled in Exchange 2007 organization but once mailboxes will be moved to Exchange 2013, OA will definitely be used – we will provide OA on Intranet as well as Internet
All the internal URLs including Autodiscover point to VIP (Load Balancer IP)
Autodiscover is not currently published on Internet, but we have a plan to publish it now once Exchange 2013 is introduced
We want to keep a single CAS NameSpace BYOD.ABC.Com for our ActiveSync and OA (and not going to allow OWA) access from Internet. We want to have Split-DNS for our new Exchange 2013 infrastructure due to
the simplicity it brings. So we are going to use one name BYOD.ABC.Com from the Internet. We have GSLB that provide Fault Tolerance and Geo-Load Balance to external requests coming from Exchange clients, between two data centers. When we will
install new Exchange 2013 servers, they’ll be part of new VIP so:
In a 2 data center model, can we name our internal VIPs same in both data centers (i:e BYOD.ABC.Com) as we have decided to go with Split-DNS? Do you see any caveats to this strategy
If the above strategy will not work, what are the alternate approach(es).
If we configure same names for the VIPs in both data centers, it will mean that the Autodiscover SCPs for all the Exchange 2013 CAS objects (and Exchange 2007 CAS objects during co-existence) will point to BYOD.ABC.Com. This should not be a problem for
AD joined systems as they’ll find and contact Autodiscover endpoints in their own sites (based on Keywords attribute that tells which AD site SCP belongs to) –
Please correct me if this is wrong.
If we configure same names for the VIIPs in both data centers, this also means that we have to configure BYOD.ABC.Com on External as well as Internal URLs on all the Exchange 2013 servers across both the data centers – Wouldn’t that be a problem – in terms
of loops during CAS-CAS Proxy/Redirection?
If we configure different names of the VIPs (say BYOD1.ABC.Com and BYOD2.ABC.Com), how will the Outlook Anywhere requests be handled in both data centers. The OA requests from DC1 will expect the Certificate Principle Name to be BYOD1.ABC.Com and requests
from DC2 will expect the Certificate Principle Name to be BYOD2.ABC.Com. How to get this stuff working. As far as I know, OA expects CPN to match with it’s name.
Thanks
Taranjeet Singh
zamn

Any comments/suggestions from community......
Thanks
Taranjeet Singh
zamn

Error During install Exchange 2013 through Powershell on Server 2012 "Mailbox role: Client Access service"

Dear all
During install Exchange 2013 through Powershell on Server 2012 I got this error in Mailbox role: Client Access service :
The following error was generated when "$error.Clear();
$BEVdirIdentity = $RoleNetBIOSName + "\OWA (Exchange Back End)";
new-OwaVirtualDirectory -Role Mailbox -WebSiteName "Exchange Back End" -DomainController $RoleDomainController
set-OwaVirtualdirectory -Identity $BEVdirIdentity -FormsAuthentication:$false -WindowsAuthentication:$true;
" was run: "An error occurred while creating the IIS virtual directory 'IIS://MONAMBX2.mona.local/W3SVC/2/ROOT/o
wa' on 'MONAMBX2'.".
The following error was generated when "$error.Clear();
$BEVdirIdentity = $RoleNetBIOSName + "\OWA (Exchange Back End)";
new-OwaVirtualDirectory -Role Mailbox -WebSiteName "Exchange Back End" -DomainController $RoleDomainController
set-OwaVirtualdirectory -Identity $BEVdirIdentity -FormsAuthentication:$false -WindowsAuthentication:$true;
" was run: "The operation couldn't be performed because object 'MONAMBX2\OWA (Exchange Back End)' couldn't be fo
und on 'MonaDc1.mona.local'.".
Any advice please !!

I can't answer your question but I had a similar issue when I was trying to move our mailbox database off the C: drive. Our environment still has an Exchange 2007 server in it and when I was trying to move the database on the 2013 server, I would get
error messages saying the database does not exist. It seemed like it was trying to move the database on the 2007 server from the similar error messages that I was getting. To get around it, I deleted the database and created a new one on the drive
where we wanted it.
I discovered this when I was configuring the Antispam settings. I deleted our 2007 settings, added them to the 2013 shell, the settings appeared on our 2007 server. The shell on 2013 was making changes to 2007.
I'm not sure if there is a "Get|Set or New" command that I/we should be using when this happens. Or maybe my issues will be fixed if I just remove the Exchange 2007 server? I'm not ready to do that yet because I can't configure the spam filtering
on 2013 yet with its shell not being able to make the changes that we need.
I don't know if your environment is in coexistence mode like mine.
Hopefully someone else out there has an answer or can tell us when/how the shell can make the appropriate changes to the 2013 server. Does this happen after the 2007 server is removed?

What are share point server 2013 & Share point Designer 2013 & Office 365 & Yammer & Share point 2013 & Windows server 2008 server & Windows Server 2012 Server Data Center?

I need some clarifications.
What are share point server 2013 & Share point Designer 2013 & Office 365 & Yammer & Share point 2013 & Windows server 2008 server & Windows Server 2012 Server Data Center? How each them are related in collaboration system?
Is Share point server 2013 and Share pointer Designer 2013 available in 32bit version? If not, then how to use it in 32 bit machine by using any VMs?
Thanks
Senthil

SharePoint Server 2013:
http://office.microsoft.com/en-us/microsoft-sharepoint-collaboration-software-FX103479517.aspx
SharePoint Designer 2013:
Designer is used to develop SharePoint pages using HTML/CSS/JS as well as SharePoint Designer Workflows
Yammer:
https://about.yammer.com/
Windows Server is Windows, but the Server OS. SharePoint runs on top of supported Windows Servers editions (see http://technet.microsoft.com/en-us/library/cc262485.aspx).
SharePoint Server is 64-bit only (trial:
http://technet.microsoft.com/en-us/evalcenter/hh973397.aspx), although Designer does have a 32-bit edition (full product:
http://www.microsoft.com/en-us/download/details.aspx?id=35491).
You will need the capability to run 64bit VMs. Minimum recommended all-in-one VM for SharePoint is to allocate 24GB of RAM, but you can get away with as little as 12GB (I wouldn't go below that). Because of this, it generally rules out 32bit OSes as a virtual
machine host.
Trevor Seward
Follow or contact me at...
&nbsp&nbsp
This post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

How to configure Exchange 2013 OWA with Single Sign On

Hi All ,
How to configure Exchange 2013 OWA with Single Sign On ?
Thanks .

Hi,
From your description, I am not quite sure what you really want to achieve. Could you explain it furthermore? If you need to set up Exchange 2013 OWA single sign on with Exchange 2010, here is a helpful thread for your reference.
Exchange 2013 OWA Single Sign on with Exchange 2010
https://social.technet.microsoft.com/Forums/en-US/2899ebfc-8622-4cdc-8d77-d76b607618f7/exchange-2013-owa-single-sign-on-with-exchange-2010?forum=exchangesvrdeploy
If that is not your case, please feel free to tell me.
Best regards,
If you have feedback for TechNet Subscriber Support, contact
[email protected]
Amy Wang
TechNet Community Support

Windows Server Data Center Edition Evaluation version

Hallo,
I'm the IT buyer for a medium-sized company and my IT service provider who is preparing the migration of our data base wants me to buy a Windows 2012 Server Data Center License (11000 € with software insurance). I have my doubts about their comptence with
big back-end projects (although they are very good with day to day technical support) and so I asked them to set up the server with an evaluation license so that I can see that it really works before I pay for the license. This is the point of an evaluation
version, right? I have read that the evaluation period for Windows 2012 Server Data Center is 160 days which seems largely time enough.
But they tell me they have their doubts about whether they can convert the evaluation license into a real license and are worried that they will have to set up the system twice. This seems like nonsense to me. Does anyone have any experience with evaluation
licenses of this sort?
And if I buy the license and they don't manage to set it up to my satisfaction can I obtain a refund? Can I give the license back? My service provider is a windows reseller. Can I ask them to sell the license to someone else?
Thanks in advance for any help
Lulu

Evaluation versions are not meant to be used in a production environment. So I would not recommend using an eval version to host a live database. The ideal process is that you install the eval software and test your database/other requirements for the period
of the eval time. Then if you feel it is right for you, you purchase the full version.
You would have to set up the system twice.

Exchange 2013 SP1 on Windows Server 2008 R2 Enterprise - BSOD after DAG creation

Hi,
We are running Exchange 2007 SP3 RU13 on Windows 2003 R2 with SP2 in a 2003 native AD environment and recently decided to upgrade to Exchange 2013. We installed a pair of new DELL R420 servers running Windows 2008 R2 Enterprise then threw Exchange 2013 SP1
onto them. This all went fine and the servers are running stable.
We connected the second NIC of each server to the other via a separate switch, the second NIC has Client for MS Networks and File/Printer Sharing disabled plus a totally separate subnet with no DNS or GW address assigned. DAG setup was run and completed
OK. I created the DAG network in Exchange and enabled replication, I also left replication enabled across the production LAN. Finally, I went into the advanced network settings and made sure the replication network was below the production network in the binding
order.
After an hour or two the BSOD's started.. both servers would crash within a few minutes of each other and reboot with a Kernel Panic. I have attached the contents of the dump file below. This seems to happen every few hours and it always seems to be the
server hosting the passive DB copies crashes first, followed by the server hosting the active copies. Note that if we disable the replication NIC on both servers they do not crash.
I got the impression from somewhere that perhaps the servers had mixed up the binding order and were trying to use the replication network as primary, losing access to AD and rebooting (which I have read is the behaviour for Exchange now). It appears the
Exchange Health service has killed WININIT which causes the crash.
Thanks!!!
The crash dump text is below:
CRITICAL_OBJECT_TERMINATION (f4)
A process or thread crucial to system operation has unexpectedly exited or been
terminated.
Several processes and threads are necessary for the operation of the
system; when they are terminated (for any reason), the system can no
longer function.
Arguments:
Arg1: 0000000000000003, Process
Arg2: fffffa80192ebb30, Terminating object
Arg3: fffffa80192ebe10, Process image file name
Arg4: fffff80001dc37b0, Explanatory message (ascii)
Debugging Details:
PROCESS_OBJECT: fffffa80192ebb30
DEBUG_FLR_IMAGE_TIMESTAMP: 0
MODULE_NAME: wininit
FAULTING_MODULE: 0000000000000000
PROCESS_NAME: MSExchangeHMWo
BUGCHECK_STR: 0xF4_MSExchangeHMWo
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: DRIVER_FAULT_SERVER_MINIDUMP
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from fffff80001e4cab2 to fffff80001abebc0
STACK_TEXT:
fffff880`0d7f39c8 fffff800`01e4cab2 : 00000000`000000f4 00000000`00000003 fffffa80`192ebb30 fffffa80`192ebe10 : nt!KeBugCheckEx
fffff880`0d7f39d0 fffff800`01df7abb : ffffffff`ffffffff fffffa80`1bcf3060 fffffa80`192ebb30 fffffa80`383ea060 : nt!PspCatchCriticalBreak+0x92
fffff880`0d7f3a10 fffff800`01d77674 : ffffffff`ffffffff 00000000`00000001 fffffa80`192ebb30 00000000`00000008 : nt! ?? ::NNGAKEGL::`string'+0x17486
fffff880`0d7f3a60 fffff800`01abde53 : fffffa80`192ebb30 fffff880`ffffffff fffffa80`1bcf3060 00000000`00000000 : nt!NtTerminateProcess+0xf4
fffff880`0d7f3ae0 00000000`7772157a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`34eed638 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7772157a
STACK_COMMAND: kb
FOLLOWUP_NAME: MachineOwner
IMAGE_NAME: wininit.exe
FAILURE_BUCKET_ID: X64_0xF4_MSExchangeHMWo_IMAGE_wininit.exe
BUCKET_ID: X64_0xF4_MSExchangeHMWo_IMAGE_wininit.exe
Followup: MachineOwner

Hi Darrkon,
I suggest checking the status of the HealthMailbox on each of servers.
Also try to re-create the mailbox. You can safely delete and recreate health mailboxes.
Be aware that any local Managed Availability probes that are using the these mailboxes will fail until the Microsoft Exchange Health Manager is restarted. Once that service is restarted, it will recreate any mailboxes that it needs.
More details in the following similar thread, just for your reference:
BSOD after creating DAG
http://social.technet.microsoft.com/Forums/exchange/en-US/44d1cd98-cba1-4ed0-b0e7-8aa76ee3eabc/bsod-after-creating-dag
Thanks
Mavis
Mavis Huang
TechNet Community Support

Exchange 2013 DAG with single site and 2 multi-role servers with error "MapiExceptionIllegalCrossServerConnection"

Hi,
I've got a lab with a domain controller and an Hyper-v with on it two multi-role exchange 2013 CU7 servers on W2K12 R2 OS, configured in DAG semplified (but the problem is the same also if I use the classical DAG configuration), a witness server, and a L7
load balancer for the exchange servers.
When I made the test to disable the OWA application pool where I've got the active mailbox database of the user, the balancer in correct manner redirect the session to the other exchange multi-role server, but the client in his OWA session is no more
able to send new mail with the error "Error your request can't be completed rigt now. Please try again later."
The only strange log that I see on the server in the MAPI client access directory where there is the following error message:
2015-01-21T08:00:45.132Z,956,1,/o=First Organization/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=1247f28558d24d4db872ab127b3e5810-Healt,,Microsoft.Exchange.RpcClientAccess.Monitoring.dll,15.0.0.0,Cached,,,,MapiHttp,Client=Microsoft.Exchange.RpcClientAccess.Monitoring,R:4ab7b6c8-54ee-4be3-aa9d-f8c856c4c47c:2,C:MAPIAAAAAOC4+7OCoZOjkqeKuoumlKSEtYO5ibyGs4bc/879z/vD9sX1zP28AwAAAAAAAA==|S:0-mGmHRQ==,OwnerLogon,0x6BB
(rpc::Exception),00:00:00.0310000,"Logon: Owner, /o=First Organization/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=1247f28558d24d4db872ab127b3e5810-Healt in database last mounted on Exch2.lab.net",RpcEndPoint: [ServerTooBusyException]
Client is being backed off -> [ClientBackoffException] Mailbox was moved to a different mailbox server. A client needs to retry. -> [IllegalCrossServerConnectionException] Cannot open mailbox /o=First Organization/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=1247f28558d24d4db872ab127b3e5810-Healt.
-> [MapiExceptionIllegalCrossServerConnection] Monitoring mailbox [] with application ID [Client=MSExchangeRPC] is not allowed to make cross-server calls from [Exch1.lab.net] to [Exch2.lab.net] [diag::AAAOAAAA/wAAAAAAAAAAAgAAAAA=],,,[email protected],
The CAS try to access the mailbox on the other server, but without success.
Someone have idea how to solve?
Thanks

Hi Hinte, sorry for the answer delay.
I've run the command you suggest to check the HealthMailbox status, but seems that all are fine:
[PS] C:\Windows\system32>get-Mailbox -Monitoring | ft name, servername
Name ServerName
HealthMailbox7021deb6ae104dadbf52feedfa7fa68b exch1
HealthMailboxb83c9040b32e4d1197f7f54f6709bb7f exch1
HealthMailboxb1c32037890b43fbb2af2efe7c36ba00 exch1
HealthMailbox8d174269b494458daf9ade5099e22845 exch1
HealthMailboxaa7d10f02d2d4cc588243b291ead3e3a exch1
HealthMailboxeb32c30a019f42968a7cbc49a6ac3e65 exch1
HealthMailboxc6ff1d36ba154c5db5411b44718edcbd exch1
HealthMailbox75dc7caa7e8c4a3b812a01b607536d48 exch1
HealthMailbox16c86e512f454e7890b80c180ce19c00 exch1
HealthMailboxc6e447f7dba24d9b913f1dfcabe9f927 exch1
HealthMailbox40fa5a3f2abc4accae6286cd98abc90a exch1
HealthMailbox2712b9544bad4e7b8b671be2cda8cfde exch2
HealthMailboxe2559124da20499386bf8103dcb21e9b exch2
HealthMailbox3264c6078dad45d4a78c56a3afe81df1 exch1
HealthMailboxacacc51eb8bc4717b295ddf0adccf77e exch2
HealthMailbox64c4dd8cddac4c4e8bb7314010e797b1 exch1
HealthMailbox4a92bfa14fdd47fbb27c19513f6d2beb exch2
HealthMailbox465d2a69de93430e84b4d699a88cb0c3 exch1
HealthMailbox97b578e57cd44204820fffa416b25633 exch2
HealthMailboxb411059771db4647bb775c665ec29440 exch1
HealthMailboxf981dde6f4134f839bf41eb0000434e4 exch2
HealthMailboxc33801c7c3b1474f8aa6065249bb4fca exch1
HealthMailbox2282128ed8d14937998212edd15adf20 exch2
HealthMailboxe3d12b756cf545239b38be4607904ae1 exch2
[PS] C:\Windows\system32>
Regarding the test sugested to diable instead the OWA App Pool only the OWA virtual directory, I've not found on IIS the possibility to stop the access to this virtual directory.
Also on exchnage Administration page there is no the possibility to switch off this virtual directory only (or I don't found where is this setting).
Regards

Exchange 2010 DAG Replication - too much data crossing the wire

I’m replicating 3 Exchange databases from our production active Exchange 2010 server across the WAN to another passive Exchange 2010 server at our DR site.
The Exchange server at the DR site does not have any active databases, i.e. no users are hitting that server.
We are running Update Rollup 8 for Exchange Server 2010 SP1 on both these servers.
The two sites are connected via a 10Mb/s MPLS connection and all the databases are in sync and the replication is working fine.
I have setup a network sniffer at the primary site and see a sizable amount of data crossing the wire from the production Exchange server to the DR Exchange server.
When I query the production Exchange server using the Tracking Log explorer and only choose the EventID ‘RECEIVED’ that should show me the amount of data that has been committed to the database.
If I choose a date range that is the same exact range that I have used to capture the raw data with my sniffer the amount of data the sniffer shows crossing the wire is 10 fold compared to what the Tracking Log Explorer shows.
If I actually count up the data in the LOG files it is about 20% more than what is crossing the wire but that seems to be because the DAG is compressing the data.
If in a one hour timeframe there is 500MB of data crossing the wire to the DR Exchange server the tracking log explorer will show only 50MB.
I would like to know why the data crossing the wire far exceeds the amount of data that is truly being sent/received from the primary exchange server.
Perhaps I’m simply not getting a true view of the amount of data being committed to the exchange server using the Tracking Log Explorer.
Maybe there is a better way to report how much data is being committed to the exchange databases.
Any assistance would be appreciated…

Two things.
1 - you must update Exchange to SP3 and a recent RU. Willard has already provided the links, which point back to my blog if you want to see the lifecycle map for Exchange 2010. SP1 has been out of support since January 2013. Time to move
on pllease
2 - Looking at the tracking log is not sufficient. I would not expect that to show everything.
I want to know what traffic you see as excessive. What ports are you seeing used here?
My money is on content indexing. CI will use additional traffic over and above log repl traffic. Expect CI traffic to be roughly the same again. You can test this by disabling CI on the database or stopping the services on the DR server.
To disable the CI for the database:
Set-MailboxDatabase DBName -indexEnabled $False
Or stop the Exchange search services on the DR box to leave production unaffected.
Again - you need to update Exchange. You would be better to do that now rather than when something breaks and Microsoft support cannot fully assist you since you are not uptodate.    I'll leave discussion of the security issues resolved
in recent Exchange RUs aside.
Cheers,
Rhoderick
Microsoft Senior Exchange PFE
Blog:
http://blogs.technet.com/rmilne
Twitter:   LinkedIn:
  Facebook:
  XING:
Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.

How do you delete specific message from users in Exchange 2013 DAG database?

Our network has been inundated with spam from INTUIT.COM with the SUBJECT: PAYMENT OVERDUE and contains a link to download a form from a Dropbox. Obviously, very suspicious and clearly spam. We're using Postini as our Edge Transport/ Spam filter but messages
are still getting in. I've enable anti-spam on all my mailbox servers, set the SCL values but that hasn't worked.
I understand that Exchange Edge Transport role has the more aggressive spam fighting features but Microsoft also recommends an online spam filter.
Needless to say, we've taken steps to quarantine those messages based on subject and sender in Postini but now would like to delete those messages from the users in went to. My users are two different DAG mailbox databases. I found this article http://www.techieshelp.com/delete-mail-from-multiple-mailboxes/ but
the command didn't work. I'm thinking its because I have DAG and a couple of databases. I even tried "get-mailbox -database "databasename" | search-mailbox -searchquery subject: "Payment Overdue"" and that didn't work.
I'm running Exchange 2013 SP1 DAG across two sites comprised of four 2013 SP1 mailbox servers.

Check this out
http://technet.microsoft.com/en-us/library/ff459253%28v=exchg.150%29.aspx and specifically look at the section titled "Search messages and log the search results"
Or you can use this
http://technet.microsoft.com/en-us/library/aa996371%28v=exchg.150%29.aspx with the WHATIF parameter
Alternatively if you are open the 3rd party solutions check out Lucid8's DigiScope
http://www.lucid8.com/product/digiscope.asp
which would allow you to see the search results and then delete OR if desired you can set the On FIND action to Export to PST and then Delete so that you can preserve and then remove messages on the fly as the search system finds
Search, Recover, & Extract Mailboxes, Folders, & Email Items from Offline Exchange Mailbox and Public Folder EDB's and Live Exchange Servers or Import/Migrate direct from Offline EDB to Any Production Exchange Server, even cross version i.e. 2003 -->
2007 --> 2010 --> 2013 with Lucid8's
DigiScope

Test-ReplicationHealth Database Redundandacy and Database Avaliability *FAILED* Exchange 2013 DAG setup

Trying to setup DAG between 2 exchange 2013 servers - one of them being in the remote location with physical point to point line. We have no firewall rules between 2 locations
EX01 ( on site)
EX02 (remote)
ETH01 10.11.1.2/24 - MAPI                       ETH01 10.11.13.15/24
ETH02 10.0.0.1/30 - REPLICATIOn            ETH02 10.0.0.2/30 - REPLICATION
Witness server is in 3rd remote location
These are the test results I get from Test-ReplicationHealth and Cluster Network Validation
I also run a Nmap command to make sure udp port 3343 is open on both sides
alex serdyukov

Hi,
The error message said that current Redundancy Count was 1 but expected Redundancy Count was 2. Therefore, Database 'IT2013' does not have enough copies configured to meet the validation criteria.
Please replicate that database to another server at least. We can refer to Hinte's suggestion to
add another copy for the database 'IT2013' in the DAG then check whether the issue persists.
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 2013 DAG / client access

Hello
I'm in the planning of a new Exchange 2013 infrastructure. The infrastructure will be located in a datacenter and should host about 1000 mailboxes. I have read many whitepapers and tutorials, but some things are still unclear to me.
- Microsoft suggests multi-role servers for this amount of users because client access is no more than a reverse proxy in EX2013. Is this correct? I've read that one users with 200 mails/day needs 8.5 MCycles with only DB and 10.63 MCycles with DB and CAS
on the same server. So I plan to start with 2 multi-role servers in a DAG. What's your oppinion on this?
- Client connections: I assume the clients connect to the cluster IP of the DAG. How do they get directed to the server on which their database is online? Does each server need to have the cluster IP and a public IP to which the clients connect?
- SMTP: As I understand the documentation, mails are sent from the server which the user is active on. (Which makes sense for high availability.) What is best practice regarding the protocol logs? Do the support employees need to search in the files on 2
servers?
Thank you very much for your input!

Hi
I would use the firewall for load balancing unless there is a technical reason why this is not possible. NLB is not recommended as it is not service aware - you cannot configure a probe to test OWA is working for example - so if you already have something
better that would be my choice.
In the choice between IIS ARR and NLB or CAS and NLB I would go for IIS ARR as this reduces you license costs, but neither of these is better than the appliance/firewall option.
I've never used NLB for load balancing other than on TMGs so I cannot say what the performance is like behind a firewall, in theory your assumption would be correct.
The load balancer doesn't make this decision it just spreads the load between the active servers, the CAS role connects the use session to the correct mailbox server:
http://blogs.technet.com/b/exchange/archive/2013/01/25/exchange-2013-client-access-server-role.aspx
Steve

Exchange 2013 DAG with VMWare Clustering

Hi team,
I'm looking at a scenario where there are 3 Hosts with a SAN for storage and is
Clustered for failover with so many other server/applications. The requirement is to have a High Available environment with Exchange 2013. Now I want to know the possibility of having 2xCAS (WNLB) and 2xMailbox Servers with DAG.
1) Want to know if this is a supported scenario, where DAG is implemented in a VMWare cluster.
2) The DAG on cluster is to ensure that even if no host failure occurs i have VM level failover. and if Host Level failover occurs I have cluster based failover.
Any guidance is much appreciated.
Thank you.
Cheers!

Hello,
It is not supported configuration that combining VMware HA solution with the Exchange application-aware high availability solution.
Here are some articles for your reference.
http://blogs.technet.com/b/keithmayer/archive/2012/08/28/best-practices-for-virtualizing-microsoft-exchange-2010-msexchange-itpro-hyperv-vmware.aspx#.Uxfd2P7xuM8
http://exchangeserverpro.com/microsoft-vs-vmware-on-exchange-virtualization-and-ha-best-practices/ (
Note: Microsoft is providing this information as a convenience to you. The sites are not controlled by Microsoft. Microsoft cannot make any representations regarding the quality, safety, or suitability of any software or information found there. Please make
sure that you completely understand the risk before retrieving any suggestions from the above link.)
If you have any feedback on our support, please click
here
Cara Chen
TechNet Community Support

Move Exchange 2013 to new Virtual Server including settings?

Since we have a failing VM Exchange 2013, we need to move the installation to a new server. We have created a new Hyper-V Server 2012 and installed a new Exchange 2013 on it. After connecting the new server to the domain we can see all settings and users
of the existing Exchange Installation.
Since the old server has a corrupt RAID, we need to move all data and settings to the new server. We have moved some user mailboxes with the ecp to the new server. They are still working, but mailtraffic takes exactly 1 hour now?! Also these users who logon
with Outlook now get the error message 'problem with the safetycertificate of the proxyserver (translated)'. The mail still works, but 1 hour delay.
Can we now move the other mailboxes too? And if we have moved them, how can we move the settings of this server? If we shutdown the old server, will Exchange (the moved one) still be up and running? Because we are afraid that when we shutdown the old server
it will not boot again.
Thanx for any tips of leads in the right direction.

1. Outgoing mail from https://echange/owa is
working.
Did you try https://ip-address-of-newserver/owa and send an email outside?
2. Outlook 2010 does not start, cannot find mailboxes to open, so user won't have mail in the morning.
Get-OutlookProvider -Identity EXCH | FL
If is field CertPrincipalName empty type following:
Set-OutlookProvider EXCH -CertPrincipalName msstd:FQDN-YOUR-MAIL-SERVER
After this it should work (assuming all your mailboxes moved to the new server).
Please check this to see you the mailbox servername
http://www.zerohoursleep.com/2013/02/manual-outlook-configuration-with-exchange-2013/
3. Incoming mail cannot be delivered by the Barracuda (connection refused).
Ensure Barracuda is sending email to the new server and new server is not blocking incoming traffic.
4. OWA and ECP not working from outside (public IP).
Ensure you NAT is correct by site. Check it is listening to the port using http://www.canyouseeme.org/
Please check these and get back
Thanks, MAS
Please mark as helpful if you find my comment helpful or as an answer if it does answer your question. That will encourage me - and others - to take time out to help you.

Accessing Exchange 2013 Mailboxes from Terminal Server hosted on Server 2003 Std - Cert Issues

We are in the midst of deploying an Exchange 2013 SP1 CU5 environment and have run into some issues. Currently there is a good coexistence between a single Exchange 2007 server and the 5 2013 servers. Mail is flowing through 2013 and then being
relayed to 2007 when necessary.
We have a number of Server 2003 Terminal Servers. On two separate machines, both running the lastest rollups of Outlook 2010, any user with a 2013 mailbox receives a password prompt after launching Outlook. It is trying to connect to one of the
two CAS, fills in the user's account, and will not accept any password. In addition, a window pops up behind stating "There is a problem with the proxy server's security certificate. the name on the security certificate is invalid or does
not match the name of the target site mail.pvschemicals.com. Outlook is unable to connect to the proxy server. (error code 0)." 2007 mailboxes are not affected.
We have checked pretty much everything that we can think of. Virtual Directories are good, certificate is good, etc. The strange thing is that only happens on 2003 TS machines, so I have to think that it's related. Our 2008 TS' are just
find.
We have applied the 2003 SHA2 certificate hotfix.

Hi,
According to your description, the configurations of Outlook Anywhere are proper. And based on my research, the issue can be related to the version of the terminal server 2003. Thus, please check if your terminal 2003 server is 2003 R2 SP2 or later.
For more information, you can refer to the following thread:
http://social.technet.microsoft.com/Forums/exchange/en-US/295bf2bc-584b-4de2-85fb-94096fac52e7/outlook-connectivity-problem-on-2003-term-server-exchange-2013?forum=exchangesvrclients
Thanks,
If you have feedback for TechNet Subscriber Support, contact
[email protected]
Angela Shi
TechNet Community Support

Configuration Exchange 2013 DAG on two Server Data center 2012 with Hyper -V roles

Similar Messages

Maybe you are looking for