Seeing a strange issue. When MDT (Microsoft Deployment Toolkit) deploys an image, it creates a registry key called “HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Deployment 4”. When you follow this path through Registry Editor, or PowerShell you can clearly see it. When queried through BigFix, it comes up false. exists key “HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Deployment 4” of registry Any thoughts on why this comes up as false? thanks!
The default registry inspectors query the 32-bit redirected registry, for backward compatibility.
This checks the 32-bit registry, actually looking for “HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Deployment 4”
q: key "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Deployment 4" of registry
This one would look at the “native” registry, ignoring 32-bit redirection and checking the right place:
q: key "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Deployment 4" of native registry
Note the use of ‘native registry’ rather than ‘registry’.
We also have ‘x32 registry’ and ‘x64 registry’ in case you need to explicitly check one or the other.
3 Likes
Adding “native registry” worked, thanks!
1 Like