PowerShell Profiles – The structure of your _PSH_BASE.ps1 file

In my previous post PowerShell Profiles – The profile.ps1 file I showed you my profile.ps1 file. In this post, I’ll show you a way to structure your base file, so that you can use it for your functions and aliases. Make sure that you always use max 2 files. 1The first file is your profile.ps1 file and the other file is this _PSH_BASE.ps1 file. If you use like 3 or 4 files, it can take a couple of seconds to load your PowerShell session.

Continue reading PowerShell Profiles – The structure of your _PSH_BASE.ps1 file

PowerShell Profiles – The profile.ps1 file

Welcome to this blog series about PowerShell profiles. I’m using PowerShell profiles for a couple of months now to make life a lot easier. To start this blog series, I would like to show you my Profile.ps1 file. It’s located in “C:\Users\<Your username>\Documents\WindowsPowerShell”. Because I use my PowerShell profiles at multiple locations such as my work notebook, home computer and sometimes at projects, I need to make sure that my PowerShell script home is always right so that the rest of the PowerShell profile is able to load successfully. That’s why I have these commands at the beginning of my profile:

Continue reading PowerShell Profiles – The profile.ps1 file

Windows Continuum

Microsoft heeft tijdens het Microsoft Ignite evenement een nieuwe feature van Windows 10 getoond, genaamd Continuum. Met Continuum is het mogelijk om je telefoon of tablet in een desktop te veranderen.

Joe Belfiore (Corporate Vice President, Operating Systems Groupq @ Microsoft) liet vol trots deze nieuwste ontwikkeling zien. Je telefoon staat, in de meest ideale situatie via Bluetooth, in verbinding met toetsenbord en muis. Door de telefoon op een beeldscherm aan te sluiten, schakel je automatisch van telefoonmodus naar een beperkte desktopomgeving. Voor zover te zien was, zijn alleen Modern Apps in deze omgeving te gebruiken. Een interessante ontwikkeling wanneer je voornamelijk de Office Suite als Word, Excel, PowerPoint en Outlook gebruikt, gezien deze (hoewel in een beperkte vorm) beschikbaar zijn als een Modern App. Dit versterkt het motief voor bedrijven om Modern Apps te blijven ontwikkelen, omdat deze straks op verschillende Windows devices te gebruiken zijn. Zo ontwikkel je een enkele app voor telefoon, tablet, laptop, desktop en zelfs voor de Xbox. Als documenten vervolgens overal beschikbaar zijn door OneDrive for Business, kan dit een ideaal werkpaard voor onderweg zijn.

Continue reading Windows Continuum

Windows 10 – Intel HDMI Audio doesn’t work

After installing Windows 10 on my production device (with a Windows 8.1 Hyper-V VM as back-up, of course), I had an issue with the HDMI Audio of my Dell Latitude E6540 notebook. I found some topics online about setting the default format of the Audio device, such as sample rate and bit depth, but that doesn’t work for me.

Continue reading Windows 10 – Intel HDMI Audio doesn’t work

SCCM 2012 R2 SP1 – Make Windows 8.1 drivers supported on Windows 10 with PowerShell

I had an issue within my lab with deploying Windows 8.1 drivers to Windows 10 with SCCM 2012 R2 SP1. It isn’t possible to make all Windows 8.1 drivers compatible with Windows 10 within the SCCM 2012 R2 SP1 console with just one click. Because I was running within a lab environment and I only had 2 driver packages for Windows 8.1 x64, I was able to make the drivers available for deployment to all platforms. You can do this with the magic of PowerShell:

Continue reading SCCM 2012 R2 SP1 – Make Windows 8.1 drivers supported on Windows 10 with PowerShell

Windows 10 – SCCM 2012 R2 SP1 fails with error 0x80070032

I was deploying Windows 10 with SCCM 2012 R2 SP1 and the task sequence failed after “Installing device drivers” with error code 0x80070032 (or 80070032). The “Auto Apply Drivers” task works fine, but doesn’t install a lot of drivers.

The smsts.log file:

Dism failed with return code 50 Failed to add driver to driver store. Code 0x80070032 Failed to provision driver. Code 0x80070032 Exiting with return code 0x80070032


  • Make sure you’re using the latest MDT version, compatible with Windows 10.
  • Make sure you’re using at least ADK 10.
  • Check if your boot image has OS Version 10 or higher. If not, create a new boot image with MDT or ADK.

Manually remove SCOM 2012 or SCOM 2007 R2 Agent

I was doing a migration project from System Center – Operations Manager 2007 to System Center – Operations Manager 2012 R2. Some computers had troubles with the upgrade of the agent. I first tried to do a client push deployment. 80 % of the installations succeeded, but I had a couple of computers with failed installations/upgrades.

1. Start the agent installation manually on the failed computer. Run the MOMAgent.msi installer.
2. Click “Next”. Accept the terms and click “I agree”.
3. Notice the “Upgrade” button instead of the “Install” button.
4. Close the setup and check the solution below.


I was able to fix this to remove the product registry key of the SCOM 2007 Agent. You can find it at HKEY_CLASSES_ROOT\Installer\Products\. Search for a key with ProductName “System Center Operations Manager 2007 R2 Agent”. Back-up your registry and remove the key. Try the setup again and notice the “Next” button instead of the “Upgrade” button. The agent push will work now.