Windows 10 Auto Update
-
@scottalanmiller said:
If people are used to just accepting whatever without reading, they are going to find themselves on Windows 10 and be "surprised."
This of course is what MS is hoping for.
-
It just seemed odd it happened over this past weekend. Almost makes me wonder if they did indeed change wording or something.
I'll have to Google screenshots of what it looks like.
-
I heard about this change at least 2 weeks ago, perhaps more from Paul Thurrott.
-
I know they made a change.
It's just odd it hit people I know THIS week, and not a few weeks back.
-
@BRRABill said:
I know they made a change.
It's just odd it hit people I know THIS week, and not a few weeks back.
They are still doing rolling deployments. I wouldn't expect an automatic upgrade to Win 10 until sometime next year, and that's only assuming that MS continues to give it away free after July.
-
@Dashrender said:
@BRRABill said:
I know they made a change.
It's just odd it hit people I know THIS week, and not a few weeks back.
They are still doing rolling deployments. I wouldn't expect an automatic upgrade to Win 10 until sometime next year, and that's only assuming that MS continues to give it away free after July.
We have enterprise keys and this is still occuring. I thought that wouldn't be the case
-
@wirestyle22 said:
@Dashrender said:
@BRRABill said:
I know they made a change.
It's just odd it hit people I know THIS week, and not a few weeks back.
They are still doing rolling deployments. I wouldn't expect an automatic upgrade to Win 10 until sometime next year, and that's only assuming that MS continues to give it away free after July.
We have enterprise keys and this is still occuring. I thought that wouldn't be the case
Are you on a domain? Are you using WSUS?
That part was very unclear. I'm pretty sure if you're using WSUS you won't get it automatically, but if you're not - you had to push out a deny option through GPO to prevent it.
I heard something about domain joined machines wouldn't get it, but that didn't seem entirely sure.
-
@Dashrender said:
@wirestyle22 said:
@Dashrender said:
@BRRABill said:
I know they made a change.
It's just odd it hit people I know THIS week, and not a few weeks back.
They are still doing rolling deployments. I wouldn't expect an automatic upgrade to Win 10 until sometime next year, and that's only assuming that MS continues to give it away free after July.
We have enterprise keys and this is still occuring. I thought that wouldn't be the case
Are you on a domain? Are you using WSUS?
That part was very unclear. I'm pretty sure if you're using WSUS you won't get it automatically, but if you're not - you had to push out a deny option through GPO to prevent it.
I heard something about domain joined machines wouldn't get it, but that didn't seem entirely sure.
No WSUS because _____. Another thing I requested as was denied. No all of my PC's are connected to our domain. This will change when I fully install ZeroTier etc.
-
What's going to change?
Did you deploy the GPO options to prevent WIn10?
-
@wirestyle22 said:
No WSUS because _____. Another thing I requested as was denied. No all of my PC's are connected to our domain. This will change when I fully install ZeroTier etc.
What's going to change? Adding them all to AD?
-
@scottalanmiller said:
If people are used to just accepting whatever without reading, they are going to find themselves on Windows 10 and be "surprised."
I will admit to not reading hte MS stuff they throw up about licensing when updates are run.
But if they are hiding a Windows 10 install in there, that's pretty shady.
I was assuming (I know, I know) that the full Windows 10 upgrade screen would come up. AKA the user would HAVE to see they were upgrading to Windows 10.
-
@scottalanmiller said:
@wirestyle22 said:
No WSUS because _____. Another thing I requested as was denied. No all of my PC's are connected to our domain. This will change when I fully install ZeroTier etc.
What's going to change? Adding them all to AD?
I can't change GPO for all PC's through the domain and have it affect all of my computers. When I connect all of my PC's to the domain I'll be able to do that. Currently I'm using a script on each PC not connected to the domain.
-
@BRRABill said:
@scottalanmiller said:
If people are used to just accepting whatever without reading, they are going to find themselves on Windows 10 and be "surprised."
I will admit to not reading hte MS stuff they throw up about licensing when updates are run.
But if they are hiding a Windows 10 install in there, that's pretty shady.
I was assuming (I know, I know) that the full Windows 10 upgrade screen would come up. AKA the user would HAVE to see they were upgrading to Windows 10.
From my understanding it's not hidden, but it's not like a bright red flashing sign either.
Remember, MS wants people to upgrade. Most home users are no upgrading because they have heard to much FUD - that said, forcing this upgrade is not good either because there is nothing ensuring that users have backed up their systems first as you should before any upgrade.
-
@Dashrender said:
@BRRABill said:
@scottalanmiller said:
If people are used to just accepting whatever without reading, they are going to find themselves on Windows 10 and be "surprised."
I will admit to not reading hte MS stuff they throw up about licensing when updates are run.
But if they are hiding a Windows 10 install in there, that's pretty shady.
I was assuming (I know, I know) that the full Windows 10 upgrade screen would come up. AKA the user would HAVE to see they were upgrading to Windows 10.
From my understanding it's not hidden, but it's not like a bright red flashing sign either.
Remember, MS wants people to upgrade. Most home users are no upgrading because they have heard to much FUD - that said, forcing this upgrade is not good either because there is nothing ensuring that users have backed up their systems first as you should before any upgrade.
I'd say the opposite, it's extra good that they allow users to punish themselves as it is only an issue when they don't pay attention to what they are accepting AND don't make backups AND were trying to run old systems.
-
@Dashrender said:
Remember, MS wants people to upgrade. Most home users are no upgrading because they have heard to much FUD - that said, forcing this upgrade is not good either because there is nothing ensuring that users have backed up their systems first as you should before any upgrade.
All my calls were from friends with small businesses that apparently run software not compatible with Windows 10.
Or couldn't find any of their programs.
-
@scottalanmiller said:
I'd say the opposite, it's extra good that they allow users to punish themselves as it is only an issue when they don't pay attention to what they are accepting AND don't make backups AND were trying to run old systems.
@scottalanmiller always cheery!
-
@BRRABill said:
@Dashrender said:
Remember, MS wants people to upgrade. Most home users are no upgrading because they have heard to much FUD - that said, forcing this upgrade is not good either because there is nothing ensuring that users have backed up their systems first as you should before any upgrade.
All my calls were from friends with small businesses that apparently run software not compatible with Windows 10.
Or couldn't find any of their programs.
Then the obvious question would be...
Why would a business not have a patching control process in place if they are subject to using legacy software with such dependencies? How did they get caught by surprise, is their IT not overseeing things? The only way that you get caught, I think, is if users are running as local admins and, if so, my pity is in the negatives.
-
@scottalanmiller said:
Why would a business not have a patching control process in place if they are subject to using legacy software with such dependencies? How did they get caught by surprise, is their IT not overseeing things? The only way that you get caught, I think, is if users are running as local admins and, if so, my pity is in the negatives.
It goes back to even though it is understandably wrong, there are a lot of companies that do their own IT support, or only want to pay when things break.
I'm not saying they are they type of client you want, but just know there are a lot of them out there.
-
@BRRABill said:
@scottalanmiller said:
I'd say the opposite, it's extra good that they allow users to punish themselves as it is only an issue when they don't pay attention to what they are accepting AND don't make backups AND were trying to run old systems.
@scottalanmiller always cheery!
I actually am. I see encouraged updates as a good thing. People who run old OSes hurt everyone. They raise the cost of systems, they encourage vendors to not keep packages updated, they put IT into more reactive than proactive mode, they invest against forward motion, and they increase the security risk for everyone (larger global attack surface.)
Keeping everyone updated isn't just good for MS, it's good for everyone, especially IT pros.
-
@BRRABill said:
It goes back to even though it is understandably wrong, there are a lot of companies that do their own IT support, or only want to pay when things break.
Nothing wrong with that, it's only wrong to feel bad for them when things do break. It means that they decided, sometime in the past, that it was more effective to have things break than to try to prevent it. That's their call. They've already gotten all of their benefits to this and now they have to pay the toll that the rest of us paid long ago. Did people feel sorry for us, no. Do not feel sorry for them, it's just business and they bet that this would cost them less overall. If it has, then they made the right decision and you should be happy for them. If it did not, they need to learn and improve like we all have to do every day. It's just another business decision, not something anyone forced them to do.
