I have a requirement to let Smtp virtual server receive incoming emails and send it to the drop folder.

the domain of the SMTP is different than the local domain. I created an alias. but it did not work.

any help

Mashhour Faraj

Hi all

Have the following Exchange 2013 Environment:

2X CAS
2X MBX

all running CU9.

Every minutes the following happens on the two Mailbox Servers:

Event 1, MSExchange Error Logging Module

(Process w3wp.exe, PID 6796) "Unhandled exception 'Object reference not set to an instance of an object.' when processing request /powershell?ping=probe."

Event 1309, ASP.NET 4.0.30319.0

Event code: 3005

Event message: An unhandled exception has occurred.

Event time: 19.07.2015 17:16:49

Event time (UTC): 19.07.2015 15:16:49

Event ID: c83ef382e7624e6997e51f4b989b3692

Event sequence: 1696

Event occurrence: 1509

Event detail code: 0

Application information:

    Application domain: /LM/W3SVC/1/ROOT/PowerShell-1-130817022857915843

    Trust level: Full

    Application Virtual Path: /PowerShell

    Application Path: C:\Program Files\Microsoft\Exchange Server\V15\ClientAccess\PowerShell\

    Machine name: server1

Process information:

    Process ID: 6796

    Process name: w3wp.exe

    Account name: NT AUTHORITY\SYSTEM

Exception information:

    Exception type: NullReferenceException

    Exception message: Object reference not set to an instance of an object.

   at Microsoft.Exchange.Configuration.Core.WindowsIdentityToGenericIdentityModule.OnAuthenticateRequest(Object source, EventArgs e)

   at System.Web.HttpApplication.SyncEventExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()

   at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)

Request information:

    Request URL: http://server1.dom.local/powershell?ping=probe

    Request path: /powershell

    User host address: fe80::cd13:2806:71ca:37446796

    User: 

    Is authenticated: False

    Authentication Type: 

    Thread account name: NT AUTHORITY\SYSTEM

Thread information:

    Thread ID: 11

    Thread account name: NT AUTHORITY\SYSTEM

    Is impersonating: False

    Stack trace:    at Microsoft.Exchange.Configuration.Core.WindowsIdentityToGenericIdentityModule.OnAuthenticateRequest(Object source, EventArgs e)

   at System.Web.HttpApplication.SyncEventExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()

   at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)

Custom event details:

Something with Powershell.

Thank you for your help.

Best regards

Stefan

Hi all,

Exchange 2013 CU1 has a new OWA LogOff behaviour when Basic or Windows Integrated Authentication is configured. When clicking the LogOff Button you receive the message "Close All your Browser Windows.." but OWA does not sign out. This is not the case when using Formbased Authentication...

The problem in our case is the OWA publishing over the Internet via TMG. When publishing via TMG, only Basic and NTLM authentication is supported. This means you have to change the Authentication for the OWA Virtual Directory to basic or Windows Integrated. OK so far, now we can use the TMG Authentication Form. but... TMG is not able to Catch the OWA LogOff. So we will still receive "Close all your Browser Settings.." and no log out from OWA.

It is a known issue that TMG cannot catch the OWA Logoff with the Exchange 2013 CU1 Release..So my Question:Does anyone get that "Real LogOut" fixed via TMG or directly on the CAS Server for Exchange 2013 CU1?

I know another possibility is to activate Form Based Authentication on the CAS Servers and external users directly authenticate against the CAS Server without pre-authentication at TMG Level, but this of course does not provide the highest security we can have.

I have a new Exchange 2010 install on a new 2012 R2 server. I have successfully migrated the old Exchange server to the new one but when I run EMC and try to change to view the new server it gives the following error:

I have been working on a solution for about a month now and keep running into dead ends. I have deleted and recreated the bindings in IIS after removing the HOSTS  from both 443 and 80. Both are using a * for the IP Address.

I have also made sure that WinRM is recognizing both IPv4 and IPv6 when I view the config.

Any help would be awesome!

Hi Forum Members,

I seem to be getting a lot of these errors and can't seem to resolve it. I have a 2 node DAG with five (5) mailbox databases. Content Index of just two databases are healthy on just a server while all others show failed on both servers. Please can someone help with resolving this as I believe this is the key to permanently solving this content index issues. Please see image of error below:

Hello,

