So I have a pretty specific use case. My SCCM is in HTTPS only mode and I'm adding linux clients so I have to use certificates. Because the linux clients can't enroll for their own certificates (https://configurationmanager.uservoice.com/forums/300492-ideas/suggestions/13416162-let-the-linux-sccm-client-make-use-of-the-enrollme), I create one with powershell and then use winscp to provide it to our puppet server, that then distributes the cert and installs the client on the endpoint.
This cert business a manual process, and we came up with this about 2 years ago. Now the certs are expiring and I need to replace/renew all of the certs. The puppet server has all of the pfx's together in a directory so I just need to SSH to the puppet server, read the contents of the directory, loop through all the files there, create new pfx's and replace the old one, or renew the existing. Puppet will handle distributing the new certs and reinstalling the client with the new easy enough. I can do all of this through winscp, but thought that if I ran my script on Windows 10 Anniversary Edition that I could use bash. I can get "bash -c ls" to work in a console window, but I get bash -c ls E r r o r : 0 x 8 0 0 7 0 0 5 7 When I try to do the same thing in ISE. Does bash work from script/ISE? Am I going about this all wrong? Todd
