How can I in-place upgrade to Windows 10 1803 using Powershell App Deployment Toolkit and SCCM (System Center Configuration Manager) 2nd edition

Introduction

Back in May i did a post on how to leverage Powershell App Deployment Toolkit and Configuration Manager to in-place upgrade to Windows 10 1803. Find the post in the link below:

Today I’m providing you with an update on the topic and giving you an updated version of the content. Note that the basic instructions for using all of this, is still found in my original post above.

What’s new?

I have slightly modified the Powershell script initiating the in-place upgrade task sequence to no longer include the registry tattooing.

Instead, this is done in the end of the actual task sequence. See below snippet. This allows the application in the Software Center to be rerun in case something goes amiss POST running the application. Note that this will yield an error in the application until the Application Deployment Eval Cycle has run and picked up the detection method.

Execute-OSUpgrade.ps1

The script initiating the task sequence now looks like this:

1803UpgradeHasRun.ps1

For your convenience, the Powershell script tattooing the registry is provided below (this is the step I highlighted in the snippet from the task sequence above):

Powershell App Deployment Toolkit

In regards to the Powershell App Deployment Toolkit, following are added/changed:

  • Testing for attached power adapter
    • If no power adapter is attached, allow the user to attach one and continue
    • If no power adapter is attached, the script will exit the installation with exit code 1618 (fast retry in the application, which means SCCM will retry the installation 10 times every 2 hours)
  • Allows the user to say no to proceeding the installation, which again will exit the installation with exit code 1618 and thus acts like a sort of deferal

Download the changes here: PSADT_1803UpgradeV2.zip (253 downloads)

The battery check looks like below pictures.

End user experience

All of above was added/changed due to some comments on my previous post. Thank you for the feedback – much appreciated.

Please let me know if this is useful. Enjoy πŸ™‚

11 thoughts on “How can I in-place upgrade to Windows 10 1803 using Powershell App Deployment Toolkit and SCCM (System Center Configuration Manager) 2nd edition”

  1. This is fantastic! Thank you for sharing this, it has certainly made my life a lot easier when it comes to upgrading Windows 10. Just one thing… it would be handy to have a connected ethernet check as well as the battery check. I have to update a number of Surface devices and need them to be plugged into via the ethernet adaptor before upgrading.

    • Thank you! Checking on Ethernet cable is perfectly doable, but in my test wasnt 100% accurate on all models why I didnt include it πŸ™‚

  2. Hi Martin,

    has your Upgrade OS Task Sequence changed in any significant manner to cater for these enhancements?
    Looking at the TS snippet you provided above it’s a bit different to the original one you shared in Part 2.

    I’m still working on pulling all this good stuff together along with WaaS stuff from Mike Terrill and Gary Blok.

    You three should all work together on the Mother of all IPU task sequences!

    • Hi Andy, yeah I believe it changed slightly. I’m still using Powershell App Deployment Toolkit to initiate the TS, but the TS I’m sharing in part 2 of my WaaS posts, is the one I’m using today. For one I’m back at tattooing the registry for the detection method in the the actual PSADT application, but enabled the option to repair it. It’s just minor things that have changed πŸ™‚ Thank you for kind words – that’s something that motivates me πŸ™‚

  3. Hi Martin, your blogs for WaaS are a great inspiration! Thank you so much for all the scripts πŸ™‚
    This is a very hot topic and especially improving the user experience in the upgrades is a important thing!
    Have a nice spring and be proud of your work!

  4. I’ve just been reading through your Toast notification post which of course linked through to this. Amazing work, thank you for a) explaining your methods b) letting other people use your code and c) making our work better!

  5. Hi Martin,

    In your Toast notification, what species the logo in the top left hand corner as the Software Center logo? I’ve amended one for a deployment and its the Powershell logo? thanks,

    • Hey Jimbo, it’s the app doing the notification, more specifically the changes to the registry I’m doing during the script. I’ve included Powershell as a second option if the toast is used on a device without sccm client, but the default should be Software Center.

Leave a Comment

This site uses Akismet to reduce spam. Learn how your comment data is processed.