Exchange 2010 3 node DAG and split datacenters

Hi all,
I have a Exchange 2010 setup with 3 DAG nodes, 2 servers in Primary site & one in DR site, 2 active directory Sites, one domain controller per site. All roles on each server.
Each server has a single NIC, with the following configs:
Primary Site:
MBX1 IP = 192.168.1.11 - Network Name MAPI-Primary
MBX2 IP = 192.168.1.12 - Network Name MAPI-Primary
Cluster IP = 192.168.1.10
DR Site:
DRMBX1 IP = 192.168.100.11 - Network Name MAPI-DR
Cluster IP = 192.168.100.10
Dag name = DAG1
Under the DAG Networks, I see 3 Networks
DAG1_MAP1-Primary with the 192.168.1.0/24 subnet and the 2 MBX Network IP's in it.
DAG1_MAP1-DR with the 192.168.100.0/24 subnet and the 1 DR MBX Network IP in it.
and one called DAG1_Replication, which has a 10.1.1.0/24 subnet and NO NIC's in it. I think this was an original replication subnet used when there was only 2 nodes in the DAG and a cross over cable was used.
Can I delete the DAG_Replication network from the config?
Should I consolidate the 2 DAG1_MAPI-Primary and DAG1-MAPI-DR networks under one simply called DAG1-MAPI?
Secondly,
When I look at cluster manager on each of the 2 Nodes MBX1/2, I can see the 3 Nodes. Trying to run cluster manager on the DR node, and I can't connect to the DAG1 cluster, get an error saying not ready. Am I right in thinking this should not be
happening? I have a managed firewall, but don't have access too logs, any idea what ports could be dropped from DRMBX1?
Finally,
Cluster manager on the 2 working nodes shows an error:
Cluster Network Name is not online, and the Cluster Core resources panel shows cluster name DAG1 Offline, with ONLY 1 IP address, the DAG VIP (192.168.1.10) being online. Should I see the other 192.168.100.10 DAG VIP as well? Is this also a manifestation
of the firewall?
I have inherited this config, so I am not fully sure what a correct working condition should report look like. Any help on a clearer understanding would be greatly appreciated.
Thanks in advance !!

In answer to your first question, yes, if no server is listed with an IP address in that replication network, you can delete it without affecting the DAG operations.
As for your second question, if your servers are in different subnets, you need at least two networks defined in your DAG. And since your servers are in different Windows sites, I have to assume they are in different subnets. I believe that if
you check them in the EMC, you will only see IP addresses for the local servers in each network. So no consolidation is possible.
On your question about Cluster Manager, don't do anything in Cluster Manager - my personal experience has been that the Exchange toolset is sufficient for all management tasks related to an Exchange DAG. What are you trying to determine? Also,
Microsoft doesn't support a DAG installed across a firewall - either you open all ports between these servers (and all domain controllers in your forest), or you will have an unsupported configuration.
For your final question, I assume DAG1 is your DAG's network name, and those two IPs are the ones for the two datacenters. If this is the case, only one IP address will be active at a time.

Similar Messages

Exchange 2010, UCC SSL, and the "new" CA/BROWSER Forum not issuing for .local

I don't know how many people have run into this yet, but the CA/BROSWER Forum, the "standards" authority for SSL issuing, has mandated that CA's can no longer issue a certificate using a FQDN "intranet" name for new or renewal SSL certificates effective
Nov 1, 2012. i.e. the Microsoft standard of mydomain.local will no longer be accepted as a SAN on a UCC for Exchange 2010. I've looked thru the KBs and Social forums, but haven't really found any guidance on how to solve this. I'm presuming
that the certs will have to be split and the "external" domain name of server.mydomain.net will just become a single server SSL, and the internal name of server.mydomain.local will become a Self-Signed certificate. With the increasing prevalence of OA
and ActiveSync devices, is there any baseline guidance yet on how to make this happen without completely fouling up production servers and killing access to the user community?

