Exchange 2013 - Delivery Groups, Routable DAGs and Delivery Queues

Hey Team,
I am trying to better understand Exchange 2013 Delivery Groups and Boundaries. I think I have it almost figured out, I reviewed this article here which helped clear it up for me:
http://www.msexchange.org/articles-tutorials/exchange-server-2013/planning-architecture/exchange-2013-mail-flow-part2.html
I need to understand the difference between and exchange 2013 delivery and how a delivery is group is different from the way that Exchange 2010 routed mail.
For some reason I am just not getting the differences between 2013 and 2010 in terms of message delivery.
Thanks,
Robert
Robert

Hi,
In Exchange 2013 there are only two roles, while five roles in Exchange 2010. There is difference between Exchange 2010 and Exchange 2013 on mail delivery.
The following articles can help you to understand the difference of mail delivery between Exchange 2010 and Exchange 2013.
Mail routing (For Exchange 2013)
http://technet.microsoft.com/en-gb/library/aa998825(v=exchg.150).aspx
Understanding Message Routing (For Exchange 2010)
http://technet.microsoft.com/en-gb/library/aa998825(v=exchg.141).aspx
Hope this is helpful to you.
Best regards,
If you have feedback for TechNet Subscriber Support, contact
[email protected]
Belinda Ma
TechNet Community Support

Similar Messages

Delivery not before date and Delivery not after date

Hi Everyone,
Can anyone help me in this issue, we need to map "delivery not before date" and "delivery not after date" from an EDI 850 into a sales order.
Are there any fields to which we can map the data? if not would anyone suggest how to go about it?
Thanks,
Michelle.

Michelle,
We have a similar requirement, albeit we call it a Delivery Window. We have implemented this by mapping two E1EDK03 qualifiers (we use 033 & 034) to two Z fields extended to VBAK, which we then include in our Sales Order Delivery Date logic.
Not very elegant, but then my understanding is that SAP has no concept of the Delivery Window.
Cheers, Paul.

Exchange 2013 Windows Server 2012 NLB and DAG on the same server

Hi all, I am installing Exchange 2013 infrastructure with two servers.
Both servers have the CAS and Mailbox roles.
For mounting on High Availability, will create a DAG.
Client Access I have no external Network Load Balancer.
I thought about installing the NLB servers in the DAG members, this could not be done before.
I do not know if in Windows Server 2012 and Exchange 2013
Can I install NLB on members of a DAG?
regards
Microsoft Certified IT Professional Server Administrator

Hi,
I’m afraid that WNLB and DAG cannot coexist in the same server. Because WNLB is incompatible with Windows failover clustering. If we're using an Exchange 2010 DAG and we want to use WNLB, we need to have the Client Access server role and the Mailbox server
role running on separate servers.
For more information, you can refer to the following article:
http://technet.microsoft.com/en-us/library/ff625247(v=exchg.141).aspx
Thanks,
Angela Shi
TechNet Community Support

Unable to send to external email recipients - Multi Tenant Exchange 2013 - MultiRole servers in DAG

Greetings all, I hope someone can help.
I have created a Exchange 2013 multi-tenant organization, with two servers, both multi-role - CAS and Mailbox roles.
Internal mail flow is fine (external email addresses can send to the domain).
External firewall port forwards ports 443 and 25 to the Internal DAG IP address.
There are two multi-role Exchange servers that are members of the DAG.
I am able to connect to OWA and ECP via https://externalIP/OWA and https://alias.domain.com/OWA
No SSL certificates have been purchased or installed yet.
Exchange URLs have not been changed since default configuration at install.
OWA and ECP works both internal and external.
External DNS works with SPF and PTR records correctly configured
Exchange RCA - Send test only fails with one Spam Listing (this Blacklist provider now flags all domains and you cannot ask to be removed)
Send Connectors are the default ones created during install. Receive connector is standard configuration with - * -
When sending email to an external address, I receive a failure notice
ServerName.test.corp.int gave this error:
Unable to relay
Your message wasn't delivered due to a permission or security issue. It may have been rejected by a moderator, the address may only accept email from certain senders, or another restriction may be preventing delivery.
More Info -
ServerName.test.corp.int
Remote Server returned '550 5.7.1 Unable to relay'
I have been troubleshooting this for many hours with no progress.
I have created new Send Connectors for the server that is advising that it is unable to relay, but they have all failed.
I have tried setting the Internal IP address for Exhange Server 1 (Exchange Server 2 reports failure), with most combinations of Security (Anonymous, Exchange Users, etc).
I have also tried with the IP range 192.168.11.0/24 to allow the whole the subnet, I still receive the unable to relay failure notice.
I have tried this guide - hxxps://glazenbakje.wordpress.com/2012/12/30/exchange-2013-how-to-configure-an-internal-relay-connector/ - with different combinations, still no resolution.
I am at a loss as to why I can't send out with the default configuration. I would assume that email would flow out without any changes, but this does not happen.
Can someone please assist before I lose my sanity.
Thanks in advance,
Terry

Greetings all, I hope someone can help.
I have created a Exchange 2013 multi-tenant organization, with two servers, both multi-role - CAS and Mailbox roles.
Internal mail flow is fine.
Incoming mail from external senders is also fine. -
external email addresses can send to the domain).
External firewall port forwards ports 443 and 25 to the Internal DAG IP address.
There are two multi-role Exchange servers that are members of the DAG.
I am able to connect to OWA and ECP via https://externalIP/OWA and https://alias.domain.com/OWA
No SSL certificates have been purchased or installed yet.
Exchange URLs have not been changed since default configuration at install.
OWA and ECP works both internal and external.
External DNS works with SPF and PTR records correctly configured
Exchange RCA - Send test only fails with one Spam Listing (this Blacklist provider now flags all domains and you cannot ask to be removed)
Receive Connectors are the default ones created during install. Send connector is standard configuration with - * -
When sending email to an external address, I receive a failure notice
ServerName.test.corp.int gave this error:
Unable to relay
Your message wasn't delivered due to a permission or security issue. It may have been rejected by a moderator, the address may only accept email from certain senders, or another restriction may be preventing delivery.
More Info -
ServerName.test.corp.int
Remote Server returned '550 5.7.1 Unable to relay'
I have been troubleshooting this for several days with no progress.
I have created new Receive Connectors for the server that is advising that it is unable to relay, but they have all failed.
I have tried setting the Internal IP address for Exhange Server 1 (Exchange Server 2 reports failure), with most combinations of Security (Anonymous, Exchange Users, etc).
I have also tried with the IP range 192.168.11.0/24 to allow the whole the subnet, I still receive the unable to relay failure notice.
I have tried this guide - hxxps://glazenbakje.wordpress.com/2012/12/30/exchange-2013-how-to-configure-an-internal-relay-connector/ - with different combinations, still no resolution.
Even more info - Further troubleshooting -
I found my one of my Exchange servers had an extra NIC. I have since added a second NIC to the other server, so now both Exchange servers have dual NICs. I removed the DAG cleanly and recreated the DAG from scratch, using this link -
hxxp://careexchange.in/how-to-create-a-database-availability-group-in-exchange-2013/
The issue still exists, even with a newly created DAG. I also found that the Tenant Address Books were not 'applied'. I applied them but still no resolution
I think the issue is related to multi-tenant configuration even though the error says that it can't relay. The unable to relay message can appear when sending from a domain that the Organization does not support. Like trying to email as [email protected]
when you domain name is apple.com - But through extensive research I still can't resolve the issue.
Can someone please assist before I lose my sanity.
Thanks in advance,
Terry

Moving witness server to CAS server two Exchange 2013 servers with a DAG

Inherited a situation where there is one Exchange 2007 Build 83.6 server running on Win2008R2, acting as witness, and hub transport and yes is a file server too. In addition there is relays, email and service accts that need to be moved to Exchange
2013.
Presently there are two Exchange 2013 cu3 servers that are part of a DAG that also run on Win 2008r2... We wish to add another node to the DAG, and move the witness to another server.
Do I need to also add a CAS Exchange 2013 server to replace the Ex 2007 server?
Can this server also act as the Witness?
What would be the best practices for this senario. All of these machines are VM's.

Inherited a situation where there is one Exchange 2007 Build 83.6 server running on Win2008R2, acting as witness, and hub transport and yes is a file server too. In addition there is relays, email and service accts that need to be moved to Exchange
2013.
Presently there are two Exchange 2013 cu3 servers that are part of a DAG that also run on Win 2008r2... We wish to add another node to the DAG, and move the witness to another server.
Do I need to also add a CAS Exchange 2013 server to replace the Ex 2007 server?
Can this server also act as the Witness?
What would be the best practices for this senario. All of these machines are VM's.
With an odd number of nodes, the File Share Witness will not be used, but you can still define it.
Any server ( any including any non-Exchange server) can serve as the FSW as long as its not a mailbox server n the DAG and it has the Exchange Trusted SubSystem group in the local admin group on that server.
Since you are using VMs, ensure the FSW isn't on the same host as a MBX DAG member.
Not sure what you mean by adding a CAS Exchange 2013 server. Do you mean you have not installed the CAS role yet for 2013? If so, then absolutetly you need one.
Twitter!: Please Note: My Posts are provided “AS IS” without warranty of any kind, either expressed or implied.

