onfigmgr

SCCM 2012 R2 – Remove Expired Updates

Hi All, every time i need to remove an expired update from a baseline is always the same…select the baseline, show members, select the updates i want to remoe…edit membership… This action takes time, imagine that you need to do it once a month (yes, patch Tuesday). but if you have many sw update groups?!?!? yes, you’ll spend bit of time doing it. based on this, i’ve created a powershell script as well as a console extension that will allow you to remove all expired updates from a sw update group. To do it, download the RemoveExpiredUpdates zip file, extract and add the files to the following places: RFL-SUP Deployment Group.xml to <CM12R2Console Installation Path)\XmlStorage\Extensions\Actions\2853886b-cce5-4ed4-af43-df69efb2e7d8 and <CM12R2Console Installation Path)\XmlStorage\Extensions\Actions\bb1a22d4-816f-438c-b6e7-51cbc210112f (change the CM12R2Console to the path of the console :)) RemoveExpiredUpdates.ps1 to C:\Scripts\CM12R2Console on the same computer where you installed the CM12 R2 Console Note: the RFL-SUP Deployment Group.xm has the same name as the a…

SCCM 2012 – Non-Compliant

Hi All, Have you ever needed to know which computer is in a non-compliance state for a baseline? Well..there are 2 options. Option 1 is the open reports (Monitoring->Reports->Compliance and Settings Management->Summary compliance by Configuration Baseline) and then drill down to see what machines are not compliant… Another option is to create a collection, and the best option to do it is on the Deployments tab for the Baseline, select the deployment you want, right click, select create new collection and select non-compliant and follow the wizard. All steps are easy, isn’t it? but if you have many deployments and don’t want create a collection for it? or if you don’t want create a collection even if you have only 1 deployment? and let’s face the fact..opening the report will take too much of our time… based on this, i’ve created a powershell script as well as a console extension…

SCCM 2012 – Retire Application

Hi All, SCCM 2012 (and 2012 R2) have an option called Retire that allows you to block creation of new deployment of the application. It is useful when using with Supersedense when you’re upgrading an application and you don’t want deploy the old application anymore. Per documentation, When you retire an application, it is no longer available for deployment but the application and any deployments of the application are not deleted. Existing copies of this application that were installed on client computers will not be removed. If an application that has no deployments is retired, it will be deleted from the Configuration Manager console after 60 days. However, any installed copies of the application are not removed. Well…this is really interesting, it is more interesting that you can “reinstate” the application if needed, but be aware, only retiring the application will not block people from installing. if have an active…

SCCM 2012 – Removing old revision

Hi All, every time you change something to any application or deployment type, SCCM keeps a history of this change and will delete it, after specific period of time. This behaviour can be changed on the site maintenance, task Delete Unused application revisions. the default is 60 days. Anyway, i wanted to know how many revisions i had for each application as well as the application version. To do it, i used powershell the posh script below will shows you the Application Name, Version and number of revisions.

  Easy, but what if i don’t want to wait for SCCM to delete it for me, what can I do? well..there is another powershell for it. the below powershell will delete all revisions that is not the last one, leaving you with only 1 review, the last one.

  This script is really useful when you have many people…

SCCM 2012 – DeploymentType – empty SDMPackageXML

Hi All, while working on a script (that will be published here soon), i noticed that it was failing after i had tested it…but why was not clear. After troubleshooting, i discovered that the SDMPackageXML was empty. i really don’t know why it happen, but it should not happen anyway, once i discovered this, i wanted to see how many DT had this issue and it was almost 50% of my lab…but how did i found out?! Easy, i ran the following powershell

  as you will see, every single App/DT that appear in this list, has problem with the SDMPackageXML, but how to fix it? Well it was simple, you just need perform a change on the DT, but if you have many!?!?!?. Again, i used powershell the below powershell will add an “A” to the administrative comment as well as remove it

  but now, you…