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

Monitoring Orchestrator runbook events from Operations Manager

Today I will follow up on my colleague’s post Mr ITblog (Knut Huglen) about monitoring Orchestrator Runbook events.  He has build a nice double up SNMP loopback feature that does self monitoring in Orchestrator resulting in entries written to a special Windows Eventlog. Now we need to raise alerts in SCOM when one of his runbooks fails or sends a platform event, who knows there could be trouble lurking in his paradise.

We are not going to do anything fancy, however these are the steps we will be focusing on today:
Create a Management Pack for our customizations Create rules that collects the events from the orchestrator serverOff we go then and fire up the SCOM console and a powershell window. First we create a MP, I am going to use powershell to do this, however you may use the SCOM console as well (Administration – ManagementPacks – Action: Create Management Pack):



Import the Management Pack into SCOM and move on to the Authoring section in the SCOM console. Create a new rule:



Give the…

Powershell – Log like you mean it

How do you do logging in powershell? Why should you do logging? What should you log? Where do you put your log? How do you remove your log? How do you search your log? All important questions and how you answer then depends upon what your background is like and the preferences you have. This will be a 2 part blog post and this is part 1.


Why should you log?

Well it is not mandatory, however I have 2 reasons:
Help with debugging a script/module/functionSelf documenting script/module/function
Firstly; Do you know any program that does not contain any bugs? Working with IT for the last 2 decades, I cannot name one. When you create scripts/modules/functions, you will create bugs, that is where they live and try to make your life a living mess.

Secondly: Adding a little extra information to your logging will make them self documenting. Do you like writing documentation? Well I normally am not fond of it and use logging while debugging to get two birds with one stone.


What should you log?

Anyt…

Powershell - List information about your WIFI networks

This is just a quick post about this new function I have created. Basically this is a text-output to powershell object output function that uses netsh to query the WIFI information. This illustrates the importance of changing the authentication level on your WIFI-network. No matter if you use WEP/WPA/WPA2 your password is available in clear text in your profile.



Cheers

Tore