Windows 10: Any way to restrict P2P updates to specific networks?

Is there any way to restrict the peer to peer sharing of Windows Updates (WUDO, just so this shows up in searches) to only specific local networks? I know I can say to get/share updates with PCs on the local network, or local plus internet. But I'd like to restrict this further - don't share on every local network I happen to be on, but only on the local network when I'm at my office, for example.

All of my users have laptops, and most travel extensively. We have bad bandwidth at the office, so the P2P would definitely be nice. But I don't want them sharing updates when they're travelling, as they're often in locations with strict (and/or expensive) capping. Is there any way to do this without the user having to manually turn the option on or off depending on location?

:)

 

Any way to disable updates

Hi UF6,

First, change your login to a local Account:

Open the Settings App

Go o Accounts - Sign In Options

Choose to sign in with a local Account

Click your Start Button, type services and hit ENTER

Scroll down the list of services to find Windows Update

Double click the service

If it has started, click 'Stop'

Then you must set its startup type to 'Disabled' - 'Manual' will not do!

Restart your PC

That's It!

 

Any way to disable updates

It seems like a fair amount of work. I will try some of these suggestions, but I think I may just set up an Ubuntu dual boot.

 

So, digging further, I've found this:
MDM_Policy_Result01_DeliveryOptimization02 class (Windows)

Which shows an option to allow WUDO for a specific group, then allows in a different policy for you to specific a GUID as group id. Does this just mean that I can make up a GUID, and put that out as the group ID via policy, and then that will tag everything with that group ID and essentially limit the P2P to just machines receiving my group policy? That would meet my requirements if so, assuming my machines didn't go out into the wild and encounter another network where the computers there happen to be using the same GUID, but that seems desperately unlikely. I'm just not 100% sure I'm interpreting this correctly. Anyone tried this, or have further info?