
Excellent..
BOFH logo telephone with devil's horns “I don’t know what to say,” the Boss says, looking confused. “It’s OK, there’s nothing to say,” I reply. “It happens every year – you’ve just not been here long enough to know.” The Boss has a dilemma. A pair of our main virtual hosts has some interoperation hardware issue which is …
The BOFH, the PFY and the Boss working together. This can only end in tragedy. I wonder who for?
Yes, it's a shame that all desktops have cameras now, and that the ironic accident just happened to be in sight of at least 3 separate ones.
Why else do you think they want those USB sticks?
:)
There was me expecting them both to go out of the window.
Getting money to replace server kit is like pulling teeth sometimes.
It is much easier to keep rebooting that old Exchange box you want to replace to cause downtime. Of course you would move the MDs mailbox on to that server before you starting your campaign of random reboots. The project gets of the ground quite fast after the MD can't access his mailbox of few times.
Of course I have never done this and you can't prove I did. ;)
".....old Exchange box....." One trick that seemed to be in vogue a few years back was to give a "monitoring function" to a server. In essence, many monitoring tools allowed you to dump reports out as HTML, so it was easy to write a C program to get the unformatted HTML file from the real monitoring server, format the HTML into a webpage file, and then have this read from your internal webserver. Getting reports and monitoring data online was all the rage. Then, simply give any server under review the formatting program for a vital service, such as Exchange. When the beancounters started asking if you really needed server X (which just happened to be your Counterstrike server and illicit MPEG storage), you could say; "Well, it runs our Exchange monitoring function, and email is a critical business service, and I'm not sure we want to run the risk of losing visibility of a critical business service....."
Of course, an added benefit was if you were ever seriously pushed to make cuts in your server estate (and after the obligatory stonewalling and emphasis on how hard a task that would be, as in requiring overtime), you could simply collapse a few "monitoring function servers" into one and claim "significant server estate reduction".
lmao, this used to be one of my many tricks when we needed new ESXi upgrades... be careful if you do this, consider a carefully placed and unassumingly named script on the server to take care of it.
Though nobody ever clocked on it was 1 VM that had a "problem", rather than the whole ESXi host (which was running about 20 VM's).
Another tip. when the Firewall needs an upgrade, switch on QOS and drop the priority of (or rate limit) HTTP, HTTPS and VOIP.
Indeed, what is better than a boss who is willing to get his hands dirty for the greater good? One who's aims are *broadly* in line with the BOFH and PFY? Also must come as a great relief to know that it is not only their window that seem to be an H&S trap...
Methinks a few nice new 4k monitors and fast desktops are coming to desks near by, such as shame of one was *caught* with pr0n on it...but maybe the boss is too useful...
The window situation is now dealt with - I have to wonder how the charged brass pole will be handled next.....
Apparently Simon has either decided that this Boss is someone he can work with, or the plot is far deeper and more twisted than we've seen before. I'm guessing there's a director's female offspring in the mix somewhere.....
“No, it’s too generic and we already have safety servers."
That made me snort. It's a shame you can only plant a crop in some fields every few years. Usually the cycle corresponds to the changing of the employment status of the Senior Beancounter. If there's nobody around to say "Hey, didn't you buy a new CMS server 2 years ago?" then it's time to do a PO for a new CMS server...
This post has been deleted by its author
For us, it's more of a "well, the previous manager decided to collapse the virtual machines running on 11 hosts to a blade chassis with 8 servers on it without consulting us to make sure that it would support the load and have enough spare capacity for expansion."
which is why we are spending an Imperial Arse-load of money on servers instead of storage this year. (that was about the only GOOD thing the last manager did was to buy a metric f*&k-tonne of storage during his tenure, except that I would have preferred an upgrade and expansion to the existing storage appliance than replacing it with one that does only about a third of what the old one did.)
anon for obvious reasons.