The https://massgrave.dev activation scripts have support for various versions and also for enabling Extended Updates (ESU), but this is a bit off-topic and HN mods might come after us ;-)
I'm not sure it is off-topic. The parent to this one was talking about, presumably, dodgy Windows keys (that shouldn't be allowed) but from my understanding, the massgrave scripts just use internal Windows mechanisms to activate.
It's not actively usurping Windows security.
In fact, I've read more than once that Microsoft tech support have been known to use massgrave scripts to help with activation-related issues with clients: Although I should caveat that with saying that it may have been Reddit I found that info so pinch of salt and all that...
So, my take on this is if the massgrave scripts allow activation without breaking any laws then sobeit. I'm talking about doing stuff that, while it appears dodgy, actually just manipulates the ultra-complicated processes under the hood that Microsoft has already built into the OS.
It's like publicising the workarounds for the now-mandatory Microsoft account when installing Windows 11. These involve things like reg hacks and commands: they're already in Windows so publicise them all you want imo.
For me just now, I had to take a bit of a breather and calm down for a second, as soon as I saw "Exploring IRC" I was taken back 30 years in time or so, when IRC was brand newish, and it paid to have a text file somewhere full of details to join the network and find out, in realtime, what was happening in the world.
This is how articles should be written, this is why I’m reading El Reg (a.k.a. The Register) all these decades, this is what happens when high management cares only about profits and when real engineers don’t eat the RTO bullshit. Bravo for putting this online.
P.S. I’m not an Amazon hater, replace the company name with any other big one of your choice and the article will have the same meaning ;-)
It's not your feeling about Amazon that would cast doubt on your take, it's that you've reduced it to one pet cause and decided a source is well written because it appeals to your dislike of RTO. Nowhere has any evidence of the relevance of that to this been presented, Amazon has had outages since before WFH even began, they've all always had their occasional outages and bad days.
The Register is an opinionated tech tabloid filled with outrage bait. This article is not an exception, drawing far reaching conclusions from little evidence.
“Little evidence?” If the “aws” partition doesn’t actually exist when IAD breaks, Amazon hasn’t even discovered how to make multi-region cloud infrastructure. That’s a big deal.
After all the complaints and upheaval created after their silly management/leadership decision, they finally understood something.
As an owner and administrator of many Synology NASes I agree that Synology offerings are a bit underpowered compared to what is available in the market (from H/W point of view), but the ease of use and peace of mind within the Synology ecosystem (DSM software, apps) outweighs whatever drawbacks they have.
If Synology management takes the decision to refresh their H/W with new CPUs, NICs and more RAM, I'm sure they'll stay on the market ;-)
Nice one, thanks for sharing. For sure I’ll give it a try.
Have you thought of creating a setup so as to package all libraries and dependencies needed? You have a very nice installation guide, but there are many users who just want the setup.exe :-)
Thank you! Not sure I can package everything because of license requirements. IANAL. I think the container image basically automates the various dependencies, but I didn't create it and I don't use it so I'm not 100% sure.
Basically, I would love to know how to do this correctly for each platform, but I don't know how. Help would be welcomed.
reply