Sunset Windows Server 2008

Sunset Windows Server 2008

IT admins are starting to wonder what they will do when Microsoft® sunsets Windows® Server 2008. Server 2008 had a pretty long run, debuting in 2008 and entering its sunsetting phase right now. Unfortunately for IT admins though, that long run is coming to a close quickly, and they’ll need to have a plan in place in order to to maintain compliance, security, and access.

Windows® Server Upgrade Apprehension

high costs

Many IT admins that have been using Windows Server 2008 aren’t motivated to upgrade to newer Windows Server models (Server 2012 or Server 2016) because it can result in some pretty substantial upgrade processes and costs. It’s also a lot of work. Plus, some admins may need to purchase and implement entirely new servers, while others are reluctant because they may need to buy new versions of their existing software applications. Plus, continuing to upgrade ties you to Microsoft, so you’ll continually need to pay them. All that said, one thing is certain—all IT admins wish the process were simpler.

Active Directory® and the Domain Controller

server domain controller

While there are a wide number of uses for Windows Server 2008, there is one use case that seems to come up time and time again: Active Directory® (AD) and the domain controller. That’s because Active Directory provides the source of truth that the domain controller checks against to see if a given user is allowed to access a particular network resource. Eliminating Active Directory and the domain controller would leave organizations unable to control access to vital IT resources.

As a result, many IT organizations are loath to change their identity management approach because it is so critical. So, many IT admins are wondering just how long it’s possible to stay on Server 2008. Unfortunately for them Microsoft is ending support for Server 2008 on January 14, 2020. That is not much time. Also, new Server products entering the market in 2019 inflict additional costs that some IT admins aren’t used to. These costs stem from Server 2016’s pricing based on number of CPU cores rather than socketed CPUs. (Read more...)

*** This is a Security Bloggers Network syndicated blog from Blog – JumpCloud authored by Ryan Squires. Read the original post at: