There appears to be a bug when using this Cmdlet, where the -ResourceGroupName parameter incorrectly states that the parameter value for the resource group exceeds a length of 90 when a variable is used, i.e. $rgName (string length is actually 19 <CZEU2-APP-NP-RGP-01>. When the hard coded value of: "CZEU2-APP-NP-RGP-01" is used however, the Cmdlet works as designed.

I hope powershell have a cool module about the network tool ,make them work like tcpdump , netcat in linux.

It's very very cool things , will make me fly in our daily task.

Any group that contains a user account that is cross-forest to the group object is hitting the non-descriptive error in the title when running Get-ADGroupMember. I can successfully run the command with on groups where all members are in the same forest as the group object.

The current workaround is to use Get-ADGroup and expand the Members property and then make a subsequent Get-ADObject call for each member. This takes about 5x longer to run.

Add Smartcard support to Get-Credential in Powershell 7. Add a cmdlet for enumerating certificates on a smartcard

Accessing Active Directory Web Services (ADWS) by launching and running a number of PowerShell Runspaces in parallel from within the same process makes ADWS fail with error message "invalid enumeration context".

Apparently, the ActiveDirectory PowerShell module is not thread-safe.

Please fix soon. There is no workaround for this issue.

See this repository for steps to reproduce:

https://github.com/SetTrend/powershell-test

json is becoming the new standard (if not already)
It would be nice to have an import-json and a export-json as we have in xml/csv instead of the two steps process with get-content and convertfrom-json and convertto-json.

Make ConvertFrom-String available in PowerShell core as it's super useful when parsing txt files.

Get-ChildItem -LiteralPath doesn't support long path, for example:

Get-ChildItem -LiteralPath 'D:\aaaaaaaaaabbbbbbbbbbccccccccccddddddddddeeeeeeeeeeffffffffffgggggggggghhhhhhhhhhiiiiiiiiiijjjjjjjjjjkkkkkkkkkkllllllllllmmmmmmmmmmnnnnnnnnnnooooooooooppppppppppqqqqqqqqqqrrrrrrrrrrssssssssssttttttttttuuuuuuuuuuvvvvvvvvvvwwwwwwwwwwxxxxxxxxxxyyyyyyyyyyzzzzzzzzzz.txt'

Which path is longer than 260 bytes, even if the file DO exists in that path.

But `Get-ChildItem` WITHOUT `-LiteralPath` works well with that long-path file.

$PSVersionTable

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

Set-DfsrConnectionSchedule doesn't change a replication partner of a group to use custom settings. I've even waited a day and it didn't change it.

While the UI for ExchangeOnline and Office365 can use UTF-8 when creating new resources, the Powershell cmdlet cannot.

-Confirm & -WhatIf Optional Parameters not honoured on Remove-PrintJob even though they are included in documentation.

The `-NoEnumerate` switch doesn't work when when the input is named using the `-InputObject` argument in PowerShell version 5.1.

The following script returns `False`:

Function Test {Write-Output -InputObject (,'Test') -NoEnumerate}
(Test) -is [Array]

While this script returns `True`:

Function Test {Write-Output (,'Test') -NoEnumerate}
(Test) -is [Array]

$PSVersionTable

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

This issue doesn't appear with PowerShell Core 6.2

Hello, we've been using command Get-AuthenticodeSignature to validate a signed/time stamped file, and this works as expected in Server 2008 R2 and Server 2016 machines. But targeting the same file from Server 2012 R2 Powershell ISE, returns empty TimeStamperCertificate property. I've confirmed PS1, .NET framework and Authenticode module versions to be latest, and server patches are up to date. It seems that the root issue is within Microsoft.Powershell.Security library.

Thanks

Vlad

Since some version of Windows 10, creating a symbolic link should not require administrator privilege. In cmd, using mklink to create a symbolic link without administrator privilege works, but New-Item in PowerShell doesn't work.

Does DISM cmdlets have a GitHub repository so I can add and extend WinPE-DismCmdlets-Package?

Quoted feedback from documentation feedback provided by MSFT team below. (via @jordanmills)

> When resolving SRV records (example: Resolve-DnsName -Name "_kerberos._tcp.dc._msdcs.$env:userdnsdomain" -Type SRV), the cmdlets also attempts to resolve any returned A or AAAA records and sends them to the pipeline as a separate object collection. This breaks pretty much any attempt to sort, group, filter, or otherwise process the data. How can we make it not return A and AAAA records for SRV queries?

https://github.com/MicrosoftDocs/windows-powershell-docs/issues/302

A Git(hub) place for Windows PowerShell 5.1 code base (Win32/x64) suppository with changes, improvements, bug-fixes, NEW-Cmdlets, etc... merged back into itself.

When creating a new partition with the parameter UseMaximumSize, the partition is created with 1031680 bytes less than reported by the SizeMax value from the Get-PartitionSupportedSize cmdlet.

I tested this on Windows 2019 on ESX 6.7 and Azure.

To reproduce (example with a 10GB disk):

New-Partition -DiskNumber 2 -DriveLetter F -UseMaximumSize

(Get-PartitionSupportedSize -DriveLetter F).SizeMax
10720624128

(Get-Partition -DriveLetter F).Size
10719592448

Resize-Partition -DriveLetter F -Size 10720624128
Resize-Partition : Size Not Supported
Extended information:
The size of the extent is less than the minimum of 1MB.

Possibly related issue in https://windowsserver.uservoice.com/forums/301869-powershell/suggestions/36967870-get-partitionsupportedsize-and-msft-partition-clas