@gjacobse said in Powershell Start-Process Differences:
@irj said in Powershell Start-Process Differences:
How big is the organization? Have you talked to others in IT about what's acceptable and what isn't?
It sounds like you need the ability to write powershell scripts. Why not bring it up to your manager and other teams if need be?
It's been a (sore) subject since I started... Having worked with @EddieJennings and @Dashrender on some scripts and the goal of moving to PS over MS Batch.. I wanted to do more..
But between Execution Policy and such, it's pretty much trying to pour water through a wall... just not going to happen due to security (reasons). We are a clinic - so security is of course important. But the State dealt with PHI and such as well and the Policy was permitted.... sigh
I don't suppose being cheeky and calling powershell commands from a batch file works differently? I'd assume not, but might be worth a try.
Someone at state has things a little backwards if they're allowing cmd bat files but not powershell ps1 scripts!
Just because I don't like powershell, doesn't mean it's not more useful than cmd.