The problem with publishing a browser in Citrix is that it becomes very difficult to control what the hell these tards that call themselves users are actually doing.
Case in point, we have a slew of applications on our intranet that are accessed via a central login provided by websphere. Hence to access any one of them, a user needs to log in to the main page first. So it's just about impossible to limit what these wankers can get to since they all have the same launch page to get there.
So as one might imagine we're having performance problems with a web app. Surprise! Of course as we all know, some crap application going bulimic on system resources is always a Citrix issue. Oh right, because the chance of some half-cocked web application having problems is far and remote! Never mind that it was written by some 2 dollar outsourced developer who could likely not even spell "Terminal Services" much less write anything to run on it.
Like any other homicidally frustrated system admin, we went back to the original business group who absolutely had to have the application published or the company would never make another dime and we calmly said to them, "Hey, your shit is broken."
Then we said it again.
...and again.
...and again.
(you get the idea)
Finally, I consider taking a hostage when I receive an email from one of these business whelks saying that they have no reason to believe that the application is causing performance issues.
AGGGH!! WHAT??
How about the edgesight reports (great product, btw), screenshots, perfmons, and RM reports we sent you? How about the 15 years of experience I bring to the table that might lead me to believe that perhaps I would be able to spot a problem application when it repeatedly projectile vomits all over my damn servers? How about because I friggin say so?
Sometimes it's not even worth bringing the KY.
-CG
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment