4 ms·
As i said below i am more on about MS even considering this as a default option for a server environment, not about the lack of control.
by morrbo 10y ago
As i said below i am more on about MS even considering this as a default option for a server environment, not about the lack of control.
- Mithaldu 10y agoFor one: There is no lack of control. I don't know about Home, but from Pro and up you have full and fine-grained control available if you use the correct APIs. For the other: This is primarily a shift in their philosophy of considering every user someone who would happily endanger the entire internet for their convenience. If you're not the type of person to have received notification of this change as part of your training and/or doesn't double-check it as part of their job duties, they expect you to be the type of person who lets their servers go unpatched and infected by worms sending out spam and DDOS attacks for years. Mind, they're not saying this out loud, but their actions speak very loud.
- Meph504 10y agoMight want to check that, anniversary update simple made many of the previous group policy functions, and API calls, only functional on educational and enterprise versions.
- Mithaldu 10y agoNope, i'm using them on an up-to-date pro version. They work. A lot of that is also misreporting and half truths by journos who don't give a damn about anything but being the first to get the clicks with the most exciting headline. For example the group policy update configuration was changed with the anniversary update to not reflect in the user update ui, but still works perfectly fine and is still reflected in the group policy ui.