DexterPOSH's Blog

Well in the quest of automating ConfigMgr 07.....WMI is the key. Now this post isn't a primer on how to use WMI with PowerShell. There are very good resources which you can hit like: Free Ebook by Ravi Sir (PowerShell MVP) - " WMI Query Language via PowerShell " (referred to me by  @LaerteSQLDBA  :) ) Book by Richard Siddaway (PowerShell MVP) - " PowerShell and WMI " There are other good resources like  HeyScriptingGuy's  blog where one can serach for WMI tag, there is whole bunch of information out there on leveraging WMI with PowerShell. If you haven't checked out this yet then you are missing something very cool to manage your Infrastructure. That being mentioned the journey to exploring WMI starts by connecting to the SCCM Site System which has the SMS provider installed. Open the ConfigMgr console > Connect to your Central Site/Primary Site > Site Management > Right -click site ...select Properties. The information where SMS

Few months back, I made a resolution of automating the deployment process used in our Project, Scenario So if a User needs applications in their machine , they raise a request for the same. After the approval process it comes to our team and we handle the deployment of these apps to the User machines using SCCM 2007 (or ConfigMgr). So this is how we do it ....we have the QueryRules for the Application collection in place we just go there and add the machine name there manually in the Query Rule for the Application Collection.  To go with the post I have a test collection in place by the name " Deepak Test 1 "...So first I will be showing how we do this manually and then later on how I did it using PowerShell. There something called "Click Count" which is a rough count of how many mouse clicks am using to do these actions in ConfigMgr MMC Console (rough estimate) Click Count = 1 Manual Way Step 1. Right  Click and open the properties for