3 ms·
> your claim about GPO policies is blatantly nonsense, since that's what you use for Enterprise deployments. It says right in the GPO policies which operating
by UnoriginalGuy 10y ago
> your claim about GPO policies is blatantly nonsense, since that's what you use for Enterprise deployments.
It says right in the GPO policies which operating systems they apply to. For example in your screenshot you set "Do not allow web search" to quote the policy itself that only applies to:
> Microsoft Windows XP, or Windows Server 2003 with Windows Search version 3.01 or later
Doesn't do anything on Windows 10. So it isn't "blatantly nonsense." You are just playing with pro functionality you don't understand.
> Also, if you had actually researched before publishing, you'd known that Microsoft removed the disable option from the Hamburger menu during the Anniversary Update.
Nope. http://i.imgur.com/nzHBVex.png http://i.imgur.com/nzHBVex.png
As you can see I am on 10.0.14393 which is the Anniversary Retail Release and have the option.
- vic-traill 10y agoYour point about various GPO settings being version specific is absolutely correct. I will say that I definitely do not want to manage options via clicky-click. Local policy editing (and domain group policies in the enterprise) have been a replicable, scalable way to manage settings in a Windows environment since at least XP/Server 2003 (the earliest Windows client + server environments I've admin'd IIRC). Configuration outside of LP/GP doesn't scale particularly well beyond personal use, I'd say and as such I get what the other poster was driving at.