Making PowerShell Cmdlets Discoverable in SCCM
Presently the PowerShell Cmdlets for SCCM require use from the console or running a separate script like below.
Import-Module "$($ENV:SMS_ADMIN_UI_PATH)\..\ConfigurationManager.psd1" # Import the ConfigurationManager.psd1 module
Set-Location "$((Get-PSDrive -PSProvider CMSite).Name):" # Set the current location to be the site code.
An alternative would be two options (Neither means re-writing the Configuration Manager console.
One. Create a shortcut to launch the above script as a "PowerShell Configuration Manager Console"
Two. Leverage some variant on a solution found here on the TechNet Script Repository which drops in a Hardlink with MKLINK pointing to the Configuration Manager BIN folder with the correct name for the PowerShell module, and adding it to the standard PowerShell discoverable path.
Both approaches would help meet the community need without re-writing the Configuration Manager console.
1702 has added support for logical path (approach 2). See https://docs.microsoft.com/en-us/powershell/sccm/configurationmanager/1702_release_notes for more details.