haunter 1 day ago

I wish they didn't discontinue the free Hyper-V server, last release was in 2019. Yes Proxmox or xcp-ng (Xen) are better choices nowadays but if you have some Windows VMs or legacy Windows software then I think Hyper-V was/is pretty cool (in fact it doesn't matter because you can run Linux, BSD any OS inside the hypervisor it doesn't matter). I have a homelab PC running it, the actual only big downside is the lack of ZFS support. Otherwise it's still a good solution (in a 'not great but works perfectly' sense)

  • noAnswer 1 day ago

    What do you mean by that? You can still (without extra cost) install Hpyer-V on 11 Pro an Server 2025. I do that all the time.

    • cheema33 1 day ago

      > What do you mean by that? You can still (without extra cost) install Hpyer-V on 11 Pro an Server 2025. I do that all the time.

      You are paying for Server 2025 in your example. The option from MS that parent poster was talking about does require you to pay for the server OS to host VMs.

    • sippingabonedry 1 day ago

      Hyper-V Server Core was a freeware product. If you knew how to use it, it blew VMware out of the water at the time at zero cost.

      • DaiPlusPlus 3 hours ago

        > it blew VMware out of the water at the time at zero cost

        Unless you need USB support, or even an emulated SoundBlaster - or really, any emulated hardware necessary for running legacy desktop applications; or if you want to run any non-current version of Windows, really.

        Hyper-V is great for running (and live-migrating) headless VMs, but that's it. The lack of any real Guest hardware customization makes it useless for desktop virtualization tasks.

SimianSci 1 day ago

I very much implore anyone who is part of the decision process of server software acquisitions to avoid using Windows Server if you have the choice. It is painful to work with over many years and has been outclassed in many ways by free and open alternatives that are easy to adopt.

