Thanks for the quick response. Ok except... I have Event ID 10016 and Vista
lead me to a "COM Security Policy Configuration" for Server 2008. Sounds
like the same issue just different solutions from MSFT? I can only assume a
whole bunch of people using Vista in a home network get these meaningless
errors and just don't look at the event log or complain? Think maybe MSFT
will fix whatever is causing them for Vista? The only reason I was looking
at the event errors is becasue one of the machines was booting very slow
after I installed a SP1 and a SATA DVD Drive on the Intel controller set for
Raid. I updated the Intel driver and all those issues went away - thank you
Google and the Internet. The slow booting had nothing to do with SP1.
"Mark L. Ferguson" <MarkLFerguson@xxxxxx> wrote in
message news:92C5557A-B184-4D28-B414-F22EE24775E5@xxxxxx
Quote:
> Since you are not connected to a domain, and don't use Kerberos sign on
> validation, that error, and the Com error are meaningless in your context.
> DCOM Error Messages Logged in Event Log:
> http://support.microsoft.com/kb/298095/en-us
> --
> Was this helpful? Then click the Ratings button. Voting helps the web
> interface.
> http://www.microsoft.com/wn3/locales...eAPostAsAnswer
> Mark L. Ferguson
> .
>
> "Ken" <krlorenz@xxxxxx> wrote in message
> news:#Y5kKc5jIHA.6136@xxxxxx Quote:
>> I thought I had "clean machines" until I installed SP1. Now I get two
>> new errors - Kerberos event id 15016 and DistributedCOM event id 10016.
>> Any suggestions on how to make these go away. Seems like Server 2008 is
>> now part of Vista and has created some new situations. I am surprised
>> there is no action on the internet concerning these errors since I have
>> two machines, one running Ultimate and one running Home Premium and they
>> both get Kerberos but only the Home Premium machine gets the added bonus
>> of the DistributedCOM error. I read the MSFT Technet article on the
>> DistributedCOM error but could not figure out what I had to do. Help
>> would be appreciated.
>