On the same topic, though likely different environment...
Against recommended deployment, I have a number of clients running all their services on one box. Windows Server 2008, Active Directoy, DNS, Exchange 2010 ...and so on. These servers all have .local addresses, which means of course that the SAN
certificates have .local addresses as one of the SANs.
I've read alot online about this issue, and am trying to find the most cost effective solution to switch numerous production servers running this configuration.
The best solution I've come up with so far is...
1. Virtual AD with new external domain, 2. Migrate Exchange CAS to this domain, 3. Reconfigure network through the box.
Obviously these steps will contain alot more details, but this is just the outline atm. At best, I see me having to take a second box with me to each location to perform these steps, and I can't see it happening without disruption to the work flow
of employees.
Thankfully, all of these businesses are relatively smal...under 25 employees. Still, I'd like to find the smoothest transition solution possible.
Any suggestions would be greatly appreciated!
Regards

Exchange 2010 management tools and others

Win2k8 domain, Exchange 2010 servers
We want to move to Win8.1 but we, the admins, are preventing it because our tools like the Exchange 2010 Management tool doesn't work with Win8.0 so we're stuck with Win7.
I've googled around and most suggestion never worked.
Does Microsoft have any plans at all to have Exchange 2010 management tools and other tools we use to manage our domain work with Win8.1?

Hi Rino,
Thanks for your sharing and efforts put on this issue.
This will benefit others who encounter the similar scenario as yours.
Happy holiday~
Kate Li
TechNet Community Support

Real-world experience with Exchange 2010 SP3 RU5+ and Powershell 4?

The support-ability matrix for Exchange (http://technet.microsoft.com/en-us/library/ff728623(v=exchg.150).aspx) says Exchange
2010 SP3 RU5+ and Powershell 4 are compatible. But, there is very little actual discussion about how well that works.
I use Powershell extensively for mission critical and somewhat complex processes, with Exchange 2010 on 2008 R2 and AD access/reads/updates.
Can I get a summary of the caveats and benefits from someone who has actually done this in a
real-world/production scenario (more than one server, managing from a separate non-Exchange server), and who has scripting experience with this configuration?
Also, how has this affected EMC operations?
As always thank you in advance!

I believe the matrix states that its supported to install Exchange into an environment where __ version of WMF is present. Exchange 2010, launched from a Win 2012 server, reports version 2.0 when you call $host. For example, calling the ActiveDirectory
module from EMS on an Win 2012 server (ps 3.0) fails.
I'll double check the extent of this scenario and get back to you.
Mike Crowley | MVP
My Blog --
Planet Technologies

[SOLVED] Can't add a node to the cluster with error (Exchange 2010 SP3 DAG Windows Server 2012)

Hi there!
I have a problem which makes me very angry already :)
I have two servers Exchange 2010 SP3 with MB role started on Windows Server 2012. I decided to create a DAG.
I have created the prestaged AD object for the cluster called msc-co-exc-01c, assigned necessary permissions and disabled it. Allowed through the Windows Firewall traffic between nodes and prepared the File Share Witness server.
Then I have tried to add nodes. The first node has been added successfully, but the second node doesn't want to be added :). Now I can add only one node to the DAG. I tried to add different servers first, but only the first one was added.
LOGS on the second nodes:
Application Log
"Failed to initialize cluster with error 0x80004005." (MSExchangeIS)
Failover Clustering Diagnostic Log
"[VER] Could not read version data from database for node msc-co-exc-04v (id 1)."
CMDLET Error:
Summary: 1 item(s). 0 succeeded, 1 failed.
Elapsed time: 00:06:21
MSC-CO-EXC-02V
Failed
Error:
A database availability group administrative operation failed. Error: The operation failed. CreateCluster errors may result from incorrectly configured static addresses. Error: An error occurred while attempting a cluster operation. Error: Cluster API '"AddClusterNode()
(MaxPercentage=100) failed with 0x5b4. Error: This operation returned because the timeout period expired"' failed. [Server: msc-co-exc-04v.int.krls.ru]
An Active Manager operation failed. Error An error occurred while attempting a cluster operation. Error: Cluster API '"AddClusterNode() (MaxPercentage=100) failed with 0x5b4. Error: This operation returned because the timeout period expired"' failed..
This operation returned because the timeout period expired
Click here for help... http://technet.microsoft.com/en-US/library/ms.exch.err.default(EXCHG.141).aspx?v=14.3.174.1&t=exchgf1&e=ms.exch.err.ExC9C315
Warning:
Network name 'msc-co-exc-01c' is not online. Please check that the IP address configuration for the database availability group is correct.
Warning:
The operation wasn't successful because an error was encountered. You may find more details in log file "C:\ExchangeSetupLogs\DagTasks\dagtask_2014-11-17_13-54-56.543_add-databaseavailabiltygroupserver.log".
Exchange Management Shell command attempted:
Add-DatabaseAvailabilityGroupServer -MailboxServer 'MSC-CO-EXC-02V' -Identity 'msc-co-exc-01c'
Elapsed Time: 00:06:21
UPD:
when Exchange servers ran on the same Hyper-V node, the DAG is working well, but if I move one of VM to another node, It stops working.
I have installed Wireshark and captured trafic of cluster interface. When DAG members on the same HV-node, there is inbound and outbound traffic on the cluster interface, but if I move one of DAG member to another node, in Wireshark I see only outbound traffic
on both nodes.
It's confused me, because there is normal connectivity between these DAG members through the main interface.
Please, help me if you can.

