Issue connecting windows 7 slave to debian master on jenkins

Question

I am trying to connect a windows slave to a linux master on jenkins and I always see the error below. I have tried everything that the link below mentions but I still see the same error.

ERROR: Access is denied. See http://wiki.jenkins-ci.org/display/JENKINS/Windows+slaves+fail+to+start+via+DCOM for more information about how to resolve this.
org.jinterop.dcom.common.JIException: Message not found for errorCode: 0x00000005   
    at org.jinterop.dcom.core.JIComServer.init(JIComServer.java:542)    
    at org.jinterop.dcom.core.JIComServer.initialise(JIComServer.java:458)
    at org.jinterop.dcom.core.JIComServer.<init>(JIComServer.java:427)
    at org.jvnet.hudson.wmi.WMI.connect(WMI.java:59)    
    at hudson.os.windows.ManagedWindowsServiceLauncher.launch(ManagedWindowsServiceLauncher.java:225)
    at hudson.slaves.SlaveComputer$1.call(SlaveComputer.java:200)   
    at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)   
    at java.util.concurrent.FutureTask.run(FutureTask.java:138)     
    at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
    at java.lang.Thread.run(Thread.java:662) 
Caused by: rpc.FaultException: Received fault. (unknown)    
    at rpc.ConnectionOrientedEndpoint.call(ConnectionOrientedEndpoint.java:142)
    at rpc.Stub.call(Stub.java:112)     
    at org.jinterop.dcom.core.JIComServer.init(JIComServer.java:538)    
    ... 10 more

Answer 1

1. Launch 'regedit.exe' as 'Administrator'
2. Find the following registry key: 'HKEY_CLASSES_ROOT\CLSID{76A64158-CB41-11D1-8B02-00600806D9B6}'
3. Right click and select 'Permissions'
4. Press 'Advanced'
5. Double click on Administrators
6. Allow Full Control
7. Restart Remote Registry Service

UPDATE: As mentioned by @Kobi in comments,

If you cannot change the permissions, you need to first change the owner of this registry path, under "Advanced > Owner".

A step by step instructions on changing ownership can be found here.