The GUID 61738644-F196-11D0-9953-00C04FD919C1 corresponds to the service “IIS WAMREG Admin Service”. This also applies to other processes of Sharepoint.
Let’s try the following steps:
1. Click Start -> Run, type "dcomcnfg" in the text box, and click OK.
2. Expand Console Root\Component Services\Computers\My Computer\DCOM Config
3. Find "IIS WAMREG Admin Service" in the list, right click, Properties, and on the Security tab, click Customize.
4. Grant the Network Service account with "Launch and Activation Permissions".
5. Click OK.
On a Windows Server 2003 or Windows Server 2008 machine you would just fire up the dcomcnfg utility (with elevated privileges) and enable Local Activation for your domain account.
But for Windows Server 2008 R2 (and Windows 7, since they share the same core) you cannot do this, the property dialog is all disabled due to permission restrictions. It doesn't matter if you are logged in as an administrator or using elevated privileges. The change is probably due to some new security improvements.
The reason for it being disabled is that this dialog is mapped to a key in the registry which the Trusted Installer is owner of and everyone else only has read permissions. The key used by the IIS WAMREG admin is:
HKEY_CLASSES_ROOT\AppID\{61738644-F196-11D0-9953-00C04FD919C1}
Image on the left shows the default permissions for Windows Server 2008 R2 and on the right the default settings for Windows Server 2008.
To be able to change the Launch and Activation Permissions with dcomcnfg you have to change the ownership if this key. Start the registry editor (regedit), find the key, click Advanced in the Permissions dialog of this key and select the Owner tab. Now change the owner of the key to the administrators group for example, then set full control to the administrators group. Make sure not to change the permissions for the TrustedInstaller.
Now you have to restart the dcomcnfg application and once find the IIS WAMREG application and then set the Launch and Activation settings that you need to get rid of the DCOM 10016 error.