I say this as someone who has been responsible for server clusters for over a decade and has had the unfortunate fate of maintaining critical business infrastructure on Windows Servers.

  • burnte 1 day ago

    To counter this, while usually a non-Windows server can be better, there are plenty of use cases where Windows is the best solution and you should use it in those circumstances. Evaluate every deployment individually and pick the best tool for the job.

    Maintaining a Windows server removes most of the headaches of long term Windows server use, and it's also the area most people don't keep up with causing the issues to start.

  • g_host 1 day ago

    What equivalent (or better) alternative is there to Active Directory?

    I'm no Windows-lover, but usually ADDS is the thing enterprises are after with Windows Server infrastructure.

    Leveraging an AD Domain makes life a lot simpler when your workforce isn't mostly developers and engineers.

    • vel0city 1 day ago

      In the cloud, just ditching ADDS and moving towards cloud IAM. Workload identites, OIDC, and more. So nice, so much better than ADDS.

      If you're not in a big cloud environment though, I do agree. ADDS is hard to beat.

      • justsomehnguy 1 day ago

        And when "your" "cloud" is offline...

        • vel0city 1 day ago

          And when "your" "server" is offline...

          We're all reliant on many third parties to different extents to keep our services online.

          I'll have fun with modern IAM and cloud network security tooling.

        • hnlmorg 1 day ago

          OIDC generates a credential. That credential isn’t going to instantly expire for zero-trust clients. You’ll generally have anything from 8 hours to several days before needing to re-auth against your identity provider.

          Just like with Windows logins against AD. Once you’ve had an initial login from your laptop, you can continue to log into your laptop for days without having a connection to AD.

          • justsomehnguy 1 day ago

            Yes, but if your AD DC somehow failed you can do things like recover from the backups. With the cloud you can only pray it would be restored before the credential expire.

            • hnlmorg 1 day ago

              I get engineers would rather be the ones fixing the problem rather than relaying messages that it’s in the process of being fixed, but what you’re describing is ostensibly the same thing.

              Either way, the users of your platform are impacted the same way.

              But from a business perspective, it makes more sense to have those engineers focused on building projects that earn the business revenue .

              Infrastructure like identity management is generally a sunk cost. Customers don’t pay for a product because the company that sells it manages their own identity provider for internal systems. So unless your company is large enough that it becomes cheaper to self-host instead of paying for SaaS licences, it makes smarter business sense to have those engineers focused on more profitable projects.

              And that’s the real reason people outsource these kinds of systems.

              • justsomehnguy 20 hours ago

                > on building projects that earn the business revenue .

                And when the cloud is down there is no business revenue. And when there is 'sorry dataloss incident have $20 redeem" there is no more business revenue.

                At least when you control the data and services - you can control how much you can invest in your resiliency. With the cloud you have no resiliency.

                > Infrastructure like identity management is generally a sunk cost.

                Security guard on the entrance is generally a sunk cost. Having a building for people to be miserab^W^W commute in everyday so they are miser^W under a pretense of being a team under a middle-management who knows nothing about how to 'build projects' and doing nothing except meetings and meetings about meetings is totally a sunk cost. Both are readily spent because that's a business decision which is made based on a custom. No reality check or engineering goes in it.

                • vel0city 15 hours ago

                  > At least when you control the data and services

                  Do you actually control the data and services? Do you really have plans when your colocation goes dark? Do you really have effective plans when your office catches fire? How many days do you have diesel contracted for to run those generators? Are your ISPs or network peers similarly ready to handle disasters? We pretty much all rely on third parties on some part of the stack.

                  It's often quite cheap to be multi-az, and having a pilot light setup in another region isn't always too expensive. Standing up an entire other datacenter (or two, or three, or five, or more) fully stocked is quite an investment.

                  • justsomehnguy 14 hours ago

                    > Do you really have plans when your colocation goes dark?

                    Do you really have plans when your cloud goes dark?

                    If you don't have an answer for that when your push for clouds is not going anywhere.

                    Because you suddenly have an urge to compare a cloud to the over-provisioned geo-resilient on-premise infrastructure supplied and supported by follow-the-sun IT team... because there is only this way you can somehow go on top with the cloud offering.

                    And no, somebody who can 'cheaply be multi-az' doesn't need 'entire other datacenter'.

                    • hnlmorg 10 hours ago

                      Answering the GPs question with a question doesn’t work here because you’re the one arguing that self-hosting is better for resilience.

                      I’ve been in the industry for 30 years, so long before SaaS was a thing. And our approach back then for things like email outages, outages in identity providers, and such like, is exactly the same as it is for orgs that uses SaaS now: tell the company staff to be patient and that the service will be back up as soon as possible.

                      The only material difference was back then, I’d have to stop working on customer projects and now i don’t.

                      Working in DevSecOps, I’ve had to define disaster recovery systems before SaaS. And 99% of the time the board of directors would say “that’s far too expensive. We will just accept that risk”, just like what happens now when people talk about multi-cloud now.

                      There is no material difference. It’s just the egos of engineers who think they’re better in a crisis (and they might be, but that doesn’t mean their time isn’t better spent elsewhere).

        • AdieuToLogic 1 day ago

          > And when "your" "cloud" is offline...

          Then the rest of "your" "cloud deployed services" are offline as well?

    • cowlevel 1 day ago

      Microsoft got that right - they determined what people actually wanted, then created a product that did that. Nobody is doing as well in Linux, not even Red Hat. Should we start today?

      • ChocolateGod 1 day ago

        There's bits and bobs from RH, but the Linux desktop isn't a thing in enteprise outside of some very niche use cases.

      • tosti 1 day ago

        Nah, (long story short) they created an inferior alternative to Novell and put their weight on ensuring Novell couldn't compete. Novell sued, lost, went bust.

    • OneDeuxTriSeiGo 1 day ago

      TBH I've not used it professionally but Samba actually has done a lot of work building up a usable AD DC platform that works on linux. It punts a lot of work over to LDAP and co generally but you can get substantial parity to ADDS on linux nowadays.

    • oneplane 1 day ago

      If you need an isolated (so no Entra and no Intune) built-in management option, then AD is probably the best fit. It will work with Samba or just plain LDAP and Kerberos (without GPOs), but that's probably not what you are after.

      If you need to manage Windows clients, you should probably not use ADDS either way, and use their cloud offering (which is, of course, a subscription game). No server required for that.

      The true use cases for greenfield ADDS installations are getting smaller and smaller every day.

      • darksim905 1 day ago

        samba can be stood up as a domain controller since who knows how long at this point. There's a lot of janky setup and I'm surprised it even works with how complex (to me) the DNS records are in a Windows environment. But for very simple environments, it works. If I recall you can also utilize GPOs and templates. I don't know how straight forward it is to make or provision GPOs on a samba only domain, but it shouldn't be a problem.

        Of course, there's having a working network, 'managing' Windows clients, vs software deployment of Windows clients.

        • asteroidburger 1 day ago

          Does anyone seriously use that in production? I can’t imagine forking out for Windows licenses but then turning around and running Samba DCs.

          • nwmcsween 1 day ago

            In the extremely fun and interesting Windows land you pay for Windows server licenses and then pay for users to access the Windows server.

          • darksim905 1 day ago

            What?

            It can be stood up as a domain without Windows or an existing domain...

            I've heard of people doing things like this, but it is usually extremely small teams and environments, like a library or a small startup that will remain less than 50 users as a non-profit or some such. People don't necessarily openly talk about it as much as I'd like but you also see people use it in the sysadmin sub-reddit. It's somehow still not as painfree to set up as you would on Windows but I imagine that's going to change more and more with people getting up to speed faster with AI type coding and tooling.

            • oneplane 1 day ago

              It's great for CI/CD too, just have a ready to do AD DC in a container, test your applications against that, nuke it all at the end of the run. Fast, cheap, dependable.

              For the classic "have users use different workstations" that doesn't really matter as much any more, you can get a laptop and just take it with you. No network/directory login needed. If it were about GPOs, you could do that, but Ansible etc. can do that too, as well as Intune. GPOs also still work (albeit non-replicated/HA), but if you're doing that kind of management, you could also consider Chromebooks at that point.

              Realistically, a lot of the 'work' that used to be done like that would be done on an iPad. There are of course still the special windows-only apps, but that's the sort of thing you'd want to box in and isolate as it doesn't tend to be the best quality software that is built like that (think: CnC controllers, planning software, thick clients, general enterprise software at large).

          • oneplane 1 day ago

            Yes, it's used a ton in isolated systems where some manufacturer delivers a Windows client that you run in kiosk-mode but doesn't require anything else. Instead of paying double and having a bad time doing maintenance, you can emit as many fleets of that type as you need using generic DevOps practises.

            I wouldn't run it in the classic way (server in the backroom of an office with a couple employees using it to log in and deal with files), but that's not because it's Samba, that's because I wouldn't do it with Windows Server either, that stuff gets yeeted into a cloud unless there is an actual budget to do it right.

        • oneplane 1 day ago

          The problem with Samba is that it can't do full HA. Yes, it's possible to do something like NFS re-sharing but that messes up permissions, you can't reliably spoof SMB and NTFS intrinsics that way. DFS-R isn't really viable with Samba. The reason this is important is that 'real' AD uses the SYSVOL over DFS to make sure every SYSVOL has the same data on it, and if any client talks to any advertised DC it gets the same interaction.

          There is some irony to this: the vast majority of currently janky AD setups tend to be the yolo-single-instance windows server installation on physical hardware (usually with no backup, a tape backup or a crappy external USB HDD that will fail the first time it has to power down and back up again). Those could easily be replaced with Samba since it does exactly the same thing. It's usually paired with perhaps 4 to 10 workstations where 5 to 7 are actually used by multiple users with roaming profiles etc.

          In bigger setups you wouldn't do any of that either way, and you'd either already be stuck in the horror that is legacy AD, hybrid AD or offline AD.

          There tend to be excuses like "yeah but this user/admin will already be familiar with windows", which doesn't really make sense, because if that were the case it would be patched, well-configured, and have some piece of paper with minimal disaster planning written out. Most of those will even come with whatever you buy, as well as with most of the built-in docs and wizards and clickops stuff you go through in those systems, but they tend to be ignored all the same.

    • bigbuppo 1 day ago

      Don't you mean Entra ID P2 bundled with Microsoft 365 E7 for every user including the janitor?

    • jon128 1 day ago

      RedHat Identity Management is the analogue to Active Directory in RedHat Linux environments. RedHat IdM interoperates with Active Directory too.

      Some hosting companies have used FreeIPA (open source distro of RedHat IdM).

      RedHat IdM / FreeIPA are used in places that have compartmentalized security teams and a mandate from the top of the org to implement meaningful compartmentalization down the org.

      The hard part with RedHat IdM / FreeIPA is they are very "old world", for a time when things were at a slower pace, or today for places with big budgets that do very "enterprise" things.

      In places with large Linux/Unix footprints, on both server, and "desktop", some combination of cron, Salt or Ansible, pubsub (for "push" events), and cleverly applied cryptography are used. This approach can be very robust and agile. But only places that attain and retain necessary multi-disciplinary talent enjoy the potential of these.

        https://docs.redhat.com/en/documentation/red_hat_enterprise_linux/7/html/linux_domain_identity_authentication_and_policy_guide/introduction
      
        https://www.freeipa.org/page/Main_Page
    • kwanbix 1 day ago

      I never really understood the need for Active Directory (AD).

      When I worked at IBM, for almost 15 years until 2010, we were allowed to install pretty much any OS on our ThinkPads, as long as it was supported by a tool that monitored certain security and compliance requirements, such as the screensaver activating after five minutes, the OS being up to date with security patches, etc.

      The tool supported Windows and several Linux distributions, including Red Hat, Ubuntu, and SUSE, IIRC. I'm sure I'm forgetting a few others.

      And I don't recall us having any major issues from not using AD, despite IBM being a massive company with hundreds of thousands of employees.

      But maybe I'm missing something? What would AD have provided that couldn't be handled by that kind of setup?

    • jsiepkes 1 day ago

      Closest thing is probably FreeIPA.

  • nsxwolf 1 day ago

    I know how to use it real good though. 20 years of familiarity is hard to replace.

  • xyst 1 day ago

    anybody that decides "windows server " should be part of their infra stack in the past 20 years clearly has ulterior motives (ie, kickbacks); and has likely never touched/managed a windows server

  • jiggawatts 1 day ago

    In many ways it hasn't been outclassed. Every time I dip a toe into the Linux waters, I recoil in horror at the things that lurk beneath the surface.

    You're all suffering from Stockholm syndrome.

    Where to begin?

    There is no Linux, except the kernel. There's dozens of distros, and none are even vaguely compatible in their user space in the same way Windows is. Docker containers are effectively mandatory if you want to retain your sanity.

    Configuration files are ad-hoc, unspecified, text formats (huuurk) with arbitrary and capricious escaping and quoting rules. It's rare for these to be formally specified anywhere. Good luck doing anything to Linux configuration programatically!

    A Linux operating system in general is "write only, once" -- which also explains the popularity of docker. Trying to manage a fleet of heterogeneous servers with Ansible, Puppet, or whatever is an exercise in frustration. They're barely more than script-execution engines, applying opaque changes that are difficult to audit later. You're always best off discarding servers entirely and starting from scratch.

    Linux barely even has a concept of a "service", which invariably require a full stop-start to pick up configuration changes. When -- finally -- systemd was introduced to catch it up to NT4, there was much wailing and gnashing of teeth. It's still inconsistent, so publishing server software for Linux is again, you guessed it, best done with containers.

    Don't even get me started on how Linux stumbled into UTF-8 in an era where Windows, MacOS, and Solaris had already been doing Unicode for a decade.

    Can I put spaces in file names yet, or is that still considered an eldrich incantation to greybearded admins?

    Unicode in user names?

    Central auth without hard-coding IP addresses for "the" (singular) Kerberos server, like it's an MIT lab in the 1980s?

    Here's a trivial operation on Windows that would make any Linux admin collapse into a twitching heap and foam at the mouth: Make every server and workstation trust the same private root certificate authority, for every HTTPS client on the system, not just one particular web browser or app runtime.

    Or... ensure the existence of a consistent firewall rule to every Linux computer, e.g.: for Tenable scanners.

    Or... add a local user to every Linux computer with some non-trivial rights.

    PS: I've done all of the above and was horrified about the time, complexity, and cost.

    • eddythompson80 1 day ago

      First of all, this is about Windows Server, not client. The extent to which you need a Windows Server is to manage a fleet of Windows Clients.

      All the issues you mentioned are irrelevant for a Linux server (distro selection, any ill-conceived notion of svchost benefits on a server, client CA management, adding local users, etc) or much better on Linux as a server (utf8, file length, and yes you can have space on the file, you can have more that 256 spaces as a matter of fact)

      You can get all the windows client benefits if you lock on a distro like you said or use macOS. Windows is garbage ware.

      • jiggawatts 1 day ago

        Ironically, Microsoft is busily removing the need for that! Windows desktops can now be managed with just Entra ID and Intune, there's no need for Windows Server.

        In practice, ~80% of Windows Servers in typical deployments are not used to manage the client fleet, they're hosting web apps on IIS, database servers, etc.

        • trueno 1 day ago

          they gave me a windows server as a dev environment. i laughed. it never gets used, because it sucks.

    • Boxxed 1 day ago

      Rather than refute your points individually, I'll just say that if you think having spaces in file names requires some kind of Eldritch incantation then you are so far off base and/or unskilled it's not even worth engaging.

      • tosti 1 day ago

        This. For every point he has, I can think of one or several counterpoints. But I can't be bothered with an obvious troll.

    • the8472 1 day ago

      > Configuration files are ad-hoc, unspecified, text formats (huuurk)

      depends, toml and json are becoming more widespread. systemd's format is also specified.

      > Docker containers are effectively mandatory if you want to retain your sanity.

      If your application consists of a sprawling mess of files and depends on specific library vesions then yeah, but that's no fun on windows either where you either need to run a bunch of prerequisites-installers or bundle a ton of dlls before you run the actual application.

      It's entirely possible to write single-binary executables that integrate themselves into a system, sans containers. I have done so for windows and linux. On windows it registers itself as system service, on linux as systemd unit. Afterwards things start to diverge a lot. On windows if you want to talk to the system you either need to call a lot of C APIs or or startup a powershell interpreter to run cmdlets wrapping those APIs. On linux you can write a bunch of config files or invoke the a CLI tool directly without indirecting through a shell.

      > Can I put spaces in file names yet, or is that still considered an eldrich incantation to greybearded admins?

      Has been possible for decades. Some shell scripts might be handling them incorrectly, but passing command line arguments in cmd/pwsh is fraught too. I'd say windows' argument passing is worse than unix.

      > Don't even get me started on how Linux stumbled into UTF-8 in an era where Windows, MacOS, and Solaris had already been doing Unicode for a decade.

      As I understand it it was only with windows 11 that they finally finally converted the *A APIs and the terminals to utf8, before that they defaulted to some legacy codepages.

      > Make every server and workstation trust the same private root certificate authority, for every HTTPS client on the system, not just one particular web browser or app runtime.

      As the eMudhra debacle showed neither windows nor linux can do this since various applications started shipping embedded certificate bundles instead of using the system store.

    • ocdtrekkie 1 day ago

      Yeah. As a Windows and Linux server admin, the capitalism leads to a lot of dumb in Windows Server like Edge having Game Mode and Xbox Services starting by default on Server out of the box. Most of what Windows does badly isn't poor engineering... it's own-goals due to business interests.

      But Linux is downright primitive in comparison in a lot of ways. It's nice to have a robust free operating system, but Linux is downright primitive sometimes in comparison. And a lot of it does come down to being fifty separate systems with no clear vision. Things like discovering disabling suspend in GNOME doesn't actually disable suspend, because that only applies when you are logged in.

      systemd has helped a lot in closing the gap, but while I'd rather have a Linux server "just running", I'd definitely rather troubleshoot a problem on a Windows box.

    • darksim905 1 day ago

      The funny thing about callouts like this is it ignores stupid things like Microsoft saying to never rename a domain controller in the pre server 2012 days. Now it's a lot more accepted/easier to do and there aren't as many warnings, if any. But I recall in so many books, guides, videos and documentation they mentioned to not rename a domain controller hostname under any circumstances. Windows is not without it's faults and some of it's quirks are no different that Linux.

    • sippingabonedry 1 day ago

      There is a lot of LARPing on HN.

      Unfortunately they give most of the unsolicited advice.

    • jen20 1 day ago

      > Don't even get me started on how Linux stumbled into UTF-8 in an era where Windows, MacOS, and Solaris had already been doing Unicode for a decade.

      The Unicode story is hardly a triumph for Windows here. UTF-16LE is strictly worse for almost every case.

  • kev009 1 day ago

    The open source options are still a bit like a kit car, while Windows is an awkward but finished product. And I say that as a FreeBSD and NetBSD developer and a career primarily building high scale Linux infra. If you can use some type of PaaS/FaaS perhaps the concern approaches zero since you are again using some more finished product.

    The one area I think Windows can gain some market is HyperV, with VMWare becoming expensive. I recently landed a bunch of fixes to FreeBSD network drivers so they SR-IOV mode works. It's an odd hypervisor, but it seems to work in my limited testing.

  • sippingabonedry 1 day ago

    > has had the unfortunate fate of maintaining critical business infrastructure on Windows Servers

    Skill issue.

    This sentence implies you were probably the open-source IT guy who thought "oh it's just Windows I can figure it out".

    Being a good Windows admin takes skills and experience, it's no different than e.g. RHEL.

  • k0morebi 1 day ago

    Fixed it for you:

    I very much implore anyone who is part of the decision process of {software_type} software acquisitions to avoid using {microsoft_product} if you have the choice. It is painful to work with over many years and has been outclassed in many ways by free and open alternatives that are easy to adopt.

