Windows 10 1703 - PDQ Deploy

0

I'm having a hard time finding out if I can use PDQ to install/upgrade to 1703 on my Windows 10 machines.  All my machines currently have 1607, but I would like to test deploy 1703 to a couple.   I see (KB4015583) but is this the actual upgrade to 1703 or fixes for people that already have 1703. 

Cancel
login to comment
0

hi Christian,

thanks for suggestion but I have all my servers in the same place so I can't do that. :(

 

Cancel
login to comment

0

Hey everyone,


Just wanted to give a follow up.  I ended up deploying a WSUS server at one of our locations and using it to upgrade from 1607-1709 after posting here.  We're on the current branch with all updates managed using WSUS.  I had to get them updated quickly and just went the WSUS route.

 

Christian is right though, we have a DFS share and it's so much easier.

 

Thanks,
Donnie

Cancel
login to comment

0

Hi Massimo,

you can learn about the parameters here:

https://docs.microsoft.com/en-us/windows-hardware/manufacture/desktop/windows-setup-command-line-Options

I have 9 sites, but thanks to the DFS share i don't need different packages for each site.
If your 2 sites are in the same domain, you should think about a DFS share, makes deployment so much easier.

https://www.youtube.com/watch?v=aJ8PD1KBrtk

https://www.youtube.com/watch?v=o6pLhDKgdCM

Have fun

Cancel
login to comment

0

hi christian, it works for me: thank you so much!

to manage my organization (2 sites) i prefered use 2 different depoy folder (and 2 2 differente package too, of course), one for each site: deployment time is about the same now, but before this vpn was like a bottleneck!

now, for my knowledge, can you explain all the parameter you use?

 

Cancel
login to comment

0

Maybe the 32bit source files are corrupt or the Edition is not correct?

Start the Upgrade on the 32bit systen with a double click on the Setup.exe, maybe you get a better readable error message.

Cancel
login to comment

0

yes, I'm sure it's 32bit source file, and I get this error " setup.exe returned error code -1047526904"

I tried it for several types of PCs.

Cancel
login to comment

0

Hello Nada,

there is no difference between 32 and 64 bit, and yes i upgraded 32bit Systems this way too.


But be sure you don't try to Upgrade a 32bit System with the 64bit source files, that's not possible.


For 32bit you have to Point to the Setup.exe inside the x86 Folder and set the condition in the Setup step to 32 bit only.

For 64bit you have to Point to the Setup.exe inside the x64 Folder and set the condition in the Setup step to 64 bit only.

If you don't have a x86 and x64 Folder, your ISO ist only for one O/S Architecture (64bit i guess). Then Download the multi O/S Architecture iso or the 32bit Version and Point to the right Setup.exe there.

 

 

Cancel
login to comment

0

Thank you Christian.

it's worked for me only for 64-bit. did you try it for 32-bit?

Cancel
login to comment

0

Actually, I am all set, it worked beautifully. Thank you so much Christian!! You are the BEST. 

Cancel
login to comment

0

Christian,

