Pr3++yG33kyTh1ng

So anyway, the rest of the team and I decided to set the new guy on rebuilding a server for (company name deleted to comply with the non-disclosure agreement). Having tried this myself, I got to run down the history of the trauma involved in this piece of hardware:

First, it was built and turned over to the client.
Then, a drive controller failed.
IBM replaced the controller with a newer, cooler controller.
When attempting to rebuild the server after this, Windows no longer has the driver for the new controller. It therefore cannot see the drives.
The fix is to manually install the drivers prior to the Windows installation, right? No problem.
Using the (company name deleted to comply with the non-disclosure agreement) supplied Server 2003 media, I blank the supplied password during the install and complete the build.
Upon reboot, the password as I know it doesn't work. Crap. Locked out of a brand new server.
So I rebuilt it, being extra careful with the password field this time.
Still no luck logging in.
I employed the Emergency Repair Disk option and load to that OS to change the password. A good plan, except that the Emergency Repair Disk can't see the drives because of the new controller.

Good times. And I wasn't allowed to do any of it.
The awesomeness happened when I went to escort him back to the server. My boss told me that the IT director for (company name deleted to comply with the non-disclosure agreement) was ON-SITE today and working in the cage next to the busted server.
He could not see me near his stuff.
Ninja time.
I told my boss I'd just leave my ID badge at my desk. The guy has never seen me, so there should be no problem. I can just knock when I get back up here.
He told me they might not let me back in.
"That is a risk I'm willing to take, Steve."
In the end, I borrowed the access badge of a co-worker and wore it picture down. So now the deception is personal. And I'm wearing jeans.