Deploy .NET Framework 4.6.2 with SCCM

How to Deploy .NET Framework 4.6.2 with SCCM

How to deploy .NET Framework 4.6.2 with SCCM. Easy step by step guide with pictures explaining how to create the application in Configuration Manager.

One of our customers that was still on .NET Framework 4.5.2 experienced problems with the December 2016 patches from Microsoft, one patch simply would not install and reported an error. Upgrading the customer to .NET Framework 4.6.2 solved their problem and all updates installed successfully. There was no reason why they didn’t upgrade, they where just that some applications would stop working and hesitated. So after upgrading them I decided to write this guide. Read More

ConfigMgr Client Health

ConfigMgr Client Health – Fix Broken SCCM Clients

Clients with a broken Configuration Manager Client is the worst. You lose management of the client, and it drags down compliance. I have even seen some broken clients report back as compliant while they are not. I’m aware about other community solutions to reinstall the client if broken, and they are all great solutions but I one of my customers had two specific issues with their clients that caused about 10% of the computers to not receive patches, and none of those solutions would fix their problem.

I needed a way to consistently check the health sccm client and automatically attempt to fix known errors. ConfigMgr Client Health was born. Read More

Computers not patched by SCCM due to cached Group Policy WSUS setting

One of my customers had a lot of computers that didn’t receive patches because of an old group policy setting cached on the client pointing to a decommissioned WSUS server. Specifying a WSUS server in GPO is not necessary when patching clients with software updates in SCCM. Removing this group policy fixed the issue on a lot of computers, but we still had too many computers that where not compliant. GPO cache on the clients was the issue. and this is how we fixed it. Read More


Automate Pre-Deploy Software to the User’s Primary Device with PowerShell

I want the OSD process to install all user applications if the primary user on the device is known. This is very simple to achive, all you need is an active deployment of the application to the user with the setting “pre-deploy software to the user’s primary device” enabled on the deployment. Only one problem, I had to enable it for 300+ deployments.

Its easy with PowerShell. Read More

SCCM Firewall ports required by clients

SCCM Firewall ports and network ports must be defined if you want manage clients across multiple networks. Configuration Manager to properly manage clients if some ports are not been defined and opened to allow for traffic to flow properly. Typical symptoms of failed network connectivity can be clients stuck with old configuration manager client, trouble to patch and deploy software. Here is a copy of my cheat-sheet that I use (or send to the network technicians) to make sure all required traffic is let through. Read More

CCMSetup Install Switches

CCMSetup Install Switches

With this post I want to explain the CCMSetup install switches as I get asked a lot how and when to use them. The Configuration Manager client is installed by launching ccmsetup.exe. This happens to all client installations, even if client push installation from the Configuration Manager console and task sequence installations with the setup windows and configuration manager step. Read More