Windows Server 2008 is reaching its end of life in January 2020. Are you asking yourself what it takes to change over?
Sagiss CTO Jim Lancaster discusses Windows Server 2008 end-of-life and the key steps involved in the migration process. And if you’re still on the fence about moving to the cloud, Jim weighs in with his expert opinion.
The First Step: Assessment
It starts with the applications that you're running and figuring out what the vendor’s recommendations are for them. For example let's say you've got a document management system or if you’re a medical firm and you've got EMR or something like that--are you going to the hosted version of that software? Is the server that you have now going away or if you've got on-premise version of the software, what are their requirements? When we're looking at a 2008 upgrade our first step is to figure out what is it that you're running and what does the software requires. Once we’ve sorted through all that, we determine where these applications and services are going to end up. Then we look at what's left and decide whether an on-premise server is really indicated or whether to move you up into Azure.
The Second Step: Migration
Jim Lancaster: The vast majority of everything that we're doing now is going to Azure. There are legitimate reasons for having an on-premise server. Maybe the location that the client is in has low bandwidth so it’s just impossible to get good reliable Internet service, so that may be what's driving it. But for the vast majority of people, it's time to look at Azure. That’s where most upgrades will go.
The Third Step: Optimize
Jim Lancaster: Things work differently in Azure than they did they do with the old 2008. So it does require careful planning and requires somebody who knows that it’s just a really complex animal. But monitoring and managing the server once it's up and running is very similar to what we've always been doing. We have to monitor memory disk space, memory utilization, CPU utilization and that sort of thing. But in addition to that, we have to monitor cost because the Azure cost model is that you pay a little bit for everything. So, you pay a little bit for disk rights, for disk reads, for CPU, for the amount of CPU used, and for how much network traffic you send back and forth. Monitoring all of that and making sure that you don't have a runaway process that will generate a very big surprise bill at the end of the month--that requires some expertise as well.
Are you still on the fence?
Jim Lancaster: While I understand the reluctance or the reticence to move to the cloud, I think the benefits now far outweigh the negatives. The things that you can do with your servers in the cloud and with your applications in the cloud--there's so much more that you can do now. We were never able to do easily before. Principally that has to do with remote access and being able to provide our customers with access to the data no matter where they are. If they have multiple locations sharing data in a central location for all, etc. It used to be that we had to manage these locations independently and it was pretty complicated to keep everything synchronized. Those problems have gone away. Now it's more about just getting connected to the Internet and after that, you're finding your way to your infrastructure and managing and running everything there. So, it's just different I understand the reluctance. It requires a different way of thinking and it requires change. But I think it offers a lot more of everything more than what we've been able to do in the past and it's the way things are going whether we want it to go that way or not, that's the way the world is going. Even if you’re on the fence, I think it's time to at least look at the cloud.
This is part two, click here for part one