Switch the Names parameter Together with the identify of a key that exists instantly beneath the HKEY_CURRENT_USER node in the registry.
This software will make the customization files to suit your needs, therefore you dont want to bother with continuous syntax errors (which you'd probably acquire if you begin composing these on your own). You may download the application from your authors Site: Mark Cochrane (Procedure Center Configuration Manager MVP).
On condition that this is an HKLM critical, I might select or make a GPO, visit Pc Configuration/Choices/Windows Configurations/Registry and produce the suitable critical to be included and established the worth. Deploy the GPO to the necessary products and it must generate or modify the key anytime the equipment is booted.
Observe. If the error The community path was not observed seems if you try out to connect with a computer, most likely your Laptop is turned off or Remote Registry Provider will not be commenced on it. Â
LocalSystem has no use of a user's HKCU mainly because HKCU for the user is only mounted when that specific user is logged-on.
After you know very well what your going to change, logon towards your domain controller or maybe a server with the team plan administration console on.
If I deploy the MSI currently being run since the SCCM company account (that has area admin rights), will it only utilize the user reg keys to the SCCM assistance account's profile?
This may not surprisingly even be a concern, so that you can normally fall back to making use of an activesetup rather that then is executed after navigate to this website for every user logging on into the machine.
I've absent back to powershell. You will notice I posted they mentioned they "set it" in 1602 but users are reporting "That is a Lie".
If you must make the registry critical you use a poweshell script to do this which has a detection rule if it does not exist then execute, this would be 1 configuration product.
also, like u/ohwowgee pointed out down below, you can exclude the default user profile by manipulating that script a tiny bit.
While in the systems Homes you ought to pick "Operate with User Correct's" then It will probably be run With all the users permissions in the user context.
Once i consider the configuration merchandise for that DWORD benefit, "remediate" is checked, but Creating Current User Registry Keys in a SCCM Package with the keys, remediate is not any, and to the life of my I can not uncover the choice to generate the keys if it will not exist. The rule is existential, but I do not see a "Remedite if critical just isn't have a peek at these guys there" solution.
If I recall properly, I believe HKCU is admittedly merely a pointer for the HKU hive to the currently logged in user. If there's no user logged into the equipment once the script operates, then I don't think HKCU details to anything at all.