Troubleshooting Service Pack 3
Windows .Net Magazine editors also have been getting a lot of
feedback on SP3, and what problems have cropped up. They have a
good article here with most of the problems they ran into and some
solutions. If you are planning to deploy it, you should check this
More Travel Experience With Non-Secure W2K Systems
Dan Hensley just sent me this, and I have had the same experience
myself on two occasions during my recent travels. Here is his story:
"I was in a motel recently and they had 2 computers (W2K) set up for
people to use for checking their email. They were logged in as
administrator and just sitting there. They were set to store cookies
and passwords. Everyone that used them left a trail of passwords,
cookies and files. Admin gave anyone the rights to do anything they
wanted with these systems. They were completely open to the world.
I went to a lot of sites using the last user's login to his email
So, tell your users that if they check their email to make sure and
get rid of residual user names and passwords that are stored in the
Web browser. You certainly want to do this if you ever use a public
computer (such as those in libraries, airports and hotels). Here's
how you do it in WinXP:
- Open Internet Explorer and click on the Tools menu.
- Click on the Internet Options command.
- Click on the Content tab. On the Content tab, click on the
AutoComplete button in the Personal Information frame.
- In the AutoComplete Settings dialog box, click on the Clear
Passwords button. Click OK to clear all passwords. Click on
the Clear Forms button and then click OK to clear all forms.
- Now all that personal information should be removed from Web
pages viewed in Internet Explorer. Make sure you restart the
computer just to be sure the changes "take".
W2K SP3 in Healthcare: Damned If You Do, Damned If You Don't?
An interesting discussion has been building in the healthcare arena
since Microsoft changed its EULA for W2K SP3. Since, under HIPAA
regulations, a healthcare organization is required to safeguard
patient data to the best of current technological capabilities, the
application of SP3 appears to present a no-win situation. If you
don't apply the service pack, you're leaving the OS open to known
If you do apply it, you're agreeing to allow Microsoft access to
the server for, ostensibly, "updating the server." Even though I'm
sure Microsoft claims to only access the necessary system files,
we are all aware of their less-than-stellar record. The fear is
that if MS were to inadvertently access patient data on one of the
patched servers, the healthcare organization could be held liable.
I wonder what the MS lawyers are able to reply on this issue...
What Certification Next? You'll Be Surprised.
"The effects of the Enron scandal and financial irregularities at
other companies may also have an impact in IT. The surveyor said
he's just beginning to see an upward trend in demand for IT
professionals with experience in financial controls and internal
audit functions, although it didn't have much impact on his firm's
midyear survey." Here is an article over at techrepublic but you
need to register to read it. At least it is a direction you can
think about in the sense of your next certification.