Quite a few of my Windows XP machines are giving me DCOM Errors like the one below: The application-specific permission settings do not grant Local Launch permission for the COM Server application with CLSID {7E89FF0B-F649-4F9A-A9C3-F05DFAAA3DA1}to the user NT AUTHORITY\SYSTEM SID (S-1-5-18). This security permission can be modified using the Component Services administrative tool. Searching the registry for theCLSID in this error, shows that it's coming from the SMS Agent Host App. I'm looking into Component Services for the SMS Agent Host and under the security tab, all the Permissions are Customized. What Permissions should I be looking for to troubleshoot this error?

This article is related but for a different issue, maybe this will point you in the right direction. Unless you have a GPO that locks this down or some tool, this could be a one-off issue. http://support.microsoft.com/kb/290398

Thanks Stan. I'll check the article out and see if it helps with my issue.

Did you solve this? Could you please let me know how?

I was able to fix this issue by modifying the DCOM permissions: Start -> Run -> dcomcnfg Expand Componennt Services, expand Computers , expand My Computer , expand DCOM Config Right click on SMS Agent Host , click Properties Select the Security tab, click Edit in the Launch and Activation Permissions section Select System , ensure Local Launch is Allowed Click OK, Click OK

Hello! I have the same issue with Windows 7 clients. Resolution through correcting DCOM permissions helps me, but I have more than 100 clients. How could I resolve that problem within enterprise environment? For example through GPO or other.

See http://support.microsoft.com/kb/206484/en-us how to change those settings programmatically.

Thank you for your reply. Helpful link. But I would like to know what is the cause of those DCOM errors? Client push account have domain admins permissions and so on. Clients are installed successfully, logs are clear, the system status is OK. Does anyone know why those errors are appeared?

I would also like to know why these errors are appearing. My client is working fine... I'm able to run DCMs, patch, software deliver, OSD, task sequences, scupdates, etc... I've not had any issues with the client on these Win7 machines. Anyone know what the agent was attempting that generated the access denied? Also, if the fix is to grant DCOM launch permissions, then why wasn't this set when the client agent was installed? nick