Why JEA is using the "Default" session type instead of the "RestrictedRemoteServer"?SummaryThe list of commands and cmdlets that the restricted mode provides is not enough for the needed set of commands for a full discovery experience with JEA. A list of commands is shown in Role Capability file: jea_disco.psrc, you can find the details here.InstructionsSince the "RestrictedRemoteServer" SessionType will not be able to execute all the commands which we want, we are doing with "Default" SessionType as per design as a need to perform the desired discovery.Related LinksThe RestrictedRemoteServer command list does not suffices for the needed set of commands.RestrictedRemoteServer is defined as explained in the following Microsoft documentation:The -SessionType RestrictedRemoteServer field indicates that the session configuration is used by JEA for secure management. Sessions of this type operate in NoLanguage mode and only have access to the following default commands (and aliases):Clear-Host (cls, clear)Exit-PSSession (exsn, exit)Get-Command (gcm)Get-FormatDataGet-HelpMeasure-Object (measure)Out-DefaultSelect-Object (select)