Exchange 2013 SP1 Object is corrupted and inconsistent state after Lync 2013 Installation

Hi Fellows,
I am facing an issue with Exchange 2013 SP1 (5.0.847.32)
environment. I recently installed Lync 2013 (version: 5.0.8308.0) a week ago and just recently start getting the below error when configuring delegation or modifying the users/groups from Exchange Control Panel:
"The Object <object DN> has been corrupted, and it's in an inconsistent state. The following validation errors happened:
The access control defines the ObjectType <object guid> that can't be resolved.."
I can see some forum threads with same issue (links given below) but unable to find if this is a known issue and how to get it resolved. Need assistance if anyone has faced same and could help me out to figure it.
http://social.technet.microsoft.com/Forums/exchange/en-US/72310530-d1de-4b39-a0fb-1592247df03f/access-control-entry-issue-after-installing-lync-2013-into-the-forest?forum=exchangesvrdeploy
http://www.networksteve.com/exchange/topic.php/Issue_with_exchange_2013_lync_2013_intergration/?TopicId=37192&Posts=2
J.A

Hi
Usually the affected SID objects are referring to deleted objects.
Use the PsGetSid tool to try to resolve them.

Exchange 2013 issues along with toolbox and exchange powershell

I have a server 2012 with exchange 2013, no errors on install, we have about 50 user mailboxes setup. about 3-5 times a day sending and receiving will stop working, we have to reboot about 3 or 4 times then it starts working again.
Also the Exchange power shell doesnt work, we get :
VERBOSE: Connecting to NVSVMSX.KATV.local.
New-PSSession : [nvsvmsx.katv.local] Processing data from remote server nvsvmsx.katv.local failed with the following
error message: [ClientAccessServer=NVSVMSX,BackEndServer=nvsvmsx.katv.local,RequestId=3c4178cd-3e21-4ebf-9c65-23e5855cf
17f,TimeStamp=11/11/2014 6:53:03 PM]
[AuthZRequestId=b12c2ecf-ff1f-42df-b0f8-441878180bfa][FailureCategory=AuthZ-CmdletAccessDeniedException] The user
"KATV.local/Computers/NVSVMSX" isn't assigned to any management roles. For more information, see the
about_Remote_Troubleshooting Help topic.
At line:1 char:1
+ New-PSSession -ConnectionURI "$connectionUri" -ConfigurationName Microsoft.Excha ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : OpenError: (System.Manageme....RemoteRunspace:RemoteRunspace) [New-PSSession], PSRemotin
gTransportException
+ FullyQualifiedErrorId : IncorrectProtocolVersion,PSSessionOpenFailed
we get that 3 times then nothing.
Also on the Toolbox we get MMC error
"Type is not resolved for member "Microsoft.Exchange.Configuration...."
Please help, we are at a loss and not sure what to do at this point, we have looked every where for a permissions issue and have found nothing so far.
thank you
BD

Hi,
Please check if this user was in Organization Management Group. If not, please use the following cmdlet to add this user to this group.
Add-RoleGroupMember “OrganizationManagement” -Member <member>
If this issue still exists, Run Setup /PrepareSchema and Setup /PrepareAD again.
In addition, please refer to this similar thread
https://social.technet.microsoft.com/Forums/sharepoint/en-US/33038c63-a993-4032-9355-023ae91a1c6a/cant-access-ecp-after-install?forum=exchangesvrdeploy
And hope KB 2898571 will be helpful for you.
To solve ToolBox issue, please try to install or uninstall ASP.NET 4.5 on Windows 8 or Windows Server 2012, use one of the following options:
Run the following command from an administrative command prompt: dism /online /enable-feature /featurename:IIS-ASPNET45
For Windows 8 client computers, turn on "IIS-ASPNET45" in "Turn Windows Features On/Off" under "Internet Information Services-> World Wide Web Services -> Application Development Features -> ASP.NET 4.5".
For Windows Server 2012 computers, enable "IIS-ASPNET45" using Server Manager, under "Web Server (IIS) -> Web Server ->Application Development -> ASP.NET 4.5".
Refer from
http://support.microsoft.com/kb/2736284
Best Regards.

