Excellent. I'm happy to hear that.

Regards,

Michael B. Smith
Consultant and Exchange MVP
http://TheEssentialExchange.com

From: Leedy, Andy [mailto:ale...@butlerschein.com]
Sent: Tuesday, May 03, 2011 2:39 PM
To: MS-Exchange Admin Issues
Subject: RE: Two Exchange 2010 bugs...

Applied the registry fix and both issue [1] and [2] are resolved.  Not sure how 
it could affect [2] but everything seems ok now.

Thanks again!
-Andy

From: Leedy, Andy [mailto:ale...@butlerschein.com]
Sent: Tuesday, May 03, 2011 2:16 PM
To: MS-Exchange Admin Issues
Subject: RE: Two Exchange 2010 bugs...

Thanks!

From: Michael B. Smith [mailto:mich...@smithcons.com]
Sent: Tuesday, May 03, 2011 2:15 PM
To: MS-Exchange Admin Issues
Subject: RE: Two Exchange 2010 bugs...

Sure. http://technet.microsoft.com/en-us/library/cc937923.aspx

I've done this at several of my clients experiencing that issue.

Regards,

Michael B. Smith
Consultant and Exchange MVP
http://TheEssentialExchange.com

From: Leedy, Andy [mailto:ale...@butlerschein.com]
Sent: Tuesday, May 03, 2011 2:11 PM
To: MS-Exchange Admin Issues
Subject: RE: Two Exchange 2010 bugs...

"You can address item [1] by hard coding the netlogon SiteName"

I'm not sure how to accomplish. Do I need to edit a file or the registry? Can 
you elaborate?

Thanks,
Andy

From: Michael B. Smith [mailto:mich...@smithcons.com]
Sent: Tuesday, May 03, 2011 1:55 PM
To: MS-Exchange Admin Issues
Subject: RE: Two Exchange 2010 bugs...

You can address item [1] by hard coding the netlogon SiteName. This is a 
Windows problem at its core. Exchange MAY end up coding around it, but they 
expect (hope) Windows will address it. Both teams are certainly aware of this 
problem.

I've not seen item [2] or heard it discussed. My initial SWAG would be to set 
the startup on that service to "Automatic (Delayed Start)", set the service to 
auto-restart, and have a script in Task Scheduler that runs "10 minutes after 
boot" (or another appropriate value) to start the service. Generally, I catch 
and autocorrect things like this with monitoring solutions such as Operations 
Manager.

Regards,

Michael B. Smith
Consultant and Exchange MVP
http://TheEssentialExchange.com

From: Leedy, Andy [mailto:ale...@butlerschein.com]
Sent: Tuesday, May 03, 2011 1:27 PM
To: MS-Exchange Admin Issues
Subject: Two Exchange 2010 bugs...

I found two bugs in Exchange 2010.  They both have to do with services starting 
in the proper order. Or in this case the incorrect order.


1)      MSExchange ADAccess Event ID's 2601, 2604, 2501 in application logging 
every 15 minutes. This happens after every reboot and continues every 15 
minutes because Exchange services startup before the server is able to talk to 
the AD.  The solution according to Microsoft is restart the Exchange AD 
Topology service.  It sucks to restart that service every time you reboot. 
Restarting the Exchange AD Topology service, restarts ALL the Exchange services.



Here's a link to the issue:



http://support.microsoft.com/kb/2025528



Cause: "During a restart of the server, the operating system queries Active 
Directory to get its AD Site information.  On a Windows 2008 R2 server, this 
will sometimes fail.  As the Exchange services are starting, it also will do a 
query for its AD Site and that too will fail. Windows will continue to try and 
determine its AD Site name and will eventually succeed.  However, Exchange does 
not re-try the query and the above errors are logged in the application log 
every 15 minutes."




2)      Microsoft Exchange Forms-Based Authentication service doesn't start at 
boot because Web Publishing service has not yet started. Unless you start the 
Exchange Forms-Based Authentication service, your CAS OWA is down. Microsoft's 
solution is start the service.

<Rant On> I hope Microsoft addresses these issues in a future rollup.  I would 
have thought that by SP1 issues like this would have been fixed. That's one 
reason I didn't push for 2010 when it first came out. It seems like no MS 
software is stable/usable until at least SP1. By the time the issues are 
resolved though, the next version is out. In Exchange 2007, there was a CCR 
replication issue that logged erroneous errors. I reported it to MS and spent 
many hours helping them test patches. They never did fix the issue so I just 
learned to ignore the errors in the Event log. I was hoping somehow Exchange 
2010 would be different. </Rant Off>


Until then I guess I'll just run this script whenever the server is rebooted.

#Restart Services after reboot.
net stop MSExchangeTransportLogSearch
net stop MSExchangeTransport
net stop MSExchangeServiceHost
net stop MSExchangeRPC
net stop MSExchangeProtectedServiceHost
net stop MSExchangeMailboxReplication
net stop MSExchangeFDS
net stop MSExchangeAntispamUpdate
net stop MSExchangeAB
net stop MSExchangeADTopology

net start MSExchangeADTopology
net start MSExchangeAB
net start MSExchangeAntispamUpdate
net start MSExchangeFDS
net start MSExchangeMailboxReplication
net start MSExchangeProtectedServiceHost
net start MSExchangeRPC
net start MSExchangeServiceHost
net start MSExchangeTransport
net start MSExchangeTransportLogSearch

net start MSExchangeFBA



---
To manage subscriptions click here: 
http://lyris.sunbelt-software.com/read/my_forums/
or send an email to 
listmana...@lyris.sunbeltsoftware.com<mailto:listmana...@lyris.sunbeltsoftware.com>
with the body: unsubscribe exchangelist


**********************************************************************

CONFIDENTIALITY NOTICE - The information transmitted in this message is 
intended only for the person or entity to which it is addressed and may contain 
confidential and/or privileged material. Any review, retransmission, 
dissemination or other use of this information by persons or entities other 
than the intended recipient is prohibited. If you received this in error, 
please contact the sender and destroy all copies of this document. Thank you.

Butler Schein Animal Health

**********************************************************************

---
To manage subscriptions click here: 
http://lyris.sunbelt-software.com/read/my_forums/
or send an email to 
listmana...@lyris.sunbeltsoftware.com<mailto:listmana...@lyris.sunbeltsoftware.com>
with the body: unsubscribe exchangelist

---
To manage subscriptions click here: 
http://lyris.sunbelt-software.com/read/my_forums/
or send an email to 
listmana...@lyris.sunbeltsoftware.com<mailto:listmana...@lyris.sunbeltsoftware.com>
with the body: unsubscribe exchangelist

---
To manage subscriptions click here: 
http://lyris.sunbelt-software.com/read/my_forums/
or send an email to 
listmana...@lyris.sunbeltsoftware.com<mailto:listmana...@lyris.sunbeltsoftware.com>
with the body: unsubscribe exchangelist

---
To manage subscriptions click here: 
http://lyris.sunbelt-software.com/read/my_forums/
or send an email to 
listmana...@lyris.sunbeltsoftware.com<mailto:listmana...@lyris.sunbeltsoftware.com>
with the body: unsubscribe exchangelist

---
To manage subscriptions click here: 
http://lyris.sunbelt-software.com/read/my_forums/
or send an email to listmana...@lyris.sunbeltsoftware.com
with the body: unsubscribe exchangelist

Reply via email to