However, with newer versions of Microsoft
Windows, all you need is one unstable software application, utility
program or buggy piece of hardware to literally crash your Microsoft
Windows PC configuration into oblivion. That’s why the system
protection and recovery enhancements in Microsoft Windows 2000
Professional and Microsoft Windows XP, which we discussed earlier in
the chapter, are so crucial.
So, when dealing with hardware or software that
is new to your company, you must rigorously test the product before
installing it onto someone’s PC.
The Hazards of Appeasing the Boss
For example, your CEO may be extremely eager
for you to install a new contact management program that just came
out.
But how would your CEO feel if, while you were
installing the program, the notebook locked up, wouldn’t reboot
and took three days and a $500 computer consultant emergency service
call to get the notebook back to its former working condition?
Note:
That scenario could be the same for any unknown peripheral
device such as a handheld PC cradle, digital camera or
scanner.
Cost-Effective System Testing Options
One better option – you can run through the
installation on a similarly equipped PC of someone who wouldn’t
mind if his or her PC got trashed. Perhaps that person is you,
depending on the nature of your job. Relative Cost Indicator:
$
The best choice is to maintain a spare or test
system. This PC should be relatively similar, in terms of hardware,
software and operating system configuration, to your standard PC.
That way, if the new product breaks something, it’s not disabling
someone such as your CEO! Relative Cost Indicator:
$$-$$$
If you’re testing a network application,
it’s even better if you have a second test or spare system. This
way one PC can simulate the workstation and the other can simulate
the server. Relative Cost Indicator: $$$
If you don’t have the resources for these
spare or test systems in-house, a local computer consultant usually
can provide testing services on an outsourced basis. Relative
Cost Indicator: $$-$$$
At any rate, always assume that a
program or device could be big trouble until you see it
working properly on a similarly equipped system.
Tip:
Some internal gurus and IT professionals use their home PCs
for testing new software and hardware. Just be sure the
configuration is at least relatively similar to the
standard configuration in your office. Relative Cost
Indicator: $
System Testing Action Items
Do you test new third-party software and
hardware products before installing them on various desktop PCs and
notebooks in your company?
How do you do this testing to avoid
breaking Microsoft Windows PC configurations?
Have you ever rushed to install a new
software or hardware product, only to find that haste caused major
PC support headaches?
Do any of your PCs run Microsoft Windows
2000 Professional or Microsoft Windows XP, which help protect you
from inadvertently trashing your PC configuration during
installation of new software -- and assist in the recovery efforts?
Do you have a spare PC that you can use for
testing purposes, or do you use your own PC or your home PC for this
purpose?
If you frequently install new network-aware
hardware and software products, do you have a second spare PC that
you can use to simulate a server in a controlled, non-mission
critical environment?
|
