5 ms·
This seems like it's essentially confessing to something we already knew. Back at the turn of the century Microsoft liked to claim that Windows Server and the o
by tialaramex 8y ago
This seems like it's essentially confessing to something we already knew. Back at the turn of the century Microsoft liked to claim that Windows Server and the ordinary client NT were different in some important way beyond just the branding and price. People would even try to argue that Linux couldn't be a "real" desktop OS because it lacked some kind of secret sauce not found in a server OS... Hackers eventually found out how to tell a client NT kernel to behave exactly like Server, because of course they are the same kernel, duh.
Microsoft's reaction was to stop selling the two next to each other. There is no Windows 10 Server and Windows Server 2019 doesn't have a client version. So the exact same thing continues, but now there IS no equivalent product to prove the point that they're identical bar branding and price.
- basch 8y agoMicrosoft kinda gave up on this ruse back at Longhorn and Vista SP1 days. Longhorn was a fork of the Server 2003 codebase, and Vista SP1 was a backport/newfork of changes made to Server 2008. (Server2008 and VistaSP1 were both released Feb.4.08.) They were absolutely released in lockstep. Vista SP2 was released April.28.09 and Server 2008 R2 was released Oct.22.09. At that point the consumer product became the testing ground for the server kernel. It's easier to think of Vista RTM as a giant public alpha, and and Vista SP2 as an insider preview for Server2008 R2 / Windows 7.
- dblohm7 8y ago> Hackers eventually found out how to tell a client NT kernel to behave exactly like Server It was Mark Russinovich who did it with a utility called NTTune. Now he's the CTO of Azure!
- abainbridge 8y agoYou mean Mark Russunovich the sci-fi author: https://www.amazon.co.uk/Rogue-Code-Jeff-Aiken-Russinovich/dp/1250035376/ref=sr_1_5 https://www.amazon.co.uk/Rogue-Code-Jeff-Aiken-Russinovich/d... That Azure stuff is just his hobby.
- dblohm7 8y agoHere is the archived piece from their old ntinternals.com site: https://web.archive.org/web/19970605083609/http://www.ntinternals.com:80/tune.htm https://web.archive.org/web/19970605083609/http://www.ntinte...
- kyberias 8y agoThat was always a bogus and boring argument. Was then and is now. I don't think Microsoft ever claimed that they have a different kernel. It was always clear they have. Windows Server includes a lot of OTHER SW, other than Kernel, that makes it a server when compared to desktop Windows. Server and Desktop Windows are like different Linux distros.
- dboreham 8y agoI've worked (outside MS) for 20+ years with NT, beginning with the 3.1 beta. It is news to me that anyone believed the kernels were different. I can't imagine why anybody in the least bit clueful would believe that. Furthermore I've never heard anyone suggest or argue that they were different.
- mixmastamyk 8y agoBelieve the main point of contention was a 10 client limit to the services of NT Workstation. MS argued that Workstation was not able to handle more due to fundamental differences, but those with a clue suspected it was merely a registry setting or two. Not to mention it could handle that many web clients (at least) without breaking a sweat, but licensing prohibited it in theory. Related, there's been a switch in the System control panel to prioritize services/interactive use, though it has been papered over by two layers of cruft in recent versions so is hard to find.
- unilynx 8y agoWasnt that switch mostly controlling the size of a time slice? Eg larger time slices: more throughout but more latency
- mixmastamyk 8y agoSounds right, and details easily searchable. Can't be bothered as I moved to Linux full-time after the turn of the century.
- gaius 8y agoYes - NTW was tuned for interactive desktop users and NTS for server type workloads. But everyone knew these were just tuning sets for the same kernel.
- dboreham 8y ago>MS argued that Workstation was not able to handle more due to fundamental differences I've never heard that argument made. Memory is hazy but I don't believe the client connection limit was present in older versions of NTW. Back then MS was chasing market leader Novell which had a business model dependent on charging for each client connection to the Netware server. MS attacked their dominant position by adopting a CAL model where the charge was for the client access license, conveniently bundled with your copy of Windows. So you could buy a $500 (or whatever it cost back then) copy of NTAS and use it to serve your 1000 employees with Windows desktops. Meanwhile Novell would want to charge you $$$ for a Netware server to handle that same user population. Hence Novell went out of business. The connection limit in NTW was probably added to stop people going around even the very low $500 cost of NTAS.