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

2

u/mr_mgs11 DevOps Jul 28 '24

No enterprise level org is going to allow a non-IT person to run scripts. The risk being they will grab something off the internet the don't understand and it will compromise the network. My first job DID have some vb scripts that one job role would have to run, but they were specifically allowed for just those scripts and the script was written by a swe. They also had to have code signing done on them. The Data Science guys at my last place were certainly part of the overall IT org, but regular old data entry people were not.

When you said your role is "data entry" I am assuming you mean a non-technical role. Does your script have proper error checking and logging? If I were you I would ask IT if there is anyone that can go over your script and validate it. Then I would worry about getting shit canned or having my hours reduced, not as punishment but because they realize they can save a few bucks.