Leveraging Open Source to Solve the Windows 2000 End-of-Life Dilemma

Many companies are facing the challenge of how to transition from Windows 2000.  While the default reaction to this challenge is to move to a newer Windows release this approach can lead to other concerns:

  • Am I licensed for the new OS (especially when using the OEM supplied license)?
  • Do your applications and peripherals work with the newer Windows OS versions?

Despite these challenges, in most scenarios, with proper planning, the transition can be managed effectively.  However, in some cases IT departments should take the time to evaluate the progress that Open Source platforms have made in being a viable alternative.

If you are still using Windows 2000 it is likely that these systems are being used in a limited capacity.  When the systems needing to be replaced are ‘task oriented’ terminals and a thin client is a good alternative but the cost of replacing hardware may be prohibitive, there are a variety of Linux Distributions and Open Source applications that can prove to be a valuable alternative.  Take, for example, a scenario where a Windows 2000 system is used for a limited set of applications with specific hardware and peripheral requirements.  Even better, let’s assume the Windows 2000 system is being used as an RDP terminal.  A Linux desktop may be the perfect solution waiting to be discovered.

With the recent Linux distributions it’s easier than ever to develop a custom Linux image that can meet the challenge.  Take, for example, Puppy Linux 4.3.  This small yet powerful distribPuppyLogoution is packed full of hardware device support, tons of the most typical applications, a streamlined installation experience, and flexible deployment options.  All with a 110 MB footprint! 

Check out the goals of the Puppy Linux distribution here:


As with any IT project, don’t assume or accept marketing slicks in place of due diligence.  Do your homework, test and validate potential solutions, and plan for the full life cycle management of an approach.  If done properly your organization will be successful whether the answer is Windows  7, Puppy Linux, or something off the ‘beaten path’ altogether.  With the technology advancements of today’s operating systems, taking the time to re-evaluate the options may surprise you!

Source: Coretek Services –  Sr. Systems Architect

2017-07-27T00:01:12+00:00 October 1st, 2009|Uncategorized|

About the Author:

Clint is cool as a cucumber, but has been aged in habanero brine.

Fatal error: Uncaught exception 'GuzzleHttp\Exception\ClientException' with message 'Client error: `POST https://dc.services.visualstudio.com/v2/track` resulted in a `400 Invalid instrumentation key` response: {"itemsReceived":1,"itemsAccepted":0,"errors":[{"index":0,"statusCode":400,"message":"Invalid instrumentation key"}]} ' in /home/coretek/public_html/wp-content/plugins/application-insights/vendor/guzzlehttp/guzzle/src/Exception/RequestException.php:113 Stack trace: #0 /home/coretek/public_html/wp-content/plugins/application-insights/vendor/guzzlehttp/guzzle/src/Middleware.php(66): GuzzleHttp\Exception\RequestException::create(Object(GuzzleHttp\Psr7\Request), Object(GuzzleHttp\Psr7\Response)) #1 /home/coretek/public_html/wp-content/plugins/application-insights/vendor/guzzlehttp/promises/src/Promise.php(203): GuzzleHttp\Middleware::GuzzleHttp\{closure}(Object(GuzzleHttp\Psr7\Response)) #2 /home/coretek/public_html/wp-content/plugins/application-insights/vendor/guzzlehttp/promises/src/Promise.php(156): GuzzleHttp\Promi in /home/coretek/public_html/wp-content/plugins/application-insights/vendor/guzzlehttp/guzzle/src/Exception/RequestException.php on line 113