“It is not the strongest species that survive, nor the most intelligent, but the ones most responsive to change” – Charles Darwin.
In today’s business world, where organizations face ever-escalating customer demands and expectations and little room for downtime, logic dictates that businesses today are seriously revamping their business continuity and risk management plans, or developing one if they did not have any.
This is even more pertinent given what we have witnessed in recent months in the areas of data breaches, hack attempts and the underground “war” being waged in cyberspace that has put most of the world’s powerful organizations on the defensive.
Occasionally, one runs across some application problems that “just happens for no reason”. Such was the experience with the “No printer installed” error you may get in QuickBooks.
Recently, I have been having all kinds of problems with Windows update, especially after the release of Windows 7 SP1. One of the frustrating things about Windows errors is the silly “Get help with this error” message that tells you absolutely nothing about how to fix the errors. Rants aside, here’s how to fix one of those cryptic errors, specifically error code 8007000D also represented by its hex variant 0x8007000D.
Apple has thrown its hat into the cloud “gold rush” ring and all of a sudden, we have started hearing the old but boring cries of the death of Windows. A lot of noise is being made about Steve Jobs’ statement that “We’re going to demote the PC and the Mac to just be a device – just like an iPad, an iPhone or an iPod Touch. We’re going to move the hub of your digital life to the cloud”
The tough economy is taking its toll on small businesses and organizations and many are still using old hardware and operating systems simply because they cannot keep up with the high cost of licensing, or the perpetual upgrade fees.
As more companies with national security interests come forward with admission of breaches related to the hacking of RSA’s SecurID technology, one wonders if it is time for RSA to break its stubborn refusal to tell the public what exactly was stolen or when the breach actually occurred. At this stage, it is not just enough to tell the public that it had been hit by a phishing email exploiting a zero-day vulnerability in Adobe Reader.