We are deploying XP SP3 using SCCM to about 3000 computers. We've gotten many issues with running Task Sequences to do this, as, the SP3 install periodically on some computers (they are all Dell Optiplex, with Intel NICs) creates a NAP & DCOM problem:Event Type:ErrorEvent Source:DCOMEvent Category:NoneEvent ID:10016Date:3/29/2009Time:12:38:51 AMUser:NT AUTHORITY\SYSTEMComputer:ECH-WS39856Description:The application-specific permission settings do not grant Local Launch permission for the COM Server application with CLSID {24FF4FDC-1D9F-4195-8C79-0DA39248FF48}to the user NT AUTHORITY\SYSTEM SID (S-1-5-18). This security permission can be modified using the Component Services administrative tool. For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.This seems to impact on the computer's ability to find the MP correctly, and, things start not working correctly after that point (like a TS reboot of the computer after instaling XP SP3 won't work). Once we manually fix DCOM, and reboot the computer, things finish.Is there any way to avoid this happening, or, to do something to autiomatically fix it, or, a way to fix it remotely?Thanks!

I have exactly the same problem and since SP3 was installed the machine hangs on a the first boot (icons not loading). Was this problem ever resolved?

All we've been able to do is to use DCOMCNFG to give the missing rights back for this issue.I've seen no "fix" from MS.Also, WMIDIAG doesn't recognize XPSP3 and Office 2007, and, you will get unfixable issues reported when running it. They need to update/fix that, too.With WMI being the backbone of the client working right, and, with it being so easily broken, and, so hard to repair (quickly and easily--we ALL have the time to spend 30-60 minutes per computer fixing it manually, running WMIDIAG, etc.), it's way past due for MS to address these issues.