Hi, Jared! Thank you for the reply.
Of course I did it already :) I have new info:
when Exchange servers ran on the same Hyper-V node, the DAG is working well, but if I move one of VM to another node, It stops working.
I have installed Wireshark and captured trafic of cluster interface. When DAG members on the same HV-node, there is inbound and outbound traffic on the cluster interface, but if I move one of DAG member to another node, in Wireshark I see only outbound traffic
on both nodes.
It's confused me, because there is normal connectivity between these DAG members through the main interface.

Moving Exchange 2010 Production DAG Setup and Servers to difrent Date Center with new IP Addresses

My Setup
Exchange 2010 SP3 2 Mailbox, 2 Hub/CAS, 2 TMG Servers in Production
Exchange 2010 SP3 2 Mailbox, 2 Hub/CAS, 2 TMG Servers in DR Site
Exchange 2010 DAG implemented with site level redundancy
Requirement
Need move Production Exchange setup along with DAG configuration to a new location.
IP Addresses for servers and DAG setup will change
No change in Server name and DNS names
During production server movement Mail services will be activated from DR Site
Need help in planning and executing the IP Address change/DAG Change
and Server movement.
Kumar K S

Hi,
I will have the following plans:
1. Active the DR site as the main site during the migration.
2. Moving the Server to the new site
3. Change the activate back to the Production Servers
https://social.technet.microsoft.com/Forums/exchange/en-US/fb9a27c3-81f8-4079-aeb8-42119b1e23bf/changing-ip-address-of-exchange-server
Thanks,
Simon Wu
TechNet Community Support

Exchange 2010 SP3 DAG Witness/Quorom Server Placement with 3 Datacenters

Hi we have 2 Exchange 2010 SP3 Server in the same Organization in a DAG
First one in Datacenter 1 in Germany
Second one in Datacenter 2 in Austria
There is a Third Datacenter available in Switzerland
Where should we place the Witness Server?
Our major concern is not a WAN Link will go down, most time a Datacenter will loose Power for some hours due
maintenance work or other things.
Is it a good idea to place the Witness Server in the third Datacenter!?
We found a Document which some missconception which talks about placing the witness always in
the primary Datacenter. But the Datacenter Switchover Document for Exchange 2013 says use a third Datacenter.
Is that also okay for Exchange 2010 or are they totally different?
Thank you in advance
Troga

