Put some plain language into the error messages

and is formatted that way because that is the way that Microsoft writes the error. 

Hi Jeremy,

Dare I point out that we use AD authentication with Tripwire and while their raw error message contains that same text (I remember the "vece" part fondly), they do report the other details in their alerts? :-)

It's just that it is a 99% useless error message. It requires me to obliquely recognize what it really means after I open the MHT attachment and then request one of the infrastructure folks track down what happened because security does not have access to AD (separation of duties and all that). It requires that at least two people get involved for each failed authentication alert.

If the alert had the user name and source IP, I could handle it myself immediately.

I won't go into what has to happen when it occurs off-hours and I can't open the MHT attachment on my phone. :-)

Ray

that we should include more useful information on our alerts/notifications as well as being able to have them sent in another format.

I had the same reaction the first time I had a case where the customer was wondering what in the world that error referred to. 

It is a good idea.