Windows 10 Feature Update
Comments
-
Here are the command line switches I found out.
/Push
/Install
/SetupFile
/SkipSelfUpdate
/ReUseCatalog
/SkipEULA
/OobeUi
/OobeRS2Ui
/EosUi
/PostEosUi
/TenSUi
/PreventWUUpgrade
/SetOobeTourniquetRunningRegKey
/SetPriorityLow
/UninstallUponExit
/UninstallUponUpgrade
/ForceUninstall
/MinimizeToTaskBar
/ShowProgressInTaskBarIcon
/SkipCompatCheck
/QuietInstall
/NoRestartUI
/EnableTelemetry
/InstallationFolder
/Edition
/Language0 -
Is it upgrading to 1909 version or latest?
Ex. now latest 2004. is it upgrade 1909 or 2004?
0 -
@Dmitrij Kondrasov, this procedure downloads the file:
https://download.microsoft.com/download/9/b/f/9bf08afb-bfd8-488a-9ce6-90134cea4d8f/Windows10Upgrade9252.exe I just downloaded and ran this on my 1909 computer and it says "Thank you for installing the latest Windows", with no option to upgrade.Then I went to this page: https://www.microsoft.com/en-us/software-download/windows10 and downloaded the upgrade assistant from there. The download URL is different: https://download.microsoft.com/download/8/3/c/83c39dca-2d27-4c24-b98b-0a4d6d921c80/Windows10Upgrade9252.exe
Same .exe filename, but different URL paths.
It looks like this procedure links to the 1909 upgrade assistant only.
0 -
Just checked. This procedure upgrading to latest build. For now it 2004.
0 -
I can seem to import the script after downloading it.....tried it on multiple computers...it just does not show.0
-
I cannot import the script after downloading it.....tried it on multiple computers...it just does do anything. neither does it show up in any of the folder in the Agent Procedure section/menu0
-
same here i cant import the script. Nothing shows on the tree of agent procedures.
0 -
You need to go to System > Server Management > Import Center to import this script. Not from Agent Procedures. As it says in the Installation Guide. LOL
0 -
I'm getting "File was not uploaded" when I try to import it via the Import Center.
0 -
hey Guys
I am testing this to upgrade from 1909 to 2009 directly.
It did the download of the ESD etc all ok and I think it did what it needed to do just fine but didn't reboot the computer.
Once I manually rebooted the computer, it started the actual upgrade of the OS.
Checking the log file called upgrader_default, I saw that it said "waitforrestart" so I assume it waits for reboot?
Is there a way to force the upgrader file to reboot the computer when it needs to?
The plan is to do this upgrade overnight so it has to reboot and not inconvenient the user, in case they reboot the computer during working hours.
BTW, this procedure itself finishes once the upgrader executable is launched with appropriate switches. The agent procedure successfully running doesn't check if the upgrade process itself went fine or not.
Anyone had this? The computer doesn't reboot to finish the upgrade? Would love to have it work properly.
Dhaval
0 -
Are you on SaaS or do you have your own VSA? I use this script to upgrade windows 7 machines and to update windows 10 machines. I have no issues with the script no rebooting the machines.
0 -
This should not depend on SAAS or On-Prem. There are a number of things that can prevent the update from starting, including free space, pending updates, pending reboots, O/S licensed, etc. This is why our tool has an optional and comprehensive pre-check mode you can run before actually downloading and running the updates. If the machine passes the check phase, it's got a great chance of completing the update without issue.
This is probably why the upgrade started after you rebooted - a pending restart flag was likely active.
Our experience has been that regardless of the initial platform build, the upgrade process takes just under 2 hours and performs 3-5 reboots. I've never had a machine not reboot after updating. If you aren't sure about pending updates/reboots, you can try starting with a reboot and then running the updater.
0 -
Hi everyone,
The procedure works fine in upgrading to the latest version which currently is 20h2 (2009). I would instead like the option to either choose which feature update to install or to always get the second to last one. My (current) goal is to upgrade to 2004 instead of 2009.
The procedure downloads the Windows10Upgrade.exe from the following link: (this one seems to always upgrade to the latest version (20h2/2009))
https://go.microsoft.com/fwlink/?LinkID=799445I managed to find these URLs online:
1903: https://download.microsoft.com/download/9/6/4/96409c48-4ad8-4660-8482-0ca61f05d58b/Windows10Upgrade9252.exe
1909: https://download.microsoft.com/download/9/b/f/9bf08afb-bfd8-488a-9ce6-90134cea4d8f/Windows10Upgrade9252.exe
2004: https://download.microsoft.com/download/8/3/c/83c39dca-2d27-4c24-b98b-0a4d6d921c80/Windows10Upgrade9252.exe
2009/20H2: https://download.microsoft.com/download/7/a/a/7aa0472b-49a0-46d1-b651-e8a2c53f1fe4/Windows10Upgrade9252.exeHowever, every single one of them seems to upgrade to the latest version anyway (20h2/2009). Does anyone know a way to upgrade to 2004 (so the second to last feature upgrade currently). I'm trying to acomplish this using a Kaseya procedure or a Powershell script that I will call using Kaseya, any help would be much appreciated.
0 -
Ivo - the URLs for the upgrade trigger a process to determine the current build of the local machine and then download the package to upgrade to the latest build. It's unlikely that those URLs will work the way you expect. You would need to identify the specific download package needed for a specific update, not the upgrader tool in the above links. You would need to identify specific packages to upgrade from the current to the specific build number. For your case, you might want to consider creating your own set of updaters using media from a 2004 ISO.
0 -
After importing the xml file, where does it go? I can't find it0
-
Running the upgrade procedure worked perfectly on my test rig that was on an 20H2 and I am now up to date on 21H1.
With the release of Win 10 21H1 however it has become apparent that Microsoft are not changing the ReleaseID value in the registry between 20H2 and 21H1 so it may be better to use CurrentBuild during the audit to distinguish between the two, 20H2 is 19042 and 21H1 is Build 19043.
0 -
I agree. Version 2009 refers to both 21H1 and 20H2. And I can't find anywhere that documents what this procedure refers to as a "version".
I would prefer it if the procedure could use the version listed in this Microsoft link - https://docs.microsoft.com/en-us/windows/release-health/release-information - which seems to be the standard reference.
Also note that the documentation should also point out that the references in the reports needs to be changed to refer to the actual Custom Variable if they are going to work. This was also omitted in today's IT Toolkit session.
0 -
I agree. Version 2009 refers to both 21H1 and 20H2. And I can't find anywhere that documents what this procedure refers to as a "version".
I would prefer it if the procedure could use the version listed in this Microsoft link - https://docs.microsoft.com/en-us/windows/release-health/release-information - which seems to be the standard reference.
Also note that the documentation should also point out that the references in the reports needs to be changed to refer to the actual Custom Variable if they are going to work. This was also omitted in today's IT Toolkit session.
0 -
I agree. Version 2009 refers to both 21H1 and 20H2. And I can't find anywhere that documents what this procedure refers to as a "version".
I would prefer it if the procedure could use the version listed in this Microsoft link - https://docs.microsoft.com/en-us/windows/release-health/release-information - which seems to be the standard reference.
Also note that the documentation should also point out that the references in the reports needs to be changed to refer to the actual Custom Variable if they are going to work. This was also omitted in today's IT Toolkit session.
0 -
Isn't software management supposed to take care of this? Why doesn't it?
0 -
I'm new to this, but I don't always see a needed Feature update after a scan and I don't see any other way of triggering this via Software Management.
0 -
Feature update for 21H1 is supported by Software Management, BUT the endpoint MUST be at least version 2004.
Prior versions will need to use this Upgrade Assistant process.
0 -
We are not using software management yet but I did find an article in Kaseya about enabling Microsoft Enablement Package Patch which is related to what Chris Hindson mentioned.
Windows 10 Feature Updates via Software Management (Microsoft Enablement Package Patch)
0 -
It would appear to me that Microsoft has decided that with 21H1 they will no longer update the ReleaseId and instead update the new Key added with 20H2 of DisplayVersion.
0 -
I guess I maybe really old school but I just use the View to tell me what OS version is installed from the Agent TAB.
Our network does NOT connect to MicorSoft (Firewall Blocked except for one IT Subnet) so this has not been an issue for me. ( by our choice - we do not want anyone doing any bypass updates on any devices)
I download the entire offline install package for any version into a Kaseya server folder.
For deploy: use the Application deploy to create the Setup.exe push ( from th efolder created with all the files\folders of the install) to the device with the parameters. I use this as my base for the deploy.
Then I edit this procedure:
writeDirectory - too push the folder to the device ( wherever you choose on the C:)
getVariable -Agent Install Drive (C:\) agentDrv to install the setup.exe
******* this is the original Deploy Procedure******
writeFile too push the setup.ext to the device ( wherever you choose on the C:)
executeFile runs setup.exe with /auto upgrade /quiet /showoobe none
****************************
sendEmail send email to me let me know the process has run
deleteDirectory Recursively remove the folders you added in the beginning
To Run: Create a Agent View to specify that version you are looking for and select the Devices in Agent Procedures to run anytime
Once it is built once, just change download folder and edit procedure to advance to next version.
This can be used to step older versions of win 10.
May not be the most elegant way to do it, but when something works....
0 -
Ken, would you share what IP ranges you blocked for microsoft? We use O365 on the cloud so i would need to keep access to that. But i would love to shutdown all the random updates that come whether you want them or not
0 -
wrong ken.
0 -
wrong ken.
0 -
wrong ken.
0 -
Sorry to ruffle someone feathers.
I am Kenneth L W Houtz 27 years IT
MS IP change all the time , it was a hit or miss but we started with the URLS
Careful not to shoot yourself in the Foot. Always test on your oen
As much as we hate to, we do allow O365 updates to run on their own
http://windowsupdate.microsoft.com
http://*.windowsupdate.microsoft.com
https://*.windowsupdate.microsoft.com
https://*.update.microsoft.com
http://download.windowsupdate.com
http://*.download.windowsupdate.com
http://ntservicepack.microsoft.com
There is always a constant license check that hits the firewall from random devices. Our block has never rejected a MS device registration/Activation from anyplace on the network
I would start obvious listed (http://*.windowsupdate.microsoft.com) and add a few at a time while testing.
I work for a County in MD. We have 600 Workstation with over 20 buildings in the county. 7 people on our team.
0
