Skip to main content

ConfigMgr – Scripting with powershell module


I read David O’Brien’s post about automation with SCCM. He identified an issue with the SCCM-Powershell module that requires a manual “job” before you can start to automate with the module. You have to start Powershell from the SCCM-console to import the certificate that the module is signed with. Read all about it in his post. I am only providing a solution for you so you do not have to do regular “manual” labour (no pun intended).


Above you will find an DSC script resource you can use in your configurations and a function you can use in your scripts. Look me up on Twitter if you have any questions or leave a comment.

Cheers

Tore

Comments

  1. Hi Tore,

    When I tried to run your code above in Admin mode, I keep getting the following error on the first line:

    This is the line it is referring to: Configuration SCCM

    Configuration : The term 'Configuration' is not recognized as the name of a cmdlet, function,
    script file, or operable program. Check the spelling of the name, or if a path was included,
    verify that the path is correct and try again.

    At C:\Users\fk41337\Cdev\ConfigSCCM.ps1:1 char:1
    + Configuration SCCM {
    + ~~~~~~~~~~~~~
    + CategoryInfo : ObjectNotFound: (Configuration:String) [], CommandNotFoundException
    + FullyQualifiedErrorId : CommandNotFoundException

    ReplyDelete
    Replies
    1. hi,

      As it says bellow the script listing, it contains to different things. A function to use in a powershell script AND a Desired State Configuration(DSC)(keywork Configuration). Desired state is only available in Powershell 4 and later. I suspect that you have tried to run the DSC-configuration on an earlier version of powershell.

      Delete

Post a Comment

Popular posts from this blog

Serialize data with PowerShell

Currently I am working on a big new module. In this module, I need to persist data to disk and reprocess them at some point even if the module/PowerShell session was closed. I needed to serialize objects and save them to disk. It needed to be very efficient to be able to support a high volume of objects. Hence I decided to turn this serializer into a module called HashData. Other Serializing methods In PowerShell we have several possibilities to serialize objects. There are two cmdlets you can use which are built in: Export-CliXml ConvertTo-JSON Both are excellent options if you do not care about the size of the file. In my case I needed something lean and mean in terms of the size on disk for the serialized object. Lets do some tests to compare the different types: (Hashdata.Object.ps1) You might be curious why I do not use the Export-CliXML cmdlet and just use the [System.Management.Automation.PSSerializer]::Serialize static method. The static method will generate t

Toying with audio in powershell

Controlling mute/unmute and the volume on you computer with powershell. Add-Type -TypeDefinition @' using System.Runtime.InteropServices; [Guid("5CDF2C82-841E-4546-9722-0CF74078229A"), InterfaceType(ComInterfaceType.InterfaceIsIUnknown)] interface IAudioEndpointVolume { // f(), g(), ... are unused COM method slots. Define these if you care int f(); int g(); int h(); int i(); int SetMasterVolumeLevelScalar(float fLevel, System.Guid pguidEventContext); int j(); int GetMasterVolumeLevelScalar(out float pfLevel); int k(); int l(); int m(); int n(); int SetMute([MarshalAs(UnmanagedType.Bool)] bool bMute, System.Guid pguidEventContext); int GetMute(out bool pbMute); } [Guid("D666063F-1587-4E43-81F1-B948E807363F"), InterfaceType(ComInterfaceType.InterfaceIsIUnknown)] interface IMMDevice { int Activate(ref System.Guid id, int clsCtx, int activationParams, out IAudioEndpointVolume aev); } [Guid("A95664D2-9614-4F35-A746-DE8DB63617E6"), Inte

Something completely different – PoshARM

I needed a project for my Xmas holiday and I needed something remotely work related. Thus the dubious PoshARM PowerShell module was born and brought to life during my Xmas holiday. Simply put it is a module that lets you build – for now – simple Azure Resource Manager (ARM) templates with PowerShell .  The module can also import templates from a file or from the clipboard/string. Your partial template or ready made template can be exported as a PowerShell script. This blog post will walk you through how to use it and the features that is currently implemented.  Update 08.02.2017: The module is now published to the PowerShellGallery ( https://www.powershellgallery.com/packages/posharm ). It is still in beta version, however test coverage have increased and some bugs have been squashed during the testing. Also help is present, however somewhat lacking here and there. Update 18.01.2017: The module is now on GitHub. Here is the link to the repro  ( PoshARM on GitHub ) What