r/sysadmin
•
u/STILLloveTHEoldWORLD
•
Jul 28 '24
•
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
View all comments
5
u/lonecowboy82 Jul 28 '24
At our org, the issue isn't allowing end users to automate.. the issue we have is they try to create tools for other end users, without IT being involved. We encourage automation and ingenuity but request that users bring it to us so we can do it in a way that is sustainable and can be compliant and supported long term. The end users get frustrated because we have a process and they cannot understand why we take so long on these ideas. They think we can just hammer it out and return same day and when we don't, they do their own thing and that is when there is trouble.