Skip to main content

Worklet: Automox OS Upgrade to Latest Windows10 OS version


Show first post

67 replies

askornia
Forum|alt.badge.img
  • Novice
  • 20 replies
  • December 7, 2020

Doing this prompts this message in the activity report:

The Upgrade will commence shortly. Your PC will be rebooted. Please save any work you do not want to lose.

Since I’m assuming it’s running silently, I’m not 100% if it’s actually upgrading or doing anything, so I’ll let it run tonight and check back in tomorrow morning. I appreciate the speedy recommendation!


You can tell if its working by the presence of an Upgrade Assistant process running in the background. The script only calls the executable and exits. It doesnt continue running with the upgrade tool. This does it make a bit more difficult to guage progress.


  • Novice
  • 5 replies
  • December 17, 2020

Just wanted to say thanks for this script. Powershell is not my strong suit and I just used this to update the first 100 machines to 20H2 last night with a simple copy & paste. We’ll see how the rest go!


  • Novice
  • 5 replies
  • December 30, 2020

So I spoke too soon. This was working great for a while and has now ceased to function. It seems to coincide with the 1.0-30 agent. I’m now seeing this error in the activity log:

Failed to download ISO at path specified. At C:\ProgramData\amagent\execDir939412927\execcmd817330194.ps1:145 char:9 + throw “Failed to download ISO at path specified.” + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + CategoryInfo : OperationStopped: (Failed to downl…path specified.:String) [], RuntimeException + FullyQualifiedErrorId : Failed to download ISO at path specified. COMMAND TIMED OUT.


jasonehand
Forum|alt.badge.img
  • Novice
  • 11 replies
  • December 30, 2020

Hmmm, make sure your virus software or firewall has this path whitelisted. We have Sophos for both and I remember going in and whitelisting that entire amagent directory globally. Maybe that will help.

Jason


  • Novice
  • 23 replies
  • January 12, 2021

@askornia
Can you run the ISO manually and it passes the eval checks?
I know my hardware (Lenovo) is still unable to upgrade from 1909 > 2002/20H1 due to issue with a driver for an SSD.

https://support.microsoft.com/en-us/help/4592819/error-when-plugging-in-a-thunderbolt-nvme-ssd


Tony-Automox
  • Automox Employee
  • 35 replies
  • January 15, 2021

Shouldn’t there be an assignment to $iso at the top of the evaluation? Would it be:
$iso = ‘C:\Windows\Temp\Windows10.iso’


jasonehand
Forum|alt.badge.img
  • Novice
  • 11 replies
  • January 15, 2021

Yup, that line at top worked, thanks!

Jason


  • Rookie
  • 0 replies
  • February 24, 2021

Hey Guys

This is Carlos, I need help Deploying this. Every time I run the Worklet I am successful with ISO download, Mount with D Drive ISO in reports also get that computers are about to RESTART but it never does I get an ACCESS DENIED can someone help, please?

ERROR: Program ‘setup.exe’ failed to run: Access is denied

VERBOSE: Attempting to generate a 64-bit windows 10 iso download link VERBOSE: Attempting to download windows 10 iso to ‘C:\Windows\Temp\Windows10.iso’ WARNING: The Upgrade will commence shortly. Your PC will be rebooted soon. Please save any work you do not want to lose
image


  • Novice
  • 14 replies
  • March 3, 2021

Good afternoon all–

I have tested this worklet on several PC’s and it appears to work fine. My question is more concerned with the logistics of rolling this out to several hundred PCs—most of them located outside of our main building location. Since this takes over an hour to complete and reboots the PC without warning, how have you been working with users to upgrade PCs? Are you notifying groups of users in advance to make sure they have their PC powered on? Are you doing it in the evening? Are there any issues with users that shut down their PC in the middle of the process? Any insight would be greatly appreciated.

Thanks,
Dave


  • Novice
  • 14 replies
  • March 3, 2021

I am trying this method now but I don’t seem to get any response on my test PC. It’s just replacing that last line in the remediation code, correct? I see the Powershell task kickoff in Task Manager and it seems to run a few minutes and then disappears. I don’t received any notifications and can see no other signs of the Upgrade Assistant running.


  • Novice
  • 23 replies
  • March 3, 2021

@djdink828
If you’re upgrading from 1903 or later to 20H2, I would just use the feature enablement update rather than the full iso install.


  • Novice
  • 14 replies
  • March 4, 2021

Rob, are you referring to this process:

https://support.microsoft.com/en-us/topic/feature-update-through-windows-10-version-20h2-enablement-package-02d91e04-931e-f00d-090c-015467c49f6c

Will this work for Win 10 Pro versions earlier than 2004?

Also, excuse my Automox ignorance, I’m new, but how would this be applied in Automox if it can be done?

Thanks in advance for your help.

Dave


  • Novice
  • 23 replies
  • March 4, 2021

@djl52602

You can read Automox’s guide here - Controlled Windows 10 Feature Updates through Automox Patching

Essentially you have a worklet that runs this “Worklet: Enable Controlled Windows 10 Feature Updates through Automox Patching” - just change the $rInfoValue variable to whatever version you want to upgrade to, i.e 20H2.
This sets a registry entry telling Windows that the version you can upgrade to is XXX.

Then from there, you create a patch policy that installs ‘Feature Upgrades’.
I.e. an advanced policy I use that has a scope like this:
Make sure this policy has a reboot otherwise it will not install

Make sure you apply the worklet and policy to the group(s) that contain the devices you want to be updated.

In short:

  • worklet to set the target version
  • patch policy to install the feature upgrade

  • Novice
  • 14 replies
  • March 4, 2021

Thanks Rob, I tried this several days ago and hosed two PCs but I think I did it wrong. I’ll follow your directions tomorrow and try another test. Thanks again.

Dave


  • Rookie
  • 3 replies
  • March 10, 2021

I have run into the same issue but can see the feature update available in the windows UI but nothing through automox. Looked for the reg key as well but no luck yet the feature updates appears released to the machine. If anyone has any advice I would appreciate it!


  • Novice
  • 14 replies
  • March 12, 2021

Sorry, deleted this post…I was posting in wrong topic area.


Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings