Title: TechTarget
>>About this email: >>Click here to receive this email as text in the future 
 May 29, 2002a newsletter from TechTarget 
Windows 2000 in the Enterprise: Technology strategies in action
Oops! True IT blooper #35: What About Bob?

by David Pye

We all know that it doesn't get any better than spending the majority of your time checking server event logs. Although it ranks right up there with skydiving and parasailing in terms of excitement, it isn't always a walk in the park.

S P O N S O R E D  B Y : NetIQ
FREE Security Webcast from Microsoft and NetIQ

Are hackers threatening your Windows network? Get the hand-to-hand tactics you need to combat hacker exploits. Don't miss the free one-hour Webcast, "Defending the Enterprise: Hacker Methods and Countermeasures." You'll also receive "Defense in Depth," a free white paper detailing the evolution of network security via e-mail after the event.

Register now!


Accidentally overwriting all of the administrator accounts in your domain might not be quite as career-ending as say, a chute that isn't packed properly, but it's still reason for concern and needs a speedy fix. It's also cause for anonymity, so the user in question will be called Steve in this story. When the smoke from this episode's blooper finally cleared, Steve ended up with a red face and a newfound respect for Windows 2000 Group Policy Objects.

A competent and experienced IT contractor, Steve had been at his job only a short time when multiple server log errors began to rear their ugly heads. "Active Directory had just been implemented in the production environment," he said. "We were getting two particular errors on the domain controllers every other minute. They were not causing any issues, just filling up the logs."

Steve researched his problem and found an article that stated, "The errors could be caused by the defined administrators account in the default domain controller's policy." He decided that the best course of action would be to follow said article's advice and change the administrators account section of the GPO to a name that was not currently in use by Active Directory.

Maybe Steve was feeling a bit playful, or perhaps he just felt a special someone around the office needed a little ego boost. Whatever the motivation, as he went about his duties Steve decided to kill two birds with one stone: "Bob was my supervisor at the time, so I picked the name `Bobrules' for the fix." What a guy.

Steve had "all the documentation in hand" and the approval of an on-site consultant, so he went ahead and made the changes. Who wouldn't? Everything seemed to be running smoothly, and he went home that evening feeling relieved. His troubleshooting skills had been successfully tested once again.

Upon his return to work the next day, Steve was dismayed to see that the errors were still occurring. To top it off, as his coworkers began arriving he found that a nasty rumor had been circulating around the office. The guy sitting next to him "asked if I heard about the possibility of a hacker gaining access to our network." Deeply concerned by this new information, Steve asked his friend for more information.

What Steve was told next made his heart sink. "As he started explaining the issue, `Bobrules' came crashing into the conversation." Steve quickly set about finding out exactly what was happening in the server room.

What had Steve done wrong? "I had placed the `Bobrules' on the root of the domain, not domain controllers," he said. "After I had left and replication had taken place, `Bobrules' had replaced of all the administrator accounts in the domain." What began as a harmless joke had become a mystery that the whole office was trying to solve. "We didn't have a formal change control at the time -- Active Directory was new -- and so no one thought to check domain policies," Steve said.

You may wonder what the namesake of this misguided fix was doing during all of this. Well, Steve's attempted `pick-me-up' had backfired horribly. Bob had stayed late into the previous evening trying to deal with the strange phenomenon. "No matter what he did," said Steve, "the names would always revert back to `Bobrules.' Bob thought the hacker had a personal vendetta against him and spent many hours trying to correct it."

Bob vowed to show the `hacker' who was the true king of his domain. He figured out what had happened, changed everything back to the original configuration and the day was saved.

Although relieved, Steve was not very optimistic about his future with the company. "As a contractor, I had all my bags packed in anticipation of my supervisor's arrival," he said. "Luckily for me, he looked over the documentation, found it a valid mistake and laughed it off."

All's well that ends well, but what did Steve learn from this fiasco? Don't name your fixes after other employees, no matter how good your intentions are? Make sure your supervisor has a good sense of humor? Not quite. As Steve puts it: " Moral of the story: Watch out for those GPOs!"

Perhaps now Steve will get back to those event logs and leave the comedy to Don Rickles.



MORE ON THIS TOPIC:
>> Here is a full listing of all our true IT bloopers

>> Share your true IT blooper today to win: Submit blooper!

A B O U T     T H I S     E - M A I L:
This e-mail is brought to you by TechTarget where you can get relevant search results from over 20 industry-specific Web sites.

If you no longer wish to receive this newsletter simply reply to this message with "REMOVE" in the subject line. Please allow 24 hours for your "REMOVE" request to be processed.

Copyright 2002 TechTarget, Inc. All rights reserved.


Reply via email to