fail to detect by registry after deployment

[P3nnyw1se]

this is simple, I push out an application, an exe file.
And of course I need to create a detection method.

In this example I'm not able to use any file, as the versions don't differentiate on files,
and I need to be able to tell different versions apart.

 

So instead I turne to registry, there is a value in there that lets me differentiate versions.
Here is what I do ->

 

 

I confirm that the registry exists after installation, but it fails detecting the program anyway.
So basicly the deployment works, but it can't see this registry.

Why?, the path is correct.. I've tried using both the flag in '32'bit and without.

[P3nnyw1se]

Update: Seems to be a security issue, I'm not able to connect to computers trying to reach their registry, but I'm very much able to connect to their drives.
thats a problem, because I simply can't differentiate on the files.


Update: Okay its definetly a security issue, I dont seem to have permission to go into a domain computers registry.

So New Question!!
How do I allow SCCM access to the devices registry?
I dont care how I do it, if its through GPO etc. but whats do I need to change?

[Peter van der Woude]

ConfigMgr itself should have access to the registry, as it's running using SYSTEM credentials.

[P3nnyw1se]

I'm assuming this is the problem.
because when I wanna browse a detection method, I'm able to connect to machines going to the folders.
but I'm not able to connect to any machines on my domain if I pick registry as source.
furthermore when I add a registry as my detection method by hand.. it just doesn't Work.

can I shomehow check configMgr has the access it needs?

[Peter33]

You have probably not enabled remote registry on your machines. That would explain why you cannot connect to your clients registry from the console.

[P3nnyw1se]

and where do I set that? .. I've been browsing through Administration settings and can't find client registry allowance anywhere

[Peter33]

Remote registry is a service on the Clients (RemoteRegistry).

[Jaybone]

You can enable the remote registry service for the endpoints you're interested in via GPO, if that's suitable for your needs.

 

If you want to just do a quck check on a system or two remotely, running 'sc \\targetName start remoteRegistry' should suffice.

 

As Peter said, though - you shouldn't need to do this for CM to be able to check. Enabling remote registry will allow you to connect from elsewhere, e.g. your workstation with the proper credentials, but the CM client itself is local, and shouldn't be effected by remote registry being turned off

[P3nnyw1se]

well I simply had to give up on it.. I can't look in the registry of the machines using detection methods, but I got full access on all accounts.