Hi,
It is a new configuration option in Exchange 2013 that we use a third location for hosting the witness server.
Placing FSW in the third location will privide the ability automatically failover databases to the other datacenter in response to a datacenter-level failure event.
For more details, you can look at the "Witness server placement considerations" section in the following article.
http://technet.microsoft.com/en-us/library/dd298065(v=exchg.150).aspx
Best regards,
Belinda Ma
TechNet Community Support

Exchange 2010 - Management Console and Shell Very slow

Heya
I have an Exchange 2010 SP3 enviroment, with 2 HUBCAs and 5 MBX servers.
This servers were 2008 R2 standard, and they were working fine.
This weekend, in order to configure DAG, i upgrade 3 of them to server 2008 R2 enterprise with dsim. Is not the first tiem i do this, and never had problems before.
After the upgrade, the server started fine, the mailboxes, the database.. everything fine.. except, de mmc and the shell.
Both, the mmc and the shell wont start. It gives me the winrm error, but because a time out.
I have installed the installed the iss-winrm feature, delete on regedit and %appdata% the "cache" for the management console, checked the firewal... and nothing worked.
Well, thats not true, in one of the servers, the Management console started working fine, but the shell, it connect, but every command i launch it takes like 10-15 minutes to execute (for example, a get-mailboxdatabase).
In the other,, no the Management console, no the shell connects, i get a winrm timeout.
I dont know were to continue cchecking why happens this, just started after changing the 2008 R2 from standard to enterprise
Thanks for the help!!

Hi,
Please check that your time is in sync as well on your Exchange Server.
Please check whether this issue caused by performance.
More details in the following article:
Understanding Memory Configurations and Exchange Performance
http://technet.microsoft.com/en-us/library/dd346700(v=exchg.141).aspx
http://technet.microsoft.com/en-us/library/dd346699(v=exchg.141).aspx
Please also paste the detailed error message without sensitive information for the further troubleshooting.
Found some related blog for your reference:
Resolving WinRM errors and Exchange 2010 Management tools startup failures
http://blogs.technet.com/b/exchange/archive/2010/12/07/3411644.aspx
Troubleshooting Exchange 2010 Management Tools startup issues
http://blogs.technet.com/b/exchange/archive/2010/02/04/3409289.aspx
Thanks
Mavis
Mavis Huang
TechNet Community Support

Exchange 2010 SP3 DAG Flip Flop File Share Witness Issue

Hi All,
We are facing one strange issue with Exchange 2010 SP3.
Our environment is as below
a single DAG spanned accross 2 AD sites with 6 MBX server.
Each site have 3 MBx server.
File Share Witness is on Hub server in primary site.
Note: The DAG IP is from Primary DC VLAN and which cant be streched accross DC due to network restrictions/limitations.
It was working fine till date.
But, yesterday onwards we are facing issue.
All DB dismounted and DAG name disappear from EMC and while doing refresh its giving error as below
Exception type: Microsoft.Exchange.Data.DataValidationException
Exception message: Could not convert property WitnessServer to type UncFileSharePath. Error while converting string 'vesthub700.mydomain.com\DAG1.mydomain.com' to result type Microsoft.Exchange.Data.UncFileSharePath: "vesthub700.mydomain.com\DAG1.mydomain.com"
is not an acceptable path. You must use an absolute, local, long file path, that doesn't contain '~', or a UNC path. Parameter name: path
We are not able to execute any cmdlets related to databaseavailabilitygroup from EMS and its giving same error.
Failover Cluster DAG resource is Flip/Flip continuously.
Its only become stable after reboot of the hub server holding FSW and the 1st mailbox server.(Cluster Owner)
We are even not able to move cluster group to different server.
Performed ExBPA no such issues found which related to DAG.
Performed clsuter validation.
Only generic cluster events in Mailbox servers.
Observation:
Its only become stabe if we remove the msExchFileShareWitness Value for DAG1 using ADSIEdit.
And the problem recurs if we set it back again.
Any help or suggestion is appreciated.
Thanks,
soumen
Soumen Ghosh

