{"id":58182,"date":"2022-01-14T11:00:00","date_gmt":"2022-01-14T16:00:00","guid":{"rendered":"https:\/\/jumpcloud.com\/?p=58182"},"modified":"2022-12-12T14:41:15","modified_gmt":"2022-12-12T19:41:15","slug":"ditch-your-domain-controllers","status":"publish","type":"post","link":"https:\/\/jumpcloud.com\/blog\/ditch-your-domain-controllers","title":{"rendered":"Why I Ditched Domain Controllers"},"content":{"rendered":"\n

Running a small to medium-sized enterprise (SME) with my brother taught me that every dollar counts toward the bottom line. That mindset carried forward when I began to do IT consulting work, because every dollar counts to a business owner. One engagement put that ethos to the test and changed how I think about managing IT. My experience shaped the recommendations I\u2019d initially offered, which were appropriate for the client but anchored by a formulaic approach that revolved around the perception that domain controllers are still \u201cindispensable.\u201d The status quo wasn\u2019t in her best interests and so my final guidance was: <\/p>\n\n\n\n

Don\u2019t buy a new server \u2026 you\u2019ll save a lot of money, and you\u2019ll get more out of JumpCloud.<\/p>\n\n\n\n

Arriving at that decision was a teachable moment, but let\u2019s backtrack to how I arrived at the conclusion to ditch the server, which may be a choice that you\u2019re wrestling with. <\/p>\n\n\n\n

When Something Breaks, Opportunities to Grow Arise<\/h2>\n\n\n\n

The job began with my client\u2019s urgent need to replace an outdated domain controller that was running Windows Server 2008, along with a list of aspirations that would modernize IT at her family business that we\u2019d address afterward. That edition of Windows Server couldn\u2019t even run Windows Update anymore, and was an acute security threat. Her brother, who is not a security analyst, was so bothered by the sound of the running machine (alongside cobwebs beneath the stairs) that he switched it off every night. While that wasn\u2019t a terrible<\/em> idea, I considered the server to be compromised at the onset. Therefore, the first priority was to replace and decommission the server as quickly as possible.<\/p>\n\n\n\n

We initially spoke over the phone and developed a solid plan to address her needs, which also saved her family business thousands of dollars over a competitor\u2019s quote by selecting refurbished hardware. Overall, the strategy would improve security, flexibility, and prioritization<\/a> of future projects. We planned to use a better EDR; implement configuration, SSO, MFA, and RADIUS server to secure company Wi-Fi; improve onboarding\/offboarding; and conduct security awareness training. The next step was to visit the office to assess what was really going on in the spider preserve (server room).<\/p>\n\n\n\n

A Do-Nothing Domain Controller<\/h2>\n\n\n\n

My assumption was that the domain controller was doing something<\/em>, <\/em>but it really wasn\u2019t performing any kind of role that would justify spending anything<\/em> on new hardware. Plus, obtaining buy-in for IT spending can be an uphill battle at a family-run SME \u2014 not wasting money on unnecessary stuff and working with senior family members who were raised to make do with what they already have.<\/p>\n\n\n\n

Here\u2019s the gist of what I learned while poking around on-site:<\/p>\n\n\n\n