Add a label/marker for settings that set a policy and lock UI elements post-install

Sinical

Sinical

New Member
Several settings lock the relevant UI elements after deployment. It would be nice to know if a setting I'm changing is going to lock after installing.

2024.3.9783.0
 
What do you consider as "locked"? Settings which are managed by a Group Policy, and users can't override them?
 
What Sinical means, is some things inside NTLite also set a group policy or other additional tweak, but it's not indicated to the user. This leads to confusion for those unfamiliar with policies, because when the user goes to mess with a settings page or whatever and it has the red admin text or the interface is hidden, which is unexpected for some users. NTLite's March 12th, 2024 update addresses OneDrive's example of this scenario:
Components: ‘OneDrive’ removal won’t be setting OneDrive disable policy as well. To set as before, use the Settings page in conjuction
Click to expand...
 
Last edited:
Hellbovine said:
What Sinical means, is some things inside NTLite also set a group policy or other additional tweak, but it's not indicated to the user. This leads to confusion for those unfamiliar with policies, because when the user goes to mess with a settings page or whatever and it has the red admin text or the interface is hidden, which is unexpected for some users. NTLite's March 12th, 2024 update addresses OneDrive's example of this scenario:
Click to expand...
Agree on the first part, and nope on the second. That OneDrive fix was my bug report.

When you remove the OneDrive component, NTLite automatically hides OneDrive from Settings as a cleanup task. But if the user re-installs OneDrive later, then it remains hidden because SettingsPageVisibility hasn't been cleared.

The poor user doesn't know about Page Visibility, so your goodwill gesture has backfired.
 
I didn't know about the bug report, but in previous versions of NTLite, OneDrive removal sets a registry key related to network data or whatever it is, I'm not at my desktop to paste it here. I thought the NTLite update was addressing that, so nuhi may want to clarify the changelog.
 
Last edited:
There's a related problem where removing OneDrive automatically sets DisableFileSyncNGSC.

The only reason for doing that is you're afraid the OneDrive self-updater tasks haven't been correctly removed, and it will magically re-install w/o your consent. A flip side is it also breaks OneDrive on re-install. Which is the lesser of two evils to invoke?
 
Yeah, I'm not advocating for any one particular solution, since many things are situational or have to be generalized for a wide range of scenarios, so some of them will just never be perfect. I agree with the spirit of this thread though, since it has come up in the past while helping users. Me personally, I'd be fine with making a note in the status bar when clicking on an individual component to state that it will also add group policies, or something else simple to help improve the transparency when a situation warrants it, that's all.
 
I agree with this. It's just a bit of extra clarity about how the settings are being implemented so the user understands they will have to get admin approval if they want to change a particular setting back.
 
You must log in or register to reply here.
Back
Top