PowerShell
The PowerShell forum accepts bug reports as well as feedback and suggestions. For more information, check out the PowerShell Homepage
The following is a list of the states we use to track items.
| status | meaning |
|---|---|
| survey | We saw this and we are considering it. Please upvote if it’s important to you. |
| needs more information | We don’t understand the issue and need additional details. |
| investigating | We are looking at this internally to understand things like: scenario, reproduction of issue, costing, or other technical details. |
| in queue | The issue is understood and in our unprioritized backlog. Your votes will be used to drive prioritization of this work. |
-
Get-PSSessionCapability returns capabilities even when the speficied user doesn't have permissions to connect to the session
The documentation on Get-PSSessionCapability states it returns information (capabilities) on the session configuration the specified username has on it, but it also returns it for a SessionConfiguration (created with a pssc file) when it wasn't created with a RoleDefinition, no matter if the specified user can or cannot access it.
I would expect it not to return any information for that SessionConfiguration, or have a property that indicates the specified doesn't have the required permissions (invoke / fullcontrol).3 votes -
Add A "Start In" Directory for Enter-PSSession
By default, we are placed into Documents (at least I am), then have to change directories. It would be nice to be able to specify a directory we'd like to start in using Enter-PSSession.
18 votes -
Block WinRM operations during servicing
The WinRM service starts normally and accepts requests during component servicing operations (eg, "Working on Updates", "Working on Features" screens after a post-update/feature-change reboot). This causes problems for configuration management in cases where the servicing process triggers further reboots, especially since there doesn't appear to be a documented way to determine that servicing is underway. WinRM should either wait to accept requests until servicing is complete, or a way for third-party tools to determine that servicing is underway from Powershell should be documented.
1 vote
- Don't see your idea?