I have a client in my network, the client have some issue with the outlook sync.

Anyone know how to fix this issue?

We migrate Exchange 2007 to Exchange 2013. Exchange 2007 co-exist with Exchange 2013 now. Out of Office does not work ( not replay) for all migrated mailbox on Exchange 2013 in several databases. Remain mailboxes on Exchange 2007 send OOF without problem. Users on Exchange 2013 turn on oof without problem, but senders do not get oof replay messages

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

Hi,

Is there any seetings in Exchange 2013 (O365 V15 tenant) to restrict attachment counts in a single Email ? If the setup is already available and configured how to know the details ?

Regards

Rakesh

Several months ago, I completed a staged migration of our users (~90 users) from our Exchange 2007 on-premise server to Office365.  All is well, and I'm now ready to deprecate the aging Exchange 2007 on-premise box which I no longer use for any other purpose than to create users.

I'm using DirSync (recently upgraded to Azure AD connect actually) to sync AD to Office365.  Currently, if I have a new user, I create them via EMC to allow me to configure the proxy address and SMTP external address (contoso.onmicrosoft.com for example) and then edit remaining properties via AD once the user has been created.  In order to remove the Exchange 2007, do I simply decommission and uninstall, which will then allow me to manage Exchange fields for users in EAC Exchange Online for Office365? Or do I need to keep a local on-premise server installation if only for the EAC 2013?  Or will I still be able to edit Attributes (AD is 2007) for Exchange, then allow Azure Sync to connect, then enable licenses?

Thanks in advance for any clarity.

-TarTech

hi all,

i get a lot of this error's in the eventvwr.

How can I resolve this?

event id 4

source managedavailability.

Maintenance workitem "XmlDefinitionReaderWorkItem" (ID: 11) has failed. Health Manager has detected it is either set to run once and failed, or has been failing consistently. Maintenance workitem failure could cause monitoring gap and should be investigated.
The error message from the last result is:
System.Exception: The following definitions were not created successfully:
Wac Discovery Failure Event Maintenance Workitem: An item with the same primary key 136 already exists in the table. Existing definition name: Wac Discovery Failure Event Maintenance Workitem. New definition name: Wac Discovery Failure Event Maintenance Workitem

   at Microsoft.Office.Datacenter.ActiveMonitoring.XmlDefinitionReaderWorkItem.DoWork(CancellationToken cancellationToken)
   at Microsoft.Office.Datacenter.WorkerTaskFramework.WorkItem.Execute(CancellationToken joinedToken)
   at Microsoft.Office.Datacenter.WorkerTaskFramework.WorkItem.<>c__DisplayClass2.<StartExecuting>b__0()
   at System.Threading.Tasks.Task.Execute()

-------------------------------------------------------------------------------

States of all monitors within the health set:
Note: Data may be stale. To get current data, run: Get-ServerHealth -Identity 'PRD-MXSRV002' -HealthSet 'Monitoring'

State               Name                                    TargetResource                     HealthSet                     AlertValue     ServerComponent     
-----               ----                                    --------------                     ---------                     ----------     ---------------     
NotApplicable       HealthManagerWorkItemQuarantineMonitor                                     Monitoring                    Healthy        None               
NotApplicable       ServerHealthStateCollectionMonitor      PRD-MXSRV002                       Monitoring                    Healthy        None               
NotApplicable       MaintenanceFailureMonitor.Monitoring                                       Monitoring                    Healthy        None               
NotApplicable       HealthManagerSchedulingLatencyMonitor                                      Monitoring                    Healthy        None               
NotApplicable       PrivateWorkingSetWarning.M.exchange.... microsoft.exchange.monitoring      Monitoring                    Healthy        None                
NotApplicable       PrivateWorkingSetError.M.exchange.mo... microsoft.exchange.monitoring      Monitoring                    Healthy        None                
NotApplicable       ProcessProcessorTimeWarning.M.exchan... microsoft.exchange.monitoring      Monitoring                    Healthy        None                
NotApplicable       ProcessProcessorTimeError.M.exchange... microsoft.exchange.monitoring      Monitoring                    Healthy        None                
NotApplicable       PrivateWorkingSetWarning.msexchangeh... msexchangehmhost                   Monitoring                    Healthy        None                
NotApplicable       PrivateWorkingSetError.msexchangehmhost msexchangehmhost                   Monitoring                    Healthy        None                
NotApplicable       ProcessProcessorTimeWarning.msexchan... msexchangehmhost                   Monitoring                    Healthy        None                
NotApplicable       ProcessProcessorTimeError.msexchange... msexchangehmhost                   Monitoring                    Healthy        None                
NotApplicable       MaintenanceTimeoutMonitor.Monitoring                                       Monitoring                    Healthy        None               
NotApplicable       CrashEvent.M.exchange.monitoring        microsoft.exchange.monitoring      Monitoring                    Healthy        None                
NotApplicable       CrashEvent.msexchangehmhost             msexchangehmhost                   Monitoring                    Healthy        None               
NotApplicable       PrivateWorkingSetWarning.msexchangeh... msexchangehmworker                 Monitoring                    Healthy        None                
NotApplicable       PrivateWorkingSetError.msexchangehmw... msexchangehmworker                 Monitoring                    Healthy        None                
NotApplicable       ProcessProcessorTimeWarning.msexchan... msexchangehmworker                 Monitoring                    Healthy        None                
NotApplicable       ProcessProcessorTimeError.msexchange... msexchangehmworker                 Monitoring                    Healthy        None                
NotApplicable       CrashEvent.msexchangehmworker           msexchangehmworker                 Monitoring                    Healthy        None                


