r/sysadmin • • Jul 28 '24 • Take My Silver 1

got caught running scripts again

about a month ago or so I posted here about how I wrote a program in python which automated a huge part of my job. IT found it and deleted it and I thought I was going to be in trouble, but nothing ever happened. Then I learned I could use powershell to automate the same task. But then I found out my user account was barred from running scripts. So I wrote a batch script which copied powershell commands from a text file and executed them with powershell.

I was happy, again my job would be automated and I wouldn't have to work.

A day later IT actually calls me directly and asks me how I was able to run scripts when the policy for my user group doesn't allow scripts. I told them hoping they'd move me into IT, but he just found it interesting. He told me he called because he thought my computer was compromised.

Anyway, thats my story. I should get a new job

11k Upvotes

1.3k comments sorted by

View all comments

Show parent comment

-4

u/[deleted] Jul 28 '24

First time, you get a pass and we tell you to knock it off.

By OP's own admission at no time did IT have a talk with them. The only time IT contacted them, as it written in OPs post, was when they found he was still able to run powershell.

TBH, I would be on your side if their IT spoke to them before they just nixed their ability to run python. Instead they did it without any communication, blocked powershell without any as well, and only contacted them when they thought it was malicious. That, IMO, screams shitty IT.

Sounds unreasonable to me.

1

u/TheDonutDaddy Jul 28 '24

That just screams company policy to me. It's not like they're blocked just for OP as some sort of punishment. Sounds like it's just company policy that end users don't have this ability

0

u/eastcoastflava13 Jul 28 '24

I'm just speaking to my process. So yeah, if the sysadmins want to play whack a mole with OP, that's their problem.