Stories
Slash Boxes
Comments

SoylentNews is people

Submission Preview

Link to Story

Windows 10 is forcing itself onto domain happy Windows 7 PCs

Accepted submission by Arthur T Knackerbracket at 2015-08-07 14:27:22
/dev/random

Story automatically generated by StoryBot Version 0.0.1e (Development).

Note: This is the complete story and will need further editing. It may also be covered by Copyright and thus should be acknowledged and quoted rather than printed in its entirety.

FeedSource: [TheRegister] collected from rss-bot logs

Time: 2015-08-07 11:13:46 UTC

Original URL: http://www.theregister.co.uk/2015/08/07/windows_10_auto_injects_itself_into_windows_7/ [theregister.co.uk]

Title: Windows 10 is forcing itself onto domain happy Windows 7 PCs

Suggested Topics by Probability (Experimental) : 30.0 hardware 30.0 OS 10.0 science 10.0 mobile 10.0 digiliberty 10.0 careers

--- --- --- --- --- --- --- Entire Story Below --- --- --- --- --- --- ---

Windows 10 is FORCING ITSELF onto domain happy Windows 7 PCs

Windows 7 PCs are being force fed a diet of Windows 10, breaking a promise made by Microsoft.

The problem is affecting domain-attached Windows 7 PCs not signed up to Windows Server Update Services (WSUS) for patches and updates, but looking for a Microsoft update instead.

The upshot is PCs, ranging from 10s to hundreds at a time, simultaneously chowing down on the 3GB-plus Windows 10 load, killing business networks.

The problem began showing up on Monday with complaints beginning to notch up online.

One Reg reader got in touch to complain: “Customers using hosted services are really struggling with the competition for bandwidth – effectively taking them off the air.”

And it’s all happening despite Microsoft promising – here [microsoft.com] – that it wouldn’t.

According to that advice, the Windows 10 upgrade is automatically blocked when the computer or device is joined to a domain. It's one of the firm's three scenarios when the update is blocked.

Users have logged urgent enquiries with Microsoft’s helpdesk but in the meantime have resorted to triage to stop the problem.

That means blocking traffic at the firewall stage that would normally have gone to Microsoft Update. Another option is to switch settings to the WSUS server.


Original Submission