I just have to vent this so I don't actually have an aneurysm.
BACKGROUND: The Client has Major App for Network A (which I'll dub "MANA" for short). MANA basically lets users access Network A through a virtual desktop. They log into a base machine with a 'dummy' account, which takes them to the MANA log-in prompt, where they enter their usual login credentials, and boom, they click an icon that launches their virtual desktop.
MANA is a necessary application at The Client, since there have been recent upgrades to the Network A desktop environment (which I'll dub "Envy"), requiring many users to use MANA to access Envy. However, plenty of users still use MANA to access NetA's regular desktop environment (which I'll dub "ADE" (A Desktop Environment)).
TL;DR Background Summary -- For lots of users at The Client, in order for them to access their files and systems, they must have MANA. [Insert your mana-related jokes here. ]
Today, MANA stopped working for some reason. As a result, we got flooded with calls from users who couldn't get into Envy or ADE. As luck would have it, this happened just after most of the day shift had left for the day, leaving us scrambling to figure out what was going on. The users were basically getting an error that their username or password were wrong, even if they weren't.
When the IT Service Desk figured out we had a major issue here, we quickly created a Global Tier2 Trouble Ticket and sent it up the pipeline to get fixed. The ITSD supervisor also put a message on our automated system, which basically said:
"We are currently tracking a global incident in which users are unable to log into MANA or Envy. If you are experiencing any other issue, please stay on the line."
In short, telling people that we know about the MANA problem, so don't call us to tell us it's not working.
Naturally, we still got slammed with calls saying they couldn't get into MANA. I must have handled about a dozen calls (which, when there's only two or three people still fielding calls, is a lot) from people.
The worst was from the person who, once she got through, said that yes, she'd heard the message, but she really needed to get into Envy so she could send an important email. Given the nature of The Client, I have no doubt it might have been an important email. However, that does not change the fact that MANA was down, and thus, she cannot get into Envy until it's fixed.
We weren't given a timeframe on when MANA would be back up, either, all I could tell people is that we'd take the automated message down once MANA was back up. And yet still I'd get people calling up and going, "Yeah, when I try to log into Envy, it says my username and password are invalild. Is that related to the global ticket on your message?" ARRRRGH.
Eventually, the calls petered out, as the lusers realized that MANA wasn't coming back up soon, and wandered off to go home, and I was relieved when I finally got a call that wasn't MANA-related.
About half an hour after the calls petered off, they rebooted a server that got MANA back up and running, and people could log back into Envy again.
BACKGROUND: The Client has Major App for Network A (which I'll dub "MANA" for short). MANA basically lets users access Network A through a virtual desktop. They log into a base machine with a 'dummy' account, which takes them to the MANA log-in prompt, where they enter their usual login credentials, and boom, they click an icon that launches their virtual desktop.
MANA is a necessary application at The Client, since there have been recent upgrades to the Network A desktop environment (which I'll dub "Envy"), requiring many users to use MANA to access Envy. However, plenty of users still use MANA to access NetA's regular desktop environment (which I'll dub "ADE" (A Desktop Environment)).
TL;DR Background Summary -- For lots of users at The Client, in order for them to access their files and systems, they must have MANA. [Insert your mana-related jokes here. ]
Today, MANA stopped working for some reason. As a result, we got flooded with calls from users who couldn't get into Envy or ADE. As luck would have it, this happened just after most of the day shift had left for the day, leaving us scrambling to figure out what was going on. The users were basically getting an error that their username or password were wrong, even if they weren't.
When the IT Service Desk figured out we had a major issue here, we quickly created a Global Tier2 Trouble Ticket and sent it up the pipeline to get fixed. The ITSD supervisor also put a message on our automated system, which basically said:
"We are currently tracking a global incident in which users are unable to log into MANA or Envy. If you are experiencing any other issue, please stay on the line."
In short, telling people that we know about the MANA problem, so don't call us to tell us it's not working.
Naturally, we still got slammed with calls saying they couldn't get into MANA. I must have handled about a dozen calls (which, when there's only two or three people still fielding calls, is a lot) from people.
The worst was from the person who, once she got through, said that yes, she'd heard the message, but she really needed to get into Envy so she could send an important email. Given the nature of The Client, I have no doubt it might have been an important email. However, that does not change the fact that MANA was down, and thus, she cannot get into Envy until it's fixed.
We weren't given a timeframe on when MANA would be back up, either, all I could tell people is that we'd take the automated message down once MANA was back up. And yet still I'd get people calling up and going, "Yeah, when I try to log into Envy, it says my username and password are invalild. Is that related to the global ticket on your message?" ARRRRGH.
Eventually, the calls petered out, as the lusers realized that MANA wasn't coming back up soon, and wandered off to go home, and I was relieved when I finally got a call that wasn't MANA-related.
About half an hour after the calls petered off, they rebooted a server that got MANA back up and running, and people could log back into Envy again.
Comment