Gilozard: Yeah, I did - some people are seriously scared of scripts, don't understand how computers work, etc. Including some who are doctors / lawyers / whatever. You claimed to have supported users before - how is this news to you?
JMich: Thus the incompetent buffoons comment above. The users I had support which couldn't run a script were in the incompetent buffoon category. The users that were not there could do a "paste this into a file, save it as .bat, run it".
Gilozard: Just to clarify - I'm not sure why you're having such hard time with this, there's got to be some misunderstanding - I'm saying that your attempt to claim that MS removing Windows Update functionality is fine because we have this script so there's no need to complain is completely wrongheaded. That I can run a script on a computer as a stopgap to fix what MS broke doesn't mean that MS didn't break it in the first place.
JMich: My claim is that while MS made it a bit harder to choose what updates to install, the functionality is still there. The script is the easy way to do it, but one can also do it without it. It's similar to saying that the tar.gz that GOG provides cannot be used because they don't create shortcuts, unlike the .deb ones. The functionality is still there, just hidden from most users. If a user really needs to select what updates to install, he will have to do some digging. And my experience has shown that a user that isn't willing to do said digging most likely doesn't need to select what updates to install.
Gilozard: Yeah, setting up schedule tasks is on my list of things to do. It just keeps getting shoved down the list because of director requests.
JMich: Are the users logging in a local account or a networked one? If local, it is a bit more time consuming to deploy, but if it's networked, you should be able to do it in less than 5 minutes. Group policy is again quite helpful, and you may be able to get away with using logon scripts instead of scheduled tasks.
Do ask if you need help, even if just for the time consuming part of verifying the script and identifying the location it should go.
Here we have people who are good in their field - some of them very good - but who are not tech savvy at all or are afraid enough of breaking something that they won't do anything without me there. I strongly prefer that to whoever installed malware, but it does mean spending more time.
Eh - I still say that MS removing (for a value of remove that means average users can't find it) OS functionality was a mistake, and saying it's OK because we have a script is just going to mean they feel OK with removing more functionality. Also, scripts aren't as reliable in the sense that they aren't as guaranteed - code the script depends on could be changed at any point by the OS devs, for example. OS features tend to be more stable in that sense, which is why I prefer them.
Thank you so much for your offer of help! We're still in the middle of heading off high-level requests this week, but hopefully the week after I'll have time to impose some organization.
JMich: Will have to double check the default settings (and their description) when the next computer in the house asks to update, but I do recall that I didn't have to dig that hard to find it. It did say something to the tune of "Click next if you want personalized ads", but memory is faulty.
But yes, if you go "Next, Next, Next, Install" in the installation screens, you will run into trouble, no matter what you install.
hedwards: By default they're sharing an awful lot of information. Most of it s visible without scrolling, which is good. But none of it should be shared by the OS at all. There's just no reason for it. If something needs that kind of permission it should have to ask for it specifically, rather than the OS having it.
The OS is in a position to take all sorts of information without the user's knowledge, so it makes sense that it not be allowed to do any data collection without opting in. With possible exceptions for legitimate crash diagnostics and similar.
Even that probably shouldn't be allowed as there's a ton of confidential information in a crash dump that aren't relevant to the problem.
Yes, this is potentially a huge security problem, and already definitely a major privacy violation. OSes are in a much more trusted position than a browser and need to respect that.