States of all health sets:
Note: Data may be stale. To get current data, run: Get-HealthReport -Identity 'PRD-MXSRV002'

State               HealthSet                     AlertValue     LastTransitionTime       MonitorCount        
-----               ---------                     ----------     ------------------       ------------        
Online              HubTransport                  Healthy        6/07/2015 15:45:33       96                  
Online              RWS.Proxy                     Healthy        28/04/2015 21:21:26      11                  
NotApplicable       ProcessIsolation              Healthy        2/09/2014 21:36:22       25                 
Online              RPS.Proxy                     Healthy        28/04/2015 21:21:27      6                   
NotApplicable       MessageTracing                Healthy        2/09/2014 21:35:52       5                   
NotApplicable       ActiveSync                    Healthy        28/04/2015 21:32:44      2                   
NotApplicable       ExtendedReportWeb             Healthy        2/09/2014 21:35:49       7                  
NotApplicable       Autodiscover.Protocol         Healthy        28/04/2015 21:21:26      8                  
NotApplicable       Search                        Healthy        5/05/2015 19:02:17       123                 
Online              Autodiscover.Proxy            Healthy        28/04/2015 21:21:26      1                   
Online              OWA.Proxy                     Healthy        28/04/2015 21:21:28      2                   
NotApplicable       FIPS                          Healthy        2/09/2014 21:34:35       7                   
Online              ActiveSync.Proxy              Healthy        28/04/2015 21:21:59      1                   
Online              OAB.Proxy                     Healthy        28/04/2015 21:21:28      1                   
Online              ECP.Proxy                     Healthy        28/04/2015 21:20:37      1                   
NotApplicable       ActiveSync.Protocol           Healthy        28/04/2015 21:23:40      7                  
NotApplicable       UM.Protocol                   Healthy        9/02/2015 7:21:27        24                  
Online              EWS.Proxy                     Healthy        28/04/2015 21:21:25      1                   
NotApplicable       Autodiscover                  Healthy        28/04/2015 21:22:20      4                   
NotApplicable       ECP                           Healthy        28/04/2015 21:21:26      12                  
NotApplicable       EventAssistants               Healthy        2/09/2014 21:58:26       20                 
NotApplicable       EDS                           Healthy        2/09/2014 22:18:41       43                  
NotApplicable       AD                            Healthy        25/11/2014 15:04:11      24                  
NotApplicable       EWS.Protocol                  Healthy        28/04/2015 21:22:41      8                   
NotApplicable       MailboxMigration              Healthy        25/11/2014 15:06:19      24                 
NotApplicable       EWS                           Healthy        28/04/2015 21:22:29      4                   
Online              FrontendTransport             Healthy        28/04/2015 20:41:13      12                  
NotApplicable       Monitoring                    Healthy        6/07/2015 15:48:06       20                  
NotApplicable       OWA.Protocol.Dep              Unhealthy      6/07/2015 7:27:30        2                  
NotApplicable       DataProtection                Healthy        1/04/2015 9:56:01        106                 
NotApplicable       MailboxTransport              Healthy        25/11/2014 16:06:49      31                 
NotApplicable       MSExchangeCertificateDeplo... Disabled       1/01/0001 1:00:00        2                  
NotApplicable       Network                       Healthy        2/09/2014 21:40:46       4                   
NotApplicable       OWA.Protocol                  Healthy        21/06/2015 19:18:26      7                   
NotApplicable       OWA                           Healthy        28/04/2015 21:24:25      46                  
NotApplicable       RemoteMonitoring              Healthy        5/11/2014 16:44:06       4                  
NotApplicable       PublicFolders                 Healthy        2/09/2014 21:46:42       6                   
NotApplicable       RPS                           Healthy        28/04/2015 21:28:22      12                  
NotApplicable       SiteMailbox                   Healthy        2/09/2014 21:38:53       3                   
NotApplicable       Store                         Healthy        28/04/2015 20:14:19      137                 
NotApplicable       UserThrottling                Healthy        2/09/2014 22:04:09       7                   
Online              UM.CallRouter                 Healthy        9/02/2015 7:21:27        10                  
NotApplicable       DAL                           Healthy        25/03/2015 12:13:41      21                  
NotApplicable       IMAP.Protocol                 Healthy        30/12/2014 12:15:56      12                  
Online              IMAP.Proxy                    Healthy        30/12/2014 12:15:56      1                   
NotApplicable       IMAP                          Healthy        30/12/2014 12:15:56      1                   
NotApplicable       AMScanTimeout                 Healthy        2/09/2014 21:23:45       6                   
NotApplicable       AMScanError                   Healthy        2/09/2014 21:38:01       11                  
NotApplicable       AMMessagesDeferred            Healthy        2/09/2014 21:23:41       1                  
NotApplicable       AMADError                     Healthy        2/09/2014 21:30:49       2                   
NotApplicable       AMTenantConfigError           Healthy        2/09/2014 21:24:00       1                  
NotApplicable       Compliance                    Healthy        6/07/2015 8:40:33        22                  
NotApplicable       DLExpansion                   Healthy        2/09/2014 21:34:06       3                   
NotApplicable       Ediscovery.Protocol           Healthy        6/05/2015 1:39:21        1                  
NotApplicable       AMScanners                    Healthy        2/09/2014 21:23:45       2                   
NotApplicable       OAB                           Healthy        25/11/2014 15:05:46      10                  
NotApplicable       EAS                           Healthy        2/09/2014 21:33:09       2                   
NotApplicable       ClientAccess.Proxy            Healthy        2/09/2014 21:32:36       2                  
Online              Transport                     Healthy        2/09/2014 21:32:35       2                   
NotApplicable       FfoMonitoring                 Disabled       1/01/0001 1:00:00        24                  
NotApplicable       FreeBusy                      Healthy        2/09/2014 21:33:10       2                   
NotApplicable       BitlockerDeployment           Healthy        2/09/2014 21:33:48       2                  
NotApplicable       FEP                           Healthy        2/09/2014 21:35:27       2                   
NotApplicable       FfoRws                        Healthy        2/09/2014 21:34:09       2                   
NotApplicable       Places                        Healthy        2/09/2014 21:24:06       2                   
NotApplicable       Clustering                    Healthy        2/09/2014 21:35:06       5                   
NotApplicable       AMEUS                         Healthy        2/09/2014 21:23:45       4                   
NotApplicable       AMScannerCrash                Healthy        2/09/2014 21:23:45       1                   
NotApplicable       AMFMSService                  Healthy        6/09/2014 16:04:37       6                   
NotApplicable       Outlook.Protocol              Healthy        28/04/2015 21:29:12      17                 
NotApplicable       OutlookMapiHttp.Protocol      Healthy        28/04/2015 21:31:25      2                  
NotApplicable       AntiSpam                      Healthy        2/09/2014 21:33:51       5                   
NotApplicable       Security                      Healthy        2/09/2014 21:35:59       6                   
NotApplicable       CentralAdmin                  Healthy        2/09/2014 21:35:18       5                   
NotApplicable       Datamining                    Healthy        2/09/2014 21:35:58       10                  
NotApplicable       Provisioning                  Healthy        2/09/2014 21:36:00       5                   
NotApplicable       POP.Protocol                  Healthy        2/09/2014 21:36:15       10                  
Online              OutlookMapiHttp.Proxy         Healthy        28/04/2015 21:22:04      6                  
NotApplicable       Calendaring                   Healthy        2/09/2014 21:35:43       5                   
NotApplicable       Psws                          Healthy        2/09/2014 21:35:52       10                  
NotApplicable       PushNotifications.Protocol    Healthy        2/09/2014 21:33:27       5                  
NotApplicable       OutlookMapiHttp               Healthy        28/04/2015 21:17:35      1                  
NotApplicable       Outlook                       Healthy        28/04/2015 21:29:54      1                   
NotApplicable       AMService                     Healthy        25/11/2014 15:04:04      6                   
Online              Outlook.Proxy                 Healthy        28/04/2015 21:21:59      6                   
Online              EdgeTransport                 Healthy        2/09/2014 21:35:20       4                   
NotApplicable       Antimalware                   Healthy        25/11/2014 15:04:14      2                   
NotApplicable       EmailManagement               Healthy        2/09/2014 21:26:10       2                  
NotApplicable       FfoCentralAdmin               Healthy        2/09/2014 21:32:43       2                  
NotApplicable       JournalArchive                Healthy        2/09/2014 21:34:22       1                   
NotApplicable       UnifiedMailbox                Healthy        2/09/2014 21:23:54       2                   
NotApplicable       UnifiedGroups                 Healthy        2/09/2014 21:36:17       24                  
NotApplicable       PeopleConnect                 Healthy        2/09/2014 21:23:54       8                   
NotApplicable       OWA.WebServices               Healthy        2/09/2014 21:23:54       1                  
NotApplicable       HDPhoto                       Healthy        2/09/2014 21:23:56       10                  
NotApplicable       OWA.SuiteServices             Healthy        2/09/2014 21:23:56       2                  
NotApplicable       RemoteStore                   Healthy        2/09/2014 21:32:36       1                   
NotApplicable       RWS                           Healthy        2/09/2014 21:34:51       1                   
Online              SharedCache                   Healthy        2/09/2014 21:35:45       5                   
NotApplicable       FfoUcc                        Healthy        2/09/2014 21:36:21       5                   
NotApplicable       E4E                           Healthy        2/09/2014 21:35:33       5                   
NotApplicable       HxService.Mail                Healthy        2/09/2014 21:35:16       5                   


