Gregory Suvalian

My feedback

  1. 2 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    3 comments  ·  PowerShell » PowerShell Engine  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Gregory Suvalian commented  · 

    Also I have no option to create file any other way but by editing text file as the other bug I submitted does not allow to create any JEA endpoints via New-PsSessionConfigurationFile. So I end up manually creating configuration file in Notepad and adding JEA specific data.

    An error occurred while saving the comment
    Gregory Suvalian commented  · 

    Per documentation of configuration file (about_Session_Configuration_Files) I can edit it directly in configuration location and it does not even require restart. So I did that. But yes it appears it's another bug since if I edit it directly in location then changes are not being imported into WinRM but if I register/deregister configation file then it will work.

    Editing a Session Configuration File

    To edit the session configuration file that is being used by a session
    configuration, begin by locating the active copy of the session configuration
    file.

    When you use a session configuration file in a session configuration,
    Windows PowerShell creates an active copy of the session configuration file
    and stores it in the $pshome\SessionConfig directory on the local computer.

    The location of the active copy of a session configuration file is stored
    in the ConfigFilePath property of the session configuration object.

    The following command gets the location of the session configuration file
    for the NoLanguage session configuration.

    PS C:\> (Get-PSSessionConfiguration -Name NoLanguage).ConfigFilePath
    C:\WINDOWS\System32\WindowsPowerShell\v1.0\SessionConfig\NoLanguage_0c115179-ff2a-4f66-a5eb-e56e5692ba22.pssc

    You can edit the file in any text editor. The file is changed as soon as
    you save it and is effective in new sessions that use the session configuration.

    Gregory Suvalian shared this idea  · 
  2. 2 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  PowerShell » PowerShell Engine  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Gregory Suvalian commented  · 

    Still present in latest "RTM" build

    Gregory Suvalian shared this idea  · 
  3. 5 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  PowerShell » Documentation  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Gregory Suvalian commented  · 

    Still present in "new" RTM

    Gregory Suvalian shared this idea  · 
  4. 3 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  PowerShell » PowerShell Engine  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Gregory Suvalian commented  · 

    Looking at ConfigFileConstants which is used by Test-PSSessionConfigurationFile cmdlet it shows that none of JEA constants were added to it.

    internal static ConfigTypeEntry[] ConfigFileKeys = new ConfigTypeEntry[27]
    {
    new ConfigTypeEntry(ConfigFileConstants.AliasDefinitions, new ConfigTypeEntry.TypeValidationCallback(ConfigFileConstants.AliasDefinitionsTypeValidationCallback)),
    new ConfigTypeEntry(ConfigFileConstants.AssembliesToLoad, new ConfigTypeEntry.TypeValidationCallback(ConfigFileConstants.StringArrayTypeValidationCallback)),
    new ConfigTypeEntry(ConfigFileConstants.Author, new ConfigTypeEntry.TypeValidationCallback(ConfigFileConstants.StringTypeValidationCallback)),
    new ConfigTypeEntry(ConfigFileConstants.CompanyName, new ConfigTypeEntry.TypeValidationCallback(ConfigFileConstants.StringTypeValidationCallback)),
    new ConfigTypeEntry(ConfigFileConstants.Copyright, new ConfigTypeEntry.TypeValidationCallback(ConfigFileConstants.StringTypeValidationCallback)),
    new ConfigTypeEntry(ConfigFileConstants.Description, new ConfigTypeEntry.TypeValidationCallback(ConfigFileConstants.StringTypeValidationCallback)),
    new ConfigTypeEntry(ConfigFileConstants.EnvironmentVariables, new ConfigTypeEntry.TypeValidationCallback(ConfigFileConstants.HashtableTypeValiationCallback)),
    new ConfigTypeEntry(ConfigFileConstants.ExecutionPolicy, new ConfigTypeEntry.TypeValidationCallback(ConfigFileConstants.ExecutionPolicyValidationCallback)),
    new ConfigTypeEntry(ConfigFileConstants.FormatsToProcess, new ConfigTypeEntry.TypeValidationCallback(ConfigFileConstants.StringArrayTypeValidationCallback)),
    new ConfigTypeEntry(ConfigFileConstants.FunctionDefinitions, new ConfigTypeEntry.TypeValidationCallback(ConfigFileConstants.FunctionDefinitionsTypeValidationCallback)),
    new ConfigTypeEntry(ConfigFileConstants.Guid, new ConfigTypeEntry.TypeValidationCallback(ConfigFileConstants.StringTypeValidationCallback)),
    new ConfigTypeEntry(ConfigFileConstants.LanguageMode, new ConfigTypeEntry.TypeValidationCallback(ConfigFileConstants.LanugageModeValidationCallback)),
    new ConfigTypeEntry(ConfigFileConstants.ModulesToImport, new ConfigTypeEntry.TypeValidationCallback(ConfigFileConstants.StringOrHashtableArrayTypeValidationCallback)),
    new ConfigTypeEntry(ConfigFileConstants.PowerShellVersion, new ConfigTypeEntry.TypeValidationCallback(ConfigFileConstants.StringTypeValidationCallback)),
    new ConfigTypeEntry(ConfigFileConstants.RoleDefinitions, new ConfigTypeEntry.TypeValidationCallback(ConfigFileConstants.HashtableTypeValiationCallback)),
    new ConfigTypeEntry(ConfigFileConstants.SchemaVersion, new ConfigTypeEntry.TypeValidationCallback(ConfigFileConstants.StringTypeValidationCallback)),
    new ConfigTypeEntry(ConfigFileConstants.ScriptsToProcess, new ConfigTypeEntry.TypeValidationCallback(ConfigFileConstants.StringArrayTypeValidationCallback)),
    new ConfigTypeEntry(ConfigFileConstants.SessionType, new ConfigTypeEntry.TypeValidationCallback(ConfigFileConstants.ISSValidationCallback)),
    new ConfigTypeEntry(ConfigFileConstants.RoleCapabilities, new ConfigTypeEntry.TypeValidationCallback(ConfigFileConstants.StringArrayTypeValidationCallback)),
    new ConfigTypeEntry(ConfigFileConstants.TranscriptDirectory, new ConfigTypeEntry.TypeValidationCallback(ConfigFileConstants.StringTypeValidationCallback)),
    new ConfigTypeEntry(ConfigFileConstants.TypesToProcess, new ConfigTypeEntry.TypeValidationCallback(ConfigFileConstants.StringArrayTypeValidationCallback)),
    new ConfigTypeEntry(ConfigFileConstants.VariableDefinitions, new ConfigTypeEntry.TypeValidationCallback(ConfigFileConstants.VariableDefinitionsTypeValidationCallback)),
    new ConfigTypeEntry(ConfigFileConstants.VisibleAliases, new ConfigTypeEntry.TypeValidationCallback(ConfigFileConstants.StringArrayTypeValidationCallback)),
    new ConfigTypeEntry(ConfigFileConstants.VisibleCmdlets, new ConfigTypeEntry.TypeValidationCallback(ConfigFileConstants.StringArrayTypeValidationCallback)),
    new ConfigTypeEntry(ConfigFileConstants.VisibleFunctions, new ConfigTypeEntry.TypeValidationCallback(ConfigFileConstants.StringArrayTypeValidationCallback)),
    new ConfigTypeEntry(ConfigFileConstants.VisibleProviders, new ConfigTypeEntry.TypeValidationCallback(ConfigFileConstants.StringArrayTypeValidationCallback)),
    new ConfigTypeEntry(ConfigFileConstants.VisibleExternalCommands, new ConfigTypeEntry.TypeValidationCallback(ConfigFileConstants.StringArrayTypeValidationCallback))
    };

    Gregory Suvalian shared this idea  · 
2 Next →

Feedback and Knowledge Base