Adventures with house IT

I'm currently experimenting with PowerShell but my scripts won't run even though I've got every local permission. The error message indicates it's a GPO problem.
"No problem" le me thinks and calls IT hotline.
After 2 incompetent and unprofessional technicians i've still got no solution. I'm waiting for the second tech to call back because he "needed some time to get to know PowerShell" (he is a trained and certified SysAdmin).
During my call he couldn't decide if it was a GPO problem or not.
And this is just one story of their incompetence...

Who in their right mind would gpo disable the c drive on a dev workstation...

Computers at college have so many GPO that the average computer takes 10 minutes to boot and at least another 3 to get to the desktop with an additional 3 before you can actually do anything. Oh and they have college wide power consumption GPOs meaning that even the newest most powerful computers act like they came from the early 2000s

Not really a bug, but I have recently finished organising our Domain Controller.

It was a server set up about 8 year ago by someone with zero experience with server OS.

I had to completely re-work every single group, GPO, User Account, Login script, shared drives and DHCP.

I have now solved 90% of re-occurring problems with our network.

Now they want me to do the same with our Digital Storefront...

?rant: a lot of people(including me) hates microsoft for the mandatory win10 updates, but I recently found out that you can block it from group policy. Is this not enough or people just dont know about it?