BIOS Upgrades for Meltdown/Spectre – HP Compaq Elite 8300 USDT

I was having an issue silently <hpqFlash.exe -s> upgrading the BIOS to the latest version for HP Compaq Elite 8300 USDT computers.

Everything seemed like it was working but after the reboot it was still at the same version.

I read the log files and pasted the warning in Google and found two results. Luckily this one had my answer.

The machines were sporting Version 2.06. I had to jump to Version 2.99 in order to then jump to version 3.06. Works flawlessly from our remote patching server.

The BIOS was too old to upgrade to the current version so I had to upgrade it twice like so.


Here is a nice tool to quickly check if you are compliant without having to use the Microsoft provided Get-SpeculationContol cmdlet.



ConfigMgr Windows 10 Updates Baseline – “Title does not contain” Criteria

I found this less than intuitive but it works. I need to create a Windows 10 Baseline for Windows updates and I am only concerned with Windows 10 x64 Version 1703.

I added the criteria “Title does not contain x86-based”, but wanted to add “Title does not contain the following: Version 1507, Version 1511, Version 1607, Version 1709, Version 1803, Version Next

I figured there is some update some where with (KB1507……, KB1511….) etc, so I included Version in the search string.

This is not possible since the interface only allows the OR operator and not the AND.


To resolve this, I created a Software Update Group using the initial “Title does not contain x86-based” called Baseline – Windows Updates – Windows 10


Then searched that SUG with “Title does not contain Version 1507″, then created a SUG with those results. Then I did the search for the other versions until I had the SUG I wanted.


I could have just manually removed these updates from the original “Title does not contain x86-based” SUG but being human, I prefer machines to do the work they are meant to do.

Finally, I had the SUG I wanted and didn’t have to download a whole bunch of updates I don’t need.


Thank to Dan Gleason from this thread.



PowerShell and ConfigMgr

I just set up a new computer to import all of the various PowerShell modules so I can have them all in one place.

I discovered that in order to connect to my SCCM site, I had to install the ConfigManager Console and use the following import-module command.

Import-Module (Join-Path $(Split-Path $env:SMS_ADMIN_UI_PATH) ConfigurationManager.psd1)

Now I can work with SCCM on the same computer where I develop all of my scripts.

And, this is how to import VMWare.PowerCLI

Find-Module VMware.PowerCLI
InstallModule Name VMware.PowerCLIScope CurrentUser