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
Hi Tore,
ReplyDeleteWhen 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
hi,
DeleteAs 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.