DCOM event 10020 after Sysprep'ing a system.

[Joe]

I setup a machine, and included IIS. Then Sysprep'd. All machines brought
to life with this sysprep image are logging the following error in the event
log.

I assume this has something to do with the machines being renamed during the
imaging process? Any fix for this? is this "bad"?

I went to the Component Services administrative tool, but have no idea what
to reset.

Can anyone provide information about this error please?

Thanks,

Joe

Event Type: Error
Event Source: DCOM
Event Category: None
Event ID: 10020
Date: 26-Jan-06
Time: 10:14:45
User: N/A
Computer: ZATHRAS
Description:
The machine wide Default Launch and Activation security descriptor is
invalid. It contains Access Control Entries with permissions that are
invalid. The requested action was therefore not performed. This security
permission can be corrected using the Component Services administrative
tool.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.

[Kim Gräsman]

Hi joe,

> I went to the Component Services administrative tool, but have no idea
> what to reset.
>
> Can anyone provide information about this error please?

I think you want to right-click your machine (usually called My Computer)
in Component Services, go to the COM Security tab and hit the Edit Default...
button for Launch and Activation Permissions. Possibly you'll need to reset
Access Permissions as well, but it doesn't seem to be complaining about that
yet.

I believe the default values for these vary between Windows versions, so
try and check a clean machine that's working and see what settings it has.
Then set your sysprep'd machine to the same thing.

--
Best Regards,
Kim Gräsman

[Joe]

Hi Kim et al -

For what its worth, I went in to Component Services on the context menu of
My Computer, went to the COM security tab, hit the Edit Default button for
Launch and Activation Permissions. In there I reset the 2 entries for
IUSR_computername and IWAM_computername . I basically removed them and then
inserted them with exactly the same permissions they had before.

I no longer get any of these errors in my event log. Problem solved.

Thank you very much for the pointer.

Joe

"Kim Gräsman" <k...@mvps.org> wrote in message
news:453b99c6815198...@news.microsoft.com...