This particular specimen is a cursed administrator who calls a company for enterprise level support.
He/She is most likely cursed with pagan spells of some sort. For whatever reason, everything that can go wrong always does whenever they call for help.
The last time I encountered this user in the wild, it was a problem with the Exchange Server. The environment was completely virtual. VMWare running Exchange, Domain Controllers, SQL servers, and somehow... most of the workstations. I never really figured out how that happened.
Anyway, he calls up and does not speak very good English, so a Webex session is necessary. Due to the language barrier, an email must be sent with the link to the Webex session so that he can connect the most efficient way. This is where things start to break down.
The customer is logged into the machine I want to administer, but because I sent him an email, he RDPs to his own workstation to click the link. When the desktop is finally shared, we are looking at his desktop, so I say... "Could we connect to the system that is experiencing the problem" MISTAKE!!! The customer then RDPs back to the system he is physically logged into.
As many of you know, this opens up a wormhole in the time space continuum, and causes an "echo" effect, opening remote session after remote session after remote session, until eventually the server (Production) crashes.
To avoid this, of course... the user "bounces" the server, KILLING THE ENTIRE WEBEX...
So we wait, in silence, while the server comes back up. We have been on the call now an hour, and have nothing to say to one another; mute is your friend at this point, as you are questioning your entire IT future.
The server comes back online, and you specifically ask him to open up Outlook Web Access from the server in question, but this turns sour very quickly. Finally you are repeating the web address 15 times, before giving the session number 18 times, and you are IN!!!
Now for the problem... which has mysteriously disappeared after a reboot.
ARRRRRRRRRGH!!!
He will be in hell, I know it. He will be there with his virtual production environment, and a red phone that dials my number every 15 minutes.
Slashdot Mirror
Anyway, he calls up and does not speak very good English, so a Webex session is necessary. Due to the language barrier, an email must be sent with the link to the Webex session so that he can connect the most efficient way. This is where things start to break down.
The customer is logged into the machine I want to administer, but because I sent him an email, he RDPs to his own workstation to click the link. When the desktop is finally shared, we are looking at his desktop, so I say... "Could we connect to the system that is experiencing the problem" MISTAKE!!! The customer then RDPs back to the system he is physically logged into.
As many of you know, this opens up a wormhole in the time space continuum, and causes an "echo" effect, opening remote session after remote session after remote session, until eventually the server (Production) crashes.
To avoid this, of course... the user "bounces" the server, KILLING THE ENTIRE WEBEX...
So we wait, in silence, while the server comes back up. We have been on the call now an hour, and have nothing to say to one another; mute is your friend at this point, as you are questioning your entire IT future.
The server comes back online, and you specifically ask him to open up Outlook Web Access from the server in question, but this turns sour very quickly. Finally you are repeating the web address 15 times, before giving the session number 18 times, and you are IN!!!
Now for the problem... which has mysteriously disappeared after a reboot.
ARRRRRRRRRGH!!!
He will be in hell, I know it. He will be there with his virtual production environment, and a red phone that dials my number every 15 minutes.