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

SSMS 17 - Start Powershell returns 'No SQL Server cmdlets found on this computer' but sqlserver module is installed and works outside of SSMS 17

When trying to create Dynamic Distribution Groups via Powershell with the Set-DynamicDistributionGroup cmdlet, there are many filterable properties. The properties are supposed to be what you see via 'Get-Recipient'.

One Property in particular, 'Capabilities' does not appear to be valid for use with Set-DynamicDistributionGroup.

Could this be added, as it would be very useful to filter people based on what license(s) they have assigned.

When trying to create a Dynamic Distribution Group via PowerShell using Set-DynamicDistributionGroup, TechNet lists many filterable properties, including 'ProhibitSendReceiveQuota'. However, it doesn't appear to actually work.

The only way I've gotten it to produce any results is to say:

Get-Recipient -RecipientPreviewFilter {(ProhibitSendReceiveQuota -lile "*")}

If you do a 'Get-Recipient', 'ProhibitSendReceiveQuota' isn't even a property returned.

https://technet.microsoft.com/en-us/library/bb125127(v=exchg.160).aspx

Bug filing.

According to other articles I read this problem may be prevalent in other/all AD cmdlets. To work around this bug you have to use | Select * | as an intermediate step to correctly bind to your $computername/$name parameter.

When creating a new service, I would like to set the user account to a virtual service account. Since the -Credential parameter expects a PSCredential object, which doesn't seem to accept predefined local accounts at all, this isn't currently possible.

Having a -VirtualAccount switch would be great.

Get-MpPreference .AttackSurfaceReductionRules_Actions returns incorrect value(s) compared to registry. Specifically a value of 2 is always returned for rule id BE9BA2D9-53EA-4CDC-84E5-9B1EEEE46550. There may be other anomalies that I haven't yet found for different rule id's.

If I scheduled a job for weekly running on specific days it will always fail with error code Task Scheduler stopped instance "{[GUID]}" of task "\Microsoft\Windows\PowerShell\ScheduledJobs[myjob]" as request by user [my windows logon]

However the job works with the -daily switch. It only fails with -daysofweek

Test-Path returns false for valid paths contained within quotes. See example below. Due to the frequent need to quote paths containing spaces, this leads to needless bugs.

Repro follows.

PS C:\WINDOWS\system32> Test-Path 'C:\Windows\System32\ntdll.dll'
True

PS C:\WINDOWS\system32> Test-Path '"C:\Windows\System32\ntdll.dll"'
False