DexterPOSH's Blog

This is one of the many posts to follow on my experiments with the new Application Model introduced in Configuration Manager 2012. In this post will use PowerShell to create a new application, deployment type (from a MSI) and then finally deploy it to a machine. So without further delay..... Let's get to it  Create the Application using New-CMApplication cmdlet: New-CMApplication -Name "Quest Active Roles Managment Shell for AD" -Description "Quest Snapin for AD Admins (64-bit only)" -SoftwareVersion "1.51" -AutoInstall $true The above will create a Application Object in ConfigMgr which can be used in Task Sequences as well (-AutoInstall $true ). Now let's open the Console and have a peek at the properties of the Application created. The Set-CMApplication Cmdlet can also be used to set property on the Application Object later.  Let's create a new App Category and then add the above application to it. New-CMCatego

In this post, would share PowerShell way of enabling Client Push Installation on a Site . Divided into 3 Steps: Enable Client Push Installation Create Boundary Group, Add Boundary and set Content Location Distribute the Config Mgr Client Package Enable Client Push Installation After loading the ConfigurationManager PowerShell module, if we search for the commands with noun clientpush we get following output: PS DEX:\> gcm -Noun *clientpush* -Module configurationmanager CommandType Name ModuleName ----------- ---- ---------- Cmdlet Get-CMClientPushInstallation configurationmanager Cmdlet Set-CMClientPushInstallation configurationmanager Now one can go and read up help for these, I personally prefer the Online version of the help as it shows the Parameter sets and is always up to date too. How to do that

Post #3 in the PowerShell with ConfigMgr 2012 series. Trying to do the things mentioned in this post --> @ Windows-Noob Before I begin, I had an interesting discovery. While trying out the Cmdlets in the ConfigurationManager Module, I had been facing a lot of issues....like in the Discovery Post few weeks ago was not able to use the -ActiveDirectoryContainer parameter. So had to resolve to WMI way. When I was trying out things mentioned in this post with PowerShell I faced a lot of Errors and asked around, finally was able to get a workaround. I have ConfigMgr 12 R2 Preview installed on the server and the Eval version is out. So I downloaded the ConfigMgr 12 R2 Eval version and just did a re-install of the ConfigMgr Admin Console on one of my machines. Now the downside of this is the GUI won't connect to the Site Server because of the version mismatch but the PowerShell module works fine (this is what I was after). I still have old ConfigMgr Admin Console installe