Me: -submits ticket- “our recycle bins don’t work anymore. What happened?”
IT: “we scripted them to disable every time you guys log in from now on.”
Me: “……why?”
IT: “don’t know, but you won’t be getting recycle bins back until the upgraded computers roll out.”
Me: “okay, when will that be?”
IT: “dunno. We have to do the entire company and we can only do about 4 a week.”
Me: “dude, set up a fucking FOG server, throw all the interns at hooking the new machines up to a cheap switch, and multicast out an image. Bang this out in a few weeks.”
IT: “nope, open source doesn’t have support so we don’t use it.”
Me: “and who is “supporting” you at a rate of 4 pcs a week?”
IT: “……is there anything else I can help you with?”
Yeah, a big part of my job is helping deploy thousands of systems with in one customer case a contractural commitment to be able to redeploy all 3,000 of their systems in 30 minutes…
But when it comes to my own system, I am mandated by company policy to let our IT handle it, who does it by hand from a USB stick… So when the time comes they want to reimage my system for whatever reason, II turn in my laptop for a few days, get it back and put my second m.2 disk back in to boot back into the OS I maintain after letting them do what they wanted to my alleged ‘primary’ OS.
Do things in recycle bin not get synced to the cloud/backed up?(edit: nope seems everything from breaking migration tool, ballooning profiles and overzealous compliance can be mitigated elsewhere). Hence doing so in the roll out? No idea otherwise or why they wouldn’t know. Sometimes we just get told to do things a certain way. Not IT anymore but currently work with engineers who try shortcutting triage queues (probably in an attempt to save everyone time, not maliciously) and we have to undo their assignment and triage it as laid out. Specifically we were told “people will try to tell you who to send internal requests to, ignore them”. Largely for accountability so tickets/requests don’t get dropped or breach SLA and also because it can break workflows. Locking out recycle bins without being able to provide a good reason is pretty wild though lmao.
They said they it’s a Citrix thing. They are getting rid of Citrix too, which is fine as it’s a pain in the ass, but moving to full PCs for remote workers tha don’t need them is a ridiculous waste of time and money, especially now. It’s just going to make things worse because supporting that won’t scale as cleanly.
And why this migration? It’s not like Citrix was a bad idea on the first place. It actually solves some real problems for us.
IT: “because we can’t remote into a Citrix box.”
Me: “the fuck you cant.”
Me: -submits ticket- “our recycle bins don’t work anymore. What happened?”
IT: “we scripted them to disable every time you guys log in from now on.”
Me: “……why?”
IT: “don’t know, but you won’t be getting recycle bins back until the upgraded computers roll out.”
Me: “okay, when will that be?”
IT: “dunno. We have to do the entire company and we can only do about 4 a week.”
Me: “dude, set up a fucking FOG server, throw all the interns at hooking the new machines up to a cheap switch, and multicast out an image. Bang this out in a few weeks.”
IT: “nope, open source doesn’t have support so we don’t use it.”
Me: “and who is “supporting” you at a rate of 4 pcs a week?”
IT: “……is there anything else I can help you with?”
Me: “gave us back our recycle bins.”
IT: “no”
Fucking Christ these guys are dumb.
Yeah, a big part of my job is helping deploy thousands of systems with in one customer case a contractural commitment to be able to redeploy all 3,000 of their systems in 30 minutes…
But when it comes to my own system, I am mandated by company policy to let our IT handle it, who does it by hand from a USB stick… So when the time comes they want to reimage my system for whatever reason, II turn in my laptop for a few days, get it back and put my second m.2 disk back in to boot back into the OS I maintain after letting them do what they wanted to my alleged ‘primary’ OS.
Do things in recycle bin not get synced to the cloud/backed up?(edit: nope seems everything from breaking migration tool, ballooning profiles and overzealous compliance can be mitigated elsewhere). Hence doing so in the roll out? No idea otherwise or why they wouldn’t know. Sometimes we just get told to do things a certain way. Not IT anymore but currently work with engineers who try shortcutting triage queues (probably in an attempt to save everyone time, not maliciously) and we have to undo their assignment and triage it as laid out. Specifically we were told “people will try to tell you who to send internal requests to, ignore them”. Largely for accountability so tickets/requests don’t get dropped or breach SLA and also because it can break workflows. Locking out recycle bins without being able to provide a good reason is pretty wild though lmao.
They said they it’s a Citrix thing. They are getting rid of Citrix too, which is fine as it’s a pain in the ass, but moving to full PCs for remote workers tha don’t need them is a ridiculous waste of time and money, especially now. It’s just going to make things worse because supporting that won’t scale as cleanly.
And why this migration? It’s not like Citrix was a bad idea on the first place. It actually solves some real problems for us.
IT: “because we can’t remote into a Citrix box.” Me: “the fuck you cant.”
That’s what happens when you subcontract out your IT.
Would you believe we didn’t do that? They are just convinced that’s how this should go.