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
  • 116 Downloads
  • Released on July 27th, 2017
  • Reviews

    Windows 10 Creators Update has no reviews.

    Discussion
    Gravatar for Richard H
    Richard H 6 months ago

    Tried and test. Works like a charm.

    Gravatar for Chris Sanny
    Chris Sanny 5 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 5 months ago

    Chris, I just emailed you the XML file.

    Gravatar for Douglas Sanchez
    Douglas Sanchez 5 months ago

    Chris, I just emailed you the XML file.

    Gravatar for Chris Sanny
    Chris Sanny 5 months ago

    Got it, thanks!

    Gravatar for Chris Sanny
    Chris Sanny 5 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 5 months ago

    line breaks got eaten I guess, sorry!

    Gravatar for SHRIKANT E DANGE
    SHRIKANT E DANGE 5 months ago

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

    Gravatar for Chris Sanny
    Chris Sanny 5 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 5 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 5 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 5 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 5 months ago

    Douglas, Could you please drop an email of XML.

    Gravatar for Peter McDonnell
    Peter McDonnell 4 months 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 4 months 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 3 months ago

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

    Gravatar for Anthony Johnson
    Anthony Johnson 3 months 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 3 months 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 3 months 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 3 months 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 3 months 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.

    Gravatar for Douglas Sanchez
    Douglas Sanchez 2 months ago

    @James this hasn't happened on any of my tests, I'd would need to see where it is stopping, it might require a different switch to bypass it.

    Gravatar for Douglas Sanchez
    Douglas Sanchez 2 months ago

    About 1709, I tested the same procedure with a new ISO with Windows 1709 and the deployment was as smooth as 1703. I have not been able to find a URL link to include in the procedure to download the ISO directly, so as mentioned earlier, the best way to go about it is to create a new one with the Media Creation Tool (https://www.microsoft.com/en-us/software-download/windows10) then split the file in 3 and upload them to the VSA server. I will upload a new package with updated content, but these are the steps to take in the meantime.

    Gravatar for KaseyaUser
    KaseyaUser 2 months ago

    My server setup is that my Kaseya server is at a different site, but I hosted the ISO zip files on a local file server at the same site as the target PC. Although I was able to get the file transfer to work with the “writefilefromagent” Kaseya command (http://help.kaseya.com/WebHelp/EN/VSA/9040000/#7879.htm), it only copied the file over the network at 30 megabits/s. When I did a file drag and drop test from the local server to the local PC at the same location, I got 400 megabits/s. ------------------- Do you have any examples or forum posts of copying from a “samba” share, i.e. \\fileservername\sharename in a Kaseya script? ------------------I could do a robocopy command to copy the files from the file server’s samba share to the local computer, but I not sure how work with permissions from within a Kaseya script. ---------------------Seems like I would just have to do something like this example, where I save a password in plaintext in the script. https://klyavlin.wordpress.com/2012/09/19/robocopy-network-usernamepassword/ --------------- It just seems like a lot of work which I wish Kaseya could help automate…

    Gravatar for Duane Godwin
    Duane Godwin 2 months ago

    Is there any reason to split the installer into three parts?

    Gravatar for Duane Godwin
    Duane Godwin 2 months ago

    Is there any reason to split the installer into three parts?

    Gravatar for Tim Merritt
    Tim Merritt 2 months ago

    I can't fathom why you'd want to transfer 3+GB to any number of machines using this script. I reviewed the script, extracted the ISO to a Win10 folder in the lan cache and created my own script to call it from there. It wouldn't work... I downloaded an enterprise Windows 10 ISO from VLSC as the target machines were running enterpirse and it worked great from the share!

    Gravatar for Tim Merritt
    Tim Merritt 2 months ago

    My almost too simple agent procedure goes like this: line1: UseCredential line2: executeShellCommand("\\server\share\folder\setup.exe /auto upgrade /quiet", "Execute as User", "Windows 10", "Halt on Fail")

    Gravatar for Tim Merritt
    Tim Merritt 2 months ago

    I see there's a Fall Creators Update (1709) on here now. I assume it's the same thing with an updated windows.iso. After the 1703 windows.iso that's included didn't work, I downloaded 1709 and used that with the above script.

    Gravatar for Anthony Johnson
    Anthony Johnson 2 months ago

    I'm guessing the installer was split into 3 parts so the downloads are more likely to succeed before timing out. One reason for transferring 3+ GB to computers, over the Internet via the procedure, is if they can't all access the LAN cache. We're managing 2,040 Windows 10 computers total, across 145 different networks, and many of them are laptops, Surfaces and remote desktops. I split the 1709 Fall Creators ISO into 7 parts instead of 3, and created 7 different procedures for downloading each individual part, then one procedure that schedules those 7 downloads separately. It's a lot more complex but unfortunately it's the only way we could efficiently get these updates downloaded & installed on all these devices. (We have a GPO in place that enables the local Windows Update client for patching, but it has only had a 30% success rate in getting these major updates installed).

    Gravatar for Tim Merritt
    Tim Merritt 2 months ago

    That makes sense! I'd be afraid to start the upgrade under those circumstances. No telling what the user might do mid-upgrade! I figured having the local option for those that can get the machines on the LAN when needed, would be a good alternative to shooting terrabytes of data out of their Kaseya server. Of course, it doesn't need to be the lan cache. That's just one convenient location to toss the extracted ISO.

    Gravatar for Douglas Sanchez
    Douglas Sanchez 2 months ago

    As you all mentioned, I split the ISO in 3 files due to upload/download time out. From my testings, the 3 files are at a size that work well with the VSA. When I tried a 3Go file .... I could never get the procedure to complete before timing out. Once you have the file, it is fairly easy to tweak it to fit your infrastructure, either using a lan cache, a file server accessible locally by the endpoints, or leaving it on the VSA server for the remote machines out of the network/domain.

    Gravatar for Douglas Sanchez
    Douglas Sanchez 2 months ago

    @KaseyaUser One of the commands you can use to transfer the files from your local share is TransferFile directly from the Agent Procedure. Here is a community post about it: http://community.kaseya.com/xsp/f/28/t/23658.aspx Otherwise I've had great success with Robocopy, you should not have to include a user when you use it if your users have the correct permissions to the location of the files. Take a look at https://technet.microsoft.com/en-us/library/cc733145(v=ws.11).aspx for more details.

    Gravatar for Tim Merritt
    Tim Merritt 2 months ago

    Don't forget the fall creators update is out so if you're using this package, you're doing all this work only to end up a build behind. A big thank you to Douglas Sanchez for the time and effort to get this out to everyone! Here's the latest build: https://automationexchange.kaseya.com/products/443