Finding and Removing Unused ConfigMgr Drivers

This is this the third and final part of my series on driver management in ConfigMgr. Part 1 can be found here. Part 2 can be found here. The script can be found here. Driver Cleanup Have you ever tried to clean up old or unused drivers in ConfigMgr and quickly became overwhelmed? It can become pretty hard to determine what drivers are truly not in use since if you attempt to import drivers that already exist, which is pretty common, you can quickly run into drivers that are in several driver packages and driver categories which can make for a challenging puzzle to unravel. Read more →

ConfigMgr Client Push Installation Failing

Retrieved package version 23. But it is smaller than the expected version 24. Content is not ready yet. GetDPLocations failed with error 0x87d00215 Failed to get DP locations as the expected version from MP server.domain.local. Error 0x87d00215 You can find this in the ccmsetup.log on a client device. This happened to me after a 2012 r2 to Current Branch upgrade. (SQL, OS, everything) At some point the client package got out of whack apparently. Read more →

Removing ConfigMgr Drivers with missing source files

You can find the drivers with missing source files removal script here. This is the second article in a series a driver articles. You can find part 1 here. Driver management with ConfigMgr can be a bear at times. Without some attention to detail towards organizing your driver source locations it is not uncommon for driver source files to be deleted before the driver is removed from ConfigMgr, by accident or otherwise. Read more →

Import boot image drivers from existing boot image

With the new “Current Branch” model of ConfigMgr and Windows 10 we can expect a faster release cycle of the ADK, which means new boot images pretty regularly! Creating new boot media is really simple. However, reimporting all of your required drivers into that boot image can be a real chore. Here is a script that identifies drivers in a source boot image and imports them into a destination boot image. Read more →

“Mfc120u.dll is missing from your computer” when viewing Status Message Queries in ConfigMgr Console

When trying to view status message queries from the ConfigMgr console – The program can’t start because mfg120u.dll is missing from your computer. Try reinstalling the program to fix this problem. You are missing the VCRuntime 2013 x86. The installer can be normally be found at \primarysiteserver\sms_xxx\client\i386\vcredist_x86.exe or from Microsoft Read more →

Maintaining Your Office 2016 Installation Source

Deploying an updated Office installation has always been an annoyance of mine. It is ideal to be able to deploy a fully updated Office installation so you don’t have to run a software update scan and then wait for all the office patches to download and install. Having to install less software updates can reduce your deployment or build and capture times significantly. To avoid all of this legacy overhead, use Office 365 Click to Run edition. Read more →

Enable Isolated User Mode in Windows 10

UPDATE This for any Windows 10 release pre 1607 (Anniversary Edition). With 1607 this functionality is baked into Hyper-V. You need to enable Isolated User Mode in Windows 10 if you want to, among other things, utilize the virtual TPM chip in generation 2 virtual machines. If you try to start a gen 2 virtual machine with the TPM chip enabled but without Isolated User Mode enabled you get this error message: Read more →

Git and the PowerShell prompt

There is lots of information out there on using Posh-Git. This is nothing new, its just a little helper for me since I have been recently been shuffling through workstations at an alarming rate. If it is useful for you as well, stellar! Install GIT From an elevated powershell prompt: Install-Package posh-git Modify your profile for PowerShell and PowerShell_ISE Reference for PowerShell profiles Read more →

Nested PowerShell Modules

If you are curious about how to import a PowerShell module that has dependencies on other modules this can be done with the module manifest file (PSD1). You can do some pretty wild stuff with a PowerShell Module Manifest file. For starters here is a great outline how that file works with some decent examples. Here is an example of how to have nested PowerShell modules. The nested module in this case being a C# compiled . Read more →