Updating registry entry
Access to the location is redirected must be specified.
Typically, this is only necessary to ensure compatibility with 32-bit applications that are running on a 64-bit operating system.
When you try to edit a protected registry key, you’ll run into a few different errors, but they tell you that you lack permissions for making changes.
However, since it is just a permissions issue we can get around this by granting your user account in Windows the correct permissions! When trying to create a new entry within a protected Key you’ll see the following error: If you are encountering the above errors, without a doubt, you’ve encountered a protected registry key.
Reason I need to turn it off is that none of our users have Admin and therefore the client driven update process is useless.
Instead I need to get the SCCM package updated monthly with the new Power BI Desktop release and then have my users rerun.
Normally these keys are only open to modification by the System, but if you follow the steps below, you’ll learn how to make your user account a powerful registry editing demi-god. In regedit (Registry Editor) If you want, you could take control of the top tree of the registry.
The auto-updating procedure is performed by Google Update, which is based on the open-source Omaha project.
The chef-client can access any reflected or redirected registry key.
The machine architecture of the system on which the chef-client is running is used as the default (non-redirected) location.
However, this is not recommended for security purposes unless you plan on removing said permissions when you finish working. You should now be able to edit any of the entries within the registry key that you just modified permissions for.
Note 64-bit versions of Microsoft Windows have a 32-bit compatibility layer in the registry that reflects and redirects certain keys (and their values) into specific locations (or logical views) of the registry hive.