Our legacy 2007 exchange migration has been completed.  It has been cleanly uninstalled and the server removed from the domain.

For whatever reason in Exchange 2013 we are still getting these event message periodically.

EVENT #	3769234
EVENT LOG	Application
EVENT TYPE	Warning
OPCODE	Info
SOURCE	MSExchange Front End HTTP Proxy
CATEGORY	Core
EVENT ID	3005
DATE / TIME	3/12/2015 10:30:08 AM
COMPUTERNAME	EMAIL
MESSAGE	[Ews] Marking ClientAccess 2010 server mail.domain.com (https://mail.domain.com) as unhealthy due to exception: System.Net.WebException: The operation has timed out at System.Net.HttpWebRequest.GetResponse() at Microsoft.Exchange.HttpProxy.ProtocolPingStrategyBase.Ping(Uri url)

We get 8 of these messages every so often, and each one is a slightly different tail end of the URL: /PowerShell, /owa/Calendar, /rpc/rpcproxy.dll,  /owa, /ecp, /OAB, /Microsoft-Server-ActiveSync, /EWS.

Some of those aren't even available in Exchange 2007!

I double checked in 2013 ECP and there are no other exchange servers found besides the 2013 one.

Running Get-WebServicesVirtualDirectory only shows the proper 2013 exchange server.  So no where should it be thinking the old server needs a health check.

How can I clean up these periodic event log messages?

• Edited by KJSTech1 Thursday, March 12, 2015 2:58 PM

It looks like the Exchange 2007 uninstall process removed the info from AD cleanly.  I do not see any references to the old exchange server at the location you specified above in ADSI Edit.

The Exchange 2013 server is running CU6, so that is def. past SP1.

Should I try to restart the health monitoring services on Exchange 2013?

Ok this seemed to resolve itself.  Doing a filter in Application Event log for Exchange 2013 server, the last event id 3005 warning referencing the old exchange 2007 server was yesterday, 3/12 at 12:45 PM.  Prior to that it was firing every 15 minutes from 3/10 to 3/12.

Here is my timeline of events:

Full Exchange 2013 Migration was completed 3/10

Exch 2007 server was shut down until the morning of 3/10 (just to make sure there were no outstanding dependencies and the organization could run without it).

The early morning of 3/12 Exch 2007 was powered back on, data removed from it, Exchange 2007 uninstalled, and server removed from domain.

I guess it took a few hours for Exchange 2013 to "update" this.

• Marked as answer by KJSTech1 18 hours 17 minutes ago

Ok this seemed to resolve itself.  Doing a filter in Application Event log for Exchange 2013 server, the last event id 3005 warning referencing the old exchange 2007 server was yesterday, 3/12 at 12:45 PM.  Prior to that it was firing every 15 minutes from 3/10 to 3/12.

Here is my timeline of events:

Full Exchange 2013 Migration was completed 3/10

Exch 2007 server was shut down until the morning of 3/10 (just to make sure there were no outstanding dependencies and the organization could run without it).

The early morning of 3/12 Exch 2007 was powered back on, data removed from it, Exchange 2007 uninstalled, and server removed from domain.

I guess it took a few hours for Exchange 2013 to "update" this.

• Marked as answer by KJSTech1 Friday, March 13, 2015 1:05 PM