Download

Windows 10 Creators Update

Upgrade Windows 10 to Creators Update

Description

This agent procedure will upgrade Windows 10 to the creators update (Build 1703.)
This will perform an entire Operating System upgrade, it is recommended to perform a backup and/or system restore point before proceeding with the OS upgrade.
The workstation will be restarted as part of the procedure.
The agent procedure comes with 3 files of about 1 Go each that will be decompressed to a 3.5Go Iso file required for the upgrade.
The whole process takes between 45 minutes and 2 hours until the workstation can be used again.

Categories
Developer
  • Name: Douglas Sanchez
  • Company: Kaseya
  • Website: http://www.kaseya.com
  • Contact Developer
  • Summary
  • Windows 10 Creators Update
  • 65 Downloads
  • Released on July 27th, 2017
  • Reviews

    Windows 10 Creators Update has no reviews.

    Discussion
    Gravatar for Richard H
    Richard H 3 months ago

    Tried and test. Works like a charm.

    Gravatar for Chris Sanny
    Chris Sanny about 2 months ago

    How about providing just the XML with links to which ISOs were used? Download is telling me it will take 4 days to complete...

    Gravatar for Douglas Sanchez
    Douglas Sanchez about 2 months ago

    Chris, I just emailed you the XML file.

    Gravatar for Douglas Sanchez
    Douglas Sanchez about 2 months ago

    Chris, I just emailed you the XML file.

    Gravatar for Chris Sanny
    Chris Sanny about 2 months ago

    Got it, thanks!

    Gravatar for Chris Sanny
    Chris Sanny about 2 months ago

    For those interested, this is basically taking the ISOs you get from the media creation tool (https://www.microsoft.com/en-us/software-download/windows10), mounting them (or you could extract in advance), and running: setup.exe /auto upgrade /quiet I've had success running the command like this as well: /auto upgrade /migratedrivers all /dynamicupdate enable /showoobe none

    Gravatar for Chris Sanny
    Chris Sanny about 2 months ago

    line breaks got eaten I guess, sorry!

    Gravatar for SHRIKANT E DANGE
    SHRIKANT E DANGE about 2 months ago

    Chris, do you have generated XML of procedure for offline ISO upgrade?

    Gravatar for Chris Sanny
    Chris Sanny about 2 months ago

    The commands I listed will work fine if your ISO is downloaded locally on the machine. You can't really use kaseya to do an "offline" procedure unless you use it to schedule a task for a specific time.

    Gravatar for SHRIKANT E DANGE
    SHRIKANT E DANGE about 2 months ago

    Chris, Actually, I need to run it on multiple machines so need to execute it from Kaseya. and don't want to increase my bandwidth usage.

    Gravatar for Douglas Sanchez
    Douglas Sanchez about 2 months ago

    You could place the ISO on a local shared drive and modify the agent procedure to transfer it from there to the endpoint, then just stagger the procedure to not have the transfer eat up all you network.

    Gravatar for Chris Sanny
    Chris Sanny about 2 months ago

    Ask Douglas for the xml if you don't have it. you can deploy the ISO however you like in advance. Familiarize yourself with lancache if you haven't already, though for something this large I'd recommend using a file server at each client or something like that. Good luck!

    Gravatar for SHRIKANT E DANGE
    SHRIKANT E DANGE about 2 months ago

    Douglas, Could you please drop an email of XML.

    Gravatar for Peter McDonnell
    Peter McDonnell about 1 month ago

    Would we be able to just get the XML as a download? Also might be an idea to modify this to just to pull the files from the LanCache?

    Gravatar for Douglas Sanchez
    Douglas Sanchez about 1 month ago

    I created a second listing that only contain the XML file: https://automationexchange.kaseya.com/products/414 It will require changes to make it work with shared drives/Lan Cache, let me know if you guys have any questions. (douglas.sanchez@kaseya.com to reach me directly)

    Gravatar for Nicholas Tobin
    Nicholas Tobin 5 days ago

    Will this also update to 1709 (when/if available), or is this 1703 specific?

    Gravatar for Anthony Johnson
    Anthony Johnson 5 days ago

    This method downloads/mounts/upgrades Windows 10 using an ISO image of the 1703 / Creators Update build of the OS. For 1709 you'll have to download the new ISO file, split it into 3 parts with 7-Zip, upload it to your KServer, change the procedure to write the new files, then test to make sure the same switches/script will work for installing it. Here's a link for the 64-bit version of Windows 10 version 1709 (I'm downloading it now at 1.5 megabytes/sec): https://software-download.microsoft.com/pr/Win10_1709_English_x64.iso?t=35a03b90-1ca2-4e02-a0bc-a999a1c41947&e=1508351229&h=945eeab10c77d8c2195c8b37ff4d56ea

    Gravatar for Nicholas Tobin
    Nicholas Tobin 5 days ago

    Awesome, thanks for the link Anthony. I just downloaded the ISO. I will test it out tomorrow. and update the script.

    Gravatar for Peter McDonnell
    Peter McDonnell 5 days ago

    I would suggest that the link will time out in 24 hours, so you can download it either via the mediacreationtool or via getting around the block using either Chrome developer tools or a spoofing your machine as a mobile device (as per this: http://www.technicalnotes.org/direct-link-download-windows-10-iso-without-media-creation-tool/ ) My personal favourite is Chrome UA spoofer

    Gravatar for Peter McDonnell
    Peter McDonnell 5 days ago

    I would suggest that the link will time out in 24 hours, so you can download it either via the mediacreationtool or via getting around the block using either Chrome developer tools or a spoofing your machine as a mobile device (as per this: http://www.technicalnotes.org/direct-link-download-windows-10-iso-without-media-creation-tool/ ) My personal favourite is Chrome UA spoofer

    Gravatar for James Morozin
    James Morozin 4 days ago

    Looks like the script is getting us to the point where we need to initiate a scheduled time/reboot now via the prompt. Anyway to automate this? We found simply rebooting does not do the trick.