dead_hn_theory 1 day ago

I'm going to try to stay on topic: what are the practical use-cases for the folks here who are running Windows Server, to continue to do so? Momentum? Legal?

  • SV_BubbleTime 1 day ago

    A. We need to run Windows programs. Our 3D cad PDM is windows only. Our ERP is windows only. Our camera system and access controls, also windows. We need to work with other businesses, and guess what? They use windows too. It’s pure fantasy that you can run many businesses without Windows. Maybe self-contained ones that sell software or services directly to customers. I’m in automotive; it’s all windows.

    B. Our MSP like almost all of them is a windows shop. It’s what they know how to use and they can train employees on it. We could hire internal IT, but it would be at least double what we’re paying our pretty good MSP and we don’t need to deal with staffing. We aren’t an IT company and don’t want to be.

    Personally, I won’t use windows ever again. But, most of our people have no choice. Put it down to institutional momentum if you must.

  • ortusdux 1 day ago

    I know of one case where the answer is CMMC compliance for a few odd reasons.

  • jojogeo 1 day ago

    Usually org enforced in my experience, or folks running onprem AD:DS etc.

  • lenerdenator 1 day ago

    C-suite and execs know it, the software the customer is running on it is proven stable for their use case (inertia as opposed to momentum), and maybe the people deciding on things get intimidated by figuring out which other OS to use. Do you use Red Hat? Canonical? Do you give a child's eternal soul over to Larry Ellison as a part of the contract for Oracle Linux? If you just stick with Windows Server, for better or worse, you don't have to answer these questions.

  • wmchen 1 day ago

    Typically Active Directory, and organizational inertia (existing software is meant to run on Windows Server, knowledge/contractors/etc. are familiar with WinServer) as you mentioned. Sometimes, certain applications are only certified for compliance on Windows Server. Small businesses seem to run Windows Server because it comes with a UI, usually because IT is an off-the-side of the desk thing for someone.

  • e40 1 day ago

    Cooperative development on Windows. That's how we've used it. We're on 2012 R2 still. We run a very, very narrow set of tools and don't uses browsers on the machine.

    We updated a 2nd machine to 2016, but with SSDs the performance was as bad as the 2012 R2 machine with spinners. OLD spinners.

    I spent 2 days looking into how to purchase a more modern version... honestly, I was shocked how confusing it was. That was a couple of years ago.

    • tosser811 1 day ago

      Congratulations on the liability and job security.

  • NikolaNovak 1 day ago

    In big enterprises it's fairly pervasive for all the imaginable reasons - the ubiquity of Office / Exchange to run your business, and the build out through Active Directory and outwards to properly capture your IT.

    FYI / fwiw and on a more specific note, we use them as RDP to run a large number of software and utilities only available in Windows form. For example, the Peoplesoft ERP can and does run on Linux and aix, but the proprietary GUI IDE is windows only. Our dbas use Toad. For whatever reason our RPA Blueprism is running on windows as well.

  • mamcx 1 day ago

    The main? This is like ask: Why use a linux server(should be a windows one!) when I use a linux desktop?

    That way, in server I user power shell and in desktop bash! how should be!

  • wvenable 1 day ago

    The reason why anyone runs any OS: because it runs the software that we need.

    Some of that software might be dependency of some other software which is a dependency on some other software deployed everywhere.

    Almost any organization is a complex series of integrations -- almost nothing is it's own silo that doesn't communicate with another system or application.

    • trueno 1 day ago

      i wish we had that excuse. ours is purely because our head of IT is a diehard microsoft fanboy. we could sunset some sql servers and completely remove the need. we're entraid'ing now so don't even have the AD excuse. the guy just keeps renewing licenses and then handing out microsoft teams branded junk he gets at conferences. it's kind of insane.

  • thisisnico 1 day ago

    Local AD, Fileserver, Integration between services, DNS and DHCP, MS SQL Server for ERP Systems.

  • aetherspawn 1 day ago

    Honestly because it’s cheaper than Enterprise Linux: buy CD keys of Windows Server perpetual licenses for like $100 rather than $900/year subscription per CPU for something like RHEL.

    I find Windows to be more stable, too. RHEL kept randomly dropping fiber optic adapters every few weeks, which would require network manager to be restarted, and nobody knew why. Stock standard Dell PowerEdge with certified RHEL, supposed to be rock solid but not as stable as expected

    • SimianSci 1 day ago

      non-comparable You are talking about gray market unofficial keys, versus a software subscription with dedicated support.

      • aetherspawn 1 day ago

        When we used RHEL we used to hit the support like 2 or maybe 3 times per year, mostly issues with things breaking during upgrades.

        Since switching virtualisation hosts to Windows Server (we still run Linux VMs), performance has been measurably the same, updates have been fully automatic with zero intervention, and management has been simple — we haven’t needed any support for the last 5 years.

        I was pretty surprised at WS stability as a virtualisation host because everything online said HyperV was crap, but it’s actually pretty good. Our workloads are HPC: we hold all the cores at 90% nearly 24/7.

    • darksim905 1 day ago

      You've never administered SQL server, have you...? :)

  • apimade 1 day ago

    There isn’t a good reason to be running Windows Server today, besides quirky legacy compatibility requirements.

    If it requires user auth integration, Windows is really the best choice still for high compliance environments where user auth stems from AD. But I’d argue organisations deploying servers that still need user auth are doing something drastically wrong today.

    Windows is a well paved road for legal and compliance, but so is RHEL.

  • SoleilAbsolu 1 day ago

    A deep and abiding love of Microsoft's CAL Licensing?! Err, no...I'm relieved that we moved from on-prem Server/hybrid AD to Entra ID.

  • Juvination 1 day ago

    Self hosting Web Forms through IIS.

    Would love to have switched off of Windows but we run to many legacy applications.

  • wcoenen 1 day ago

    Build servers for .NET Framework projects.

    • darksim905 1 day ago

      I imagine with the way Microsoft is going with Windows 11 and the developer configurations where you can just build on a box via the commandline with the WinAppC CLI, this will be less and less of a requirement unless you're a very large organization.

  • layer8 1 day ago

    Active Directory, Windows domain controller, Exchange server.

  • dbl000 1 day ago

    I work in the cybersecurity space and I see Windows Server everywhere. More common with smaller shops (think ~50 or less people). HN tends to skew very tech forward and isn't aware of the breadth chaos that's out there. A lot of the times this is because smaller companies don't do their own IT. Think of your dad/aunt trying to use a computer. Those same people sometimes end up running business that need servers. They don't manage the IT but go through a MSP for it. MSPs universally tend to be Windows shops that want to do things as cheaply and quickly/conveniently as possible. That means they push Windows and their clients don't know better to push back. It's also probably convenient for the end user. They don't need to think about server/computer. Their mental model can become "this is my computer, and that's the computer for the printer to work", because Windows server looks similar enough no one bats an eye. If you're not a technical person Windows server is just Windows and so you can work with it.

    We had a client (manufacturing) that still used server 2008 running some kind of access app. It hadn't been updated or even touched in years and was the cornerstone of the business for them. Until I saw it myself I thought thinks like that were only stories. I've seen them a lot at some smaller union funds/offices. They'll just have one server that's used for sharing/printing/etc. I'll bet if you go to any medium sized city in America (say Cincinnati) and find a local wealth advisors office (or other similar local mom and pop shop) they've probably got one as well. Also doctors. For some reason every smaller doctors practice I've every worked with (about 9 now) love using Windows Server. There's just so much stuff in the med space that just works with Windows only.

    Part of it's probably a very healthy dose of inertia. It works so there's no reason to spend time (and more often money) to change it.

    For people/places like this I think Windows Server is a good option. It just works out of the box, integrates well with stuff most people know, and can be managed with a GUI so it's not super scary for the non technical folks.

    • PorciiVorbesc 1 day ago

      This. Around 2020-ish, I went for a interview at small EU IoT startup that had about ~10 employees, and the founder and CEO told me how happy he was they went all-in on the MS stack since they just pay for Office 365 & Azure subscriptions and everything cloud and IT related is basically taken care of via his Macbook, no need for on-prem infra or an army of expensive sys-admins to manage a Linux stack. He said he manages everything in the company from one account on his macbook and for him that's a game changer so he can focus on the product, business and sales instead of maintaining and micromanaging a tech stack.

      And this is besides all the banks, insurance and finance corps here that have 20+ years of legacy stacks all running on MS or on their way transitioning to MS after decades of IBM(so much for EU tech sovereignty).

      I have no experience in running or configuring any of these massive MS stacks, but it seems whatever MS does it pleases the people who are paying for the product, and in those business that's the main selling point. HN PoV seems to be biased towards the user and UX rather than the beancounters.

      • dwattttt 1 day ago

        Everything seems right until the last sentence; banks, insurance, finance, a small start-up (that may or may not be tech focused, I'd guess not), they aren't getting Windows because it's a downgraded UX for their purposes. And they aren't all (or even any in some cases) bean counters.

        They are getting _something_ that they're happy about, and they're not all blind to alternatives.

    • darksim905 1 day ago

      Windows small business server is a specific kind of hell. Windows server is perfectly fine on the other hand.

    • arcanemachiner 1 day ago

      MSP:

      > A Microsoft Managed Service Provider (MSP) is an IT services company that remotely manages, secures, and supports Microsoft environments—such as Microsoft 365, Azure, Entra ID, and Intune—for businesses.

  • phendrenad2 1 day ago

    Mostly because Microsoft is a huge company and thus it's perceived as more trustworthy than the alternatives. Imagine the average CEO looking at the Windows Server webpage vs the Ubuntu Server webpage. The Ubuntu page looks comical by comparison.

  • Lammy 1 day ago

    I run one (1) Primary Domain Controller and use Enterprise SKU on my Windows 10/11 laptops/desktop because it's the only way to beat Windows into being less-adversarial — telemetry off along with anything else that phones home, Defender off, Domain account versus MS Account vs increasingly-difficult local accounts, etc: https://ibb.co/7tpbk017

    A lot of people's (not you) tiresome kneejerk reaction to this is “then don't use Windows” as if that's something I haven't considered and as if I don't have even more FreeBSD machines than Windows machines :p

    Mine's still running Server 2019 though, and I should probably start thinking about an upgrade path while there still is one for 2019→latest.

  • geraldcombs 1 day ago

    I build and distribute software for Windows, and Windows Server has a better desktop experience than Windows Desktop.

    • speed_spread 1 day ago

      It's been like that since the Windows XP days. Server 2003 had all the enhancements of XP without the UI cruft. When XP64 came out, it was actually 2003 srv with the XP UI bolted on. Dave Cutler always knew what's up.

    • Marsymars 1 day ago

      Windows LTSC is pretty good, fwiw.

  • bigbuppo 1 day ago

    The boss mandated it. That's literally the only reason.

  • TacticalCoder 1 day ago

    > what are the practical use-cases for the folks here who are running Windows Server

    Illegal kickbacks for those who take the decision to stay with the piece of turds that Microsoft produces.

  • bob1029 1 day ago

    System.Drawing

    • Marsymars 1 day ago

      What's the upside over skiasharp?

      (I ask because we've got some products using System.Drawing in production, but at the architecture level the dependencies are abstracted they can run with skiasharp implementations.)

      • bob1029 1 day ago

        I actually have no clue. There are enough competing priorities in the business that we don't have time to get into this level of detail on everything. All I know is that drawing things is a very difficult problem and I don't want to screw with what is known to work.

  • mopsi 1 day ago

    You can run an entire large company off the product that comes in a single box. It has everything built in: hypervisor, user and group management, automated software and settings deployment, file server, print server, clustering, DHCP, DNS, CA, system imaging, virtual desktops, remote applications, and list goes on and on and on. And the people to manage that are widely available. The whole ecosystem is very mature, has books, courses, certifications, everything. It's perhaps the closest thing in the software industry to a good old-school industrial product like some conveyor belt system that you buy, set up according to its manual and your needs, and then rely on it for decades without stressing that the next update will break everything.

    I have a fleet of Windows Server hypervisors, on them a mix of Windows and Linux VMs with various applications (Windows file server for office users and Apache on Debian for browser-based internal services) and virtual desktops for remote users; physical workstations and printers for on-site people, all centrally managed through a single product. Even the office wifi authenticates against a Network Policy Server role running on a Windows Server. When we get new PCs, I plug them into the ethernet and hit F12 on boot, log in to Windows Deployment Services role on a Windows Server, and the PC gets automatically an image installed onto it and then configured for the specified role, down to details like getting Firefox with uBlock Origin installed and preconfigured with reasonable defaults - without any scripting at all, everything configured through an UI.

    There's nothing comparable on the market. Alternatives are on the same level as trying to build a Dropbox out of a bunch of bash scripts or rolling your own encryption. I'd rather not.

  • whynotmaybe 1 day ago

    It's always risky to try to be objective in a Linux vs Windows debate but I'll try.

    1. We have windows servers to run .net framework (not core!) apps that cost millions to build

    2. We have windows experts that don't know jack about linux

    3. We're a government, therefore using public money. Migrating to Linux for the spirit of it doesn't fit in the budget.

    The migration of a small system would cost a lot in qa and legal certification that aren't justified because Windows works.

    • Marsymars 1 day ago

      > 1. We have windows servers to run .net framework (not core!) apps that cost millions to build

      My company has just about finished dragging our millions-to-build .NET Framework apps forward to .NET (what-used-to-be-core). (Though we're still running all of it on Windows Server, but slowly hacking away at those dependencies so we'll at least have the flexibility of having the choice of OS in the future.)

      Eventually, it has to be done, or the apps will have to be abandoned.

  • pjmlp 1 day ago

    Game servers for those Windows games Valve cannot do without Proton.

bigtex 1 day ago

Will xbox related services still be installed but disabled on Windows Servers?

  • hulitu 1 day ago

    Of course. Together with Cortana, Copilot and Clippy. And it brings rounded corners in the server space. The best Windows ever. The most secure Windows ever. /s

liendolucas 1 day ago

GNU/Linux, FreeBSD, OpenBSD, NetBSD are way way much better choices. There are no reasons today to go with a licensed, proprietary and closed source product. Make the switch and don't ever look back.

  • sitzkrieg 1 day ago

    they are not applicable to many workloads.

  • heresie-dabord 1 day ago

    One thing ChromeOS and Fedora Silverblue get right is the built-in immutable OS file system.

    I won't consider any Windows even half-way "hardened" until it has this.

    • speed_spread 1 day ago

      Yup, agreed. It's not even complicated tech, it's like booting from a live CD and then mounting user storage overlay. They could give it a nice UI and be done, preventing a bunch of attacks for cheap.

    • solyin 1 day ago

      macOS as well! It's just the obviously right way to do it. So why hasn't Windows gotten there yet?

stuartd 1 day ago

I’ve always used Windows Server for development machines (since NT 3.5) but this sounds like that may be a bit problematic now? A shame as I am using Windows 11 at work right now and .. ok I don’t hate it. But there is plenty I don’t like.

treebeard901 1 day ago

With so much legacy code for backwards compatibility, I'd bet even Server 2028 still has a long way to go to reduce attack surface.

codeduck 1 day ago

[x] doubt

  • lysace 1 day ago

    But it's so advanced that they used the current year + 2 (2028)? :)

    Spinal tap vibes.

speedgoose 1 day ago

> TLS is limited to modern cipher suites, key exchange is hybrid post-quantum (ML-KEM), and stored keys are strongly protected.

Cool. Any plans to not have the number 4 issue by design?

  • tosser811 1 day ago

    The specific key material that's stored is not the business of the OS, at all.

    • speedgoose 1 day ago

      The OS do silently trust the corresponding public key though.

xyst 1 day ago

It’s wild to me that ms still tries to sell "windows server" as any serious platform. The ms hegemony in corporate it is crazy.