System Administration

Oops? Did you say "Oops"? What do you mean, saying "Oops" there?

Suppose you are foolish enough to allow Microsoft Windows Update to install the updated drivers for a network interface card. Suppose again that you have two NICs, both by the same vendor, and suppose that though the cards are different model numbers (3C509C-TX, 3C509B-TX), they use the same driver.

It's good that you have two cards, because the driver update killed one of them.

Update: Fixed by installing the current driver from Dell. It also works to install the current 3Com driver: they're the same.

Why didn't the Windows Update installation take? Case sensitivity? One NIC was looking for el90Xbc5.SYS while the other expected el90xbc5.sys. Or is Windows Update simply unable to handle the case of multiple NICs with identical drivers? It would be helpful if we could roll back these changes, especially given the introduction of Automatic Updates.

Somewhat more disturbing now is that the driver properties show that the file is newer than it actually is. I have to get this box out on the floor, otherwise I'd investigate further, but to me this indicates that the Registry data is inconsistent, and doesn't accurately reflect the current state of the system. This is a significant failure.

Trust Microsoft? You must be kidding.

11:41:53 AM # Google It!
categories: System Administration

Important Reminder

System Administrator Appreciation Day, July 26, 2002.

While I won't be in the office for you to bring chocolate and coffee, my Amazon wish list is over there, on the right. ;-)

10:08:52 AM # Google It!
categories: System Administration