The problem I see with that is, a lot of the time these updates come from
CDN's rather than Microsoft IP space... I'm pretty sure bad things would
happen if you try to limit access to major CDN's IP space.

I'd agree that telling anybody not to do or delay updates is a bad idea,
even if there was an easy way to do that on Windows 10... ideally, I'd like
to limit updates to something like half of the connection speed, but I
don't really see a realistic way of doing that, so we're pretty much stuck
with telling the customer to just deal with it and make sure they leave
their PC turned on until it finishes... I don't know how many customers
I've seen on our basic plan that call us to complain that their connection
hasn't worked for "weeks" and when I look at it, it's obvious that it's
been trying to do an update, but because their connection is so slow, they
just give up trying to use it and turn the PC off after a few minutes, so
it never finishes.

On Mon, Apr 17, 2017 at 10:25 AM, Steve Jones <[email protected]>
wrote:

> I think there was a thread last year about this, some cobbling of a list
> of MS IP addresses or something, probably would fail in that the IP space
> is probably shared with xbox live stuff
>
> This particular release they put out Tuesday i believe it something like
> 4-5 gb and theyre staging it out over two months or so, its just going to
> suck
>
> It will allow people to delay the installations much easier, but not delay
> the dl
>
> From the ISP side, we would never tell anybody not to do updates or to
> delay updates, and never walk a farmer through gpedit ... bad things
>
> you could always throw up an AD domain controller and join all your
> customers to it and run a WSUS server..... nothing could go wrong with
>  that :-)
>
>
>
> On Mon, Apr 17, 2017 at 10:15 AM, Paul McCall <[email protected]> wrote:
>
>> What are you guys doing to control Windows 10 update from downloading
>> updates whenever it wants to?  Windows used to have a setting for when it
>> would download and install, and now that setting (IF have you have access
>> to the Group Policy editor - some Win versions supposedly don') only allows
>> defining when it will INSTALL the updates and not when it downloads them.
>> You can make the update process manual I think through settings,  but
>> customers won't ever update then, introducing other issues.  So, that isnt
>> a great workaround.  You can also set an interface to “metered” which means
>> it won’t DL until it gets an unmetered connection but that won’t help
>> either.
>>
>> Today 3 customers (plus my PC) were killing an AP, all connected to
>> Microsoft presumably downloading updates as mine was from that IP.  That is
>> what my PC was doing when I caught the problem.  All customers and myself
>> were connected to the same MS IP address.
>>
>> Even if customers had access to GPEDIT, and if it had that ability,
>> talking customers through that would have been a not fun job for tech
>> support for all the Win10 devices out there now.  Supposedly, not all
>> versions of Win 10 have access to GPEDIT easily.  GPEDIT does have a
>> setting for maximum DL for updates which helps but that would only slow
>> things down for a loooong time to get updaes.  Much better to have it do
>> full updates after midnight.
>>
>> Was wondering if there was something that could be defined at the
>> customers CPE Mikrotik (in place at 95% of our customers) or at the tower
>> Mikrotik.
>>
>> There has to be some solution.
>>
>>
>>
>> Paul McCall, President
>>
>> PDMNet, Inc. / Florida Broadband, Inc.
>>
>> 658 Old Dixie Highway
>>
>> Vero Beach, FL 32962
>>
>> 772-564-6800 <(772)%20564-6800>
>>
>> [email protected]
>>
>> www.pdmnet.com
>>
>> www.floridabroadband.com
>>
>>
>>
>>
>>
>
>

Reply via email to