Windows 10 1703 - PDQ Deploy

Comments

41 comments

  • Christian Bacher

    It's great to hear that a simple cmd line makes so many admins happy :-).
    I haven't look into a 1803 upgrade yet, it's to early.

    But if someone use bitlocker read this blog:

    https://blogs.technet.microsoft.com/mniehaus/2018/05/02/new-upgrade-to-windows-10-1803-without-suspending-bitlocker/ 

    1803 comes with a new command-line /Bitlocker

     

    0
    Comment actions Permalink
  • Shad Behnke

    See if I can resurrect this thread. I'm trying to update many machines from a few different versions and everything seems to run until about the 30 minute mark and this happens

    Command script returned error code -2147024809 when using quiet parameter but just runs and runs with the above cmd..

    Watching the PC everything is running from the installer to updates then around 25-30 minutes this happens. Going to try to run it and get some logs...

    Any help is appreciated!

    0
    Comment actions Permalink
  • Jamie Sandell

    This works for us (going to 1803):

    Choose an install step and point the install file field to the setup.exe. Tick the include entire directory. Have this command line /auto upgrade /quiet /noreboot /ShowOOBE none /Compat IgnoreWarning /Telemetry Disable

    If you need a reference for the flags, check them - here

    0
    Comment actions Permalink
  • Steve Elgan

    Just came across this thread and am testing it out in our environment. This is much simpler than what I was trying to do using MDT. See https://github.com/OneWorldCHC/PDQDeploy-UpgradeWin10

    For those using this setup.exe method, I would encourage you to use OSBuilder from David Segura to automatically inject the latest SSU, LCU, and LSU into your install media. It'll save time for the patching process. https://www.osdeploy.com/osbuilder/overview

    Steve

    0
    Comment actions Permalink
  • Jason Riggs

    Has anyone tested this with 1809 update yet?

    0
    Comment actions Permalink
  • Mike Pullen

    Watching... (Am also wondering about upgrading machines 1803->1809...)

    0
    Comment actions Permalink
  • Steve

    I haven't had much luck upgrading from 1709 Pro to 1809 Pro. It times out. When running manually get an error that the /Auto switch isn't recognised.

    I need to spend some more time with this but it would be great if PDQ themselves created a package for upgrading....?

    0
    Comment actions Permalink
  • Steven Powell

    I have upgraded 4 1803 boxes to 1809 (pro) only issue i had was running Office apps for first time, Have to run them as administrator and also make sure user has access to C:\programdata\microsoft folder

    \\path\setup.exe /auto upgrade /quiet /migratedrivers all /ShowOOBE none /Compat IgnoreWarning /Telemetry Disable
    

    I set the time out to 180 minutes an let the install reboot if needed.

    0
    Comment actions Permalink
  • Sean Merrell

    Has anyone tried this with the new 1903? Do we have to jump to 1803 before we can do 1903, or can we just skip 1803?

    0
    Comment actions Permalink
  • Alex Alexandre

    i am trying the upgrade a couple pcs to 1903 i cant get it to work error

    0
    Comment actions Permalink
  • Alex Alexandre

    setup enter image description here

    0
    Comment actions Permalink

Please sign in to leave a comment.