Today, when you install the CM Console, the PowerShell module will be placed under the %CMInstallDirectory%\AdminConsole\Bin\ConfigurationManager.psd1

This makes sense given where the user is choosing to install the console, and that's fine. But placing it here off the beaten path means that it is not importable using PowerShell's module autodiscovery features. For instance, if a module is found in any of the standard user or system paths (or registered under the $ENV:PsModulePath) the user can easily import the module without having to specify the full path, a big user quality of life win. This is the way that SQL Server handles their modules, and they are the golden child, beloved by all PowerShell nerdoes like me.

So, my suggestion is to continue placing it where it is today, and also register the path using the standard mechanism, excerpted below.

[Environment]::SetEnvironmentVariable("PSModulePath",$p)

https://msdn.microsoft.com/en-us/library/dd878350(v=vs.85).aspx

We are using PowerShell as a frontend for creating applications. As default we create multiple deployment type, each of them intented to run in certain environemts. These environemts are defined in some custom global conditions.

When creating the deployment type we can very easily identify which global contitions shold be set as requirement. But we miss a Powershell cmdlet to automize this task. Instead we rely on the application creator to remember to add these conditions.

So far I have found a PS-script that can add one of the build-in conditions, but it fails when trying to add a custom made condition.

Monthly updating of applications like FlashPlayer, Java, Chrome, Reader DC, Office 365 Client, etc. are repetitive and tedious, so I like to automate monthly applications updates as much as possible. When creating a new application using powershell, I cannot set the "Uninstall content setting" located under the Deployment Type and the Content tab. This allows me to save on downloading large sets of files to uninstall when either an "MSIEXEC /X {GUID}" handles it with no files required, or something like Office 365 Client where 1.5 GB is needed to install, but only 5MB or so to uninstall.

The command I figure this should be a part of is both, "Add-CMMsiDeploymentType" and "Set-CMMsiDeploymentType". Something like "-UninstallContentSetting" with set values of : <SameContent | NoContent | DifferentContent>. Then you'd need another parameter to specify the location if you choose "DifferentContent", something like "-UninstallContent" or alias "-UninstallContentLocation" with a <String> path to the folder.

Without this command capability automation is broken and I have to manually make the change. (I do have automation breaks with Detection Methods and Requirements as well due to complexity of trying to use the PS method, but back to the point). If I've missed something and this is indeed available already, do let me know how to do it.

My idea is to have the scenario described below supported.

When running Save-CMSoftwareUpdate command on a CMSite-PSDrive that connects to a ConfigMgr site in a different domain (used Get-Credential to pass credentials in New-PSDrive call) than the user account the PowerShell window is running as, I get error 'The RPC server is unavailable'.

I can successfully change location to the PS drive, and run other ConfigMgr PS cmdlets.

Commands:
New-PSDrive -Name <sitecode> -PSProvider 'CMSite' -Root <siteserverFQDN> -Credential (Get-Credential)
Set-Location <sitecode>:
Save-CMSoftwareUpdate -SoftwareUpdateName <name> -DeploymentPackageName <name> -Verbose

Verbose output from Save-CMSoftwareUpdate call:

VERBOSE: Start: Execution of WQL query: Select * from SMS_SoftwareUpdatesPackage where Name='Office 2016'
VERBOSE: Finish: Execution of WQL query: Select * from SMS_SoftwareUpdatesPackage where Name='Office 2016'. Processed 1 results in 00:00:00.0533413.
VERBOSE: Performing the operation "Save" on target "SoftwareUpdate: Name="Office 2016"".
VERBOSE: Start: Execution of WQL query: SELECT * FROM SMS_SoftwareUpdate WHERE LocalizedDisplayName IN ( 'Update for Microsoft Office 2016 (KB4018322) 64-Bit Edition' )
VERBOSE: Finish: Execution of WQL query: SELECT * FROM SMS_SoftwareUpdate WHERE LocalizedDisplayName IN ( 'Update for Microsoft Office 2016 (KB4018322) 64-Bit Edition' ). Processed 1 results in 00:00:00.0858704.
VERBOSE: Start: Execution of WQL query: select distinct cic.ContentID from SMS_CIToContent cic where cic.CI_ID=16796196 and cic.ContentID not in (select pc.ContentID from SMS_PackageToContent pc where pc.PackageID='ECN0006C') and (cic.ContentLocales='Locale:0' or cic.ContentLocales = 'Locale:9')
VERBOSE: Finish: Execution of WQL query: select distinct cic.ContentID from SMS_CIToContent cic where cic.CI_ID=16796196 and cic.ContentID not in (select pc.ContentID from SMS_PackageToContent pc where pc.PackageID='ECN0006C') and (cic.ContentLocales='Locale:0' or cic.ContentLocales = 'Locale:9'). Processed 1 results in 00:00:00.0000256.
VERBOSE: Start: Execution of WQL query: select * from SMS_PackageToContent where ContentID=16790019 and PackageID='ECN0006C'
VERBOSE: Finish: Execution of WQL query: select * from SMS_PackageToContent where ContentID=16790019 and PackageID='ECN0006C'. Processed 0 results in 00:00:00.
VERBOSE: (SMS_PackageToContent.ContentID=16790019,PackageID='ECN0006C') does not exist or its IsContentValid returns false. We will (re)download this content.
VERBOSE: Using 64-bit content downloader
VERBOSE: Downloading update content CI_ID='16790019' Content Source Path='\\ecn-badcm\updatePackages\Office 2016' Download Location='' Provider='ecn-badcm.BoilerAD.Purdue.edu' Second Chance='False'
VERBOSE: Result: 1722 (0x000006ba)
Save-CMSoftwareUpdate : The RPC server is unavailable
At line:1 char:1
+ Save-CMSoftwareUpdate -SoftwareUpdateName "Update for Microsoft Offic ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : InvalidResult: (Microsoft.Confi...reUpdateCommand:SaveSoftwareUpdateCommand) [Save-CMSoftwareUpdate], Win32Exception
+ FullyQualifiedErrorId : DownloadContentError,Microsoft.ConfigurationManagement.Cmdlets.Sum.Commands.SaveSoftwareUpdateCommand

Save-CMSoftwareUpdate : The following updates failed to successfully download: Update for Microsoft Office 2016 (KB4018322) 64-Bit Edition
At line:1 char:1
+ Save-CMSoftwareUpdate -SoftwareUpdateName "Update for Microsoft Offic ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : InvalidOperation: (Microsoft.Confi...reUpdateCommand:SaveSoftwareUpdateCommand) [Save-CMSoftwareUpdate], InvalidOperationException
+ FullyQualifiedErrorId : DownloadUpdateFailed,Microsoft.ConfigurationManagement.Cmdlets.Sum.Commands.SaveSoftwareUpdateCommand

The recent Powershell features like 'Run Script' and allowing them to be added directly to a Task Sequence step are fantastic, but things are beginning to feel somewhat fragmented.

It would be great if SCCM had a central script repository, maybe backed by git, that we could pull scripts from as opposed to adding them.

This would allow us to easily use the same code in a Task Sequence and a 'Run Script' without having to maintain it in multiple places. Perhaps we could even add a special Powershell Script Package Program type that would pull a script from the central repo and run it.