You mean a machine-generated pre-translation nobody ever checked and that is unreadable?
Microsoft's alphabetical indices are even sorted after the original English name instead the translated version. To find a word in the list, you need to search for the English word.
As a random example: https://learn.microsoft.com/fr-fr/windows/win32/adschema/a-u... is "Contrôle de compte d’utilisateur" in the list on the left and sorted between "UPN-Suffixes" and "User-Cert" because "Co" sorts between "UP" and "Us" for Microsoft engineers.
Very helpful to find anything!
While the Microsoft of that era got a lot of things wrong, they did get some things right.
I had a hard time getting excited about Ansible, Puppet, Desired State Configuration, etc, because I was provisioning machines with Group Policy in 2001. Load Windows, join the domain, and the machine gets configured (software loaded, settings locked-in, defaults overridden, etc).
Today I'm provisioning tons of Windows VMs this way: PXE boot the VM to an unattended Windows setup that ends up joining the domain and getting all its configuration. It makes disposable VM instances and horizontal scaling Windows VMs a breeze.
The now-defunct Likewise Open product (https://github.com/vmware-archive/likewise-open) extended Group Policy to Linux machines. I'd lost touch with the product but it looks like it got GPL'd. It was handy, albeit I don't have the experience with it like I had with the native Windows Group Policy client. I only encountered it in one environment and, at the time, it was commercially licensed.
I'm not in love w/ the CIFS-based portion of Group Policy, but there's nothing stopping anybody from extending the AD schema and using the AD LDAP server to deliver policy settings (or any other mechanism). Using the filesystem to deliver settings always seemed like a hack born of expedience.
And Active Directory is the king of fine-grained access control, plus using the registry for that is a hack that AD never recovered from.
Everyone loves to harp on about how terrible the Registry is, but that’s missing the forest for a tree.
The registry + GPO engine is a strongly typed and layered settings engine with:
Machine, Machine Policy, User, and User Policy layered on top of each other, consistently, through pretty much every native app!
More importantly, policy would apply or unapply dynamically and cleanly.
You could move a laptop to a different office and soon as it connected the wifi its set of configured printers would change, its outbound proxy could be reconfigured, etc.
More importantly: Microsoft engineers of the era put in the work of writing up thousands of settings in template files that shipped with Windows, with simple checkbox UI controls and paragraphs of descriptions in every language!
If you think your terrible “settings automation” tool is a viable alternative just ask yourself this question: does it “put the work in” or does its user have to?