Can't uninstall Exchange 2013 - (Distribution groups)

I need help uninstalling Exchange 2013. The uninstaller fails with these 2 errors:
This computer is responsible for expanding the membership of 1 distribution groups. These groups must be reassigned to another server before Setup can continue.
This computer is responsible for expanding the membership of 1 dynamic distribution groups. These groups must be reassigned to another server before Setup can continue.
I've gone so far as to disabling all distribution groups which removes its email properties and the uninstaller still fails.
This is what happens in the eventlog:
System.Management.Automation.ParseException: At line:1 char:67
+ Get-DynamicDistributionGroup | where {$_.ExpansionServer -eq '/o='s-Hertogenbosc ...
+ ~~~~~~~~~~~~~
Unexpected token 's-Hertogenbosch/ou=Exchange' in expression or statement.
At line:1 char:175
+ ... s/cn=CADEXCDB13'}
+ ~~
The string is missing the terminator: '.
At line:1 char:38
+ Get-DynamicDistributionGroup | where {$_.ExpansionServer -eq '/o='s-Hertogenbosc ...
+ ~
Missing closing '}' in statement block.
at System.Management.Automation.PowerShell.EndInvoke(IAsyncResult asyncResult)
at Microsoft.Exchange.Configuration.MonadDataProvider.MonadPipelineProxy.ClosePipeline(MonadAsyncResult asyncResult)
] [ParentValue:"<NULL>"] [Thread:11] [Duration:00:00:00.0156248]
I'm sure what happens here is the powershell commands looking at the distribution groups fail, because of our city name ('s-Hertogenbosch). Because of the apostrophe, the parameter is not passed successfully of this legacyExchangeDN. As this check fails,
I believe the readiness check fails on these steps.
This legacy administrative group name is still left from a 2003 -> 2010 -> 2013 migration.
I've opened a Microsoft support request for this last week, but I thought someone might have dealt with this? I want to do a clean uninstall if possible.

After I removed the distribution groups, I did restart the server.
The problem is the the powershell script to check for existing distribution groups use a single quote to pass the server name to it. The server name contains a single quote itself so the parameter is not passed successfully. If the powershell script
used a double quote it would pass the parameter correctly.
This works:
Get-DistributionGroup | where ExpansionServer -eq "/o='s-Hertogenbosch/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Configuration/cn=Servers/cn=CADEXCDB13"
This does not work:
Get-DistributionGroup | where ExpansionServer -eq '/o='s-Hertogenbosch/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Configuration/cn=Servers/cn=CADEXCDB13'
Do you see the difference? (Parameter is passed in a single or double quotation)

Exchange 2013 issue / OWA time-out and WiFi/Cell problem.

Hi everybody,
I'm having some issues with an Exchange 2013 server.
When some users try to logon to the OWA page it keeps loading the page and ends with a time-out.
This only applies to 6 or 7 users, other users can login and open the page.
I tried to replace the signed certificate to solve this problem, and did a online analyzer check, most tests come out good.
I can't seem to find the source of this problem.
There are also multiple users that are having trouble to receive e-mail through the wifi on phones and tablets at home but when they switch to 3g it works fine.
You might need more information, just ask.. i don't know where to search anymore.
I tried inheritance on the AD, disabled SSL in the IIS, restarted the server, replaced the signed cert. etc.
Update:
I set the selfsigned cert in the IIS default web page,, to check if it responds to the certificate and it does, so the issue doesn't come from the certificate.
This issue probably came up after CU1, and i've read something about healthboxes..
I'm going to install CU6 and hope for good result.
Kind regards,
Tim

I've installed CU6, only one of the six users have gained access to OWA or ECP.
Al the other users won't get a logon screen, just a blank page.
So there is no option to insert a username or password to login, the page keeps loading and ends with "the page cannot be displayed"
But on my working spot i can open owa or ecp without any issues.
I've recreated the virtual directory for ECP and OWA with powershell, and checked the certificate.
I checked if the same certificate was connected to the back-end port 444, and this is set correct.
I even reconnected the cert on 444 with the following.
Open the Command Prompt
Run-
netsh http show sslcert
This will show the certs, copy and paste this information into notepad. Under IP:port : 127.0.0.1:443, note the certificate hash and application ID.
Run this command- (Yes, I know there is no :444 listed in the output from the earlier command.)
netsh http delete sslcert ipport=0.0.0.0:444
Run this command. Replace certhas with the certificate hash and appid with the application ID you saved in notepad.
netsh http add sslcert ipport=0.0.0.0:444 certhash=123123123123123 appid="{123123123123-1231231235}"
I used powershell to set the login authentication,
et-Owavirtualdirectory -identity "YourMailBoxServerName\owa (Exchange Back End)" -WindowsAuthentication $True -Basicauthentication $false -Formsauthentication $false
set-Owavirtualdirectory -identity "YourCASserverName\owa (Default Web Site)" -WindowsAuthentication $True -Basicauthentication $false -Formsauthentication $false
and iisreset /noforce
I unchecked the "require SSL" on the default website and left it enabled on the owa and ecp etc.
Checked if HTTP over Proxy is installed, but this one is need to install exchange 2013.
I've checked all ECP/OWA directories in in the IIS, the directories point to the Exchange V15 folders, this should be correct.
Something is really broken, i really can use the help..
I'm going to try to install Exchange 2013 SP1, but i don't know if this one is needed when CU6 has been installed.
The strange thing is, it seem to be location based, not user based.
I can login perfectly, but when i try this at one of the employees, it ends up blank.
When i try to connect on a location dat does not work, at the exact time i press the enter-key to open the page, the eventviewer logs the following:
Event 4634 - An account was logged off.
For the issue on the smartphones and tablets, everything worked fine a few months ago, and happens to users on different ISP connections.
I already checked the inheritance settings on the users in the AD.
Kind regards,
Tim

Exchange 2013 owa integration with ADFS and cooexistance with exchange 2007

Team,
I have successfully integrated adfs 3.0 and Exchange 2013 owa and ecp. However, we have a coexistence environment with exchange 2007. When you access owa, which then redirects you to adfs, sign-in, and then get redirected back to owa. If your
mailbox is still within exchange 2007, you get a blank login page. If you mailbox is in exchange 2013 then you successfully get the owa page for 2013. The problem is that all exchange 2007 mailbox users get blank pages at login. So I have determined
that exchange 2013 cas is not doing the service location lookup on the mailbox to determine if a redirect to the legacy owa address is needed. Is there a configuration setting that I might be missing? Or does the integration with adfs and owa not support
the much needed mailbox lookup for a coexistance environment? A side note: if we enable FBA with owa, both login scenarios work just fine (legacy and new 2013). The legacy namespace has been created, and applied to the exchange 2007 urls.

Hi,
Try using AD FS claims-based authentication with Outlook Web App and EAC
http://technet.microsoft.com/en-us/library/dn635116(v=exchg.150).aspx
Thanks,
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
[email protected]
Simon Wu
TechNet Community Support

Exchange 2013 IOPS Requirements for ActiveSync and anti-virus

I am currently planning to replace my Exchange 2003 server with Exchange 2013. I have used the Exchange Server 2013 Role Requirements Calculator but I'm stuck on how much additional IOPS to add for ActiveSync and my anti-virus solution (Symantec Mail Security
for Microsoft Exchange). The only info I've found for ActiveSync in regards to additional IOPS is to add .5 but nothing for SMSMSE. Symantec's web site has nothing on this (the question has been asked but not answered). I've also seen the ActiveSync question
asked but not answered.
Any advice or guidance would be appreciated.
Thank you.

Only Symantec can answer that for the A/V, but for ActiveSync, assuming you are using mostly Android/iOS, I would recommend using 1.3 for both IOPS Multiplication Factor and Megacycles Multiplication Factor.
Twitter!: Please Note: My Posts are provided “AS IS” without warranty of any kind, either expressed or implied.

Exchange 2013 -Distribution Group

Hi … Let me explain my issues here. I am the Part of DL called Itadmins in exchange server 2013. When ever I send a mail to itadmins I am getting copy of the mail back to me again. Is this expected behavior in exchange server 2013 ?
Regards, Srinivasu.Muchcherla

That's the expected behavior in any Exchange version... A message sent to a distribution group is delivered to all users that belongs to that DL including sender...
Blog |
Get Your Exchange Powershell Tip of the Day from here

Exchange 2013 and DKIM

