So nobody was ever in the office and nobody on the team wanted to stay (I’m guessing here) 2.5 hrs after work to actually do any troubleshooting and because it was never a problem during office hours then who cares
Read the comment more carefully… while IT was most certainly not at their posts, this implementation team was actively monitoring the rollout and witnessing the carnage.
And in those four months, did no-one think of firing up WireShark to see what was floating across that network during that time period?
Seems like someone dropped the debug/analysis ball…
As someone in IT, the answer is in the comment.
So nobody was ever in the office and nobody on the team wanted to stay (I’m guessing here) 2.5 hrs after work to actually do any troubleshooting and because it was never a problem during office hours then who cares
Read the comment more carefully… while IT was most certainly not at their posts, this implementation team was actively monitoring the rollout and witnessing the carnage.
what can you expect, they’re probably getting paid 40-50% of what they should be getting paid.
pay less get less.
my pride as an IT worker wouldn’t have allowed me to let it fester for 18 weeks though.
I wasn’t in IT, so my hands were tied. If I tried running a network scan, I’d have been able to hear the screeching all the way from city hall.