Changed

Removed the auto-import of ConfigurationManager module, and instead made it a required module in the manifest. This is to better define the dependency and provide a more "traditional" experience. Therefore, you must import the ConfigurationManager module before you can use PSCMContentMgmt.
Previously, users did not need to specify -SiteServer and -SiteCode parameters. This is because variables $CMSiteServer and $CMSiteCode were automatically defined upon import of PSCMContentMgmt (from attempting to read the registry and WMI to determine where the SMS Provider was and the site code). This behaviour has now changed. You must specify -SiteServer and -SiteCode, but only for at least one command. The same parameter values are remembered for subsequent commands within the same session. See README.md for more details.

Assets 3

16 Oct 13:47

Release 1.8.20201016.0

Fixed

Create PS drive for site code and server if it does not exist upon importing the module

Assets 3

25 Sep 09:39

Release 1.7.20200925.0

Assets 3

08 Sep 11:14

Release 1.6.20200908.0

Updated various help content to better describe -ObjectID parameter and ObjectID property

Corrected CIM query in Start-DPContentRedistribution so it actually works. Added error handling to in the event an object is not found to be already distributed to a distribution point.
More accurate error ID to reflect a win32 error code for access denied in Import-DPContent

Assets 3