Note: Subsequent detected alerts are suppressed until the health set is healthy again.

I've been looking at my Exchange 2013 servers this week and wondering about the IIS application pools. There are a number of issues that make me wonder about recycling the app pools, the worst being that on several of my servers I see the MSExchangePowerShellAppPool having allocated in excess of 6GB memory.

Are there any recommendations, or a white paper about the virtues or hazards of recycling the Exchange 2013 IIS Application pools?

If recycling is not a bad thing, what how should it be configured:
- on a scheduled basis?  weekly, daily, every 6 hours ?
- triggered on an event?  after consuming more thatn xxx GB memory ?

Does anyone have any thoughts on tis subject?

Tom

I just read an article about configuring legacy public folder access for Exchange 2013 users to access Exchange 2007 Public Folders
     http://www.exchange2013.es/on-premises-legacy-public-folder-coexistence-for-exchange-2013-cumulative-update-7-and-beyond/

I currently have the "PublicFolderDatabase" field set on my 2013 databases, but going to change one of them today, I get the message that this field has been deprecated.

So, it looks like I need to make changes using set-organizationconfig to configure user access to legacy publicfolders.
Looking at settings that should be made, I am looking at configuring using.....
     - PublicFoldersEnabled Local
My legacy 2007 and 2013 Exchagne systems are in the same organization.
     - RemotePublicFolderMailboxes pfmb01,pfmb02,pfmb03
