Registry Report keeping old values

[ScottyBC]

Hello,

I am using the custom registry scan to see the value of DisableFileSyncNGSC

I created a deployment based if the value equals 1. This works. When I run a deployment, it changes the registry value to 0. This is working. It has been tested many times.

What my issue is I have this registry scan set to scan every day. However, even is the value of the registry has been fixed and set to 0, the report is out of date and still showing a value of 1.

This has been setup for a few weeks now and the values reported are still incorrect. I am also only looking at the devices that have an up to date last connect is current. Is there a way to refresh this data?

Thank you,

Scott

[KTM]

Bringing this back up -  @ScottyBC any chance you got to the bottom of this? I'm seeing the same thing (reg values are either not showing, or being wrong, even with a successful scan.)  We use the LS Agent Service and the cloud Proxy.  
Our Registry scan interval is set to 0.

[ScottyBC]

Hi Hendrik_VE, Thank you for the response. For the registry, the scanning interval is set to 1 day. When I look at the tblregistry.lastchanged I can see when the value changed, but I can't tell the last scan time. from what I can see is the lastchanged isn't matching to the day the I made the change. I think I may have to put in a support case to see why the chages are being picked up.

Regards, Scott

[Hendrik_VE]

Have you checked the "Scanning">"Scanned Item Interval" for 'REGISTRY'? I don't know what the default value is, but I have set the refresh interval to 0 (this means, scan always).

Furthermore, you could add tblregistry.lastchanged to check when the value has been last updated.