Exchange 2013 Reports

Hello All,
I recently installed SCOM 2012 R2 and have installed the Exchange 2013 management packs however there does not seem to be any good reports that are included with this management pack. I was wondering if anybody has an tutorials on creating a exchange
specific report. The basic criteria would be cpu usage, memory usage, hard drive space, up time, and any relevant exchange metrics.

Hi,
There are no performance counters collected by this Management Pack: the monitoring does cover any performance issue that might arise, leveraging Exchange Managed Availability.
However, all Exchange PerfMon counters are still available. It should be simple to create your own performance collection rules, if you do require them.
There are no reports in this Management Pack: you can still use some of the built-in Operations Manager reports (such as the Health and Availability reports) to track organization availability, or define SLAs against the Organization.
In addition, I would like to suggest you go through the link below to get more details about Exchange 2013 MP, we should be able to see CPU and Memory performance from the MP:
SCOM Management Pack for Exchange 2013 – Top 6 Things I Like
http://ok-sandbox.com/2014/11/scom-management-pack-for-exchange-2013-top-6-things-i-like/
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]

Similar Messages

How to get a summarized mail traffic report in exchange 2013

Hi all
How to calculate the exchange 2013 SMTP mail traffic in terms of hour,day,month,top senders,largest message and top recipients list . Same time we would like to have those summarized mail traffic report for all the mailbox servers in the form of graphical
view as well as in a csv file ?
Please all of us share your thoughts and possibilities .
Regards
S.Nithyanandham
Thanks S.Nithyanandham

