Friday, July 10, 2015

The Skynet is falling The Skynet is falling!

How many times have we heard this? Y2K Armageddon, XP end of life, Criptolocker, and now 2003 end of life. Just because we haven’t had a major crash, does that mean we should just keep drunkenly driving down the pothole filled road?

The Internet is falling!

There were all kinds of wild speculations about what “Could” happen do to the Y2K issue. Everything from toasters not working to nuclear meltdown, and what did happen? Wikipedia tells us the following:

·        In Sheffield, United Kingdom, incorrect Down syndrome test results were sent to 154 pregnant women and two abortions were carried out as a direct result of a Y2K bug. Four babies with               Down syndrome were also born to mothers who had been told they were in the low-risk group.
·        In Ishikawa, Japan, radiation-monitoring equipment failed at midnight; however, officials stated there was no risk to the public.
·        In Onagawa, Japan, an alarm sounded at a nuclear power plant at two minutes after midnight.
·        In Japan, at two minutes past midnight, Osaka Media Port, a telecommunications carrier, found errors in the date management part of the company's network. The problem was fixed by 02:43           and no services were disrupted.
·        In Japan, NTT Mobile Communications Network (NTT DoCoMo), Japan's largest cellular operator, reported on 1 January 2000, that some models of mobile telephones were deleting new         messages received, rather than the older messages, as the memory filled up.
·        In Australia, bus-ticket-validation machines in two states failed to operate.
·        In the United States, 150 slot machines at race tracks in Delaware stopped working.
·        In the United States, the U.S. Naval Observatory, which runs the master clock that keeps the country's official time, gave the date on its website as 1 Jan 19100.
·        In France, the national weather forecasting service, Meteo France, said a Y2K bug made the date on a webpage show a map with Saturday's weather forecast as "01/01/19100". This also occurred on other websites, including, at the time a general-purpose portal site primarily for AT&T Worldnet customers in the United States.

Now whether there were fewer problems due the millions of dollars spent to make the required changes or the problems wouldn’t have been much worse will never be known. We can make an educated guess that adding all of those “00” to countless databases had some positive impact. I’ve never been sorry when I’ve been proactive.

The United States Navy still uses Microsoft’s Windows XP, they were not proactive. The decision to use the obsolete operating system costs the Navy $9 million every year and the total bill could be nearly 30 million dollars. For procrastinating. New figures from migration specialist Camwood show that 11 million machines are still running Windows Server 2003. As I write this there are 4 days until end of life of server 2003. Why are these 11 million machines not updated? Is it the cost of the software? The manpower cost to install and migrate? Apathy?

How many of your clients are still running server 2003? Are you pushing them hard to upgrade? Are you going to purchase extended support at $600 a server? (about the cost of 2012 R2) Are you having them sign documents releasing you from responsibility if they get hacked or infected? Are you adding additional measures to stop potential infections? Making additional backup and business continuity plans?

Just because the sky hasn’t fallen in the past is no excuse not to look up to make sure it isn’t going to hit you this time. 

No comments:

Post a Comment