Re: [PLUG] Microsoft to force upgrades to Windows 10

[Thomas Delrue <delrue.thomas@gmail.com>]

Doanyone have any confirmation as to whether this is forced upon
domain-joined/enterprise edition machines as well? From my glancing, it
looks like enterprise edition will not be force-fed Win10.
A subset of your customers may be protected (for now) from the Win10
force-feeding that way.

I'm surprised no-one has set up a free/paid WSUS server that people can
subscribe to which would scrub all Win10 updates from the aether before
they reach you. (Keith, I'm demanding royalty payments if you set this
up ;P - demanding sure... getting...??? eeehhhhhh... yaknow)

On 05/15/2016 04:54 PM, Keith C. Perry wrote:
> That's my concern too Thomas, MS being right once.  I know of some
> people personally who have have Windows automatically upgrade their
> systems and I need to avoid that at all cost for my clients.
> 
> ----- Original Message ----- From: "Thomas Delrue"
> <delrue.thomas@gmail.com> To: "Philadelphia Linux User's Group
> Discussion List" <plug@lists.phillylinux.org> Sent: Sunday, May 15,
> 2016 2:39:35 PM Subject: Re: [PLUG] Microsoft to force upgrades to
> Windows 10
> 
> There's this thing as well: https://github.com/th3power/aegis-voat 
> although I can't vouch for its reliability or trustworthiness (I'm
> not using the Windows-malware, you see). While on the bright side,
> it's a source repo, so you can look at what it's doing and modify it
> yourself as well, it's just like any one of these things, it's in
> perpetual catch-up mode: It's gotta be successful all the time,
> whereas MSFT only has to be successful once.
> 
> On 05/15/2016 01:28 PM, Russ Wenner wrote:
>> I have successfully used the freeware app from Gibson Research, 
>> "Never10".  Works like a charm. https://www.grc.com/never10.htm
>> 
>> On Sun, May 15, 2016 at 12:36 PM, Michael Leone 
>> <turgon@mike-leone.com> wrote:
>>> Supposedly, some of the latest upgrades reverse that registry 
>>> setting. I say supposedly, because those reports are few and far 
>>> between. The same way those reports about MS auto upgrading
>>> users without their knowledge or consent are almost certainly 
>>> exaggerated.
>>> 
>>> 
>>> On Sunday, May 15, 2016, Keith C. Perry 
>>> <kperry@daotechnologies.com> wrote:
>>>> 
>>>> Awesome!  I think I saw this registry hack before but I had
>>>> heard that MS might have been getting around this work around.
>>>> Either way, I going to have to spend time now getting this onto
>>>> client systems so that some order of protection is implemented.
>>>>  ________________________________ From: "Jason Plum" 
>>>> <jplum@archlinuxarm.org> To: "Philadelphia Linux User's Group 
>>>> Discussion List" <plug@lists.phillylinux.org> Sent: Sunday,
>>>> May 15, 2016 12:27:33 PM Subject: Re: [PLUG] Microsoft to
>>>> force upgrades to Windows 10
>>>> 
>>>> 
>>>> http://www.zdnet.com/article/how-to-block-windows-10-upgrades-on-your-business-network-and-at-home-too/
>>>> This is the method I have been using for my VM's at work.
>>>> 
>>>> On Sun, May 15, 2016 at 12:24 PM, Keith C. Perry 
>>>> <kperry@daotechnologies.com> wrote:
>>>>> 
>>>>> From 
>>>>> https://tech.slashdot.org/story/16/05/15/0324224/microsoft-auto-scheduling-windows-10-updates
>>>>> "Microsoft has begun to auto-schedule PCs to upgrade to Windows
>>>>> 10 with or without consent from end users."
>>>>> 
>>>>> This is very serious...  I know this is PLUG but does anyone 
>>>>> know how to stop this?  If anyone understands the Windows 
>>>>> updates process, I'll like some ideas on how this can be 
>>>>> stopped.  Off of the time of my head, I'm thinking that it 
>>>>> should be possible to watch and kill the MS update processes 
>>>>> (wsupd service?).  I don't think that that is a good long
>>>>> term solution but if MS is going to continue to use a
>>>>> malware methodology to force people to their new garbage any
>>>>> remedy is better than no remedy.
>>>>> 
>>>>> I'll be making much stronger arguments to my clients that
>>>>> now is the time to move away from Windows but whether that
>>>>> is possible or not, it should not be forced.

Attachment: signature.asc
Description: OpenPGP digital signature

___________________________________________________________________________
Philadelphia Linux Users Group         --        http://www.phillylinux.org
Announcements - http://lists.phillylinux.org/mailman/listinfo/plug-announce
General Discussion  --   http://lists.phillylinux.org/mailman/listinfo/plug