But wait, the write up on technet says that the remote mailboxes are only used if the public folder is deployed in a remote forest!!!!

If thess fields refer to remote forests, and the publicfolderdatabase field is being deprecated, how am i supposed to refer my 2013 users to legacy, same org, public folders???

Tom

Hello,

An AD user account linked to a mailbox was deleted several months back.  I was wondering where can I verify the retention period for a mailbox before it gets purged after the AD user has been deleted?

I've looked into Retention Policies but I am not sure they are being used since there are no mailboxes linked to the policies.

Thank you,

Jeannette

Hello all,

My exchange environment seems to be working well, although in my eventvwr i get the error:

"Microsoft Exchange could not load the certificate with thumbprint of 356538ED3D9052E44DF25C54292DE586E1A22D from the personal store on the local computer. This certificate was configured for authentication with other Exchange servers. Mail flow to other Exchange servers could be affected by this error. If the certificate with this thumbprint still exists in the personal store, run Enable-ExchangeCertificate 356538ED3D9052E44D2CF25C292DE586E1A22D -Services SMTP 

I dont have a certificate like that in my personal store. I only have certificates for mail.contoso.com from godaddy, as well as a cert that just says EXCHANGE2013 (my computer name) and a Microsoft Exchange Server Aut... and WMSVC-Exchange2013.