Hi Belinda,
Thanks! I have checked the Mailbox Server Application Log and found few 2155 Event Id generated at the time of the issue occured.
Process Microsoft.Exchange.ServiceHost.exe () (PID=9312). Configuration object CN=DAG1,CN=Database Availability Groups,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=xxxxxx,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=mydomain,DC=com
read from DCTDK35.mydomain.com failed validation. DataValidationException will be thrown. Set event logging level for Validation category to Expert to get additional events about each failure.
One update is that the DAG is stable now after we set an alternate FSW last night.
Regarding the 2nd IP assignment for DAG for the 2nd subnet, we have gone through technet and other sites which refering to add the same from EMC or EMS.
Is it sufficinet to simply adding the 2nd IP to DAG from EMC or EMS? Or do we need to take any other special consideration.
Also, adding another IP it will create one more IP address resource to Failover Cluster, but I belive at a time both the IP wont be online. Do we need to keep it offline manually or its automatically taken care by Exchange.
Please suggest.
Also, regarding executing the CollectOverMetrics.ps1 we are following
http://www.msexchange.org/articles-tutorials/exchange-server-2010/monitoring-operations/monitor-dag-database-failover.html
but failed to execute. Can you suggest the correct parameter.
Thanks,
Soumen
Soumen Ghosh

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

SME 7.1 not working with Exchange 2010 SP3 UR8v2 and OnTap 8.2.3 7mode

Followed IMT and installed software that NetApp said would work.Ontap 8.2.3 7-modevmWare 5.0 SP3Microsoft Windows Server 2008 R2 SP1Exchange 2010 SP3 UR8v2NetApp Host Tools 6.0.2SnapDrive 7.1.1SME 7.1 Everything connects fine. SnapDrive sees my drives. SME connects to Exchange Server. However in the process of configuring SME, I get the following error. I have followed knowledge base article and increased the timeout of DFM connection in registry, but that has not solved the problem. Has anyone run into this before? SME 6.1 works fine, but is not compatible with SnapDrive 7.1.1 (causes verifications to fail because server can't mount clone) and lower SnapDrive versions are not compatible with Ontap 8.2.3. I am in a real bind here. Thanks in advance.

the following configuration for SME 7.1 is no longer supported: Windows Server 2008 R2Exchange 2010 SP3 RU1 – RU5WMF/PowerShell 3.0SME 7.1 The supported configuration will now be: Windows Server 2008 R2Exchange 2010 SP3 RU5WMF/PowerShell 4.0SME 7.1 this is because Microsoft does not support WMF 3.0 on Server 2008 R2 running Exchange 2010 SP3, with any RU version.SME 7.1 requires a minimum of PowerShell 3.0 (part of WMF 3.0) in order to run. Feel free to review the Exchange Server Supportability Matrix located here: https://technet.microsoft.com/en-us/library/ff728623%28v=exchg.150%29.aspx. All existing documentation (ISG, Admin Guide, IMT) will be updated shortly to reflect this change in requirements. hope that helps,Domenico.

Exchange 2010 - Errors 4002 and Errors 4010

I have two CAS and two Mailbox servers. All are running Server 2008 R2 with Exchange 2010 SP3 RollUp 5.
On one of my mailbox servers i am getting the error every 5 minutes, MSExchange Availability 4002.
Process 4904: ProxyWebRequest CrossSite from S-1-1-0 to https://server.domain.org:443/ews/exchange.asmx failed. Caller SIDs: NetworkCredentials. The exception returned is Microsoft.Exchange.InfoWorker.Common.Availability.ProxyWebRequestProcessingException:
System.Web.Services.Protocols.SoapException: The authenticated user doesn't have sufficient privileges to issue this request.
   at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall)
   at System.Web.Services.Protocols.SoapHttpClientProtocol.EndInvoke(IAsyncResult asyncResult)
   at Microsoft.Exchange.InfoWorker.Common.Availability.Proxy.Service.EndGetUserAvailability(IAsyncResult asyncResult)
   at Microsoft.Exchange.InfoWorker.Common.Availability.FreeBusyApplication.EndProxyWebRequest(ProxyWebRequest proxyWebRequest, QueryList queryList, Service service, IAsyncResult asyncResult)
   at Microsoft.Exchange.InfoWorker.Common.Availability.ProxyWebRequest.EndInvoke(IAsyncResult asyncResult)
   at Microsoft.Exchange.InfoWorker.Common.Availability.AsyncWebRequest.EndInvokeWithErrorHandling(). The request information is ProxyWebRequest type = CrossSite, url = https://server.domain:443/ews/exchange.asmx
