I know, it’s 20 years old where on earth am I going to encounter Windows 3.1? That’s what i thought too, then we encountered the mother of all laser cutting machines (and not that old) being run on Windows 3.1. Once the prerequisite nostalgia had passed we were left with a rather large issue.
When faced with the prospect of retiring Windows XP from a network, the task can become quite a headache both financially and technically. The two most common choices are either replacement of existing hardware or migration to a Virtual Desktop Infrastructure (VDI). Each has it’s merits and drawbacks and I’ll set them out briefly below. Bearing in mind that this is a big project and every business case will be different it would be wise to enlist the help of a company or consultant that can guide the process.
So you’ve finally made the decision that you can’t in fact wait or bury your head in the sand and hope the Windows XP retirement doesn’t affect you?
It’s all well and good if you’ve only a couple of PC’s / Laptops but what about if you’ve a tight budget or 20+ PC’s all with OEM office? Suddenly the replacement costs are running to 4 or 5 figure sums and the Finance people are starting to cry.
Tomorrow at 11am GMT Windows 8.1 optional update to Windows XP will roll out. While it’s got a load of new usability promised and is rumored to be more service rich (not the good kind the kind that crashes things unfortunately!) the main positive is the return of the ‘start’ bar.
There are a lot of users who when they hear this first ask what do I care? I’ve never rang Microsoft for support before why would I need to all of a sudden. But this isn’t the issue, support comes in many forms and for an operating system that’s been around since October 2001 the majority of the support is in the form of patches, be they for additional functionality or security.