You may calculate hourly email traffic using "Message Tracking Logs and Log Parser".
I would like to refer you on this well explained article that will assist you step-wise to implement in your working environment : http://exchangeserverpro.com/calculate-hourly-email-traffic-using-message-tracking-log-parser/
Moreover, if you wish to achieve this goal automatically, you may also consider on this automated application (http://www.exchangereports.net/) that provides a deep-view of email traffic report in real time at
granular level.

Exchange 2013 Delivery Reports not working correctly

Hello,
I'm trying to use the "delivery reports" tool in ECP and it is not acting normally. Here's the situation:
When I try to search a mailbox ([email protected]) for mails that were sent to [email protected] (a distribution group) I only see results that were sent from [email protected] to [email protected] Not all the messages in [email protected]'s mailbox that were sent to [email protected]
So in summary, instead of showing all messages in that mailbox, it shows me all messages on [email protected]'s mailbox that were sent by [email protected] to [email protected]
I have used Exchange Online, which should be almost the same as Exchange 2013 but this was not the behavior before. Can this be a wrong setting somewhere? Can it be related to anti-spam (GFI) software on the serer? Any ideas?

Hi,
How did you use delivery reports tool to track messages ? Is it like below?
*Mailbox to Search: [email protected]
Search for messages sent to: [email protected]
In general, it will show all the messages in [email protected] which were sent to
[email protected], however, if the mailbox has applied any retention policys to delete emails or move the emails to local pst, it may cause your issue.
More information about "Delivery Reports" for your reference:
Track Messages with Delivery Reports
Thanks.
Niko Cheng
TechNet Community Support

Exchange 2013 - RCA reports RPC Proxy can't be pinged (404)

Hi, I've searched extensively and spent hours trying to fix my problem and nothing in the forums has addressed yet.
I have a new exchange server 2013 SP1 and Outlook 2013 clients can't connect. Outlook states Exchange Server is Unavailable.
This led me to Microsoft RCA. RCA reported that the RPC Proxy can't be pinged with a 404 error. But I CAN visit the server RCA references a step or two above and am treated to a white page, no 404. (
https://xch.domain.com/rpc/rpcproxy.dll?xch.domain.com:6002 )
I have set ExternalAuthenticatoin to Negotiate and internal to NTLM, I have set outlookProvider to
[PS] C:\Windows\system32>Get-Outlookprovider
Name Server CertPrincipalName TTL
EXCH msstd:*.domain.com 1
EXPR msstd:*.domain.com 1
WEB
1
The SSL Certificate is a trusted one, the External URL is set properly in the server settings via ECP as well.
Any ideas would be greatly appreciated. I'm tired and incapable of listing all of the steps I've tried, but if you know of any tips for troubleshooting and fixing RPC Ping issues, I would love to hear them.
Thanks!

Hi,
How about OWA, does it works well?
1. If OWA doesn't work, please check wether the Outlook Anywhere has been enabled.
It seems you have configured Outlook Anywhere as below. If not, please change the configuration.
Does the whole error message like this:
Attempting to ping RPC proxy mail.contoso.co.nz.
RPC Proxy can't be pinged.
Additional Details
A Web exception occurred because an HTTP 404 - NotFound response was received from Unknown.
Please make sure the configuration as below:
Set-OutlookAnywhere
ExternalClientAuthenticationMethod : Negotiate
InternalClientAuthenticationMethod : NTLM
IISAuthenticationMethods : {basic, ntlm, negotiate}
Set-OutlookProvider
Name                       Server                      CertPrincipalName            TTL
EXCH
msstd:*.contoso.co.nz     1
EXPR
msstd:*.contoso.co.nz      1
WEB                                                                                                1
More details in the following link:
Exchange 2013 Outlook Anywhere (RPC) Settings
http://infused.co.nz/2013/05/13/exchange-2013-outlook-anywhere-rpc-settings/
Disclaimer:
Microsoft is providing this information as a convenience to you. The sites are not controlled by Microsoft. Microsoft cannot make any representations regarding the quality, safety, or suitability of any software or information found there. Please make sure
that you completely understand the risk before retrieving any suggestions from the above link.
2. If the method 1 doesn't help, please collect some related error message in App Log without sensitive information for the further troubleshooting.
3. If OWA works well, just Outlook doesn't work, I suggest try to run 'Test-OutlookConnectivity' command in EMS to verify the connectivity between Exchange server and Outlook client. Please paste the details without sensitive information if there is any
abnormal.
4. Please also run 'Test E-mail AutoConfiguration' on Outlook to verify whether there is anything abnormal.
Thanks
Mavis
If you have feedback for TechNet Subscriber Support, contact
[email protected]
Mavis Huang
TechNet Community Support

Unable to open delivery reports in Exchange 2013 SP1. Gives warning "The status for the recipient can't be determined because of a temporary error. Please try again later."

This seems to be occurring with all users (have tested a few, all display the same exact error message).
When I click on "Message Delivery Report" in Outlook 2010 or 2013, it points me to the ECP and displays this message "Warning The status for the recipient can't be determined because of a temporary error. Please try again later." I'm
not sure which log files to look at. The last time I remember it worked was before I applied SP1, I think CU3.
Our environment is two servers running Exchange Server 2013 Std. SP1 (847.32) in a DAG.
Thanks.

Hi,
From the error description, I would like to clarify the following thing:
Delivery Reports is a message tracking tool that you can use to search for delivery status on email messages sent to or from users in your organization's address book, with a certain subject. In Exchange 2013, you can track messages for up to 14 days after
they were sent or received. Please make sure the message you are tracking isn't older than 14 days.
Here is an article for your reference:
Track messages with delivery reports
http://technet.microsoft.com/en-us/library/jj150554(v=exchg.150).aspx
Hope it helps.
Best regards,
Amy Wang
TechNet Community Support

Exchange 2013 Delivery Reports - Why does it not show forwarded mail?

We just migrated from 2010 to 2013 and all seems to be working well... We started using EOP at the same time with only a few hiccups. Our Get-MessageTrackingLog command shows all of our email that was delivered or failed, etc... but when I try to run
"Mail Flow -> Delivery reports", it forces me to select a mailbox and I leave the other fields empty - and it only shows emails that come directly to me. The problem is, I have half a dozen email accounts that are set to forward their email
to my exchange account. None of those emails show up with the delivery reports method - but they DO show up via the powershell get-messagetrackinglog command...
With EOP I can see all the emails if I use "Mail Flow -> Message Trace"... why does it work with EOP, but on our local box - it's nerfed to just emails who specify my direct exchange address?

Hi,
I have tested to use Delivery Reports to search my manually forward messages in my Exchange 2013 CU1 environment. And the forward messages can be searched and listed in the Search results.
Please make sure the users who forwarded emails to you are in your organization and they are sending
messages by using the Microsoft Outlook or Outlook Web App email clients. Because Delivery Reports doesn’t track messages send from POP or IMAP email clients. For more information about Delivery Reports, please refer to:
http://technet.microsoft.com/en-us/library/jj150554(v=exchg.150).aspx
Additionally, I also tested auto-forward scenario:
User1 is configured to auto-forward messages to User2 in Exchange side(for details, please click
here), when User3 sends a message to User1, the message is forwarded to User2 automatically. If so, when we use Delivery Report to search this forward message for User2, we
need to use Search for messages received from User3 instead of User1 to get this forwarded message.
Thanks,
Winnie Liang
TechNet Community Support

Error reported after Exchange 2013 Setup (initialize-ExchangeUniversalGroups)

My Exchange 2013 setup reported the error below. Just wondering if someone has experienced this and how easy it was to fix.
Error:
The following error was generated when "$error.Clear();
initialize-ExchangeUniversalGroups -DomainController $RoleDomainController -ActiveDirectorySplitPermissions $RoleActiveDirectorySplitPermissions
" was run: "Microsoft.Exchange.Management.Tasks.InvalidWKObjectException: The well-known object entry B:32:C262A929D691B74A9E068728F8F842EA:CN=Organization Management\0ADEL:81ee6b49-29e5-41ff-93d4-30c547de15b1,CN=Deleted Objects,DC=ad,DC=mydomain,DC=co
on the otherWellKnownObjects attribute in the container object CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=ad,DC=mydomain,DC=co points to an invalid DN or a deleted object. Remove the entry, and then rerun the task.
at Microsoft.Exchange.Configuration.Tasks.Task.ThrowError(Exception exception, ErrorCategory errorCategory, Object target, String helpUrl)
at Microsoft.Exchange.Configuration.Tasks.Task.WriteError(Exception exception, ErrorCategory category, Object target)
at Microsoft.Exchange.Management.Tasks.InitializeExchangeUniversalGroups.CreateGroup(ADOrganizationalUnit usgContainer, String groupName, Int32 groupId, Guid wkGuid, String groupDescription, GroupTypeFlags groupType, Boolean createAsRoleGroup)
at Microsoft.Exchange.Management.Tasks.InitializeExchangeUniversalGroups.CreateRoleGroup(ADOrganizationalUnit usgContainer, RoleGroupDefinition roleGroup)
at Microsoft.Exchange.Management.Tasks.InitializeExchangeUniversalGroups.CreateAndValidateRoleGroups(ADOrganizationalUnit usgContainer, RoleGroupCollection roleGroups)
at Microsoft.Exchange.Management.Tasks.InitializeExchangeUniversalGroups.InternalProcessRecord()
at Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__b()
at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePipelineIfFailed)".
Roger