It failed after timing out after 60 minutes , I should have checked :( Anyways, how long does it roughly take to be successful? Do I need any other parameters or the command from above is sufficient? 

Cancel
login to comment

0

This is the only step for x64


If you use a 64bit only Win 10 iso the x64 Folder doesen't exists.
Then you have to Point to the Setup.exe in the root Directory.

 

Cancel
login to comment

0

Christian, thank you for the reply! Sorry the exclamation shouldn't have been there :). 

So I downloaded the Win 10 1709 ISO, and speaking of the method above, do I just create a simple Command Prompt step in PDQ Deploy and put the command from above after I obviously mock it up? 

Do you mind briefly listing the steps for me? I am new to PDQ, I would greatly appreciate your assistance.. 

I am using the x64 (below)

\\Path_to_Win_Setup_Folder\x64\setup.exe /auto upgrade /migratedrivers all /ShowOOBE none /Compat IgnoreWarning /Telemetry Disable

Cancel
login to comment

0

Hello Aydel,

yes it works with Win 10 1709 too, it's a universal method.
I don't understand what do you mean with "full ! Win10 1709 ISO"

You can use the files from any Win 10 1709 iso that contains your Edition (Pro, Enterprise, Education, etc.). Or you can use the "Media Creation Tool" from MS to create a USB stick and copy the files from there.

Greetings

 

Cancel
login to comment

0

Also, when we download the 1709 ISO, do we mean the full !Win10 1709 ISO?

Cancel
login to comment

0

Hello there,

I am trying to push the upgrade from 1607 to 1709, I did look at this ( https://support.pdq.com/hc/en-us/community/posts/115000006652-Win-10-1511-to-1607-package-request )but it is kind of confusing and might not work, should I use Christian's method? I know some mentioned that it worked on 1709, but I want to make sure since 1607 is about to retire or not get support.  

 

Appreciate your efforts! 

Cancel
login to comment

0

Thank you, Christian! Using this same strategy for 1709 and so far (5 machines) no problems. Just what I needed. 

Cancel
login to comment

0

The duration depends on the network and local maschine performance.

Old PCs with AMD 2 Core CPUs and only 100mbit network can run into your 60min timeout, my timeout ist 150min to prevent such a error. Keep in mind, PDQ only tracks the first part until the first reboot.

It could be you running into another problem during the installation process, try to start the upgrade local to find the reason or check the logfiles under:

C:\$Windows.~BT\Sources\panther\
C:\Windows\panther\

i3 to i7 PCs with 1000mbit Network are running about 10 to 20 min until the first reboot if the networkspeed is full avaible. If you upgrade 10-20 PCs at once the first step is longer because the network is busy.

I have one PC not upgrading, because the primary HDD is not recognized during the installation.

Cancel
login to comment

0

Christian,


Thank you for replying to me message.  I've extracted the files for the Windows 10 v1703 x64 ISO and pointed the install to the setup.exe file in the main folder.  In the cmd line for the install step, I've specified the parameters mentioned for x64 installation. 

This method has prevented the error message mentioned above, but I did timeout at 60 minutes due to the deployment timeout for deployments (default 60 minutes).  

Am I running into issues because I am using the x64 ISO files?  The deployment I'm running seems to be transferring the files from my DFS to the local machine.  

 

Thanks again,
Donnie

Cancel
login to comment

0

Im not familiar with this error code, maybe you dont point to the setup.exe inside the x86/x64 folders? There is another setup.exe outside this folders, dont use this one.

if you try a install step instead the cmd line, dont forget to activate the copy of all files and folders inside the step. 

Cancel
login to comment

0

Hey Guys,

 

I'm trying to perform the upgrade like you you did, but I'm getting an error message.

 

I have the v1703 setup files out on our DFS and I have a cmd step directed at the setup.exe with your parameters. 

 

I received Command script returned error code 1.  I noticed you say you don't have the files pointed at directly in your steps, but should I?  Is there something I'm missing?   

Cancel
login to comment

0

Post upgrade to Windows 10 1703 - how to surpress all the first run garbage for Office 2013 using Group Policy, this and negates the need for entering admin credentials

 

 

Cancel
login to comment

0

 

Hi Christian,

 

Thanks for the command, it worked a treat for us too but we added the /noreboot switch to supress the automatic restart so no surprises for users!

 

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

 

We have updated 2 laptops so far and we have seen

 

1. The first logon takes a little longer (probably migrating the profile over from the old version).

 

2. Office 2013 the first time you launch Word or Excel it runs through a setup step and as you say requires a onetime admin logon. We are looking at hiding this with Group Policy will let you know if / when we fix this.

 

3. Microsoft seem to be pushing their own Windows Defender and we found that it was enabled once the update has completed, this doesnt play well at all with 3rd party security products so you may need to disable Defender from starting up. We did this with Group Policy and changed the following registry key to 3

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\SecurityHealthService\Type 

Change the Type key to 3), I think this was 10 before.

 

The only other thing we came across and the main reason we delayed upgrading to 1703 is one of our McAfee products was incompatible with Windows 10 (from memory it was DLP 9.3 - Data Loss Prevention) We have now upgraded to McAfee EndPoint Security 10.5 so all good.

Cancel
login to comment

0

No nothing missing or corrupt.

Only one very specific issue with a vacation planning application in combination with Office 2010 (not with 2007/2013/2016) , required one time admin rights after the upgrade to rerun a setup step.

And the first user login on a upgraded PC took longer than usual. This is normal, because the upgrade is technical more a new installation than a upgrade.

 

Cancel
login to comment

0

awesome! did you run into issues with Applications missing or profiles getting corrupt?

Cancel
login to comment

0

My solution with the cmd line works.


I upgraded over 250 PCs with Win 10 1607 to 1703 this way.

 

 

Cancel
login to comment

0

I haven't tried it yet.  This became a low priority.

Cancel
login to comment

0

Hi Dan, Did you manage to deploy 1703 using PDQ?  I'm also at 1607 on around 60 Windows 10 machines and need to update them, failed miserably with wsus !! 

 

Cancel
login to comment

0

Try this simple comand Line with the setup.exe (Setup folder contains 32 and 64 bit Version)

32Bit

\\Path_to_Setup_Folder\x86\setup.exe /auto upgrade /migratedrivers all /ShowOOBE none /Compat IgnoreWarning /Telemetry Disable

64bit

\\Path_to_Win_Setup_Folder\x64\setup.exe /auto upgrade /migratedrivers all /ShowOOBE none /Compat IgnoreWarning /Telemetry Disable

No need to copy the setup folders to the target, only be sure you have access to the share. That means, you can use the cmd line for install instead pointing to the setup.exe.

Cancel
login to comment

0

I think you need to do something like this: https://support.pdq.com/hc/en-us/community/posts/115000006652-Win-10-1511-to-1607-package-request?page=1#community_comment_115000073112

Cancel
login to comment

0

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!

Cancel
login to comment

0

Hi Christian,

We need to upgrade from 1709 to 1803. I see the commands you posted and will test it out.

Can you please let me know how we go about upgrading to 1803 and not any other version. I have downloaded the 1803 ISO from VLC and downloaded and created an ISO using win10 media creation tool.

How do we ensure that the updated version will be 1803?

Thank You

Cancel
login to comment

0

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

Cancel
login to comment

0

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

Cancel
login to comment

0

Has anyone tested this with 1809 update yet?

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

Cancel
login to comment

0

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....?

Cancel
login to comment

0

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.

Cancel
login to comment

0

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?

Cancel
login to comment

0

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

Cancel
login to comment

0

setup enter image description here

Cancel
login to comment

Reply