Monthly Archives: February, 2015

When you install the latest cumulative update for System Center 2012 Configuration Manager (SCCM), it automatically creates 4 new packages for client, server and console updates. If you forget to clean up after each update, you’ll end up a situation like this: Unfortunately the SCCM user interface does not support multiselect and delete, so if you want to delete all these packages, you need to walk through the delete wizard for each package. That is both extremely boring but also takes a lot of time. So I wrote this little PowerShell script that will delete all post SCCM 2012 CU4…

This morning, I got call from one of our internal SCCM Admins that wanted to test the newly released SCCM 2012 R2 CU4 update in his lab environment. He had multiple test installations so he just picked an old one that he hadn’t used in a while and, without checking anything, he just ran the setup. He did follow my Quick Start Guide but he skipped the preparing and checking part. What could possible go wrong? Setup did update the Site successfully but when the creation of the packages started, the setup failed. He knows that I always like to…

Today (on February 2nd or the 3rd, 2015, depending on your current time zone) Cumulative Update (CU) 4 for ConfigMgr 2012 R2 was released. It’s a great update. Not only does it contains 25 updates but also 32 PowerShell fixes and 35 new PowerShell cmdlets. Amazing! Can’t wait to get this baby deployed in production Here’s a list of issues that are fixed: Client (1 fix) Software Distribution and Application Management (6 fixes) Network Access Protection (1 fix) Operating System Deployment (2 fixes) Administrator Console (1 fix) Site Servers and Site Systems (6 fixes) Mobile Devices (4 fixes) Migration (1…

Here is a list of all the 35 NEW cmdlets that was added in System Center 2012 R2 Configuration Manager CU4. More information and examples will be added to this post later. Add-CMDeploymentTypeDependency Add-CMDeploymentTypeSupersedence ConvertFrom-CMApplication ConvertFrom-CMConfigurationItem ConvertTo-CMApplication ConvertTo-CMConfigurationItem Get-CMClientOperation Get-CMCertificate Get-CMDeploymentTypeDependency Get-CMDeploymentTypeDependencyGroup Get-CMDeploymentTypeSupersedence Get-CMMigrationSource Get-CMObjectSecurityScope Get-CMQuery Get-CMSiteRole Invoke-CMQuery Invoke-CMSystemDiscovery Invoke-CMUserDiscovery Invoke-GroupDiscovery New-CMADGroupDiscoveryScope New-CMDeploymentTypeDependencyGroup New-CMEmbeddedObjectInstance New-CMEmbeddedProperty New-CMEmbeddedPropertyList New-CMQuery Remove-CMCollection Remove-CMDeploymentTypeDependency Remove-CMDeploymentTypeDependencyGroup Remove-CMDeploymentTypeSupersedence Remove-CMQuery Set-CMDeploymentTypeDependency Set-CMDeploymentTypeDependencyGroup Set-CMDeploymentTypeSupersedence Set-CMQuery Sync-CMMigrationSource /Enjoy

Introduction Installing this update is very similar to previous versions but a few things have changed since I did the last post on CU updates. In this blog post, I’ll walk you through the upgrade process step-by-step in a standalone primary scenario. The full list of fixes and a link to request the hotfix is available here: http://support.microsoft.com/kb/3026739/ As always, you should start by checking the health of the system, verify the backup, etc. At a minimum, you should check the following: Install any missing updates (security, critical and important). Verify you don’t have a pending restart. Verify that you…

When upgrading the System Center Configuration Manager (SCCM) client to a new version, most customers would prefer to create new collections for this task. As a cosultant I create alot of these “ad-hoc” collections every time I visit a customer, so I’ve created a small libary of PowerShell scripts that will help me create these collections really fast when I need them. Here is a simple PowerShell script that will create 2 kinds of collections that will help you for this specific task. #CLI – Client Version; That will have all clients with a specific client version. #CU – Cumulative…