Configuration Manager



adk 1703 missing tabs sccm

ADK 1703 Missing Tabs in SCCM

ADK 1703 missing tabs in SCCM. I ran into a weird issue today after upgrading one of our customers to ADK 1703. We previously upgraded SCCM to version 1702 but choose to wait with ADK because of the driver signing issue. When we finally upgraded ADK to 1703 and created a new boot image, the tabs in SCCM to service the new 1703 boot image where missing and I could not add any drivers or optional components with the console.


Deploy NET Framework 4.7

How to Deploy .NET Framework 4.7 With SCCM

How to deploy .NET Framework 4.7 with SCCM. This step-by-step guide will hold your hand through the entire process from downloading the .Net Framework, creating the application and deployment types in SCCM with silent installer, and deploying .Net Framework 4.7 to a collection of computers


create sccm boot image using dism

Create SCCM Boot Image using DISM

How to create SCCM Boot Image using DISM. This is a step-by-step guide where we create a boot image to be used with Configuration Manager from scratch using only Windows Assesment and Deployment Kit and DISM.


No Picture

My take on the 70-695 certification exam

Today I passed the 70-695 certification exam “Deploying Windows Desktops and Enterprise Apps”, and became MCSE: Mobility. You need 700 points to pass, and I got a score of 800. This is my take on the exam and tips on what to focus on.



SCCM Upgrade stuck checking prerequisites

SCCM Upgrade Stuck Checking Prerequisites

Today I upgraded a customer to SCCM 1702, but I ran into an issue that made things difficult. For some reason, they had a SCCM upgrade stuck checking prerequisites. A previous hotfix that was not installed had been in this state for a very long time and blocked all upgrades for them. Restarting SMS_Executive service or even rebooting the server did not fix this, and the option to upgrade was not available as SCCM thought some other upgrade was running a prerequisite check. This is how I fixed it.


BIOS Compliance with SCCM

Manage BIOS Settings with SCCM Compliance Settings

Today’s blog post explains how to mange BIOS settings with SCCM compliance settings. We will  create a configuration item to enable LAN / WLAN switching in BIOS on HP Elitebook G2 and G3 computers. I will also show how you can list out every BIOS setting in Powershell so you can create a BIOS configuration baseline that works for your environment.


Computers that failed a task sequence - Configuration Item

Computers that failed a Task Sequence – Configuration Item

I recently discovered some computers that had a folder named “C:\_SMSTaskSequence”. This indicates that a previous task sequence failed, as a task sequence that completes successfully will clean up after itself and not leave junk behind. So I wanted to know how many where affected, and I wanted our helpdesk technicians to investigate the computers.


ConfigMgr Client Health

ConfigMgr Client Health version 0.5.3

I have just released version 0.5.3 of my client health check script and I’m happy to announce that ConfigMgr Client Health finally supports logging to a file share. This update also includes a rewrite of the code to make it much cleaner to read and understand.


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.





No Picture

Task Sequence has failed with the error code 0x80070070

Task Sequence has failed with the error code 0x80070070 and how to solve it.  We got this error last week for a customer who is still running Windows 7, but ADK is version 1511 (Windows 10). The error code indicates there is not enough disk space on the drive, and is usually a result of weird disk partitioning or WinPE booting into a small Bitlocker partition.



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.


No Picture

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.


PowerShell

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.