Thanks for replying.
My domain is actually routable (I just renamed it thinking that perhaps its more secure to withhold the info).
I had previously installed Es2013 and had to delete the VM. So this is a re-install on the Active Directory. I'm wondering if there isn't something in the "deleted folder" that is causing hassles.
Roger

Exchange 2013 - Event ID 4999 MS Exchange Common - Watson report about to be sent for process id: 5816

Hi,
We have a single Exchange 2013 server and are getting this error many times in a day. I haven't been able to find a solution and was wondering if anyone came across this error or have any suggestions.
Edition : Standard
AdminDisplayVersion : Version 15.0 (Build 913.22)
Watson report about to be sent for process id: 5816, with parameters: E12IIS, c-RTL-AMD64, 15.00.0913.022, M.Exchange.Imap4, M.Exchange.Net, M.E.N.NetworkConnection.BeginNegotiateTlsAsClient, System.InvalidOperationException, 99a4, 15.00.0913.007.
ErrorReportingEnabled: True
Thanks
Amit

We have exchange 2013 cu6 mailbox server and we keep getting the below event error message
Log Name:      Application
Source:        MSExchange Common
Date:          10/2/2014 1:06:25 PM
Event ID:      4999
Task Category: General
Level:         Error
Keywords:      Classic
User:          N/A
Computer:
Description:
Watson report about to be sent for process id: 30632, with parameters: E12, c-RTL-AMD64, 15.00.0995.029, M.E.RpcClientAccess.Service, M.E.Data.ApplicationLogic, M.E.D.A.U.HttpPhotoRequestBuilder.Build, System.NotSupportedException, 4e29, 15.00.0995.027.
ErrorReportingEnabled: True
Event Xml:
< Event xmlns="">
<System>
    <Provider Name="MSExchange Common" />
    <EventID Qualifiers="16388">4999</EventID>
    <Level>2</Level>
    <Task>1</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2014-10-02T20:06:25.000000000Z" />
    <EventRecordID>7826297</EventRecordID>
    <Channel>Application</Channel>
    <Computer></Computer>
    <Security />