Exchange 2013 SP1 with 1 DAG and 2 members. We are thinking about using DKIM:
http://www.emailarchitect.net/webapp/download/eaexchdomainkeys.exe
First, is this the recommended DKIM app to use or is there a different/better one? Second, we host many domains on our exchange servers. Is it possible to use DKIM with many domains? Third, if we use DKIM do we need to install DKIM on both exchange servers?
Both servers have all roles installed.

Hello, as recommended
earlier on the use DKIM in EDGE Exchange 2013 or 3rd party GW (Li Zhen)
DKIM Exchange
Server 2007/2010/2013
DKIM
Wizard
dkim-exchange
MCITP, MCSE.
Regards, Oleg
That top link is the same link i originally asked about. We may be able to do a hyper-v VM for edge server. Can this be done with an existing exchange install/setup?

Migration questions from Exchange 2007 to Exchange 2013

Dear Forum Members,
I'd ask just two short questions, regarding a migration from Small Business Server 2008 (Exchange 2007) to 2013. We installed the two Exchange 2013 servers, configured a DAG and updated every single URL (OWA, ECP, AnyWhere, Autodiscover etc.) to be a mail.domain.com
record (DNS round robin, since no HW load balancer :( )
Thankfully, the mail flow between the Internet and the other Exchange 2007 users are still working. Now for those users I've already migrated, if I check outlook connections there are several connections for GUID based servers via the DNS Round Robin
name proxy (the AnyWhere address). But I saw that there are still just one connection (type: Exchange Public Folders) to the old 2007 server. Is it okay? I'm a bit afraid to uninstall it because of this.
And the other thing: Based on what I wrote, do you think I've done it good? Or could I miss any important things? You are much experienced than me in these migrations so I hope that I can get some confirmation/advice here :(
ps: Is it good if I set NTLM authentication for Outlook AnyWhere?
Thank you really much for your help,
Best Regards,
Chris

Hi Chris,
Agree with Hinte, the user will still connect to the exchange 2007 server if there is a public folder database in the old server.
If the old public folders are no longer in use, you can delete the public folder database and create a new one in the exchange 2013 server, you can also consider migrating public folders to Exchange 2013 .
The following articles for your reference:
Use serial migration to migrate public folders to Exchange 2013 from previous versions
Set up public folders in a new organization
Step-by-Step Exchange 2007 to 2013 Migration
>>Is it good if I set NTLM authentication for Outlook AnyWhere?
The Outlook Anywhere authentication method you choose will depend on a few factors in your environment,
I recommend you refer to the following thread to understand how to choose:
https://social.technet.microsoft.com/Forums/exchange/en-US/75f8d6c4-70f4-49e5-ac32-a49dd91b5520/outlook-anywhere-ntlm-for-internal-users-and-basic-for-external-users?forum=exchangesvrclients
Exchange 2013: Configuring Outlook anywhere
Best 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]
Niko Cheng
TechNet Community Support

Exchange 2013 MP and DAG

Hi.
We got strange issue with Exchange 2013 MP. Some components in DAG are in state "Not monitoring". For example:
"Exchange 2013 Service Components" on DAG members not motitored:
Mailbox Count in organization is null:
And DAG object is in the "Not monitored" state too.
MP was installed as described in documentation (account, profile, etc.).
Proxy on DAG members enabled.
Any ideas how to troubleshoot this issue?
P.S. MP - 15.0.665.19, Exchange - CU6

Hi,
I would like to suggest you recheck Exchange 2013 Management Pack Pre-requisites and Considerations.
Before importing the Exchange 2013 MP into System Center Operations Manager, there are some pre-requisites that have to be met:
You have one of the following versions of System Center Operations Manager deployed in your organization:
System Center Operations Manager 2012 RTM or later
System Center Operations Manager 2007 R2 or later
You have already deployed SCOM agents to your Exchange Servers.
The SCOM agents on your Exchange Servers are running under the local system account.
The SCOM agents on your Exchange Servers are configured to act as a proxy and discover managed objects on other computers.
If you are monitoring Exchange Server 2013 Database Availability Groups (DAGs), ensure that all DAG members are monitored by Operations Manager.
You may refer to the link below for more details:
http://www.msexchange.org/articles-tutorials/exchange-server-2013/management-administration/monitoring-exchange-2013-scom-2012-part2.html
Regards,
Yan Li
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact [email protected]

Exchange 2013 - Delivery Groups, Routable DAGs and Delivery Queues

Similar Messages

Maybe you are looking for