I am just googling your error code here, but it seems that this is an issue with Named pipes.
This page: https://github.com/Microsoft/BashOnWindows/issues/2 suggests that you need something newer than anniversary in order to have a chance of it working the way you want it to (Build -ge 14901). Is getting it working right this time going to save time in the future? Probably. Would getting it working this time with WinSCP save time in the future? Probably. I guess it just depends on what you want to do. Good luck! Thanks, Devin Rich Systems Administrator On Wed, Sep 14, 2016 at 8:07 AM, Mote, Todd <mo...@austin.utexas.edu> wrote: > 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 > > -- The information contained in this message is privileged, confidential, and protected from disclosure. If you are not the intended recipient, you are hereby notified that any review, printing, dissemination, distribution, copying or other use of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by replying to the message and deleting it from your computer.
