|
I've known about impending firings for days before they were happening and I always had the hardest time interacting normally with people when I knew. Also I worked at a large financial institution that would warn people ahead of time that they were considering firing them. Sometimes they weren't fired. I felt like it was an insane system.
|
|
#
?
Oct 18, 2016 21:31
|
|
|
|
| # ? May 30, 2024 17:24 |
|
|
Jerk McJerkface posted:Is this a theoretical or did it happen? I just want to know so I can disable the accounts. Nothing looks like it was done beyond a few emails to other companies cussing us out that I can forward to HR / Legal. Still need to check so much other stuff in detail, but quick glance looks like they had no idea what they were doing.
|
|
#
?
Oct 18, 2016 21:32
|
|
|
I had a client fired their IT guy, I did their network/pbx, and he managed everything else. He was in the process of setting up a domain controller for them, and when he was fired he remoted into it and screwed it all up. When I found out, I just laughed since he did an awful job anyways (like using raid stripping, a hacked unlicensed Win2k8 version, etc), so I just reinstalled Windows Server and had an entirely new domain setup and ready in like an hour. There wasn't any users or anything configured, so he did actually zero damage.
|
|
#
?
Oct 18, 2016 21:35
|
|
|
Super Soaker Party! posted:Do you mean actual cutters, like the things you're supposed to use with zip ties? (I call them Xcelites but that's mostly because that's the brand I tend to have, I think the name is shear-cutters or something). Because those are amazing and if you do it right and not like a moron you actually leave no sharp points sticking up from the zip tie head at all. Of course if you're sloppy and don't take the extra half second to make sure the cutter blades are flush to the zip tie head then yeah, you leave points, and should also be killed by slow neck cutting with those points. And anyone who uses scissors on zip ties can loving die in a fire. I've always called them side cutters, the problem is we inherit or get handed a lot of poo poo done by the laziest/cheapest contractors they can find and some of the racks are just a forest of jagged poo poo. Anything my group does is done right.
|
|
#
?
Oct 18, 2016 21:51
|
|
|
The douchiest firing I've witnessed was my last job in silicon valley, I was about to leave the area to move in with my future wife. About two days before I intended put in my notice my boss hinted he was going to terminate another guy in our group. He wasn't the highest quality worker in the world but he was competent and had just had a baby. Figured I'd try and help him out and clued my boss into the fact I was leaving and he was all "thanks for the offer but I think we're going to stick with our plan." So they were out two employees that day.  Pretty low on the jerk scale but I've had a pretty sheltered career.
|
|
#
?
Oct 18, 2016 21:55
|
|
|
Cogent wins the award for worst ISP ever. Last night I was helping a customer relocate their PoP and a lot of their perimeter equipment from their headquarters to their colocation facility (including the installation of a new perimeter firewall and turning up 2 new IPSec tunnels). Cogent had been delayed in getting a person out on site to double check everything and configure the router on their end for when we turned up the new equipment. When the cutover started at 5:30, they removed the old configs from the PE equipment at the old PoP and then . . . apparently went home for the day. After troubleshooting some physical layer issues, at about 9 PM a quick round of troubleshooting revealed we didn't have a BGP neighborship, so I asked the tier 1 tech on the phone to verify the BGP neighborship was still in the INIT state on his end, which he did. I then asked him to confirm the BGP settings on his end, at which point he informed me that there were no BGP configurations specific to our ASN/CE router and that the order would be filled by the service delivery team promptly at 9AM Eastern. Incredulous, I asked the tech if he could requeue it or put is on with service delivery from another country, which he told us wasn't possible. I told the customer's IT director to have fun and then left the room laughing, because the secondary ISP's transceiver was damaged and they too had blown away their configs at the old PoP in anticipation of our move. After a bit, we found out they wouldn't have a tech on site to replace it until 3 AM. He showed up at 4. I got back to my house at 9AM after finally verifying and fixing all of the IPSec tunnels, having been awake for 26 hours straight.
|
|
#
?
Oct 18, 2016 22:24
|
|
|
Jerk McJerkface posted:"Nah, it's fine, I deserve a new car" I know there's plenty more reasons to dislike the guy than this, but I hate it so much when people use that line. It doesn't matter what you deserve, or how hard you've been working. You get what you can afford, not what you deserve.
|
|
#
?
Oct 19, 2016 00:08
|
|
|
psydude posted:Cogent wins the award for worst ISP ever. Last night I was helping a customer relocate their PoP and a lot of their perimeter equipment from their headquarters to their colocation facility (including the installation of a new perimeter firewall and turning up 2 new IPSec tunnels). Cogent had been delayed in getting a person out on site to double check everything and configure the router on their end for when we turned up the new equipment. When the cutover started at 5:30, they removed the old configs from the PE equipment at the old PoP and then . . . apparently went home for the day. After troubleshooting some physical layer issues, at about 9 PM a quick round of troubleshooting revealed we didn't have a BGP neighborship, so I asked the tier 1 tech on the phone to verify the BGP neighborship was still in the INIT state on his end, which he did. I then asked him to confirm the BGP settings on his end, at which point he informed me that there were no BGP configurations specific to our ASN/CE router and that the order would be filled by the service delivery team promptly at 9AM Eastern. That sounds like an unplanned poo poo show. If you weren't doing anything from 9PM, 11PM whenever you found out someone wasn't going to be there until 3AM you should have billed for a hotel room since you can't do anything and taken a nap. Not forgetting to loot the mini bar because gently caress them.
|
|
#
?
Oct 19, 2016 04:14
|
|
|
Jerk McJerkface posted:He said "No, I'm not. I just walked in, let me get settled and have my coffee. Listen, JMJF, I know you are new and want to impress everyone, but you don't need to scramble everytime a client calls with a critical problem. Just chill out. Mark (the manager) talks a lot, but you don't have to kill yourself answering calls. It's kind of funny that you are making GBS threads on him for this, when people in this thread have said the exact same things (albeit not when there are legit critical problems happening)
|
|
#
?
Oct 19, 2016 04:33
|
|
|
My favorite firing was a guy who spent his Friday asking clients if they would switch to his new company he was starting in a few weeks. We had a quick but interesting conversation about that at 8am Monday.
|
|
#
?
Oct 19, 2016 05:00
|
|
|
Can anyone help me with a WDS problem? Some DELL computer models boot fine, some don't. After trying jsut about everything, I've resorted to capturing traffic and it's mostly the same. Both get a DHCP ACK with the right data. The PCs that don't work send a DHCP release a little bit before, and also send a ICMP Port Unreachable right after receiving the DHCP ACK (with Source IP 0.0.0.0). If anyone could take the time to help me with this, I'd really appreciate it.
|
|
#
?
Oct 19, 2016 11:29
|
|
|
Shitiest fireing I was in my first job. The company was going down the drain, so every three months they'd lay off a bunch of people. Always less then 10% of the workforce because of local specific restructuring laws. So, one guy's phone would started rining and he'd go to the manager's office, then another guy's phone would ring, etc. They also tried to gently caress us on the severance packages.
|
|
#
?
Oct 19, 2016 13:04
|
|
|
Shittiest firing i've ever seen was when an installs guy was let off during probation for "not getting along well with the team". What actually happened was that the company boss saw him smoking a few streets down from the office (dude wasn't even wearing his company jumper) and he doesn't like smokers. The guy he fired wasn't allowed to go to his desk to get his bag. Boss called him unclean during the firing too. Not that it stopped the guy. He also smashed his monitor while he was there. Don't really blame him either. On a different note, I feel like I need it explained to me exactly why its my fault that the monthly backup back at the start of the year being empty is my fault when I only started doing them four months ago. I've been in this argument for about three weeks now. I have only touched the backup to put it into the drive. The backup is empty. I cannot magic the data. gently caress off.
|
|
#
?
Oct 19, 2016 14:12
|
|
|
Goddamn I hate panicking and short fuses, yesterday I pretty much had to explain why I didn't immediately to a full-scale investigation because a handful of people were having phone problems. (I accidentally fueled the fire by stating I'm looking at the company status page now with 10 active calls, so I said if 10 people come to me in the next few minutes then I know we have a problem) I pretty much sent over my working process for phone issues, and specifically told them in kind terms to not loving panic and cause a shitstorm among the office as I'm pretty keen on knowing when we have a legit problem and when people are loving up their phone calls. Issue; - Couple inbound cell phone fails because of their lovely signal - Couple premature hangups when transferring calls - One unknown but PABX logs don't indicate an issue on our end Super Slash fucked around with this message at 14:25 on Oct 19, 2016 |
|
#
?
Oct 19, 2016 14:23
|
|
|
If you have an out of office notification set for every day on your non working hours, you suck rear end.
|
|
#
?
Oct 19, 2016 14:36
|
|
|
Know what's cool about working in an office full of 65+ year old ladies? They're never hot enough to turn the AC on. They sit there in their little grandma sweaters even when it's 85 degrees. ITS CHILLY IN HERE! The gently caress it isn't, Beatrice. Retire already!
|
|
#
?
Oct 19, 2016 14:41
|
|
|
Bigass Moth posted:If you have an out of office notification set for every day on your non working hours, you suck rear end. I did this at my last job because clients would e-mail us late at night and then bitch about us not getting back to them (we had an emergency line for after hours work and somebody was always on-call to answer it.)
|
|
#
?
Oct 19, 2016 14:51
|
|
|
Bigass Moth posted:If you have an out of office notification set for every day on your non working hours, you suck rear end. Are you afraid all the extra emails are going to plug up the tubes?
|
|
#
?
Oct 19, 2016 15:03
|
|
|
Bob Morales posted:Know what's cool about working in an office full of 65+ year old ladies? They're never hot enough to turn the AC on. They sit there in their little grandma sweaters even when it's 85 degrees. ITS CHILLY IN HERE! Start an arms race, sweaters vs http://www.veskimo.com/why-best-cooling-vest.php
|
|
#
?
Oct 19, 2016 15:12
|
|
|
Bob Morales posted:Know what's cool about working in an office full of 65+ year old ladies? They're never hot enough to turn the AC on. They sit there in their little grandma sweaters even when it's 85 degrees. ITS CHILLY IN HERE! Contrary: office full of women hitting 50 and all getting hot flushes.
|
|
#
?
Oct 19, 2016 15:12
|
|
|
totalnewbie posted:Are you afraid all the extra emails are going to plug up the tubes? It's just annoying but maybe I am in the minority who understands most people don't work 24/7.
|
|
#
?
Oct 19, 2016 15:21
|
|
|
SEKCobra posted:Can anyone help me with a WDS problem? Some DELL computer models boot fine, some don't. After trying jsut about everything, I've resorted to capturing traffic and it's mostly the same. Both get a DHCP ACK with the right data. The PCs that don't work send a DHCP release a little bit before, and also send a ICMP Port Unreachable right after receiving the DHCP ACK (with Source IP 0.0.0.0). Try it on a different switch
|
|
#
?
Oct 19, 2016 15:32
|
|
|
Sometimes the delay in network link that STP on the switch causes conflicts with the timeout on DHCP acquisition on the network interface.
|
|
#
?
Oct 19, 2016 15:51
|
|
|
Jerk McJerkface posted:Sometimes the delay in network link that STP on the switch causes conflicts with the timeout on DHCP acquisition on the network interface. "port fast" is the keyword to search for dealing with that.
|
|
#
?
Oct 19, 2016 15:54
|
|
|
The other day someone learned, during a UPS test, that the ageing voip/softphone system does not handle a power outage gracefully. All phones in the callcenter died around 13.00 and were out until closing at 16.00. Luckily the customers didn't seem to mind terribly much as we didn't get any appreciable amount of extra calls the following day.
|
|
#
?
Oct 19, 2016 16:03
|
|
|
Jerk McJerkface posted:Sometimes the delay in network link that STP on the switch causes conflicts with the timeout on DHCP acquisition on the network interface. I read about that, but I couldn't find a cause, since the working and non working PCs are consistent on the same interface.
|
|
#
?
Oct 19, 2016 16:12
|
|
|
MrBling posted:The other day someone learned, during a UPS test, that the ageing voip/softphone system does not handle a power outage gracefully. I once worked in a an office tower with some sort of primary building UPS's when the power went out entirely (building full of servers, financial traders, etc.). Turns out some guy put the wrong UPS into pass-through mode before testing that the battery back-up worked. Since I was working the night shift, I got to wake up the CEO at 2AM.
|
|
#
?
Oct 19, 2016 16:20
|
|
|
SEKCobra posted:I read about that, but I couldn't find a cause, since the working and non working PCs are consistent on the same interface. Are the working and non-working PCs the same model? Is the BIOS firmware (or whatever controls WDS) the same? I'm not familiar with WDS, but it's some kind of remote OS installation tool, right? Is it PXE based?
|
|
#
?
Oct 19, 2016 16:35
|
|
|
Jerk McJerkface posted:Are the working and non-working PCs the same model? Is the BIOS firmware (or whatever controls WDS) the same? I'm not familiar with WDS, but it's some kind of remote OS installation tool, right? Is it PXE based? We have noticed that some dell models are needing bios updates to function correctly in MDT which the bootdisk is delivered through WDS. You are probably right.
|
|
#
?
Oct 19, 2016 16:48
|
|
|
Jerk McJerkface posted:Sometimes the delay in network link that STP on the switch causes conflicts with the timeout on DHCP acquisition on the network interface. Any network engineer using standard STP in TYOOL 2016 deserves to be flogged with a cat o' nine tails made of ethernet cables. edit: ESPECIALLY on edge ports.
|
|
#
?
Oct 19, 2016 17:11
|
|
|
Make them walk on a bed of trimmed zip ties.
|
|
#
?
Oct 19, 2016 17:14
|
|
|
Sickening posted:We have noticed that some dell models are needing bios updates to function correctly in MDT which the bootdisk is delivered through WDS. You are probably right. We tried BIOS updates, didn't change it. And no, the models are different, we got a few desktops and a laptop that aren't working. I'll check on STP tomorrow, but I kinda doubt it.
|
|
#
?
Oct 19, 2016 17:19
|
|
|
SEKCobra posted:We tried BIOS updates, didn't change it. And no, the models are different, we got a few desktops and a laptop that aren't working. I'll check on STP tomorrow, but I kinda doubt it. Can you boot the computers with the wds image with the network taken out of the loop? IE, using a thumb drive? (wds imagine on the boot drive) This is why mdt is just superior to WDS. Sickening fucked around with this message at 17:25 on Oct 19, 2016 |
|
#
?
Oct 19, 2016 17:21
|
|
|
SEKCobra posted:We tried BIOS updates, didn't change it. And no, the models are different, we got a few desktops and a laptop that aren't working. I'll check on STP tomorrow, but I kinda doubt it.
|
|
#
?
Oct 19, 2016 17:24
|
|
|
anthonypants posted:You're going to need to provide network drivers for each model on your image. ... This has nothing to do with PXE failing and comes at a far later stage.
|
|
#
?
Oct 19, 2016 17:33
|
|
|
Sickening posted:Can you boot the computers with the wds image with the network taken out of the loop? IE, using a thumb drive? (wds imagine on the boot drive) Doesn't MDT still use WDS? So if the basis isn't working, how would it work?
|
|
#
?
Oct 19, 2016 17:39
|
|
|
SEKCobra posted:... This has nothing to do with PXE failing and comes at a far later stage. SEKCobra posted:Doesn't MDT still use WDS?
|
|
#
?
Oct 19, 2016 17:40
|
|
|
anthonypants posted:Then you should've said they're failing to boot from PXE? You said it was a WDS problem but this sounds more like a DHCP problem. The answer is more "it can" but its not required. Also computers can fail pxe and it not be a network problem at all. Considering other computers can pxe just fine leads me to believe its not a network problem at all if the location of the network is controlled. WinPE can fail for all sorts of reasons. Boot disk image is too big for the computer, incorrect drivers, bugs in firmware, etc. As far as MDT vs WDS goes, I feel like MDT has had more development time than WDS has in the last 5 years. As buggy as MDT is, I feel like WDS is only good for hosting boot disks at this point and shouldn't be your primary imaging system.
|
|
#
?
Oct 19, 2016 17:53
|
|
|
SEKCobra posted:I read about that, but I couldn't find a cause, since the working and non working PCs are consistent on the same interface. Are the sets of machines that work vs not work uefi vs bios? I had to set my dhcp servers to failover instead of load balance because uefi machines would always pull from one, and bios always the other
|
|
#
?
Oct 19, 2016 18:16
|
|
|
|
| # ? May 30, 2024 17:24 |
|
|
Serfer posted:Are the sets of machines that work vs not work uefi vs bios? I had to set my dhcp servers to failover instead of load balance because uefi machines would always pull from one, and bios always the other Nope, also tried switching between Legacy and UEFI mode.
|
|
#
?
Oct 19, 2016 18:44
|
|