-
Notifications
You must be signed in to change notification settings - Fork 7.6k
JEA Not Working As Expected with RC1 #11538
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
cc @PaulHigin |
I've been able to reproduce this. But I won't be able to investigate further until Monday. |
Thanks @PaulHigin - Glad someone else can reproduce this. I am hoping this is a) not intended behaviour and b) if so, a fix can be added to RC2 or RTM??? |
Yes, I think this will be a 'must fix' for the next release. But I'll know more after I investigate. |
Not sure if it's possible - but can JEA handling be added to the test matrix?? |
Update: This seems to happen only on preview builds and I am working on contacting the WinRM team to determine why this is broken for this case. |
The fix has been merged. Thanks for reporting this! |
Thanks - I downloaded the daily build and it works as designed THanks |
I am setting up JEA on a Server 2019 VM. The idea is to use JEA to enable a user to logon and do some DNS stuff. This process works with Server 2019 and WIndows PowerShell, but is not working with PowerShell 7 RC1.
Steps to reproduce
Here is how I have JEA setup so far:
Having done that, I get odd results when trying to use it:
The set of commands available are not the same as shown after Step 11 above. Running Step 11, for example, shows the Get-HW.
If I try to run that command:
Also, none of the DNS commands work in the JEA session either.
Expected behaviour
I expected running $SB1 to show the same commands as offered from Step 11.
I expected running $SB2 to return a string (as per the function definition in Step 5), "Hello JEA World.
I expected to be able to use the DNS commands.
Actual behaviour
Environment data
The text was updated successfully, but these errors were encountered: