First things first, thanks a lot for setting up this wonderful site. I have resolved many issues by reading posts on this forum.
I have set up a hyper-v lab @home that I use to learn and test deployment using SCCM 2007 R2/SP2 on Win2k8 R2 64bit. The lab has 20 clients managed by the SCCM server that is also a root DC. All clients have been created using a sysprepd and captured image and are win2k8 server r2 64bit clients. Here's the issue. When I create and advertise a package to a collection, it gets installed on some clients while on others it just doesn't start and eventually times out in error. On the clients where it does not start, I log on to the client using domain admin ID and open the confg manager client properties in control panel. Under Actions tab, I choose "Machine policy Retrieval & Evaluation Cycle" and click Initiate Action. This is something I usually do to speed things up but in case where the package does not start, instead of successful message I get, "The action could not be initiated". It also logs Event ID 1006 in the event viewer with following details
The application-specific permission settings do not grant Local Launch permission for the COM Server application with CLSID
{F80A8D57-D338-43FF-A5E6-5D093EA80775}
and APPID
{AD65A69D-3831-40D7-9629-9B0B50A93843}
to the user DOMAIN\administrator SID (S-1-5-21-3102697118-2973695134-1900920546-500) from address LocalHost (Using LRPC). This security permission can be modified using the Component Services administrative tool.
The APP ID points to SMS Agent Host COM object. The permissions are set as default and I am assuming since it works on some clients ( and this is random, if one client gets package A ok, it can have this issue with package B or vice versa) Now, here's the kicker. If I reboot the client and login back again I can successfully launch the "Machine policy retrieval & Evaluation cycle" and the package appears as if nothing wrong ever happended. All the articles I have read so far are either outdated or the fix they provide, which is usually to change default permissions, have not resolved my issue. I do not want to change any default permissions on the com object becuase the darn thing works on some clients but not on others