</System>
<EventData>
    <Data>30632</Data>
    <Data>E12</Data>
    <Data>c-RTL-AMD64</Data>
    <Data>15.00.0995.029</Data>
    <Data>M.E.RpcClientAccess.Service</Data>
    <Data>M.E.Data.ApplicationLogic</Data>
    <Data>M.E.D.A.U.HttpPhotoRequestBuilder.Build</Data>
    <Data>System.NotSupportedException</Data>
    <Data>4e29</Data>
    <Data>15.00.0995.027</Data>
    <Data>True</Data>
    <Data>False</Data>
    <Data>Microsoft.Exchange.RpcClientAccess.Service</Data>
    <Data>
    </Data>
</EventData>
< /Event>
Services seem to be fine (Via test-servicehealth), but i do have a group of users that complain that their outlook 2013 email clients will go non-responsive a few times a days. Wondering if this is related. Also this error is appearing every few minutes.
Anyone else experiencing this?

Update reports exchange 2013

Becouse updates for exchange 2013 ar not in wsus
Is there page in can monitor by rss feed that just reports updates of exchange 2013 ?
I know the exchange team blog, there are alot more post.
I want to be triggerd only when there is an update voor exchange 2013
With kind regards, Bas van den Dikkenberg

Actually there is one option and it's best available option.
You can use Exchange Team Blog
http://blogs.technet.com/b/exchange/
All the updates for new release comes here first.
Cheers,
Gulab Prasad
Technology Consultant
Blog:
http://www.exchangeranger.com    Twitter:
  LinkedIn:
   Check out CodeTwo’s tools for Exchange admins
Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.

Exchange 2013 /m:recoverserver constantly failing due to MSExchangeSubmission.exe

Hi all,
I am trying to recover my lab Exchange 2013 server after removing a component of IIS messed all IIS functions, including all virtual directories.
The server is running on Hyper-V so I have removed and rebuilt the OS disk whilst the Exchange data resides on a separate disk. I've reset the computer account in AD and then run the command:
setup /m:recoverserver /targetdir:"d:\Program Files\Microsoft Exchange\v15" /DoNotStartTransport /IAcceptExchangeServerLicenseTerms
I have now done this a number of times and on each occasion it fails when attempting to start the Microsoft Exchange Transport Submission service. The error in the event log is as follows:
Log Name:      Application
Source:        Application Error
Date:          30/03/2013 20:18:53
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      HV-E2K13
Description:
Faulting application name: MSExchangeSubmission.exe, version: 15.0.516.29, time stamp: 0x506956b8
Faulting module name: Microsoft.Exchange.Net.ni.dll, version: 15.0.516.27, time stamp: 0x5064072e
Exception code: 0xc00000fd
Fault offset: 0x0000000000639d07
Faulting process id: 0x1cc8
Faulting application start time: 0x01ce2d83cbb5568e
Faulting application path: D:\Program Files\Microsoft Exchange\v15\Bin\MSExchangeSubmission.exe
Faulting module path: C:\Windows\assembly\NativeImages_v4.0.30319_64\Microsoft.E91f4adf5#\6f9b1d97c1f0dcb9b1006260c405a5da\Microsoft.Exchange.Net.ni.dll
Report Id: 0a1e3a42-9977-11e2-93f1-00155d0a4b05
Faulting package full name:
Faulting package-relative application ID:
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
    <Provider Name="Application Error" />
    <EventID Qualifiers="0">1000</EventID>
    <Level>2</Level>
    <Task>100</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2013-03-30T20:18:53.000000000Z" />
    <EventRecordID>112812</EventRecordID>
    <Channel>Application</Channel>
    <Computer>HV-E2K13</Computer>
    <Security />
</System>
<EventData>
    <Data>MSExchangeSubmission.exe</Data>
    <Data>15.0.516.29</Data>
    <Data>506956b8</Data>
    <Data>Microsoft.Exchange.Net.ni.dll</Data>
    <Data>15.0.516.27</Data>
    <Data>5064072e</Data>
    <Data>c00000fd</Data>
    <Data>0000000000639d07</Data>
    <Data>1cc8</Data>
    <Data>01ce2d83cbb5568e</Data>
    <Data>D:\Program Files\Microsoft Exchange\v15\Bin\MSExchangeSubmission.exe</Data>
    <Data>C:\Windows\assembly\NativeImages_v4.0.30319_64\Microsoft.E91f4adf5#\6f9b1d97c1f0dcb9b1006260c405a5da\Microsoft.Exchange.Net.ni.dll</Data>
    <Data>0a1e3a42-9977-11e2-93f1-00155d0a4b05</Data>
    <Data>
    </Data>
    <Data>
    </Data>
