Has anyone else had this happen? I had to go through and un-register and reregister all of my JEA endpoints on every single upgrade I have done. Without doing this anyone connecting gets access denied...it's like the upgrade wiped all
of the security descriptors.....is it a known bug or will we have to do this every time we upgrade powershell?
JEA provides an RBAC platform that allows you to create a management endpoint on any computer and to manage it locally or remotely.
JEA is implemented as a Windows PowerShell session endpoint, which includes a PowerShell Session Configuration file and one or more Role Capability files.
And this powershell 5.1 notes:
- PowerShellGet improvements include enforcing signed modules, and installing JEA modules
so, i suspect this is the cause.
https://msdn.microsoft.com/en-us/powershell/wmf/5.1/release-notes
Best regards,
Andy
Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact
tnmff@microsoft.com.