Probably easier/more clandestine ways to go about that than running power shell scripts under your own fucking user ID.
Although the company is not totally free from fault here. Apparently they left his account or at least his user session active after he was let go. Fucking amateur hour there. Guess they don't have proper termination procedures in place. They ultimately allowed this to happen.
Yeah, Most companies do that shit. They are afraid that there are custom jobs or scripts that run under their user account and they will break and take down prod if the account is disabled.
It's a stupid fucking practice and if a company allows anything to be ran under anything but a service account or something that access can be strictly controlled they are full of fail.
Basically every single place I have worked have had this problem. I usually start with trying to move things that run as a user into a service account in the first month since no one else is willing to do it. I am paid to -un-fuck- what everyone before me fucked up.
(post is archived)