3 ms·
> in fact, based on the Windows Server 2003 codebase rather than XP per se For a while in the 1990s, Microsoft tried to pretend that "Server" and "Workstation"
by tialaramex 3y ago
> in fact, based on the Windows Server 2003 codebase rather than XP per se
For a while in the 1990s, Microsoft tried to pretend that "Server" and "Workstation" NT were substantially different. At some point somebody actually worked out which registry key actually matters, and then (though obviously it's unsupported) you could turn a "Workstation" into a "Server" or vice versa, because in fact, just like Linux it turns out an operating system kernel is an operating system kernel, marketing is bullshit, the difference is always just tuning.
After that, Microsoft didn't ship "Server" and "Workstation" variants of the exact same code. Instead they'd branch the "Server" and "Workstation" products, under different names, from the same tree at different intervals. Thus this difference is purely about the badge, and presumably they felt that the XP badge was appropriate for this product whereas a "Server" badge would give the wrong impression.
- dboreham 3y agoNobody had to "work this out" because it was widely known and acknowledged by MS since the first AS beta release (1993). The original idea was to sell a product to complete with Novell Netware (at the time the dominant thing you ran on the office file server). If MS made it easy to use the desktop NT as a file server, then they'd be "leaving money on the table" vs what Novell charged for Netware (per-client licensing that meant $thousands for a large server). So they invented a license for clients (CAL) and a product that bundled some number of licenses in the SKU, and AS was born, sold for iirc about $500. Much cheaper than Netware, which subsequently died. Then, to make it harder for customers to simply use the cheaper desktop NT in place of AS, a limit on the number of connected clients was enforced (5?). There were also some kernel tuning parameters that were different between workstation and server. Subsequently, through the 2000, 2003, ... generations, more applications were bundled into the server product (e.g. ActiveDirectory) that were obviously not present in the desktop version.
- tialaramex 3y agoWhen you say "acknowledged by Microsoft" I notice you don't provide a link or even a quote. There's a big difference between what's obvious to programmers and what you can get fanboys to accept is true about a product they've somehow connected to their self-worth. In my experience the Registry Key made all the difference and of course Microsoft were not publishing "Use this registry key to effectively pirate Windows Server" docs - unless you're claiming they did? Windows 2000 Server is like older NT versions, it's exactly the same actual code as the far cheaper Windows 2000 Professional, whereas Windows Server 2003 was a different branch from the similar XP on the desktop, there was no "Windows Professional 2003" or whatever. The bundling makes it a bit easier for customers to stomach that you're blatantly selling them the exact same product with a different badge for more money, but it's not enough. It wasn't just about Client licenses either. Some Windows "editions" (ie the exact same code with a registry change) had different hardware support. Got 4 CPUs? Can't use them in "professional" edition, you need Server. Got a huge beat with 32 CPUs? Ordinary Server won't work, get yourself Datacenter Server. Same for RAM.
- chungy 3y agoWindows XP and Server 2003 would mark the only time in Windows's history that the releases weren't fully synced up. (Unless you count Windows XP x64 Edition, which was the same OS files as Server 2003) I doubt any Windows administrators are really mystified by it. Vista and Server 2008, one and the same. 7 and Server 2008 R2, one and the same. 8.0 and Server 2012, one and the same. etc. It's even obvious if you pay attention to update files, they start with "Windows6.0-KB...", "Windows6.1-KB...", etc. As for marketing, there is a real difference between home/workstation releases and server releases. It's not in the kernel or basic OS services, but instead with things like Windows Media Player or IIS. It makes little sense to include WMP on a server. Likewise, it makes little sense to include IIS on Home Edition.
- glhaynes 3y agoI've never understood how the difference between the editions being just a matter of having different bits set means "marketing is bullshit". How's changing the bits post-install different from, say, having Workstation vs. Server come on different CDs with those bits flipped? It's all bits in the end.
- drewcoo 3y agoThere's more difference than timing of when they cut a release. Different SKUs are crippled in different ways with features actually removed. And you can pay extra for upgrades to less crippled crippleware. IANAL, so I'm surprised the RICCO Act doesn't apply.
- EvanAnderson 3y agoMark Russinovich wrote about this back in 1996: https://www.itprotoday.com/compute-engines/inside-difference-between-windows-nt-workstation-and-windows-nt-server https://www.itprotoday.com/compute-engines/inside-difference... I don't know if modern versions of Windows will still blue-screen when you attempted to make changes to the "ProductType" and "ProductSuite" REG_SZ values in the "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\ProductOptions" key. (I see some values under that key in Windows 10 that I don't remember seeing in older Windows versions, too.)
- majormajor 3y agoI don't think it was ever a secret that the kernel and system was the same lineage, it was all about the config and whether various optional things (like IIS) were there by default. NT and 2000 were always business-targeted products with all the attendant usage-based licensing stuff that wasn't present in the consumer world, even though 2000 had a wide enthusiast userbase that was tired of 98 and ME and mostly figured out how to get games running well enough. Apple and various linux distros separated their products into "server" and "workstation" variants in the same way, too.
- scarface74 3y ago> At some point somebody actually worked out which registry key actually matters That “someone” was Mark Russinovich. He is now the CTO of Azure. https://en.wikipedia.org/wiki/Mark_Russinovich https://en.wikipedia.org/wiki/Mark_Russinovich