Mailbox list = <lastname, firstname>SMTP:user@Domain, Parameters: windowStart = 2/1/2014 12:00:00 AM, windowEnd = 4/1/2014 12:00:00 AM, MergedFBInterval = 30, RequestedView = FreeBusy
. ---> System.Web.Services.Protocols.SoapException: The authenticated user doesn't have sufficient privileges to issue this request.
   at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall)
   at System.Web.Services.Protocols.SoapHttpClientProtocol.EndInvoke(IAsyncResult asyncResult)
   at Microsoft.Exchange.InfoWorker.Common.Availability.Proxy.Service.EndGetUserAvailability(IAsyncResult asyncResult)
   at Microsoft.Exchange.InfoWorker.Common.Availability.FreeBusyApplication.EndProxyWebRequest(ProxyWebRequest proxyWebRequest, QueryList queryList, Service service, IAsyncResult asyncResult)
   at Microsoft.Exchange.InfoWorker.Common.Availability.ProxyWebRequest.EndInvoke(IAsyncResult asyncResult)
   at Microsoft.Exchange.InfoWorker.Common.Availability.AsyncWebRequest.EndInvokeWithErrorHandling()
   --- End of inner exception stack trace ---
. Name of the server where exception originated: Server. Make sure that the Active Directory site/forest that contain the user's mailbox has at least one local Exchange 2010 server running the Availability service. Turn up logging for the Availability
service and test basic network connectivity.
Every 10 minutes on my CAS servers i am getting the error MSExchange Availability 4010.
Process Microsoft.Exchange.InfoWorker.Common.Delayed`1[System.String]: Request from S-1-5-21-562707881-1060713641-168829947-11538 failed security checks.
I have adjusted the registry setting HKLM\System\CurrentControlSet\services\MSExchange Availability\Diagnostics from 0 to 5 on the CAS servers. I don't have an Availability Service under Services.
The errors keep occurring.

http://forums.msexchange.org/m_1800549466/printable.htm
Refer This Link
DushYant'

Exchange 2010 accepted domain and email address policy

So I need some help as to which accepted domain is right for us. We are a single forest single domain that is subbed to a parent domain.
sub.domain.com
We run our own exchange 2010 separate from domain.com. We want all mail to show up as @domain.com for our users. The @domain.com will be configured to forward to @sub.domain.com. This is free Linux mail server that is separate from us.
In order to configure an email address policy for @domain.com I need to pick from the 3 types. I am pretty sure we are not authoritative for @domain.com (they are the parent). So it is either an internal relay or external relay. We all
use the same networking, and our DNS servers point to domain.com as forwarders and they host a secondary copy of our DNS.
It is a little unclear as to which to use. I have gone to each account individually to test, and that works perfectly, but I would like to set this Globally.
Thanks
Tim

Hello,
Thank you for your post.
This is a quick note to let you know that we are performing research on this issue.
If you have feedback for TechNet Subscriber Support, contact
[email protected]
Simon Wu
TechNet Community Support

Exchange 2010 calendar(free and busy) cannot work

Hi All
We have a new setup exchange 2010 server.
Everything(Webmail, outlook, autodiscover, out_of_office) is working fine.
When the user check other user calendar, it is not work(no matter in Outlook 2010 or OWA), is there any idea?
Thanks

Hi there
All the user is located in the same site.
The most weird problem is the user using the OWA for checking their own free and busy, it is show no information.
I have tried o use remote connectivity analyzer and the test-outlookwebservice
RunspaceId : b08124f2-b525-4e34-93f0-ca3c6c7134a9
Id : 1011
Type : Error
Message : When querying Availability for the recipient e-mail address abc@xxx, the following error code and
message were received: ErrorServiceDiscoveryFailed:Unable to find a Client Access server that can serve a
request for an intraforest mailbox <abc>SMTP:abc@xxx.
RunspaceId : b08124f2-b525-4e34-93f0-ca3c6c7134a9
Id : 1025
Type : Error
Message : [EXCH] Error contacting the AS service at https://xxx/EWS/Exchange.asmx. Elapsed time was
12 milliseconds.
RunspaceId : b08124f2-b525-4e34-93f0-ca3c6c7134a9
Id : 1013
Type : Error
Message : When contacting https://xxx/EWS/Exchange.asmx received the error The request failed with a
n empty response.
RunspaceId : b08124f2-b525-4e34-93f0-ca3c6c7134a9
Id : 1025
Type : Error
Message : [EXPR] Error contacting the AS service at https://xxx/EWS/Exchange.asmx. Elapsed time was
249 milliseconds.
But those ews path can be reach when using the browser
Thanks

Exchange 2010 Certificates, IPs, and Domain Names...

I'm setting up a new Exchange 2010 server, migrating from an old Exchange 2003.
I'm at the point now where I'm stuck and cannot move the mailboxes of the users to the new server until I get the new server setup with certificates, reconfigure the firewall, and more Aname records. ... reason, I'd like to take advantage of the autodiscover,
sync, outlook anywhere, etc.
I've been tossing ideas around but I think I'm over thinking this entire thing on domain names, anames, certificates, etc.
Can someone tell me what the best practice would be for creating the CSR? And I'm a bit curious as to IPs.
While the examples in the New Exchange Certificate wizard all show 'mail.contoso.com' I wanted to be more specific on the functions of each but maybe I'm causing myself a lot of extra work. Each full aname needs pointed to a different public IP from my understanding
of the certificates. Can anyone tell me if this approach(below) is best practice or far from it?
I'm very intrigued with the capabilities but dont' understand why MS would use as an example the same domain name, mail.contoso.com for each function. But it may be because they'd just have to point to one IP address whereas I'll have to point several IPs
public to a single IP internal.
I'm just asking for suggestions... and ideas... and how you setup your exchange 2010
I was going to create:
Outlook Web App:
webmail.domainname.com,domainname.com
Sync:
sync.domainname.com,domainname.com
Autodiscover:
domainname.com
Outlook Anywhere:
outlook.domainname.com, domainname.com

Not sure I understand - but why do you want to map each individual service to an individual public IP ? Usually the trend is to keep as little public IPs as possible (you can get away with 1 public IP for the CAS role). For autodiscover, I've usually seen
the autodiscover.domainname.com being used, due to the domainname.com reserved (public site) - this actually keeps inside the logic used by Outlook clients to autodetect the servers (see
this link).
As for the Subject Alternate Names (SANs) on the certificate itself - it all depends whether you're publishing the server directly (in this case you'll want to get away with as little SANs as possible) or you'll use a reverse proxy (TMG/WAP) to publish the
internal box (in this case the certificate on the reverse proxy can contain little SANs, but the internal server can have SANs map to each service if you want).
Also - Allen's link is a definitely must read.

Exchange 2010 3 node DAG and split datacenters

Similar Messages

Maybe you are looking for