Exchange 2013 SP1 EDGE role content filtering ?

Hello,
Have Exchange 2013 SP1 with CU5 with antispam enabled on mailbox role server. And i wonder if i deploy 2013  Edge role, will i get more granular content filter control, like there is in Office 365? For example: i want to treat empty messages as not
spam.
I have read that control of Edge server is done ONLY by powershell. So if edge role is deployed, still there is no content filter control in ECP (like in office365) ??

Hi,
The Content Filter agent assigns a spam confidence level (SCL) rating to each message. The SCL rating is a number between 0 and 9. A higher SCL rating indicates that a message is more likely to be spam.
Based on my knowledge, I'm afraid we can't filter the empty messages and treat them as not spam.
Here is an article about content filtering in Exchange 2013 for your reference.
Content Filtering
http://technet.microsoft.com/en-us/library/bb124739(v=exchg.150).aspx
Best regards,
If you have feedback for TechNet Subscriber Support, contact
[email protected]
Belinda Ma
TechNet Community Support

Similar Messages

  • Exchange 2013 SP1 - Edge Tranport Role

    Hi.
    When Exchange 2013 was released only CAS & Mailbox roles where available. Hub & Edge Transport server roles were discontinued.
    Now with Exchange 2013 SP1, the edge transport role has came back.
    Question:
    1. Can I deploy a new Exchange 2013 Infrastructure without the Edge Transport Role. This will be a fresh deployment.
    I plan to have a UTM with spam blocking at the perimeter instead of the Edge Server?
    2. will there any be problems without an Edge Transport ?
    Thanks,
    Paul

    Hi ,
    Please find the below mentioned points .
    1. Can I deploy a new Exchange 2013 Infrastructure without the Edge Transport Role. This will be a fresh deployment.
    I plan to have a UTM with spam blocking at the perimeter instead of the Edge Server?
    Answer :
    Just ensure that the product is having all the features as you need on your side .There is not necessary to have a an edge server in all the exchange environment's. Moreover Gateway and anti spam products will differ as per the company requirements.
    2. will there any be problems without an Edge Transport ?
    Answer :
    If you are having any one the anti spamming solution to have all the emails scanned before it reaches the exchange server then it will be good .
    Just ensure that the anti spamming product what you are going to use is mainly doing the reverse dns lookup
     and spf look up .With the help of that we can able to avoid large no of forged emails.
    Regards
    S.Nithyanandham

  • Exchange 2013 SP1 mailbox role on 2012 R2 and 2012

    Hi,
    We have a client who were running the following setup:
    2 x Exchange 2013 CU2 CAS servers / Win Srv 2012
    2 x Exchange 2013 CU2 MBX servers / Win Srv 2012
    Active Directory etc, basically everything else, runs on Win Server 2012.
    Due to upgrading etc, one of the mailbox servers has been removed. It is to be installed with Ex2013 SP1 with 2012 R2 from scratch, and eventually also upgrade the remaining CAS and MBX srvers with SP1 and 2012 R2.
    So my question is..will this present a problem? Is it possible to have one MBX running 2013 CU2 on Server 2012 and one MBX running 2013 SP1 on Server 2012 R2?
    I've read that failover clustering service is not possible between 2012 and 2012 R2, but i'm not sure how this effects Exchange.
    Thanks for your time.

    Hi,
    Each member of the DAG should be running the same operating system. It is not supported to run a DAG member on Windows Server 2012 R2 and run another member on  Windows Server 2012.
    What's more, upgrading the OS is not supported on Exchange server.
    Here are some helpful threads for your reference.
    Planning for High Availability and Site Resilience
    http://technet.microsoft.com/en-us/library/dd638104(v=exchg.150).aspx
    Exchange 2013 CU2 and Upgrading from Server 2012 to Server 2012 R2 issues
    http://social.technet.microsoft.com/Forums/exchange/en-US/afba40de-efb6-4916-ae42-b09cff35e5d7/exchange-2013-cu2-and-upgrading-from-server-2012-to-server-2012-r2-issues
    Hope it helps.
    Best regards,
    If you have feedback for TechNet Subscriber Support, contact
    [email protected]
    Amy Wang
    TechNet Community Support

  • Exchange 2013 and edge role

    Hi,
    I have all exchange role installed all is working fine without edge role. CAS is load balance with nbl and MBX is with DAG. If i involve edge do i have to deploy multiple role and do same NBL for load balance, if i invovle what would be my dns setting will
    this point to edge role, what owa url will point to edge or remains on cas if on edge do Edge have to redirect to cas or ressovle itself the request. 
    Your Guideline regarding edge
    thanks 

    Hi shani,
    Thank you for your question.
    If i involve edge do i have to deploy multiple role and do same NBL for load balance
    A: if we want to receive/send email from/to Internet though Edge, we could deploy Edge server in DMZ, if we want to configure Edge server 
    redundancy and load  balance, we could install multiple Edge servers in DMZ. We suggest we put a Hub Transport server into each site, and then establish a 1:1 ratio of Hub Transport to Edge Transport servers. In such a configuration,
    each Hub Transport server is synchronized to only one Edge Transport server. And each Edge Transport server connect to a separate Internet connection through different ISPs. Servicing multiple Edge Transport servers with a single ISP creates a potential single
    point of failure. Using multiple ISPs ensures that if you will still have Internet access, even if there is an ISP problem.
    what owa url will point to edge or remains on cas if on edge do Edge have to redirect to cas or ressovle itself the request.
    A: As zhen’s said, we didn’t modify the URL to point to Edge. We just have MX record in ISP.
    If there are any questions regarding this issue, please be free to let me know. 
    Best Regard,
    Jim

  • Exchange 2013 SP1 Edge Transport Compatability

    Exchange 2013 CU3 CAS & MBX are on Windows 2012
    I would like to use a Exchange 2013 CU5 as an Edge Transport on a separate server running Windows 2012 R2.
    Is this compatible?

    Yes.
    http://technet.microsoft.com/en-us/library/ff728623(v=exchg.150).aspx
    Exchange Server Supportability Matrix
    Twitter!: Please Note: My Posts are provided “AS IS” without warranty of any kind, either expressed or implied.

  • Exchange 2013 SP1 setup fails at prerequisite Analysis

    I installed a completely new server network with Hyper-v 2012R2
    I installed two virtual 2012R2 servers: DC01 as the Domain Controller of "testdomain.local" and EX01 as the Exchange server.
    EX01 is joined the domain "testdomain" from DC01
    I log in on EX01 with an in AD created testdomain\exadmin account who is member of domain admins, enterprise admins, schema admins, administrators and group policy creator owners.
    I have run the command Install-WindowsFeature AS-HTTP-Activation, Desktop-Experience,
    NET-Framework-45-Features, RPC-over-HTTP-proxy, RSAT-Clustering, RSAT-Clustering-CmdInterface, RSAT-Clustering-Mgmt, RSAT-Clustering-PowerShell, Web-Mgmt-Console, WAS-Process-Model, Web-Asp-Net45, Web-Basic-Auth, Web-Client-Auth, Web-Digest-Auth, Web-Dir-Browsing,
    Web-Dyn-Compression, Web-Http-Errors, Web-Http-Logging, Web-Http-Redirect, Web-Http-Tracing, Web-ISAPI-Ext, Web-ISAPI-Filter, Web-Lgcy-Mgmt-Console, Web-Metabase, Web-Mgmt-Console, Web-Mgmt-Service, Web-Net-Ext45, Web-Request-Monitor, Web-Server, Web-Stat-Compression,
    Web-Static-Content, Web-Windows-Auth, Web-WMI, Windows-Identity-Foundation, Telnet-Client, RSAT-ADDS
    on EX01
    I have installed the Microsoft Unified Communications Managed API 4.0
    Then I run the Exchange 2013 SP1 setup and the prerequisite check gives the following errors:
    Error:
    You must be a member of the 'Organization Management' role group or a member of the 'Enterprise Admins' group to continue.
    For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.GlobalServerInstall.aspx
    Error:
    You must use an account that's a member of the Organization Management role group to install or upgrade the first Mailbox server role in the topology.
    For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.DelegatedBridgeheadFirstInstall.aspx
    Error:
    You must use an account that's a member of the Organization Management role group to install the first Client Access server role in the topology.
    For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.DelegatedCafeFirstInstall.aspx
    Error:
    You must use an account that's a member of the Organization Management role group to install the first Client Access server role in the topology.
    For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.DelegatedFrontendTransportFirstInstall.aspx
    Error:
    You must use an account that's a member of the Organization Management role group to install or upgrade the first Mailbox server role in the topology.
    For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.DelegatedMailboxFirstInstall.aspx
    Error:
    You must use an account that's a member of the Organization Management role group to install or upgrade the first Client Access server role in the topology.
    For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.DelegatedClientAccessFirstInstall.aspx
    Error:
    You must use an account that's a member of the Organization Management role group to install the first Mailbox server role in the topology.
    For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.DelegatedUnifiedMessagingFirstInstall.aspx
    Error:
    Setup encountered a problem while validating the state of Active Directory: Active Directory server  is not available. Error message: Active directory response: The LDAP server is unavailable.  See the Exchange setup log for more information on this
    error.
    For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.AdInitErrorRule.aspx
    Error:
    Either Active Directory doesn't exist, or it can't be contacted.
    For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.CannotAccessAD.aspx
    I can connect with the Active Directory Sites and Domains and other applets to the AD. So Why these errors???
    HELP!
    Regards, Manu
    Manu van Winkel

    Hi, thanks for the answer.
    I restarted the server and did the "run as administrator": same result.
    The first errormessage in the exchangesetup.log is:
    [ERROR] Setup encountered a problem while validating the state of Active Directory: Active Directory server  is not available. Error message: Active directory response: The LDAP server is unavailable.  See the Exchange setup log for more information
    on this error.
    When I run dcdiag /s:DC01 from EX01 it passes all tests except:
    DFSREvent "The RPC server is unavailable"
    KccEvent "The RPC server is unavailable."
    SystemLog  "The RPC server is unavailable."
    Could these be of any influence?
    Running dcdiag on DC01 passes all tests.
    The only thing I changed after setting up DC01, was changing the fixed IP-adres from 192.168.25.3 to 192.168.25.2, but I ran ipconfig /flushdns and ipconfig /registerdns and dcdiag /fix afterwards.
    The only roles installed on DC01 are AD DS (I tried installing exchange before and after adding the AD DS role), AD, DNS, DHCP and Fileservices
    I don't know where to look anymore....
    Manu van Winkel

  • Exchange 2013 SP1 Installation Errors I Cannot Resolve

    Good Afternoon All -
    Note:  I updated this post an hour after posting.  Still no solution, but please see updated info at end of this post)
    I'm trying to introduce Exchange into an existing, small environment.  The server I'm trying to install it onto is an SBS 2011 server (single server.)  Even though SBS comes with Exchange, I found out that it's installation was corrupted and someone
    had attempted to uninstall it before.  Yes, it's being installed onto a server with a DC.  I considered creating a Hyper-V VM on the server for Exchange, but thought it may be better to try to install directly onto server instead.
    Before I started, I made sure all Exchange data had been removed.  I checked for and deleted (if present) all Exchange-related objects in ADSI, ADU&C, files, and registry entries.
    When I try to install Exchange 2013 SP1, I get the below errors.  I know that some are easily resolved by installing pre-requisites - however - others aren't - especially the pending reboot one.  I've restarted the server many times when making
    changes or applying various updates and still get flagged to restart during installation.  I've tried the SBS 2011 repair disc as well, but had many issues with it.  In all honesty, the whole server needs to be wiped and re-installed, but
    cannot do at this point.
    Besides the errors below, I've zipped up the ExchangeSetupLogs folder and placed them in the link below.  Also below are system specs.  The only edit I made in them is a find/replace for server and domain name.
    ExchangeSetupLogs Folder
    System Specs
    Xeon E31270 3.4Ghz
    16gb RAM
    Windows Server 2011 SBS x64 (Domain Controller Role Installed & Used)
    C:\ - RAID 1 = 500gb
    D:\ - SATA HDD = 320gb
    E:\ - SATA HDD = 320GB
    Should I perhaps try to install to a VM on the server or think that would use too many unnecessary resources?
    Any help would be appreciated - Thanks!
    Error:
    This computer requires the update described in Microsoft Knowledge Base article KB2619234 (http://go.microsoft.com/fwlink/?LinkId=262359).
    Without this update, the Outlook Anywhere feature may not work reliably.
    For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.Win7RpcHttpAssocCookieGuidUpdateNotInstalled.aspx
    Error:
    There is a pending reboot from a previous installation of a Windows Server role or feature. Please restart the computer and then
    run Setup again.
    For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.PendingRebootWindowsComponents.aspx
    Error:
    The Windows component RSAT-Clustering isn't installed on this computer and needs to be installed before Exchange Setup can begin.
    For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.RsatClusteringInstalled.aspx
    Error:
    This computer requires the Microsoft Unified Communications Managed API 4.0, Core Runtime 64-bit. Please install the software from
    http://go.microsoft.com/fwlink/?LinkId=260990.
    For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.UcmaRedistMsi.aspx
    Error:
    An unsupported operating system was detected. Exchange Server 2013 Client Access, Mailbox, and Edge Transport server roles support
    Windows Server 2008 R2 SP1 or later and Windows Server 2012.
    For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.ValidOSVersion.aspx
    Warning:
    Installing Exchange Server on a domain controller will elevate the permissions for Exchange Trusted Subsystem to domain administrators.
    For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.WarningInstallExchangeRolesOnDomainController.aspx
    Warning:
    Setup will prepare the organization for Exchange 2013 by using 'Setup /PrepareAD'. No Exchange 2007 server roles have been detected
    in this topology. After this operation, you will not be able to install any Exchange 2007 servers.
    For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.NoE12ServerWarning.aspx
    Warning:
    Setup will prepare the organization for Exchange 2013 by using 'Setup /PrepareAD'. No Exchange 2010 server roles have been detected
    in this topology. After this operation, you will not be able to install any Exchange 2010 servers.
    For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.NoE14ServerWarning.aspx
    Ben K.
    UPDATE
    I just tried fixing a few things and tried again.  Still no luck.  Below is what I changed as well as the errors received.  Only option was Retry.  Can I just not install it onto this environment?
    What I Changed
    Installed Unified Comm Managed API 4.0 (Required Uninstalling Speech Analysis app before it would install)
    Installed KB2619234 for Outlook Anywhere
    Installed 12 updates - Server fully patched
    Exchange Setup Errors
    Error:
    An unsupported operating system was detected. Exchange Server 2013 Client Access, Mailbox, and Edge Transport server roles support
    Windows Server 2008 R2 SP1 or later and Windows Server 2012.
    For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.ValidOSVersion.aspx
    Warning:
    Installing Exchange Server on a domain controller will elevate the permissions for Exchange Trusted Subsystem to domain administrators.
    For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.WarningInstallExchangeRolesOnDomainController.aspx
    Warning:
    Setup will prepare the organization for Exchange 2013 by using 'Setup /PrepareAD'. No Exchange 2007 server roles have been detected
    in this topology. After this operation, you will not be able to install any Exchange 2007 servers.
    For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.NoE12ServerWarning.aspx
    Warning:
    Setup will prepare the organization for Exchange 2013 by using 'Setup /PrepareAD'. No Exchange 2010 server roles have been detected
    in this topology. After this operation, you will not be able to install any Exchange 2010 servers.
    For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.NoE14ServerWarning.aspx
    Thanks Guys -

    Hi,
    Agree. Windows Server 2011 SBS x64 can be the problem.
    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

  • Seemingly successful install of Exchange 2013 SP1 turns into many errors in event logs after upgrade to CU7

    I have a new Exchange 2013 server with plans to migrate from my current Exchange 2007 Server. 
    I installed Exchange 2013 SP1 and the only errors I saw in the event log seemed to be long standing known issues that did not indicate an actual problem (based on what I read online). 
    I updated to CU7 and now lots of errors have appeared (although the old ones seem to have been fixed so I have that going for me). 
    Currently the Exchange 2013 server is not in use and clients are still hitting the 2007 server.
    Issue 1)
    After each reboot I get a Kernel-EventTracing 2 error.  I cannot find anything on this on the internet so I have no idea what it is.
    Session "FastDocTracingSession" failed to start with the following error: 0xC0000035
    I did read other accounts of this error with a different name in the quotes but still can’t tell what this is or where it is coming from.
    Issue 2)
    I am still getting 5 MSExchange Common 106 errors even after reregistering all of the perf counters per this page:
    https://support.microsoft.com/kb/2870416?wa=wsignin1.0
    One of the perf counters fails to register using the script from the link above.
    66 C:\Program Files\Microsoft\Exchange Server\V15\Setup\Perf\InfoWorkerMultiMailboxSearchPerformanceCounters.xml
    New-PerfCounters : The performance counter definition file is invalid.
    At C:\Users\administrator.<my domain>\Downloads\script\ReloadPerfCounters.ps1:19 char:4
    +    New-PerfCounters -DefinitionFileName $f
    +    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
        + CategoryInfo         
    : InvalidData: (:) [New-PerfCounters], TaskException
        + FullyQualifiedErrorId : [Server=VALIS,RequestId=71b6bcde-d73e-4c14-9a32-03f06e3b2607,TimeStamp=12/18/2014 10:09:
       12 PM] [FailureCategory=Cmdlet-TaskException] 33EBD286,Microsoft.Exchange.Management.Tasks.NewPerfCounters
    But that one seems unrelated to the ones that still throw errors. 
    Three of the remaining five errors are (the forum is removing my spacing between the error text so it looks like a wall of text - sorry):
    Performance counter updating error. Counter name is Count Matched LowFidelity FingerPrint, but missed HighFidelity FingerPrint, category name is MSExchange Anti-Malware Datacenter Perfcounters. Optional code: 3. Exception: The
    exception thrown is : System.InvalidOperationException: The requested Performance Counter is not a custom counter, it has to be initialized as ReadOnly.
       at System.Diagnostics.PerformanceCounter.InitializeImpl()
       at System.Diagnostics.PerformanceCounter.set_RawValue(Int64 value)
       at Microsoft.Exchange.Diagnostics.ExPerformanceCounter.set_RawValue(Int64 value)
    Last worker process info : System.ArgumentException: Process with an Id of 7384 is not running.
       at System.Diagnostics.Process.GetProcessById(Int32 processId)
       at Microsoft.Exchange.Diagnostics.ExPerformanceCounter.GetLastWorkerProcessInfo()
    Performance counter updating error. Counter name is Number of items, item is matched with finger printing cache, category name is MSExchange Anti-Malware Datacenter Perfcounters. Optional code: 3. Exception: The exception thrown
    is : System.InvalidOperationException: The requested Performance Counter is not a custom counter, it has to be initialized as ReadOnly.
       at System.Diagnostics.PerformanceCounter.InitializeImpl()
       at System.Diagnostics.PerformanceCounter.set_RawValue(Int64 value)
       at Microsoft.Exchange.Diagnostics.ExPerformanceCounter.set_RawValue(Int64 value)
    Last worker process info : System.ArgumentException: Process with an Id of 7384 is not running.
       at System.Diagnostics.Process.GetProcessById(Int32 processId)
       at Microsoft.Exchange.Diagnostics.ExPerformanceCounter.GetLastWorkerProcessInfo()
    Performance counter updating error. Counter name is Number of items in Malware Fingerprint cache, category name is MSExchange Anti-Malware Datacenter Perfcounters. Optional code: 3. Exception: The exception thrown is : System.InvalidOperationException:
    The requested Performance Counter is not a custom counter, it has to be initialized as ReadOnly.
       at System.Diagnostics.PerformanceCounter.InitializeImpl()
       at System.Diagnostics.PerformanceCounter.set_RawValue(Int64 value)
       at Microsoft.Exchange.Diagnostics.ExPerformanceCounter.set_RawValue(Int64 value)
    Last worker process info : System.ArgumentException: Process with an Id of 7384 is not running.
       at System.Diagnostics.Process.GetProcessById(Int32 processId)
       at Microsoft.Exchange.Diagnostics.ExPerformanceCounter.GetLastWorkerProcessInfo()
    Issue 3)
    I appear to have some issues related to the healthmailboxes. 
    I get MSExchangeTransport 1025 errors for multiple healthmailboxes.
    SMTP rejected a (P1) mail from 'HealthMailbox23b10b91745648819139ee691dc97eb6@<my domain>.local' with 'Client Proxy <my server>' connector and the user authenticated as 'HealthMailbox23b10b91745648819139ee691dc97eb6'. The Active Directory
    lookup for the sender address returned validation errors. Microsoft.Exchange.Data.ProviderError
    I reran setup /prepareAD to try and remedy this but I am still getting some.
    Issue 4)
    I am getting an MSExchange RBAC 74 error. 
    (Process w3wp.exe, PID 984) Connection leak detected for key <my domain>.local/Admins/Administrator in Microsoft.Exchange.Configuration.Authorization.WSManBudgetManager class. Leaked Value 1.
    Issue 5)
    I am getting MSExchange Assistants 9042 warnings on both databases.
    Service MSExchangeMailboxAssistants. Probe Time Based Assistant for database Database02 (c83dbd91-7cc4-4412-912e-1b87ca6eb0ab) is exiting a work cycle. No mailboxes were successfully processed. 2 mailboxes were skipped due to errors. 0 mailboxes were
    skipped due to failure to open a store session. 0 mailboxes were retried. There are 0 mailboxes in this database remaining to be processed.
    Some research suggested this may be related to deleted mailboxes however I have never had any actual user mailboxes on this server. 
    If they are healthmailboxes or arbitration mailboxes that might make sense but I am unsure of what to do on this.
    Issue 6)
    At boot I am getting an MSExchange ActiveSync warning 1033
    The setting SupportedIPMTypes in the Web.Config file was missing. 
    Using default value of System.Collections.Generic.List`1[System.String].
    I don't know why but this forum is removing some of my spacing that would make parts of this easier to read.

    Hi Eric
    Yes I have uninstalled and reinstalled Exchange 2013 CU7 for the 3<sup>rd</sup> time. 
    I realize you said one issue per forum thread but since I already started this thread with many issues I will at least post what I have discovered on them in case someone finds their way here from a web search.
    I have an existing Exchange 2007 server in the environment so I am unable to create email address policies that are defined by “recipient container”. 
    If I try and do so I get “You can't specify the recipient container because legacy servers are detected.”
     So I cannot create a normal email address policy and restrict it to an OU without resorting to some fancy filtering. 
    Instead what I have done is use PS to modify extensionAttribute1 (otherwise known as Custom Attribute 1 to exchange) for all of my users. 
    I then applied an address policy to them and gave it the highest priority. 
    Then I set a default email address policy for the entire organization. 
    After reinstalling Exchange all of my system mailboxes were created with the internal domain name. 
    So issue number 3 above has not come up. 
    For issue number one above I have created a new thread:
    https://social.technet.microsoft.com/Forums/office/en-US/7eb12b89-ae9b-46b2-bd34-e50cd52a4c15/microsoftwindowskerneleventtracing-error-2-happens-twice-at-boot-ex2013cu7?forum=exchangesvrdeploy
    For issue number four I have posted to this existing thread where there is so far no resolution:
    https://social.technet.microsoft.com/Forums/exchange/en-US/2343730c-7303-4067-ae1a-b106cffc3583/exchange-error-id-74-connection-leak-detected-for-key?forum=exchangesvradmin
    Issue number Five I have managed to recreate and get rid of in more than one way. 
    If I create a new database in ECP and set the database and log paths where I want, then this error will appear. 
    If I create the database in the default location and then use EMS to move it and set the log path, then the error will not appear. 
    The error will also appear (along with other errors) if I delete the health mailboxes and let them get recreated by restarting the server or the Health Manager service. 
    If I then go and set the retention period for deleted mailboxes to 0 days and wait a little while, these will all go away. 
    So my off hand guess is that these are caused by orphaned system mailboxes.
    For issue number six I have posted to this existing thread where there is so far no resolution:
    https://social.technet.microsoft.com/Forums/exchange/en-US/dff62411-fad8-4d0c-9bdb-037374644845/event-1033-msexchangeactivesync-warning?forum=exchangesvrmobility
    So for the remainder of this thread we can try and tackle issue number two which is the perf counters. 
    The exact same 5 perf counter were coming up and this had been true each time I have uninstalled and reinstalled Exchange 2013CU7. 
    Actually to be more accurate a LOT of perf counter errors come up after the initial install, but reloading the perf counters using the script I posted above reduces it to the same five. 
    Using all of your suggestions so far has not removed these 5 remaining errors either.  Since there is no discernible impact other than these errors at boot I am not seriously bothered by them but as will all event log errors, I would prefer
    to make them go away if possible.

  • What happend New-MailboxExportRequest cmdlet in exchange 2013 SP1 is missing?

    Cmdlet New-MailboxExportRequest is not recognize cmdlet in Exchange 2013 SP1
    How can i do export mailbox to pst file in exchange 2013 SP1?

    You might be facing this issue because of not having the rights to execute the New-MailboxExportRequest CMDLET.
    Follow the steps given below in order to export the mailboxes into PST file
    1. Open the Exchange Console and run:
    New-ManagementRoleAssignment -Name "Import Export PST" -SecurityGroup "Organization Management" -Role “Mailbox Import Export"
    This will generate a new role group called Import Export PST to the Oranization Management group with the role Mailbox Import Export.
    You should Close and Restart the Exchange Management System again so that the changes made will get reflected in the settings, otherwise you will still get the same erroriIf not
    restarted. Now move to the next steps.
    2. Assign “Mailbox Import Export” role to it.
    3.  Add Desired Users to Role Group
    4.  Create Network Share ( Exchange Trusted Subsystem group has read/write permission to NTFS Permissions)
    5. Run PS New-MailboxExportRequest
    6. Monitor New-MailboxExportRequest
    Verify PST File has been created on the network Share and you are done.
    If you get the same error again, then there will be some hardware or software issues due to which you are not able to export mailboxes into PST files. In that case, you can make
    use of any third party tool like Stellar Phoenix EDB To PST converter, which will help you to export your exchange database files to PST files easily and quickly. You can try this software by downloading its demo directly from their site http://www.stellarinfo.com/email-repair/edb-pst-converter.php

  • Exchange 2013 SP1 | Another HTTP 500.0.0 Error

    Help!
    We are in the middle of migrating from Exchange 2010 SP3 to Exchange 2013 SP1 and we are being plagued with HTTP 500 errors on every Exchange 2013 server now.
    I have two Client Access servers installed (EXCHFE01 & EXCHFE02) and one backend mailbox server (EXCHMB03) with the Client Access role also installed (for troubleshooting purposes). Once I get everything working I'll install two backend 2013 servers
    with the mailbox role only for production (load-balanced, clustered, etc). I still have two Exchange 2010 mailbox servers left since one has a single large mailbox left on it and the other hosts public folders. I'll get to migrating those later. All Exchange
    2013 servers are running Windows Server 2012. All are on the same LAN and no firewalls are between them.
    On all three 2013 servers (EXCHFE01, EXCHFE02, EXCHMB03) I'm getting the dreaded HTTP 500 error whether I try to get to OWA or ECP. This did work at one point where I could at least login to the mailbox server (EXCHMB03) and migrate all my mailboxes over
    to it. Sometime this morning after the two Client Access servers were installed the mailbox server stopped working (HTTP 500 errors). This is very frustrating because I can't even login to a console to manage Exchange from any server at this point.
    Both Client Access servers aren't really showing anything of value in the event logs or the IIS logs. The mailbox server (EXCHMB03) does show the following event 3002:
    Protocol /Microsoft-Server-ActiveSync failed to process request from identity NT AUTHORITY\SYSTEM. Exception: Microsoft.Exchange.Security.Authentication.BackendRehydrationException: Rehydration failed. Reason: Source server 'NT AUTHORITY\SYSTEM' does not have token serialization permission.
    at Microsoft.Exchange.Security.Authentication.BackendRehydrationModule.ProcessRequest(HttpContext httpContext)
    at Microsoft.Exchange.Security.Authentication.BackendRehydrationModule.OnAuthenticateRequest(Object source, EventArgs args).
    ...and I get the following when I run the Exchange Management Shell tool on the same mailbox server (along with lots of other red HTML text):
    More Information:
    This error means that there was a problem while processing the request. The request was received by the Web server, but during processing a fatal error occurred, causing the 500 error.
    The Client Access servers show the following errors:
    Performance counter updating error. Counter name is Location cache update time, category name is MSExchange Active Manager Client. Optional code: 3. Exception: The exception thrown is : System.InvalidOperationException: The requested Performance Counter is not a custom counter, it has to be initialized as ReadOnly.
    at System.Diagnostics.PerformanceCounter.InitializeImpl()
    at System.Diagnostics.PerformanceCounter.set_RawValue(Int64 value)
    at Microsoft.Exchange.Diagnostics.ExPerformanceCounter.set_RawValue(Int64 value)
    Last worker process info : System.ArgumentException: Process with an Id of 4040 is not running.
    at System.Diagnostics.Process.GetProcessById(Int32 processId)
    at Microsoft.Exchange.Diagnostics.ExPerformanceCounter.GetLastWorkerProcessInfo()
    Processes running while Performance counter failed to update:
    888 svchost
    264 smss
    532 conhost
    2576 Microsoft.Exchange.UM.CallRouter
    1596 WMSvc
    3932 dllhost
    4020 svchost
    2308 dwm
    5060 taskhostex
    844 svchost
    1972 Microsoft.Exchange.Directory.TopologyService
    1228 inetinfo
    1316 vmtoolsd
    3896 svchost
    780 svchost
    1580 rundll32
    1668 mqsvc
    816 dwm
    3840 slui
    3532 rdpclip
    3980 WmiPrvSE
    4200 SppExtComObj
    4288 winlogon
    2140 SMSvcHost
    676 svchost
    1564 svchost
    1296 Microsoft.Exchange.Diagnostics.Service
    1472 Microsoft.Exchange.ServiceHost
    1204 svchost
    1292 ServerManagerLauncher
    488 winlogon
    664 svchost
    572 lsass
    3236 dllhost
    2972 WmiPrvSE
    4484 w3wp
    388 csrss
    1600 rundll32
    564 services
    1260 msdtc
    5032 sppsvc
    1448 MSExchangeHMHost
    824 LogonUI
    4204 VSSVC
    2524 userinit
    2700 MSExchangeFrontendTransport
    1708 SMSvcHost
    728 svchost
    460 wininit
    904 svchost
    992 svchost
    4996 TSTheme
    4240 slui
    4904 taskhost
    452 csrss
    4340 csrss
    4 System
    1164 spoolsv
    1988 slClient
    2760 MSExchangeHMWorker
    0 Idle
    Performance Counters Layout information: FileMappingNotFoundException for category MSExchange Active Manager Client : Microsoft.Exchange.Diagnostics.FileMappingNotFoundException: Cound not open File mapping for name Global\netfxcustomperfcounters.1.0msexchange active manager client. Error Details: 2
    at Microsoft.Exchange.Diagnostics.FileMapping.OpenFileMapping(String name, Boolean writable)
    at Microsoft.Exchange.Diagnostics.PerformanceCounterMemoryMappedFile.Initialize(String fileMappingName, Boolean writable)
    at Microsoft.Exchange.Diagnostics.ExPerformanceCounter.GetAllInstancesLayout(String categoryName)
    ... and...
    A transient failure has occurred. The problem may resolve itself. Diagnostic information:
    Microsoft.Exchange.Data.DataSourceOperationException: The request failed. The remote server returned an error: (503) Server Unavailable. ---> Microsoft.Exchange.WebServices.Data.ServiceRequestException: The request failed. The remote server returned an error: (503) Server Unavailable. ---> System.Net.WebException: The remote server returned an error: (503) Server Unavailable.
    at System.Net.HttpWebRequest.GetResponse()
    at Microsoft.Exchange.WebServices.Data.EwsHttpWebRequest.Microsoft.Exchange.WebServices.Data.IEwsHttpWebRequest.GetResponse()
    at Microsoft.Exchange.WebServices.Data.ServiceRequestBase.GetEwsHttpWebResponse(IEwsHttpWebRequest request)
    --- End of inner exception stack trace ---
    at Microsoft.Exchange.WebServices.Data.ServiceRequestBase.GetEwsHttpWebResponse(IEwsHttpWebRequest request)
    at Microsoft.Exchange.WebServices.Data.ServiceRequestBase.ValidateAndEmitRequest(IEwsHttpWebRequest& request)
    at Microsoft.Exchange.WebServices.Data.ExchangeService.InternalFindFolders(IEnumerable`1 parentFolderIds, SearchFilter searchFilter, FolderView view, ServiceErrorHandling errorHandlingMode)
    at Microsoft.Exchange.WebServices.Data.ExchangeService.FindFolders(FolderId parentFolderId, SearchFilter searchFilter, FolderView view)
    at Microsoft.Exchange.Data.Storage.Management.EwsStoreDataProvider.InvokeServiceCall[T](Func`1 callback)
    --- End of inner exception stack trace ---
    at Microsoft.Exchange.Data.Storage.Management.EwsStoreDataProvider.InvokeServiceCall[T](Func`1 callback)
    at Microsoft.Exchange.Data.Storage.Management.EwsStoreDataProvider.GetOrCreateFolderCore(String folderName, FolderId parentFolder, Func`1 creator)
    at Microsoft.Exchange.Data.Storage.Management.AsyncOperationNotificationDataProvider.GetDefaultFolder()
    at Microsoft.Exchange.Data.Storage.Management.EwsStoreDataProvider.<>c__DisplayClass1b`1.<InternalFindPaged>b__13()
    at Microsoft.Exchange.Data.Storage.Management.EwsStoreDataProvider.InvokeServiceCall[T](Func`1 callback)
    at Microsoft.Exchange.Data.Storage.Management.EwsStoreDataProvider.<InternalFindPaged>d__21`1.MoveNext()
    at Microsoft.Exchange.Data.Storage.Management.AsyncOperationNotificationDataProvider.<GetNotificationDetails>d__4.MoveNext()
    at System.Linq.Enumerable.WhereEnumerableIterator`1.MoveNext()
    at Microsoft.Exchange.Servicelets.CertificateNotificationServicelet.RemoveAllNotification()
    at Microsoft.Exchange.Servicelets.CertificateNotificationServicelet.UpdateDataInMbx(List`1 certificates)
    at Microsoft.Exchange.Servicelets.CertificateNotificationServicelet.Work()
    I've tried all sorts of recommended fixes but none have worked so far:
    ADSIEdit and remove msExchCanaryData0 data
    Reinstall Exchange multiple times
    Rebooted multiple times
    This article: http://social.technet.microsoft.com/Forums/exchange/en-US/08d3777c-dc03-4411-8c87-7db37d2f406a/exchange-2013-owa-login-error-http-500?forum=exchangesvrclients
    Rebooted DCs multiple times (no exchange servers are DCs)
    I'm sure I've left out a few troubleshooting steps since I've been working at this for two days. Can anybody offer any advice? I'm at my wits end here...

    Hi,
    Please check whether the mail.mydomain.com is pointed to your Exchange 2010 or Exchange 2013. Please run the following command to check your OWA virtual directores and ECP virtual directories:
    Get-OwaVirtualDirectory -ShowMailboxVirtualDirectories | Select Identity,name,Internalurl,ExternalUrl,*auth*
    Get-EcpVirtualDirectory -ShowMailboxVirtualDirectories | Select Identity,name,Internalurl,ExternalUrl,*auth*
    In IIS manager > Default Web Site, please make sure Anonymous Authentication is Enabled in Authentication. Confirm that "Require SSL" is checked on the SSL Settings of the default web site.
    Regards,
    Winnie Liang
    TechNet Community Support

  • Exchange 2013 SP1 readiness check failing

    Trying to install our first Exchange 2013 SP1 server on Windows 2012 R2 in our datacentre, the readiness check fails with:
    Error:
    The Active Directory schema isn't up-to-date, and this user account isn't a member of the 'Schema Admins' and/or 'Enterprise Admins' groups.
    For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.SchemaUpdateRequired.aspx
    There are many more errors relating to Enterprise admin rights etc.
    Please note that:
    My account is Domain admin, Schema admin and Enterprise admin member, it always has been.
    I tried the built-in AD Administrator which of course is part of the groups as well, no difference.
    Active Directory is at 2008 R2 for domain and forest functional levels.
    I tried rejoining the new Exchange designated server to the domain
    I've installed RSAT-ADDS, the Managed API 4.0 and all the other windows roles via powershell
    There is a local domain controller that is a global catalog server on the new Exchange server subnet
    I tried running the Exchange Setup on a different server on the same subnet as where the active 2010 Exchange server resides as well as the FSMO AD role holder resides, this works fine. I even did the AD prep from there no problem, that made no difference
    on the datacentre server
    AD replicates fine between the FSMO role holder and the Datacentre (no errors in dcdiag or repadmin /showrepl)
    This error is in the event log:
    The description for Event ID 4027 from source MSExchange ADAccess cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
    If the event originated on another computer, the display information had to be saved with the event.
    The following information was included with the event:
    ExSetupUI.exe
    6724
    Get Servers for domain.local
    TopologyClientTcpEndpoint (localhost)
    3
    System.ServiceModel.EndpointNotFoundException: Could not connect to net.tcp://localhost:890/Microsoft.Exchange.Directory.TopologyService. The connection attempt lasted for a time span of 00:00:02.0475315. TCP error code 10061: No connection could be made because the target machine actively refused it 127.0.0.1:890. ---> System.Net.Sockets.SocketException: No connection could be made because the target machine actively refused it 127.0.0.1:890
    at System.Net.Sockets.Socket.DoConnect(EndPoint endPointSnapshot, SocketAddress socketAddress)
    at System.Net.Sockets.Socket.Connect(EndPoint remoteEP)
    at System.ServiceModel.Channels.SocketConnectionInitiator.Connect(Uri uri, TimeSpan timeout)
    --- End of inner exception stack trace ---
    Server stack trace:
    at System.ServiceModel.Channels.SocketConnectionInitiator.Connect(Uri uri, TimeSpan timeout)
    at System.ServiceModel.Channels.BufferedConnectionInitiator.Connect(Uri uri, TimeSpan timeout)
    at System.ServiceModel.Channels.ConnectionPoolHelper.EstablishConnection(TimeSpan timeout)
    at System.ServiceModel.Channels.ClientFramingDuplexSessionChannel.OnOpen(TimeSpan timeout)
    at System.ServiceModel.Channels.CommunicationObject.Open(TimeSpan timeout)
    at System.ServiceModel.Channels.ServiceChannel.OnOpen(TimeSpan timeout)
    at System.ServiceModel.Channels.CommunicationObject.Open(TimeSpan timeout)
    Exception rethrown at [0]:
    at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)
    at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)
    at System.ServiceModel.ICommunicationObject.Open()
    at Microsoft.Exchange.Net.ServiceProxyPool`1.GetClient(Boolean useCache)
    at Microsoft.Exchange.Net.ServiceProxyPool`1.TryCallServiceWithRetry(Action`1 action, String debugMessage, WCFConnectionStateTuple proxyToUse, Int32 numberOfRetries, Boolean doNotReturnProxyOnSuccess, Exception& exception)
    the message resource is present but the message is not found in the string/message table

    So I decided to re-install the OS, worked perfectly now. Only difference from before would be:
    SCCM hasn't pushed SCEP 2012 to the new build of the same server yet
    The original server was installed in a different AD site and then it was physically mode and reassigned to an new AD site and subnet
    I might have installed the pre-reqs in a slightly different order (RSAT-ADDS, all the IIS etc things via powershell
    and then the UCM API 4.0. (saw few comments that the order of how you install them matters in other forums).
    10 or so Microsoft Windows updates haven't installed on the new OS build yet.
    Other than that, its identical. But if its not broken don't fix it, perhaps the above can help someone else though. 

  • Exchange 2013 sp1 move databases

    Hello all
    I am running Exchange 2013 sp1 in a two node DAG. Originally the DAG  had two under powered servers, i built two new more powerful servers added the servers to the DAG, then i moved database copies to the new servers, removed the copies from the original
    servers and then removed the original servers from the DAG. The two original servers are multi role (CAS Mailbox) and currently they are still in the org. My confusion is around this. When i run get-mailbox -identity <name>. The output from the command
    shows the mailbox is on oldserver.  Again oldserver was removed from the DAG and no databases exist on the server. I want to remove the two old servers from the org, but i am hesitant on doing this because all mailboxes seem to think they exist on oldserver 
    Thanks for any help
    Bulls on Parade

    You can ignore that:
    http://blogs.technet.com/b/timmcmic/archive/2011/09/26/exchange-2010-homemta-and-msexchhomeservername-are-not-updated-on-mailboxes.aspx
    Twitter!: Please Note: My Posts are provided “AS IS” without warranty of any kind, either expressed or implied.

  • 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 SP1 Not Receiving e-mail

    Hello,
    Mail flow between Exchange 2010 sp3 & Exchange 2013 SP1 (update Cu5) not working.
    Exchange 2013 setup is Exchange 2013 sp1 DVD
    Exchange 2010 when sending mail to external it's ok.
    Exchange 2010 when sending mail to exchange 2010 users it's ok.
    Exchange 2013 when sending mail to External it's ok.
    Exchange 2013 when sending mail to exchange 2010 users it's ok.
    or
    Exchange 2010 when sending mail to exchange 2013 not working
    Exchange 2013 when sending mail to Exchange 2013 not working
    From internet --> SMTP GW (exh edge) --> Exchange 2010 it's ok
    From Internet --> SMTP GW (exh edge) --> Exchange 2013 not working.
    organization;
    1 AD site and 1 PDC (2012 R2) + 3 DC (1x 2008 R2 + 2 x 2003 Server) (Windows Server 2003 domain fl)
    With Exchange 2010 exchange 2013 on the same subnet. Exchange 2010 physical machine, Exchange 2013 physical machine ( eth Microsoft Team Server 2012 R2 )
    All server is region setting Turkey
    Exchange 2010 error
    451 4.7.0 Temporary server error. Please try again later. PRX4 
    Exchange 2013 error
    451 4.4.0 primary target ip address responded with 501 5.5.4 Invalid arguments. attempted failover to alternative host, but that did not succeed. either there are no alternate host, or delivery failed to all alternate hosts. Th
    thanks

    Hi,
    From your description, the Exchange 2013 server can't receive emails internally and externally. I recommend you follow the steps below for troubleshooting:
    1. Please restart the Microsoft Exchange Frontend Transport service on CAS and the Microsoft Exchange Transport service on Mailbox and check the result.
    2. Please make sure that the authentication on default receive connector is right. Here is the configuration in my environment for your reference:
    Hope it helps.
    Best regards,
    If you have feedback for TechNet Subscriber Support, contact
    [email protected]
    Amy Wang
    TechNet Community Support

  • Exchange 2013 SP1 and CUCM 9.1.2 - Exch not recognizing called extension

    I think I'm almost there in getting Exchange 2013 SP1 UM working with CUCM 9.1.2...I've got two issues at the moment that I need a little help with.
    1) When I dial my VM pilot (6040) from a UM enabled extension it prompts to enter an extension. When I dial the same extension and let it ring to VM, Exchange picks up and says "the person you are trying to reach does not have a valid voice mail box
    on our system".
    2) This just started happening this afternoon, when I dial my VM pilot (6040) exch3 picks up as thats what I have my route pattern pointing to. If I enter the extension of a mailbox on exch2, I get stuck in a endless loop.
    I've followed this post as a guide but it hasn't resolved my issue.
    https://supportforums.cisco.com/discussion/11914031/exchange-2013-um-and-cucm-86
    My Exchange environment looks like this:
    Site 1:
    exch1 - CAS/Mailbox, used for mainly utility type work, journal, dedicated SMTP flows etc
    exch2 - CAS/Mailbox, part DAG13
    exch3 - CAS/Mailbox, part of DAG13
    Site 2:
    exch2dr - CAS/Mailbox, part of DAG13
    exch3dr - CAS/Mailbox, part of DAG13
    DAG13 is stretched between two sites, there are no users at our DR site so CUCM is pointing to Site 1 for UM. Each site has an internet facing CAS-only server for OWA/EAS etc.
    Any help is greatly appreciated. I'd love to get rid of Unity. 
    EDIT:
    I just found this event in the event logs:
    The Microsoft Exchange Unified Messaging service on the Mailbox server received a diverted call with ID "d51600-3a3140c5-9b8-c1414ac@EXCH3-IPADDR" for extension "4099" on UM dial plan "CUCM" from UM IP gateway "CUCM IP",
    but no UM-enabled mailbox for the corresponding extension could be found. Please check the extension and make sure that the corresponding mailbox is enabled for UM and associated with the correct UM dial plan.

    9.1.2 I think it is, we upgraded to avoid the known DNS bug
    I cant see how to PM you either
    The crux of it was outlined below with some tweaks
    http://blogs.technet.com/b/canitpro/archive/2014/04/30/step-by-step-integration-between-exchange-2013-um-and-cisco-unified-communication-manager.aspx
    As we have multiple combined role servers, our trunks are set up as follows:
    1. 1 x CAS Trunk - contains all CAS Servers on port 5060
    2. 4 x MBX Trunks - contains Maibox Server with ports 5062-5068
    On top of that, we had to Allow "Redirecting Diversion Header Delivery - Inbound (and Outbound)" on the CAS Trunk but DISABLE it on the Mailbox Trunks
    Also, make sure that you are using Telephone Extension Dial plans in Exchange 2013 (Despite them being unable to be associated with a 13 Server - EX13 answers for all calls anyway)
    Lastly, the MS documentation is a little strange - it says that as your last step of UM migration, you should point your Call Manager to 2013 - I don't agree with that statement, EX13 routes calls back to 2010 UM Servers perfectly fine, so treat it the same
    as any other CAS based service - point to 2013, and it will handle the rest

Maybe you are looking for