1. PowerShell and ConfigMgr – New cmdlets for 1511 and Beyond
Kaido Järvemets
Coretech A/S, Senior Consultant
Greg Ramsey
Dell Inc.
Dell - Internal Use - Confidential

2. Kaido Järvemets Greg Ramsey @kaidja @ramseyg Enterprise Mobility MVP44 18
Bunnies
Getting Caught in the Rain

3. Get the latest cmdlet library
Get-Module -Name ConfigurationManager | Select-Object Version
Download:

4. Get the latest cmdlet library

5. ConfigMgr 2012 R2+ cmdlets
ConfigMgr Version
Cmdlets count
Comments
ConfigMgr 2012 SP1
471
PowerShell support
ConfigMgr 2012 SP1 CU1
511
ConfigMgr 2012 R2
560
ConfigMgr 2012 R2 CU1 / CU2 / CU3
562
ConfigMgr 2012 R2 CU4
597
Standalone update for ConfigMgr 2012 R2
622
ConfigMgr 1511 Standalone update
634
module version
ConfigMgr 1601 Standalone update
654
module version
ConfigMgr 1604 Standalone update
733
Get-Command -Module ConfigurationManager | Measure-Object

6. New with CB
Improved Performance for cmdlets that utilize configuration items and applications. Cmdlets such as Set-CMConfigurationItem, Remove-CMApplication, and others are now significantly faster.
Configuration item cmdlets (such as Set-CMConfigurationItem) now ensure that they are always using the latest revision of a configuration item. In prior releases, cmdlets would exhibit undefined behavior if run against a previous revision of a configuration item.

7. New with CB - 2
Max results - In previous releases, cmdlets would fail after a certain number of results was returned (by default, this was 1000 results or a value specified through Set-CMQueryResultMaximum.) This behavior is now disabled by default and all matching results will be processed. This change was made to avoid issues around undefined cmdlet behavior when large result sets were returned. To restore the original behavior, set $Global:CMPSEnforceMaxResults = $true.

8. Configuration Manager console trace logging
The Cmdlet Library now has the ability to output Configuration Manager console framework trace logging for additional troubleshooting details. This should only be used for troubleshooting purposes.
To enable this logging, set $CMPSAdminConsoleFxTrace = 1 and $DebugLogging = Continue. By default, “Warning” and higher severity messages are logged when console trace logging is enabled. To configure the logging level, set [Microsoft.ConfigurationManagement.ManagementProvider. ConnectionManagerBase]::SmsTraceSource.Switch.Level.

9. Wildcard Handling (link)
The new optional paramters DisableWildcardHandling and ForceWildcardHandling-DisableWildcardHandling allow for cmdlets and parameters that support wildcard ("*" or "?") values to forcibly parse the parameter as a literal value instead of a wildcard value.
Consider the following scenario: You have two applications: "My IT Application" and "My*Application." The cmdlet Get- CMApplication -Name My*Application will return both "My IT Application" and "My*Application." If the intent is to retrieve only "My*Application," you can add DisableWildcardHandling to the cmdlet parameters to retrieve a match.
The ForceWildcardHandling parameter restores pre-R2 CU1 behavior and allows for many string-based cmdlet parameter arguments to be recognized as wildcard values instead of literal values. This parameter may cause cmdlets to behave in unexpected or unsupported ways and should be used with great care.
A warning message will be written to the PowerShell output stream when internal query behavior is being changed by these parameters.
Notice that, although all Configuration Manager cmdlets support these new parameters, the parameters may not be used or honored in all circumstances.
The DisableWildcardHandling and ForceWildcardHandling parameters cannot be used at the same time. If you use both parameters at the same time, cmdlet execution fails.

10. Some Get cmdlets now have a Fast parameter
Lazy Properties
Some Get cmdlets now have a Fast parameter
This allows you to filter out lazy properti values
You can suppress the warnings
$CMPSSuppressFastNotUsedCheck = $true.
1604 new stuff

11. DEMO

12. And Then …