[cartoonfoxes]

I have no idea why this scenario gets talked about so little. It is an edge case, but its a huge edge-case. There are entire ecosystems of Windows-only software where running batch operations overnight are a daily fact of life.

I'm nearly resigned to the fact that I may have to segregate engineering workstations to their own network and whitelist their traffic.

IsActiveHoursEnabled is ignored.

[UK-AL]

I would assume the large majority of windows users doing batch stuff over night are businesses.

At that point you should probably be using windows server + wsus. Which give you a lot more control over updates.

[bigbugbag]

So what about the small majority ? Do they get a "sorry not sorry, f*ck you" card ?

You should assume that windows users doing batch stuff over night are people who have better things to do with their computers during their day or want their computer to work for them while they're not sitting in front of it. Try considering the whole instead of splitting to only address the large majority.

[UK-AL]

If software worked every convincible use case, it would become impossible to use from UI perspective.

Windows 10 is focused as a consumer os, designed for users to run their applications. Similar to iOS or android.

If you want to run batch operations, use the right product.

[cartoonfoxes]

> If you want to run batch operations, use the right product.

Sorry, but this does come across as a bit asinine.

What's the right product for running software written for Microsoft Windows, if not Microsoft Windows?

"Users running their applications" isn't just Grandma on Facebook, or your little sister playing Candy Crush Saga. Microsoft's unquestionable strength has been it's support for enterprise, small-business and professional desktop users. There is a lot of deserved anger thrown their way as a result of deliberate decisions to force flexibility and choice-limiting behavior down the throat of their core market.

My shop is small, but I can count COMSOL, SolidWorks, OrCAD, LabVIEW, various SPICE frontends, and a dozen other small odds and ends for instrument control and data capture without even leaving the engineering suite. All of which are going to be forever stuck on Win 7, at this rate.

[UK-AL]

Most of those are products that are not expected run over night in batching mode.

You may get the need to have things to run overnight using engineering, simulation, rendering products with some sort of long running process. But these normally have server component that you install onto Windows Server, which the client offloads to.

[cartoonfoxes]

> Most of those are products that are not expected run over night in batching mode.

I'll be sure to let them know that long-running computations deskside are now only an experimental feature /s

In all seriousness though, we've managed over a decade without the need for dedicated compute nodes along with the costs that would entail. The only case I can make for that right now is that current Windows now ships with unpredictable uptime.

[setq]

I agree with the person above your comment. For example some simulation loads are common to run on deskside systems.

However this IS definitely an edge case and it is possible to turn it off. I have run a physical host as a build agent that has uptime of months on Windows 10.

This is administrative competence, not a problem with the product or the use case.

WSUS + Windows server is definitely fine for most workloads though.

[cartoonfoxes]

> and it is possible to turn it off

I have this dreadful feeling that Microsoft is A/B testing this stuff, making sure that there is just enough inconsistency between sites to sow doubt and confusion.

[rhodysurf]

Our company has a dc but not that kind of control over child computers and it would be a large overhaul (and out of my control) to change the whole network setup.

I wish we used wsus though. M

[setq]

You can attach a GPO to the OU that the machines are in and turn it off for everyone.