It seems that you're using an outdated browser. Some things may not work as they should (or don't work at all).
We suggest you upgrade newer and better browser like: Chrome, Firefox, Internet Explorer or Opera

×
avatar
EuroMIX: I was actually a bit naughty and dual-booted it a few days before release.
snip
avatar
ashwald: How did you do it?
It's not something I think I should really talk about here, for obvious reasons. But if you know how to use torrents and such, you'll probably know what to do. I don't necessarily recommend it though.

Oh, I nearly forgot one: I think that the new icons for things like the recycle bin, and documents, videos and such are ugly. I think the Windows 7 ones are much nicer.
Post edited July 30, 2015 by EuroMIX
avatar
Gilozard: There are a lot of people who aren't computer savvy at all but who are also not incompetent buffoons. Do you also know how to perform heart surgery, publish a textbook, and write a legal argument? No? OK then. People specialize. Often, their specialty does not involve knowing how computers work. I've done customer support for years, and sometimes people just don't or won't remember. But I still have to make sure those people can do their job, without their job turning into my job. It's a balancing act. :/
avatar
JMich: I'm sorry, did you just compare running a script to heart surgery? Because being unable to run a script does make you an incompetent buffoon. Finding the script may be a bit harder, but that's why you ask for help if required.

avatar
Gilozard: We are on automatic updates. Seriously, the real problem with update adoption is that people refuse to turn off their PCs, so the updates never get a chance to finish installing.
avatar
JMich: Scheduled tasks to the rescue. Reboot every Saturday at 23:59. Notify the users, ask them if they'd rather have the reboot at a different time. Or just say that every midnight the computers will reboot.
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?

Even if all of your users were capable of and interested in running scripts, there's a significant fraction of users who won't know how to find or run them, let alone understand what they do. Holding up a user-written script as a replacement for OS functionality is a joke.

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.

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.
Post edited July 30, 2015 by Gilozard
avatar
hedwards: People shouldn't have to be on the look out for these sorts of things, they should be able to trust that MS is going to do the right thing. But, then again, when has MS ever done the right thing? They're pretty much poster boys for abusive practices followed with little or no punishment.
avatar
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.
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.
avatar
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?
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".

avatar
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.
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.

avatar
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.
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.
avatar
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?
avatar
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".

avatar
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.
avatar
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.

avatar
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.
avatar
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.

avatar
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.
avatar
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.
Post edited July 30, 2015 by Gilozard
avatar
JMich: My claim is that while MS made it a bit harder to choose what updates to install, the functionality is still there.
I didn't read all your posts, but I'll say this:
- normal users aren't already capable of disabling system update or choosing what to get. This new change is just an annoyance for more advanced users, for no real advantage.
- day1 script needed to obtain something that was simple before = crap change.
avatar
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.
avatar
Gilozard: 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.
I'm less concerned about this because I'm running it in a VM for certain Windows only applications, but it seems to me that even if MS doesn't do anything nefarious with the information, that crackers could probably find a way of tapping into it or enabling it for their apps.

One of the big problems with the activation dialogs is that it's only as good as the person's attention and knowledge that's making the decision. And most people aren't paranoid enough to realize what happens when large amounts of data are assembled from numerous smaller sources.
Well at least M$ will get an entry in the guiness book or world records for building the biggest botnet in human history.
avatar
Klumpen0815: Well at least M$ will get an entry in the guiness book or world records for building the biggest botnet in human history.
You're dead right....
avatar
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".
Those so-called I.T. pros that denigrate their user-base like are fucking idiots and should be fired, IMHO.

Everyone has their specialties and things they are good and not good at.

In IT it seem relatively common to find fucktards that think they are oh-so-superior to everyone. They can all go fuck themselves. That man or woman that cannot (or is afraid to) "paste this into a file, save it as .bat, run it" might be an expert on surviving in the the wilderness. I know who I'd rather be with if I need survival - and it's not the fucktard "IT-guy" - I'll tell you.

I ran into this in IT all the time - fucktards that think they are superior to those they support - and always denigrate them. Those fucks either lost that attitude quick or got fired - if I found them on my teams. And if they lost the attitude, I went out of my way to make sure it wasn't just in front of the boss that they lost it.

That attitude of hubris really has no place.

JMO (fire away)
avatar
Klumpen0815: Well at least M$ will get an entry in the guiness book or world records for building the biggest botnet in human history.
avatar
russellskanne: You're dead right....
WOW. That is insane.
avatar
phaolo: - day1 script needed to obtain something that was simple before = crap change.
Day -10 script to be exact, for disabling automatic updates. Registry entry was there from before, build 99xx from what I recall. Script to choose what to install is month -8.
avatar
phaolo: - day1 script needed to obtain something that was simple before = crap change.
avatar
JMich: Day -10 script to be exact, for disabling automatic updates. Registry entry was there from before, build 99xx from what I recall. Script to choose what to install is month -8.
I don't get why you think that rebuts the point? You seem to be missing what both phaolo and I are objecting to.
avatar
Klumpen0815: Well at least M$ will get an entry in the guiness book or world records for building the biggest botnet in human history.
avatar
russellskanne: You're dead right....
LOL that kills me.

All those fanbois with their mantra's of "you can opt out / turn off / whatever" <insert convoluted individual one-off procedure for each of a thousand things> and here it is in plain sight they will turn it back on from time to time. And what isn't there today you've already given them permission to change for later.


[edit - typo]
Post edited July 30, 2015 by Martek
avatar
Martek: Those so-called I.T. pros that denigrate their user-base like are fucking idiots and should be fired, IMHO.

Everyone has their specialties and things they are good and not good at.
So if the IT is a specialist in the IT field, but a rude person, you will fire him to get a less qualified but more friendly one?

avatar
Martek: That man or woman that cannot (or is afraid to) "paste this into a file, save it as .bat, run it" might be an expert on surviving in the the wilderness. I know who I'd rather be with if I need survival - and it's not the fucktard "IT-guy" - I'll tell you.
Will said person be expecting you to be able to "Chop wood, build a fire, light it" without you screwing it up? Or would he shake his head and belittle you if you couldn't perform something that simple (and yes, chopping wood and building a fire is simple)?

avatar
Martek: That attitude of hubris really has no place.
I do agree. But there is a difference between not knowing how to code, compile and debug a program, and not being able to paste text into a file, save the file, and run it.