DCOM error after sysprep on XP Pro SP2



david
07-10-2005, 03:16 AM
I'm trying to syspep an XP Pro SP2 installation with all the latest patches,
the NVIDIA display driver, Symantec AV Corporate Edition and IIS

There are no errors in the event logs before sysprep is run. But after I
run it and restart the machine I get several of these DCOM errors in the
System Event Log:
____________________________________________________________________
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.
____________________________________________________________________

Source is DCOM
Event ID is 10020
____________________________________________________________________

My sysprep.inf file is below (slightly modified to protect the innocent):

;SetupMgrTag
[Unattended]
OemSkipEula=Yes
TargetPath=\WINDOWS

[GuiUnattended]
AdminPassword="something"
EncryptedAdminPassword=NO
OEMSkipRegional=1
TimeZone=255
OemSkipWelcome=1
AutoLogon=Yes
AutoLogonCount=1

[UserData]
ProductID=xxxxx-xxxxx-xxxxx-xxxxx-xxxxx
FullName="Ssomething"
OrgName="something"
ComputerName=HOSTNAME

[RegionalSettings]
LanguageGroup=13,17,3,2,5,16,4,12,15,7,8,10,11,9,6,14,1
SystemLocale=00000c09
UserLocale=00000c09
InputLocale=0c09:00000409

[Identification]
JoinWorkgroup=WORKGROUP

[Networking]
InstallDefaultComponents=Yes

[Display]
BitsPerPel=32
Xresolution=1024
YResolution=768

[Branding]
BrandIEUsingUnattended=Yes

[Proxy]
Proxy_Enable=0
Use_Same_Proxy=0
__________________________________________________________________

I can fix the problem manually by going into Administrative Tools/Component
Services, expand component services, computers, right click My Computer,
choose properties,COM security tab. The under the Launch and Activation
Permissions heading click Edit Default and remove the IWAM account then add
it back with the full permissions it had.

However, as this is meant to be an image for a lot of people it's going to
be hard to have to go to each machine each time to fix this problem.

Is this maybe a bug with sysprep?

Any ideas how to fix this in an automated way - maybe a script?


DCOM error after sysprep on XP Pro SP2