Are you ready for the end of product lifecycle support for Microsoft Windows Server ? Subscribe to this author's posts feed via RSS. Videos You May Like. Agile Methodology in Project Management 0 0 In this video, you will gain an understanding of Agile and Scrum Master Certification terminologies and concepts to help you make better decisions in your Project Management capabilities.
Share your thoughts Cancel reply Please fill out the comment form below to post a reply. Download the Windows Server R2 trial. Download the System Center R2 trial. Get the Microsoft Azure one-month trial. Start your free Office trial. Download the SQL Server trial. Build your migration plan — do it yourself, collaborate with a partner, or use a service. Download the Microsoft Deployment Toolkit. As you consider upgrading your Windows Server environment, don't forget about the apps.
Consider updating your overall platform to get the best database capabilities. Explore your migration options:. Get breakthrough performance from SQL Server See all. Share this page. Follow us. By using this site you agree to the use of cookies for analytics, personalised content and ads. Learn More.
Support for Windows Server is ending. Search Microsoft. Search the Web. Microsoft won't completely ignore WS; it will still offer extended support for a hefty fee, much more than your current service contracts. With dozens or hundreds of servers in a company, that can run up into the six figures, at which point it would be cheaper to buy new servers with Server R2 on it.
For that reason, Microsoft is actively encouraging migration and offering tools to help with the task. The risk is not limited to the OS itself.
With so much infrastructure built on Windows Server, databases, middleware, applications and other sensitive information can all be compromised by a single unpatched vulnerability.
Windows Server doesn't have the compartmentalization of the later versions, so once an intruder gains access to the OS, they will pretty much have free reign to move around the system unrestricted. Hardware ills: If you are running Windows Server , chances are very good that hardware is a decade old or older, which means it is long out of support from the vendor and also well past its recommended operational life. You run the risk of high failure rate, which could mean lost data, and good luck getting replacement parts.
Operational costs : If you are running an eight to 12 year old server, then it's an old bit server with barely any power management at all. Server vendors didn't get the power management religion until a few years later. Those old servers are inefficient and likely unvirtualized, and running at very low utilization. So in addition to being vulnerable they are also highly undesirable. People in fields impacted by this regulation will likely shut you out and refuse interconnections.
Software compatibility issues: As mentioned previously, Windows Server is a bit OS, and virtually everything is bit now, from device drivers to apps. Companies are abandoning bit apps for bit apps. So don't expect to update your old apps. Data breaches: All one needs to do is look at what the Home Depot and Target breaches did to those companies.
That should be motivation enough to migrate. But those firms were big enough to recover. A smaller company might not be. Microsoft is ending support for Windows Server, but the apps running on the server are just as much at risk.
Maurice McMullin, product marketing manager with KEMP Technologies, which does WS migrations, said there are two major risks to apps: it may not be maintained by the developer and a company may or not have the resource in house to maintain it. If the app falls over, who's there to support it? The implications are if they don't migrate, they are exposed on the app side and may not have the resources to fix it. The other thing is from external risks that may be discovered after support ends," he said.
Many companies not making the migration cite cost as the reason; either they can't afford it or they haven't got the budget this year but will later in the year or next year.
If you are in such a scenario, you should still begin preparing for the eventual move and not wait until you have the money to begin planning. That way you have a plan ready for execution when the funds are there. Bit9 recommends several steps in the process:. Don't do it alone: A smooth transition to a new platform will require full buy-in and agreement from any and all impacted stakeholders.
That means not just the IT department, but the business units impacted and the budgeting finance team. Dedicate time for project scoping: The average migration project will take over days to implement, from assessment, to migration, to debugging. You're not just copying files, there is much more to the migration. So find the potential pitfalls early on and not get tripped up during the migration.
Work within your budget: If you are not making the move for financial reasons, then you likely already have a good idea of your finances. You will need a clear picture of potential project risks, costs and buy-in for the necessary human resource requirements.
0コメント