Important Notice: On February 29th, this community was put into read-only mode. All existing posts will remain but customers are unable to add new posts or comment on existing. Please feel to join our Community Discord for any questions and discussions.

Windows 10 1709 Deployment Update

Hi all,

I'm having issues deploying Windows 10 1709 with PDQ Deploy, as the deployment hangs and then fails after around 4 hours.

I have downloaded an ISO for the 1709 FCU and extracted the files into a DFS share.

I have created a package in PDQ Deploy with one single 'Install' step.

The 'Install File' path is set to \'DFS share path\setup.exe' (true path hidden for confidentiality).

Initially this kept failing a couple of minutes in, returning error code "1047526904", whilst using the following parameters

"/auto upgrade /quiet"

However, when I added 'setup' to make the Parameters "setup /auto upgrade /quiet" this proceeded.

I then left this deploying overnight and came in this morning to find that it had failed after 4 hours with the following message

'Exceeded timeout for completion. Are you missing silent install parameters'

Can someone possibly shed some light and advise where I may be going wrong?

Thanks.

0

Comments

3 comments
Date Votes
  • In PDQ Deploy, go to Options -> Preferences -> Deployments -> Change Timeout (Deployment will terminate after xxx mins) value to 480 mins (8 hours).

    https://support.pdq.com/knowledge-base/1123

    0
  • 1047526904 could point out that you have incompatible apps or software installed and the upgrade doesen't move ahead.

    Run a non silent/quiet upgrade:

    //Path_to_DFS_win1709/setup.exe /auto upgrade /migratedrivers all /ShowOOBE none /Compat IgnoreWarning /Telemetry Disable /DynamicUpdate disable

    Keep an eye on the process, if the upgrade fails you see why and when. If you have incompatible software, remove the software from all PCs.

    A i3/i5/i7 PCs only need 8-30min for the first step. A Old PC (AMD 2 Core CPU) with slow networks (10/100mbit) can run into a 1 hour timeout, if you set the timeout to 2 hours you should be safe.

    0
  • Thank You!

    0