As you all may know, Microsoft tried something new with 1909 where they included it in many of the monthly Cumulative Updates (CU’s) for 1903. This means that if you were to run Windows Update on a fully patched 1903 and select the 1909 optional upgrade, your system would simply reboot and then be at 1909. All the update did was turn on the new features.
If however, you manually kicked off the setup.exe from within the 1909 ISO, you would go through the normal, 40 minute plus process of doing a in-place upgrade.
My question is: Will BigFix offer that “quick” version of the patch so that we can easily upgrade exsiting 1903 endpoints to 1909 without having to deploy the ISO as we traditionally do?
Hi Alexa…
I have been taking a look at this as an option. too.
As far as I can see there are two pre-requisites for the quick update.
According to MS you need.
Servicing stack update for Windows 10 version 1903 that is dated September 24, 2019 or a later servicing stack update
Cumulative Update for Windows 10 version 1903 that is dated October 8, 2019 or a later cumulative update
Before you can use KB4517245 to install the 1909 feature update after a reboot.Some of these have been superseded
I threw a quick and dirty relevance together and am working on the action script, but here goes… Please feel free to pick it apart.
exists wmi
name of operating system starts with “Win10”
exists ((string value of property “HotFixID” of it) of select objects “HotFixID from Win32_QuickFixEngineering where HotFixID = ‘KB4520390’” of wmi) as string OR exists ((string value of property “HotFixID” of it) of select objects “HotFixID from Win32_QuickFixEngineering where HotFixID = ‘KB4521863’” of wmi) as string OR exists ((string value of property “HotFixID” of it) of select objects “HotFixID from Win32_QuickFixEngineering where HotFixID = ‘KB4525419’” of wmi) as string OR exists ((string value of property “HotFixID” of it) of select objects “HotFixID from Win32_QuickFixEngineering where HotFixID = ‘KB4524569’” of wmi) as string
exists ((string value of property “HotFixID” of it) of select objects “HotFixID from Win32_QuickFixEngineering where HotFixID = ‘KB4517389’” of wmi) as string OR exists ((string value of property “HotFixID” of it) of select objects “HotFixID from Win32_QuickFixEngineering where HotFixID = ‘KB4522355’” of wmi) as string OR exists ((string value of property “HotFixID” of it) of select objects “HotFixID from Win32_QuickFixEngineering where HotFixID = ‘KB4524570’” of wmi) as string OR exists ((string value of property “HotFixID” of it) of select objects “HotFixID from Win32_QuickFixEngineering where HotFixID = ‘KB4530684’” of wmi) as string
not exists ((string value of property “HotFixID” of it) of select objects “HotFixID from Win32_QuickFixEngineering where HotFixID = ‘KB4517245’” of wmi) as string
operating system as string contains “(1903)”
Those seem to show all my 1903 machines that are ready for the upgrade.
Hope that helps
Thanks! I’ve created a Fixlet with that relevance and will see how many are returned. I’ll download KB4517245 and add that as an Action and test.
I tested and it says the update isn’t applicable to your computer. So there must be another requirement. This was when installing windows10.0-kb4515384-x64_d7e55a2589b1c603138c533b27b0d1222de975db.msu
Im seeing the same thing… checking
Check to see if
exists ((string value of property “HotFixID” of it) of select objects “HotFixID from Win32_QuickFixEngineering where HotFixID = ‘KB4524569’” of wmi) as string
Is installed.
I found the .cab file with a google search… Not sure about the source validity but anyway.
downloaded the file, renamed it to KB4517245.cab and then uploaded it to the server , then the actionscript looks like.
wait “{pathname of system folder}\DISM.exe” /Online /Add-Package /PackagePath:"{pathname of client folder of current site & “__Download\KB4517245.cab”}"
action requires restart
After the restart, the endpoint shows the usual message about applying updates, reboots and then shows updating again and then , depending on the endpoint’s spec, within 3 mins, comes up and logs in with little or no other user interaction…
With Alexa’s help and testing,. we believe we have this running correctly.
The Dismn command line needs to have /NoRestart and possibly /Quiet added to the end. I use both, I think Alexa doesn’t use the /Quiet.
The only “issue” I can see is if the current prerequisites are superseded, a “new” 1903 machine will only get the latest versions of the prerequisites rendering the machine. not relevant.
It also “completes” with a 3010 code (requires restart) even after it reboots, so just be aware of that.
My action now looks like
wait “{pathname of system folder}\DISM.exe” /Online /Add-Package /PackagePath:"{pathname of client folder of current site & “__Download\KB4517245.cab”}" /NoRestart /Quiet
waithidden shutdown -r -t 0
action requires restart
When complete, it exits with a code of 0
I no not use the post action restart and it seems fine.
So I used this as the relevance without changing anything except for the quotes which were giving syntax error. For some reason the one pete added are not accepted in relevance for bigfix.
name of operating system starts with “Win10”
exists ((string value of property “HotFixID” of it) of select objects “HotFixID from Win32_QuickFixEngineering where HotFixID = ‘KB4520390’” of wmi) as string OR exists ((string value of property “HotFixID” of it) of select objects “HotFixID from Win32_QuickFixEngineering where HotFixID = ‘KB4521863’” of wmi) as string OR exists ((string value of property “HotFixID” of it) of select objects “HotFixID from Win32_QuickFixEngineering where HotFixID = ‘KB4525419’” of wmi) as string OR exists ((string value of property “HotFixID” of it) of select objects “HotFixID from Win32_QuickFixEngineering where HotFixID = ‘KB4524569’” of wmi) as string
exists ((string value of property “HotFixID” of it) of select objects “HotFixID from Win32_QuickFixEngineering where HotFixID = ‘KB4517389’” of wmi) as string OR exists ((string value of property “HotFixID” of it) of select objects “HotFixID from Win32_QuickFixEngineering where HotFixID = ‘KB4522355’” of wmi) as string OR exists ((string value of property “HotFixID” of it) of select objects “HotFixID from Win32_QuickFixEngineering where HotFixID = ‘KB4524570’” of wmi) as string OR exists ((string value of property “HotFixID” of it) of select objects “HotFixID from Win32_QuickFixEngineering where HotFixID = ‘KB4530684’” of wmi) as string
not exists ((string value of property “HotFixID” of it) of select objects “HotFixID from Win32_QuickFixEngineering where HotFixID = ‘KB4517245’” of wmi) as string
operating system as string contains “(1903)”
Has anyone else made any progress on this? I’m looking at using WSUS to deploy as there seems to already be a process in place to handle the update 1903 to 1909 but i’d rather not. Do we know if we will have an official solution from Bigfix for this?
