DexterPOSH's Blog

This is the second post in continuation of Getting Started series (not diving into the WMI as of now), hoping to cover few of the common tasks which ConfigMgr admins perform in the series. Get Started with the CM Cmdlets  Boundaries [UPDATE] - Thanks to TechSmith   for giving me a free MVP copy of the Camtasia & SnagIt. Now will try to put links to youtube videos instead of the animated GIF's. So first of the simple tasks which you can do with CM cmdlets is on the topic managing boundaries. Not gonna show each and every cmdlet but few use cases. Note - Assuming you have the PowerShell console loaded with the CM Module (see the Getting Started post for this) First let's ask PowerShell which cmdlets have *boundary* pattern in the noun : PS> Get-Command -Module configurationmanager -Noun *boundary* CommandType Name ModuleName ----------- ---- -------...

This post will quickly cover on how to start using PowerShell with ConfigMgr. It's good to see that ConfigMgr Admins are finally embracing the Shell :)  Planning to have one of these getting started hangouts for PowerShell Bangalore User Group (@PSBUG) in near future. There are essentially two routes: Using ConfigurationManager Cmdlets Using WMI / CIM (next post probably) Using ConfigurationManager Cmdlets ConfigMgr starting from 2012 SP1 has got the official PowerShell support, which means when you install the ConfigMgr console on a machine then you will get a PowerShell Module along with it in the below location : <drive>\Program Files (x86)\Microsoft Configuration Manager\AdminConsole\bin Don't worry you don't have to remember this. There is an environment variable SMS_ADMIN_UI_PATH which holds this piece of information for you (Note the path we need is till bin folder only )  The best way to get the CM cmdlet...