None of these have the thumbprint described in the error.

Is this something i should be worrying about? Some articles suggest running new-exchangecertificate , but will this replace or mess up my existing certs?

Thanks.

Aditya Mediratta

I am parsing X-Forefront-Antispam-Report and X-Microsoft-Antispam headers with on-Prem rules leveraging EOP SCL, BCL, and PCL scores.

Exchange 2013 SP1 on-Prem does not seem to parse these SCL, BCL, and PCL scores from these headers, and rewrite them into the X-MS-Exchange-Organization headers for Delete, Reject, and Junk E-Mail folder processing automatically.  While I can create custom Mail Flow rules on-Prem to do so it seems very segregated, and not a Microsoft Integrated solution.

In fact, in the implementation documentation, I only found guidance to parse SFV:SPM and SFV:SKS from the X-Header, but this is far from enough.  https://technet.microsoft.com/en-us/library/JJ837173(v=EXCHG.150).aspx

Example Message Header.  X-MS-Exchange-Organization-SCL was marked by on-Prem Rule inspecting for SFV:SPM for delivery to Junk E-Mail folder.  Had the X-Forefront-Antispam-Report SCL been rewritten into the X-MS-Exchange-Organization-SCL, the message would have been rejected or deleted as a SCL score of 9.

X-Forefront-Antispam-Report: CIP:212.48.64.30;CTRY:IL;IPV:NLI;EFV:NLI;SFV:SPM;SFS:(6009001)(2980300002)(428002)(318001);DIR:INB;SFP:;SCL:9;SRVR:DM2PR12MB0555;H:xxxxxx;FPR:;SPF:None;MLV:ovr;A:1;MX:1;PTR:xxxxxx;LANG:en;
X-Microsoft-Antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:DM2PR12MB0555;
X-OrganizationHeadersPreserved: DM2PR12MB0555.namprd12.prod.outlook.com
X-MS-Exchange-Organization-Network-Message-Id: 2a2a7963-b1b2-4e4d-4a15-08d292a143e1
X-MS-Exchange-Organization-AVStamp-Enterprise: 1.0
X-MS-Exchange-Organization-SCL: 3

Are there efforts to improve the 'sharing' of SCL, BCL, PCL scoring between EOP and Exchange 2013 SP1 on-Prem?

Ok Folks,

Originally I was getting access to the http://localhost/ecp page but now when I type this URL I get the OWA page and only after flushing the cache on the browser I can see the Exchange Admin login page. But then I try logging in and I get a Page Not Found error!!

Is there a way to reset the IIS ecp virtual directory or perhaps when I set the Application Pool items to ApllicationPoolIdentity which BPA was compalining about it broke then. To be honest I think it may also be a certificate problem, Im kinda grasping at straws here and need to know how to reinstall the ECP component??

Ill stop my rambling and let an expert hold my hand please!!

Jim

Jim

EOP Message Trace is nice, but as discussed in this blog, why is this feature not available in Exchange 2013 SP1 on-Prem?

http://blogs.technet.com/b/exchange/archive/2014/02/04/extending-message-trace-to-90-days-in-exchange-online.aspx

In Exchange 2013 on-Prem, as others have mentioned in the blog comments, "Delivery Reports" is too limited.  For exchange diagnostic analysis, specifically with NDR, and Rule processing, "Message Trace" in EOP is nice (as in my environment, all inbound and outbound mail goes through EOP), but I'd also prefer to be able drill to this detail on-Prem for messages I am processing with on-Prem rules.  PowerShell is not as remotely accessible, or simple.