I'm getting some parse issues with Export-ODataEndpointProxy. It creates 119 cdxml files from my Redfish endpoint, but 8 of them have "duplicate key sequence" errors. That's pretty good at 8 of 119, but I'm unable to run any cmdlets because when I Import-Module on the folder of cdxml files, it returns the "duplicate key sequence" errors.

The current Write-Progress bar is ugly, and shows at the top of the sreen. Showing yello text over dark cyan, representing progress with some weird circles...

It should be more like the yarn progress bar, that shows immediately after the command.

https://imgur.com/GfJRHfp

Get-ADGroupMember -Recursive only reads the Group Members property. It does not also add users to the list who have a group as their primary group. Here is what it should be doing...

(Get-ADGroupMember -Identity "Domain Admins" | select distinguishedName).distinguishedName

Here is what it is actually doing...

Get-ADGroup -Identity "Domain Admins" -Properties Member | select -ExpandProperty member

Which is a different answer!

Attempting to compare two strings. When constructing one of the strings, the TrimStart method is trimming more of the string than it should. Example:

(Get-Content -Path 'C:\Program Files\SplunkUniversalForwarder\etc\system\local\server.conf' | Select-String -Pattern 'serverName').ToString().TrimStart('serverName = ')

returns

rver1.domain.company.com

expected output is

server1.domain.company.com

I expanded the TrimStart method like so:

(Get-Content -Path 'C:\Program Files\SplunkUniversalForwarder\etc\system\local\server.conf' | Select-String -Pattern 'serverName').ToString().TrimStart('serverName').TrimStart(' ').TrimStart('=').TrimStart(' ')

and get the same erroneous output. The problem appears to be with trimming the last space character.

The Set-Location/Push-Location cmdlets do not update the calling process' current directory. This leads to surprising behavior when working with non-PowerShell APIs. Simple example below.

Hello,

I have Set the arguments in the code:

$installArguments = "`"-p`" `"$ISMFileFolder`" -o `"$MergeModuleFolder`" -y `"$VersionNumber`" $PathVariableArguments -b `"$MediaOutputFolder`""

and run the exe with arguments:
& $IScmdBldRootDir $installArguments
The same scripts is running fine on Windows server 2008 R2 that has the Powershell 4.0 and it fails and return error on Windows server 2016 that has the Powershell 5.1.
The error is:
-1113: The 'p E:\Builds\Installer' switch is not recognized.

Please, expand the RemoteAccess module with commandlets that allow you to configure simple NAT like you would do with the RRAS GUI.
So far, the module allow you to configure Direct Access and VPN but not NAT and it feels like it's missing.

Hi,

it would be very useful to have SNMP cmdlets available. SNMP is still defacto standard for managing many kinds of 'network-devices'.

It could help also considering IOT devices.

I would like a way to define common parameters that all functions within that module or perhaps session share. I moved to a new position and am refactoring my automation to work in a new paradigm. This means changing a bunch of parameter names to make sense. It's about 100 cmdlets and only slightly more complex than search and replace, but still I thought to myself "There has to be a better way"

I will NOT create another account (in GetHub) to report errors in the official Microsoft documentation. I should use my MSA account. There are several errors in the documentation for Set-ADUser, for example, that I reported years ago in Connect (now retired). The documentation for the -Office and -Replace parameters are wrong.

When using calculated properties in Format-Table, you can define:
- Name/Label (the column heading/calculated property name)
- Expression
- Width (define column width)
- FormatString (to format numbers/strings)
- Alignment (alignment in table cell/column

What's missing is a way to output a calculated property in a different color. For example, use red for negative number, green for positive number, and additionally, a way to specify the background color (for the table cell). Adding ForegroundColor (to specify text color) and BackgroundColor (for cell color) to calculated properties would resolve this.

Upon running the Import-Module with the verbose flag my script within "ScriptsToProcess" section contains verbose logging but does not output to the console. I am not sure if this is by design, but I thought by passing in the Verbose option would update the session $VerbosePrefence value and have any verbose logging within the ScriptsToProcess output, but it does not.

Is this by design? If yes, then what is your suggestion to output the verbose logging?

My local env:

Name Value
---- -----
PSVersion 4.0
WSManStackVersion 3.0
SerializationVersion 1.1.0.1
CLRVersion 4.0.30319.42000
BuildVersion 6.3.9600.18773
PSCompatibleVersions {1.0, 2.0, 3.0, 4.0}
PSRemotingProtocolVersion 2.2

Something killed my Directory for all Packages.... How can i repair the Powershell-Installation withing Windows 10 ?
Already tried deactivating / activation of the feature withing windows, sfc /scannow , etc.
but i cannot use my powershell completely anymore...

$PSVersionTable

Name Value
---- -----
PSVersion 5.1.15063.786
PSEdition Desktop
PSCompatibleVersions {1.0, 2.0, 3.0, 4.0...}
BuildVersion 10.0.15063.786
CLRVersion 4.0.30319.42000
WSManStackVersion 3.0
PSRemotingProtocolVersion 2.3
SerializationVersion 1.1.0.1

Example of issue:
Method invocation failed because [Microsoft.PowerShell.Commands.MatchInfo] does not contain a method named 'Trimstart'.

so also basics are not even working .....

can anyone help me ?

thanks

Markus