'VisibleCmdlets' and 'VisibleFunctions' break internal functions usage about jea HOT 7 OPEN

Can you try adding Microsoft.PowerShell.Utility to ModulesToImport in your PSRC? JEA can get funny with dependencies because the module discovery and auto-loading doesn't work the same as it does in a full language session. We generally recommend adding any modules called inside custom scripts or functions to ModulesToImport to ensure they're pre-loaded into the session. You can also try fully qualifying the cmdlet name in your function definition: Microsoft.PowerShell.Utility\Clear-Variable

from jea.

Unfortunately it's exactly the same. We tried many different workarounds and never got back functions :-/

from jea.

@PaulHigin Any tips for Julien? I'm not sure why the built-in commands would stop working inside custom functions.

from jea.

I provided some workarounds on this page: https://jnury.github.io/JEA_term_not_recognized_name_cmdlet/

By the way, I only found 6 functions affected:

• ConvertFrom-SddlString
• Format-Hex
• Get-FileHash
• Import-PowerShellDataFile
• New-Guid
• New-TemporaryFile

These functions are all provided by the Microsoft.PowerShell.Utility module

from jea.

I'll take a look.

from jea.

@jnury Thanks for reporting this. I am able to reproduce the problem. This is old endpoint configuration code that imports core modules into the restricted session through "snapins". The Microsoft.PowerShell.Utility module consists of binary and script components but snapins only deal with the binary component and leave the script out, which is why the script functions are not available.

I think this is just old legacy code that should be re-written to use module loading rather than snapins.
Can you create an issue on https://github.com/powershell/powershell?
I believe the fix is to re-write how core modules are loaded in the InitialSessionState.CreateRestrictedForRemoteServer() method.

from jea.

Thank-you @PaulHigin !
I found this issue on UserVoice: https://windowsserver.uservoice.com/forums/301869-powershell/suggestions/17852350-wmf-5-1-restrictedremoteserver-session-type-fails so just voted and commented on it. If i can reproduce the behaviour on Powershell Core, I'll open an issue on GitHub.

from jea.