I have entire project of automation within my company on hold due to JEA being broken in PS 5.0. I hoped new RTM version just released would offer some fixes but it’s still as broken as it is. Not only that but I also opened 4 different bugs on UserVoice and since there are no votes I assume it’s not that highly visible. Bugs are
- Lack of documentation (new cmdlets and new parameters are not having help file)
- PSsessionConfiguration file cmdlets are not producing well formed XML file
- Parameters withing PSSessionConfiguration file are not being read into WinRM at all
- Remoting from PS 5.0 to PS 2.0 is broken for return values
I’m really confused as to how this issues not only slipped through QA but also that nothing has been even acknowledged by PS team. But even bigger surprise to me that nobody else seems to notice it. How JEA being broken or no documentation or remoting to downlevel clients are low key items and people are not seeing it?
For such a great tool and such a good run until version PS 5.0 it’s real letdown for me personally. I’m supposed to be a driving motion within my company to automate stuff and teach counterparts to use Powershell and show how we can separate Roles/Responsibilites with JEA and show easy to use documentation is etc. But all I have right now is some product I used to expect from open source community instead.
I don’t know if this qualifies as “bitching” but I never expect Microsoft to let down on quality of their product this much. It’s not BETA any more and not only that but it second release of RTM and stuff is broken when it matters.