Skip to main content

PS + SCCM

Collection of all my ConfigMgr + PowerShell posts, because :

Below pic says it all 


  1. PowerShell + SCCM 2012 : Get Started with CM Cmdlets  [PSBUG : Hangout Video @Youtube]
  2. PowerShell + WMI : Static & Instance Methods
  3. PowerShell + SCCM 2012 : Boundaries
  4.  PowerShell + SCCM 2012 R2 : Create Folders to organize 
  5. PowerShell + WMI Hangout with Stephane Van Gulick
  6. PowerShell + ConfigMgr : KickStart (Video Recording for PoSHBreakfast]
  7. PowerShell + SCCM : WMI Scripting
  8. PowerShell + SCCM : Run Configmgr cmdlets remotely



Rest of the posts:

  1.  PowerShell + SCCM 2012  R2 Installation
  2.  PowerShell + SCCM 2012 R2 - Discovery
  3. Use PowerShell to Remove Packages in Bulk from DP (independent of the ConfigMgr PS Module)
  4. PowerShell + SCCM 2012 - Extending Discovery
  5. PowerShell + SCCM 2012 R2 : Adding Roles & Client Settings (Device & User) 
  6. PowerShell + SCCM 2012 R2 : Client Push Installation 
  7. PowerShell + SCCM 2012 R2 : Create an Application (from MSI) & Deploy it
  8. PowerShell + SCCM 2012 R2 : Deploy PowerShell Scripts
  9. PowerShell + SCCM 2012 R2: Get the Client Info Easy Way
  10.  PowerShell + SCCM 2012 R2: Get the Device/ User Info WMI Way 
  11. PowerShell + SCCM Tip: Get MachineName for a User
  12. PowerShell + SCCM 2012 Tip : Get OS Inventory
  13. PowerShell + SCCM 2012 : Create Supersedence Rule
  14. PowerShell + SCCM 2012 : Create Dependency Rules
  15. PowerShell + SCCM 2012 : Automate Patching
  16. PowerShell + SCCM 2012 : Get-DPContent
  17. PowerShell + SCCM : POSH Deploy (Tool to automate Query Based deployments)
  18. PowerShell + SCCM 2012 : Create Packages and Programs

Other Resources:

Popular posts from this blog

Test connectivity via a specific network interface

Recently while working on a Private cloud implementation, I came across a scenario where I needed to test connectivity of a node to the AD/DNS via multiple network adapters.  Many of us would know that having multiple network routes is usually done to take care of redundancy. So that if a network adapter goes down, one can use the other network interface to reach out to the node. In order to make it easy for everyone to follow along, below is an analogy for the above scenario: My laptop has multiple network adapters (say Wi-Fi and Ethernet) connected to the same network. Now how do I test connectivity to a Server on the network only over say Wi-Fi network adapter?

PowerShell + SCCM : Run CM cmdlets remotely

Today I saw a tweet about using implicit remoting to load the Configuration Manager on my machine by Justin Mathews . It caught my eye as I have never really tried it, but theoretically it can be done. Note - The second tweet says "Cannot find a provider with the name CMSite", resolution to which is in the Troubleshooting section at the end.

PowerShell : Trust network share to load modules & ps1

Problem Do you have a central network share, where you store all the scripts or PowerShell modules ? What happens if you try to run the script from a network share ? or if you have scripts (local) which invoke scripts or import PowerShell modules stored on this network share ? Well you would see a security warning like below (Note - I have set execution policy as 'Unrestricted' not 'bypass' here): Run a .ps1 from the network share Well this is a similar warning, which you get when you download scripts from Internet. As the message says run Unblock-File cmdlet to unblock the script and then run it, let's try it.