</EventData>
</Event>
Any thoughts?
Paul

Hi,
Im dealing with the same errors when i'm trying to restore our productive mailbox from a disaster.
I've tried everything listed here but last Milind Naphade commentary.
I'm in that right now, i ll tell if it's working soon.
Ty!
Hi Again. It Failed to start MSExchangeSubmission.exe
Here is the event on eventvwr (Some details on spanish wich is the language of my server)
Nombre de la aplicación con errores: MSExchangeSubmission.exe, versión: 15.0.516.29, marca de tiempo: 0x506956b8
Nombre del módulo con errores: Microsoft.Exchange.Net.ni.dll, versión: 15.0.516.27, marca de tiempo: 0x5064072e
Código de excepción: 0xc00000fd
Desplazamiento de errores: 0x000000000062f697
Identificador del proceso con errores: 0x7d0
Hora de inicio de la aplicación con errores: 0x01cfac0a0bb16a68
Ruta de acceso de la aplicación con errores: C:\Program Files\Microsoft\Exchange Server\V15\Bin\MSExchangeSubmission.exe
Ruta de acceso del módulo con errores: C:\Windows\assembly\NativeImages_v4.0.30319_64\Microsoft.E91f4adf5#\b028905d8fd3faa99c9801b69b1500da\Microsoft.Exchange.Net.ni.dll
Identificador del informe: 4a9638fc-17fd-11e4-9404-000c29f101d8
Nombre completo del paquete con errores:
Identificador de aplicación relativa del paquete con errores:
ExchangeSetup.log ends with:
[07/30/2014 15:19:10.0220] [1] The following 1 error(s) occurred during task execution:
[07/30/2014 15:19:10.0220] [1] 0. ErrorRecord: El servicio 'MSExchangeSubmission' no puede alcanzar el estado 'Running' en este servidor.
[07/30/2014 15:19:10.0220] [1] 0. ErrorRecord: Microsoft.Exchange.Configuration.Tasks.ServiceDidNotReachStatusException: El servicio 'MSExchangeSubmission' no puede alcanzar el estado 'Running' en este servidor.
en Microsoft.Exchange.Configuration.Tasks.Task.ThrowError(Exception exception, ErrorCategory errorCategory, Object target, String helpUrl)
en Microsoft.Exchange.Configuration.Tasks.Task.WriteError(Exception exception, ErrorCategory category, Object target)
en Microsoft.Exchange.Management.Tasks.ManageSetupService.WaitForServiceStatus(ServiceController serviceController, ServiceControllerStatus status, Unlimited`1 maximumWaitTime, Boolean ignoreFailures, Boolean sendWatsonReportForHungService)
en Microsoft.Exchange.Management.Tasks.ManageSetupService.StartService(ServiceController serviceController, Boolean ignoreServiceStartTimeout, Boolean failIfServiceNotInstalled, Unlimited`1 maximumWaitTime, String[] serviceParameters)
en Microsoft.Exchange.Management.Tasks.ManageSetupService.StartService(String serviceName, Boolean ignoreServiceStartTimeout, Boolean failIfServiceNotInstalled, Unlimited`1 maximumWaitTime, String[] serviceParameters)
en Microsoft.Exchange.Management.Tasks.StartSetupService.InternalProcessRecord()
en Microsoft.Exchange.Configuration.Tasks.Task.ProcessRecord()
[07/30/2014 15:19:10.0236] [1] [ERROR] The following error was generated when "$error.Clear();
start-SetupService -ServiceName MSExchangeSubmission
" was run: "El servicio 'MSExchangeSubmission' no puede alcanzar el estado 'Running' en este servidor.".
[07/30/2014 15:19:10.0236] [1] [ERROR] Service 'MSExchangeSubmission' failed to reach status 'Running' on this server.
[07/30/2014 15:19:10.0236] [1] [ERROR-REFERENCE] Id=MailboxServiceControlLast___23a36fed7b6947e0906f388b5a90135c Component=EXCHANGE14:\Current\Release\Shared\Datacenter\Setup
[07/30/2014 15:19:10.0251] [1] Setup is stopping now because of one or more critical errors.
[07/30/2014 15:19:10.0251] [1] Finished executing component tasks.
[07/30/2014 15:19:10.0267] [1] Ending processing DisasterRecovery-MailboxRole
[07/30/2014 15:19:10.0282] [0] No se completó la operación de instalación de Exchange Server. Puede encontrar más detalles en ExchangeSetup.log ubicado en la <SystemDrive>: carpeta \ExchangeSetupLogs.
[07/30/2014 15:19:10.0282] [0] End of Setup
[07/30/2014 15:19:10.0282] [0] **********************************************
Any suggestion please??? idk what else can i do!

Exchange 2013 External Relay gives me a headache... Anonymous relay fail to external address

I tried to set up external relay on my Exchange 2013 but was not able to do it. I don't know what else to do. I tried these:
http://technet.microsoft.com/en-us/library/bb232021.aspx
and these (which is pretty much same thing)
http://www.shudnow.net/2013/06/04/how-anonymous-relay-works-in-exchange-2013/
http://exchangeserverpro.com/exchange-2013-configure-smtp-relay-connector/
http://glazenbakje.wordpress.com/2012/12/30/exchange-2013-how-to-configure-an-internal-relay-connector/
http://blogs.technet.com/b/exchange/archive/2006/12/28/3397620.aspx
But still no luck. Here is somewhat detailed description what I tried do accomplice.
Server which need to send mail reports is sending these from web server on another location connected with site-to-site VPN to location server resides like on picture. I am able to send relay to all of
addreses of local domain but when I tried to send mails to my clients to external e mail addresses exchange return me message unable to relay.
Here is log from unsuccessfully operation
Connecting to [smtp.mydomain.com] port [25]...
220 smtp.mydomain.com Microsoft ESMTP MAIL Service ready at Fri, 24 Jan 2014 17:19:45 +0100
>HELO webserver
250 smtp.mydomain.com Hello [89.x.x.x]
>MAIL FROM: <[email protected]>
250 2.1.0 Sender OK
>RCPT TO: <[email protected]>
ERR: Received the following unexpected repsonse:
550 5.7.1 Unable to relay
>QUIT
221 2.0.0 Service closing transmission channel
Here is log from successfully operation:
Connecting to [89.x.x.x] port [25]...
220 smtp.mydomain.com Microsoft ESMTP MAIL Service ready at Fri, 24 Jan 2014 18:04:52 +0100
>HELO webserver
250 smtp.mydomain.com Hello [89.x.x.x]
>MAIL FROM: <[email protected]>
250 2.1.0 Sender OK
>RCPT TO: <[email protected]>
250 2.1.5 Recipient OK
>RCPT TO: <[email protected]>
250 2.1.5 Recipient OK
>DATA
354 Start mail input; end with <CRLF>.<CRLF>
>From: Dane <[email protected]>
>To: [email protected]
>Subject: asd
>Date: Fri, 24 Jan 2014 18:03:08 +0100
>X-Mailer: Qm Version 2.1
>MIME-Version: 1.0
Content-type: text/plain
>
>test>
250 2.6.0 <3ffb1fd6-e5e0-4232-9a6e-cac7b59db9df@exchange.mylocaldomain.local> [InternalId=6240587481093] Queued mail for delivery
>QUIT
221 2.0.0 Service closing transmission channel
And here is picture:

Hello,
Thank you for your post.
This is a quick note to let you know that we are performing research on this issue.
Regards,
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

Outlook advanced search & Exchange 2013 - "Sent to...." field doesn't work correctly in online mode?

Hello,<o:p></o:p>
We've come across what seems to be a problem with advanced find in Outlook in online mode, when used with Exchange 2013.
Using the "Messages" tab of "Advanced Find", anything typed into the "Sent to...." field produces no search results. If the field is populated by clicking
"Sent to..." and selecting a name from a contact list or GAL, results are returned.
eg.
Sent items contains messages to "Charlie" who has the email address
[email protected] and sender is
"Dave" who has the email address
[email protected]
Entering "charlie" or
[email protected], (or any previously acceptable partial term such as "charl" or "@contoso.com") into the "Sent to"" field produces no results. If the user exists in a contact
list and is selected from it, the search works fine. The same is true searching the inbox, using the local user's id of "Dave" or
[email protected]
We've confirmed this issue occurs at four client's sites, plus our own internal Exchange 2013 CU3 system. Four of the sites have been transitioned from Exchange 2010, the fifth was a completely new installation. The problem occurs with Outlook
2007, 2010 and 2013.
This works fine in cached mode (not a solution as our clients are predominantly Citrix/RDS). Exchange search doesn't report any issues and the index states are all "healthy",
we've also tried rebuilding the indexes with no improvement.
Any ideas would be appreciated, or even if someone else can confirm they see the same thing.
Thanks.

Hi Winnie,
Thanks for your reply, and I'm sorry I've not responded earlier. While this problem is one that's annoying several of our clients, and while I have been doing further testing and investigation, it's had to take a back seat to other more pressing issues
until now.
OWA search works fine, as does using "From:" in instant search, and the "From" query on the Advanced tab in Advanced Find. The search services have been restarted, indexing state and copy status etc are all healthy, the indexes
have been rebuilt/reseeded, and I've gone through the diagnostics again. Nothing is logged in event viewer, and the only error that comes up when checking failed index docs for a user are for unsupported format handlers (.png etc).
The issue seems purely to be with the "Sent to..." field on the Messages tab, it's as if it gets completely ignored. The search returns instantly with "There are no items to show in this view". Just to make sure I wasn't losing
my marbles, I've compared searches on Exchange 2007 and 2010, and on those I can enter as little as a single letter or email domain and receive the expected results. On 2013 I get nothing whatsoever whatever I enter, unless I pick an address from a contact
list.
At this point, I thought that since Office 365 is Exchange 2013 based it'd be worth testing that, and sure enough I got exactly the same issue. I setup an Office 365/Outlook 2010 profile on a machine that is currently in an existing Exchange 2010
environment where search works correctly, searching Office 365 doesn't work on that either.
EDIT - Ignore this bit, a fresh install of Windows 7 and Office 2010 doesn't work with Office 365 either. I am exploring another avenue. I setup a fresh Windows 7 VM, installed Office 2010 and connected that to Office 365, search worked fine,
so I'm now looking into what the difference with that VM and the servers and workstations out "in the wild" could be. For example, the test VM isn't on a domain, it's not fully patched, it has no additional software installed etc. Outside
of Microsoft applications and operating systems and having similar configurations, I haven't isolated a common link across all of our client sites that are affected, there's no single 3rd party application or anti-virus solution in place at all of them for
example.
I'll update with any findings, but if you or anyone else has any idea in the meantime I'd be grateful for your input.
Regards.

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

Exchange 2013 - The Microsoft Exchange Transport service is rejecting message submissions because the service continues to consume more memory than the configured threshold

Noticed at about noon that no emails had been received all day. Began to investigate and found that the MS Exchange Transport service had been set to deny email submission because it was using too much memory on the server (91%).
The error message makes me think that we may have been getting used by malware or something similar.“The Microsoft Exchange Transport service is rejecting message submissions because the service continues to consume more memory than the
configured threshold.”
There are also several warning messages that list particular IP addresses and say that a connection from that IP was denied because there were already the maximum number of connections (20).
From what I can tell, all of the IP addresses are from Taiwan.
The time period for which some emails may be missing is from close of business yesterday ( 4/3/2014) through about 12:45 today (4/4/2014).
From the time I spent reading and trying to figure out the error, I think we may need to readjust our throttling policies to prevent this from happening.
The exchange server is currently running at 90%+ CPU and 50%+ memory usage the majority of the time, and I’m not sure how to fix it.
Also, I cannot get into EMS I get a access denied message from the destination computer. (Exchange server) I want to get into there to change the throttling policy back to default, since we disabled it.
The Error reads:
The WinRM client cannot process the request. The WinRM client tried to use Kerberos authentication mechanism, but the destination computer <Exchange> returned an 'access denied' error. Change the configuration to allow Kerberos authentication
mechanism to be used or specify one of the authentication mechanism supported by the server. (How do I do this?) To use Kerberos, specify the local computer name as the remote destination. (I'm trying to use EMS while logged into the local Exchange server)
Also verify that the client computer and the destination computer are joined to a domain. (Exchange is on our domain, and the computer trying to connect is the same computer) To use basic, specify the local computer name as the remote destination, specify
Basic authentication and provide user mane and password. Possible authentication mechanisms reported by server.
At line:1 char:1
+ New-PSSession -ConnectionURI "$connectionUri" -ConfigurationName Microsoft.Excha ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : OpenError: (System.Manageme....RemoteRunspace:RemoteRunspace) [New-PSSession], PSRemotingTransportException + FullyQualifiedErrorId : AccessDenied,PSSessionOpenFailed
I assumed control of this exchange system already in place and I do not have much experience with exchange 2013 or server 2012. I do know 2008, but that doesn't help very much in this situation.
Recent changes to the system:
About three days ago we switch our sessions policy to allow many more connections, and I believe this caused the issue. This is what I changed it to:
Made the registry DWORD (32-bit) "Maximum Allowed Sessions Per User" and modified the value to 1000. Location of registry change @ HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSExchangeIS\ParametersSystem
I just changed it to 10 from the 1000. I'm hoping this solves this. So far no.
Also, I am not the best in the shell or command line interfaces. Any help would be wonderful!

Hi,
Yes, could be hardware performance issue. Try recycle the Transport process and see if the issue persists.
Thanks,
Simon Wu
TechNet Community Support

High Amount of Spam on Exchange 2013 - Content Filtering is Enabled but Pfizer Spam Filling Up Everyone's Mailboxes

Hello
Previously I used Exchange 2010 with Forefront Threat Protection installed and this used to do a good job of stopping all the spam.
However since updating to Exchange 2013 earlier this year and enabling the integrated spam filtering everyone noticed a sudden increase in the amount of spam which was getting through which has been bad for a long time.
We have been living with it but in the last 3 weeks everyone has started getting about 40 emails a day from Pfizer for Viagra. All these seem to defeat the content filtering as Viagra is spelt with an extra I and the email address is always different.
Also images in emails are blocked by default but somehow all the images on these spam messages appear for everyone.
I am not sure the spam filtering is working at all and I'm not sure how to tell as ForeFront gives you a nice graphical dashboard but I can find nothing similar to this in Exchange and PowerShell seems the only way to configure the limited functionality
of the content filter.
Is there any way to get rid of these messages as it doesn't look very good when they are constantly popping up for everyone?
Thanks
Robin
Robin Wilson

Hello ManU
Thanks for the reply.
I have checked the logs and see this quite often:
AcceptMessage,,SCL,not available: policy is disabled
But other times it says this:
RejectMessage,550 5.7.1 Message rejected as spam by Content Filtering
Which seems to indicate it is rejecting some.
This is what one of the email headers look like:
Received: from RWS-MAIL.rwsservices.net (192.168.2.151) by
RWS-MAIL.rwsservices.net (192.168.2.151) with Microsoft SMTP Server (TLS) id
15.0.775.38 via Mailbox Transport; Sat, 28 Dec 2013 10:59:26 +0000
Received: from RWS-MAIL.rwsservices.net (192.168.2.151) by
rws-mail.rwsservices.net (192.168.2.151) with Microsoft SMTP Server (TLS) id
15.0.775.38; Sat, 28 Dec 2013 10:58:38 +0000
Received: from [90.169.106.204] (90.169.106.204) by mail.rwsservices.net
(192.168.2.151) with Microsoft SMTP Server id 15.0.775.38 via Frontend
Transport; Sat, 28 Dec 2013 10:58:37 +0000
Date: Sat, 28 Dec 2013 12:05:58 +0200
From: US.Pfizer eStore <[email protected]>
To: robin.wilson <[email protected]>
Message-ID: <[email protected]>
Subject: Dear robin.wilson up to 65% OFF!
X-Mailer: Airmail (223)
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="dd2ee3ea_586bb9e4_6f04"
Return-Path: [email protected]
X-MS-Exchange-Organization-PRD: 001-taxis.co.uk
X-MS-Exchange-Organization-SenderIdResult: Neutral
Received-SPF: Neutral (rws-mail.rwsservices.net: 90.169.106.204 is neither
permitted nor denied by domain of [email protected])
X-MS-Exchange-Organization-Network-Message-Id: e8825204-1f32-48be-a331-08d0d1d30209
X-MS-Exchange-Organization-SCL: 1
X-MS-Exchange-Organization-PCL: 2
X-MS-Exchange-Organization-Antispam-Report: DV:3.3.13223.464;SID:SenderIDStatus Neutral;OrigIP:90.169.106.204
X-EXCLAIMER-MD-CONFIG: 079171ba-394f-46d5-a160-56e416712e8e
X-MS-Exchange-Organization-AVStamp-Enterprise: 1.0
X-MS-Exchange-Organization-AuthSource: rws-mail.rwsservices.net
X-MS-Exchange-Organization-AuthAs: Anonymous
The emails use a different sender email address every time and there is always a poem in very light grey writing in the body of the email. The drugs are always misspelt as well. Is this why these are getting through?
Thanks
Robin
Robin Wilson

Exchange 2013 Reports

Similar Messages

Maybe you are looking for