Exchange 2013 warnings Event ID 10010, 6002, 6027, 1035

I’ve started to get a *lot* of warnings being logged lately with EventID 10010, 1035, 6027 and 6002. The specific cause I don’t know yet, but they have only appeared recently after I have been “fixing” my server after some serious disk issues. It’s hard to say though because there have been so many that my event logs have been clearing out the older entries so I need to increase their size to capture them all. While the server appears to be running fine, these warnings are appearing repeatedly now.

I don’t know if they are because of further issues since the crashes, or have started because of the way I fixed something else. I know I’m not the only one, a lot of other people have posted with the same messages, so perhaps it’s specific to Server 2012, or a recent OS update that has been applied.

Further investigation required…

UPDATE: I’ve seen some reports that this has been fixed in CU1. I haven’t installed it yet, so can’t confirm at this time.
http://technet.microsoft.com/en-us/library/jj983803(v=exchg.150).aspx

Exchange Event Viewer FailoverClustering Query Error

When you open Event Viewer to look at the “Microsoft Exchange with Database Availability Group Events” Custom view you will get a query error for “Microsoft-Windows-FailoverClustering” if you have an Exchange install that doesn’t have any Database Availability Groups (DAGs) installed. This would be typical of a small single server install.

(Check also this post on Event Viewer query errors)

While not critical, it is annoying.

A mobile friendly TMG forms based (FBA) login for Exchange OWA

I came across this blog post while trying to find ways to change the TMG2010 Forms based login page to match the Exchange 2013 OWA page. I haven’t figured out how to do the OWA 2013 thing yet, but I think this will be quite sufficient:

http://www.fastvue.co/blog/mobile-friendly-forefront-tmg-forms-based-authentication-template

Those instructions are specifically for if you are using TMG Form Based Authentication (FBA) in front of a (non-owa/normal) web site. To make it work with Exchange OWA it needs to be done slightly differently. I’m using TMG 2010 and Exchange 2013, but the settings should be the same for Exchange 2007/2010 as well.

Some users unable to connect with ActiveSync

So here’s one that had me stumped. I can’t get ActiveSync connections working for some users on some devices. I’ve found a lot of posts around the internet talking about it being an issue related to self-signed SSL certificates, but I don’t think that is what my problem is.

The environment:

• 1 x Exchange 2013 running on Server 2012
• 1 x Internal private Windows PKI handling certificates
• 3 x Active Directory based user accounts
• 2 x Windows RT Surface tablets
• 1 x iPad Mini
• 2 x PC running Windows 8
• 1 x iPhone
• 2 x Windows Phone 7

A fair collection of devices to compare the issue across.

So what does/used to work?