Download

Windows 10 Fall Creators Update (1709)

Upgrade Windows 10 to Creators Update

Description

This agent procedure will upgrade Windows 10 to the fall creators update (Build 1709.)
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.
It is recommended to have at least 20Go free on the endpoint before running the procedure, otherwise the procedure could fail without giving any error message.

To download the zip file, click Here.

Developer
  • Name: Douglas Sanchez
  • Company: Kaseya
  • Website: http://www.kaseya.com
  • Contact Developer
  • Summary
  • Windows 10 Fall Creators Update (1709)
  • 356 Downloads
  • Released on November 7th, 2017
  • Reviews
    Gravatar for Drew Ludeking
    by Drew Ludeking on April 9th, 2018

    This procedure has worked perfectly and saved me a ton of issues Thank You!!!!

    Discussion
    Gravatar for Sam
    Sam 9 months ago

    I am only seeing the .xml file in the zip file I downloaded?

    Gravatar for Douglas Sanchez
    Douglas Sanchez 9 months ago

    To correct the Zip files with the whole content, you need to click on "Visit Website" instead of "Download." We had to work around some website limitation due to the size of the file.

    Gravatar for Derek Russ
    Derek Russ 9 months ago

    This doesn't seem to be working. it is giving me the following error - Execute Powershell Command (64-bit, Run As System)-0001

    Check for powershell failed!

    Gravatar for Douglas Sanchez
    Douglas Sanchez 9 months ago

    Hi Derek, Can you give me more details about the endpoint and the error ? What line is it erroring at ? And Does the agent procedure log give you any more details as to why it is failing ? I worked on all Machines and VMs I tested it on.

    Gravatar for Nicholas Tobin
    Nicholas Tobin 9 months ago

    I have some machines in a company that uses Enterprise Volume Licensing so this installer fails and asks for a key every time that wont take. Anyone know where the ISO for that version would be?

    Gravatar for Douglas Sanchez
    Douglas Sanchez 9 months ago

    @Nicholas, as far as I know, Microsoft now hides the ISO so that it cannot be downloaded directly. I recommend using their ISO creation tool at https://www.microsoft.com/en-us/software-download/windows10 on an endpoint with the enterprise volume. Hopefully this will create an ISO for that specific system and it won't prompt for the key.

    Gravatar for Derek Russ
    Derek Russ 9 months ago

    it looks like it is on line7 when running the powershell. Two things i have noticed. the temp agent dir it copies the files to c:\windows\syswow64 since it's a 64bit system, but the path in the PS Script has system32. i ran the script.ps1 mnaully and changed the path to wow64 and it is running on my system now. Below is a screenshot of the log.

    https://imgur.com/a/mWQQS

    Gravatar for Douglas Sanchez
    Douglas Sanchez 9 months ago

    Derek, by any chance, is the endpoint a 32bit machine ? If so I can send you an update procedure that takes into account 32 bit systems.

    Gravatar for Derek Russ
    Derek Russ 9 months ago

    Hey Douglas, It is a 64bit machine.

    Gravatar for Derek Russ
    Derek Russ 9 months ago

    The cleanup procedure did work though.

    Gravatar for Heather Stover
    Heather Stover 7 months ago

    This script is incredibly helpful! But we have a handful of managed machines that are 32-bit; where can I find the procedure to run the update on those?

    Gravatar for Douglas Sanchez
    Douglas Sanchez 7 months ago

    @Heather, I would recommend using this link https://www.microsoft.com/en-us/software-download/windows10 to create a new ISO on a 32 bits machine. Then you can split it in 3 files similar to the way it is done in the procedure, and redirect to that folder with the procedure. You may want to duplicate the procedure so that you have one for 32bits machine and one for 64 bits.

    Gravatar for Fleet Admin
    Fleet Admin 7 months ago

    Hi all,
    A bit new here so excuse me in advance. I am trying to use this procedure to upgrade Windows 10 (1703) x64 machines.
    I placed all 3 files,
    Windows.zip.001
    Windows.zip.002
    Windows.zip.003

    In Window ISO folder under the shared folder... and followed the rest of the instructions... however i cannot see it working when i execute it...
    can you share some tips on what should i be seeing or monitor to see errors etc.?

    Cheers,
    EldadiO

    Gravatar for Douglas Sanchez
    Douglas Sanchez 7 months ago

    You cannot really see much while the procedure is working. You can eventually check the kworking folder as the WIndows ISO folder should get created and the files should slowly transfer there. Then it will mount the ISO, and then a Windows Upgrade process will be up for a little while before restarting.

    Gravatar for Rob Shaw
    Rob Shaw 7 months ago

    Hey Douglas, I tried testing out this procedure last night on two different 64-bit Win 10 computers here in my office. The procedure downloaded one of the ISO's and after a few hours eventually the procedure states that it was successful. The clean up procedure was also triggered and removed the left over files. The only problem is that neither computer took the update. Do you have any idea why this might be? One of the computers is sitting at version 1607 (OS build 14393.1944)

    Gravatar for Douglas Sanchez
    Douglas Sanchez 7 months ago

    Hey Rob, I cannot say for sure, but there might be an issue with going from 1607 directly to 1709 ? Eventually try letting the procedure run and cancel the cleanup one. You'll then be able to give it a shot manually and see if you have any compatibility issues.

    Gravatar for Wynema Ware
    Wynema Ware 7 months ago

    I have successfully upgraded from every version of Windows 10 to Creator's 1703 and 9. Failures like this that I experienced were due to that 4gb file never fully downloading. Not sure why the procedure says it is successful. I found out by remoting into the machine and kworking had partial files.

    Gravatar for Wynema Ware
    Wynema Ware 7 months ago

    I have successfully upgraded from every version of Windows 10 to Creator's 1703 and 9. Failures like this that I experienced were due to that 4gb file never fully downloading. Not sure why the procedure says it is successful. I found out by remoting into the machine and kworking had partial files.

    Gravatar for Douglas Sanchez
    Douglas Sanchez 7 months ago

    This is the exact reason why I ended up splitting the file into 3 different files that needed to be decompress. Send me an email at douglas.sanchez@kaseya.com and we can take a look at improving it.

    Gravatar for Rob Shaw
    Rob Shaw 7 months ago

    Yeah I did notice that only one of the ISO files transfered over and it only ended up at about 800MB. Any idea why the procedure would quit transferring? Could there be a size limit in place on our end? Forgive me, I'm still rather new to Kaseya.

    Gravatar for Nicholas Tobin
    Nicholas Tobin 7 months ago

    @Rob, This file is rather large to host in Kaseya. What I did, was using 7 zip broke the iso into 3 equal parts and hosted them on our AutoTask. I then created a public link and used GetURL within the script to download the 3 parts. The rest of the procedure "should" be the same iirc as far as unzipping the 3 parts and then running the install. IF you have any enterprise versions, you will need a different ISO.

    Gravatar for Rob Shaw
    Rob Shaw 7 months ago

    Yeah I have three different files and they are about 1.2 GB a piece. Did you break these down further? From what I understand, Douglas already broke the primary ISO down into these three files, much like what your stating.

    Gravatar for Nicholas Tobin
    Nicholas Tobin 7 months ago

    No, my files are about that same size as well. But I placed them in AutoTask rather than Kaseya file server.

    Gravatar for Nicholas Tobin
    Nicholas Tobin 7 months ago

    IF you have a place to host the files, I can email you what I use and you can edit your download links.
    Mine is actually 4 scripts. One is the download/Extract, The second is the Install, third script is a Checksum that ties into the Download/Extract script to ensure the file fully downloaded and extracted before you run the install that ties into a custom field as Pass or Fail. The fourth is the cleanup of the files.

    Gravatar for Rob Shaw
    Rob Shaw 7 months ago

    I am not sure that I do have a place to host them. I need to talk to some people in the office to get more information. I'll get back to you. Thank you!

    Gravatar for Douglas Sanchez
    Douglas Sanchez 7 months ago

    @Rob, as Nicholas mentioned, it could be faster to host the files in a server and use GetURL to download them instead of transferring from the VSA server. It all depends of the Network configurations. It is possible the download stops because it is slow and the procedure times out. You can also use them on a local file server (If you have one) and edit the procedure to transfer the files from that server to the endpoint.

    Gravatar for Karel P Kerezman
    Karel P Kerezman 7 months ago

    If you're trying to do this to Enterprise, well, the ISO creation tool won't help you either: "Windows 10 Enterprise isn’t available in the media creation tool."

    And since the volume download center still doesn't show a 1709 ISO (as of our check on Monday, Jan 15th 2018) we're still out of luck. Not that Enterprise comes up often, but WE'RE on it, and I was hoping to test this procedure on an in-house system. D'oh.

    Gravatar for Rob Shaw
    Rob Shaw 7 months ago

    Speed isn't an issue. Douglas, you were correct. The procedure was failing due to the procedure timing out before all the files could download. I bypassed this by creating 3 simple procedures to download 1 chunk of the iso each. Then I just pulled the download part out of your script and had it trigger after the last file downloaded. Only been able to test it on one computer so far but it worked flawlessly.

    Gravatar for Jonathon Blacklidge
    Jonathon Blacklidge 7 months ago

    I have the script working- it downloads the files, unzips to iso, mounts and i can see it running. But it closes after some time and doesn't take the update. I tried the copylogs switch to get more information, but that did not work either. Does anyone know where the logs for the installation are stored?

    Gravatar for Douglas Sanchez
    Douglas Sanchez 7 months ago

    @jonathon, you may want to take a look at this article: https://support.microsoft.com/en-us/help/928901/log-files-that-are-created-when-you-upgrade-to-a-new-version-of-window

    Otherwise, I would try running the install manually while the iso is mounted, you might find out what error it is running into via the GUI.

    Gravatar for Jonathon Blacklidge
    Jonathon Blacklidge 7 months ago

    @Douglas Thank you for the link! The first thing i did after the script didn't run properly was run the GUI- it installs just fine. Time to dig through the logs.

    Gravatar for Praneeth Rajalingari
    Praneeth Rajalingari 7 months ago

    Hi,

    I have the enterprise ISO for feature update how can use this procedure to upgrade the enterprise ISO? Please let me know.

    Thanks.

    Gravatar for Brian Christmas
    Brian Christmas 6 months ago

    Script works great but I find that when I schedule the deployment It will only install to 2 out of the 10 machines I have selected with a 2 hour deployment window.
    The machines that are updated though, the agent is goes offline. The only way I have found to fix is to completely remove the agent and re-install it.
    I am on VSA 6.3 with the latest patch 9.3.0.35
    Thanks in advance!

    Gravatar for Brian Barbour
    Brian Barbour 6 months ago

    I'm still struggling to get the script to work properly. The files reliably copy, but I sometimes get a mounted ISO, other times, there is an ISO, but not mounted and other times just a ZIP compilation of the 3 files. I manually ran the ISO on one machine to make sure it worked, and it did.

    Gravatar for Douglas Sanchez
    Douglas Sanchez 6 months ago

    @Brian Christmas, you may want to open a ticket with support as this is not a problem I ran into and I have not tested the procedure on 9.3

    Gravatar for Douglas Sanchez
    Douglas Sanchez 6 months ago

    @Brian Barbour I ran into similar issues when I tried deploying on machines with low hard drive space. The procedure requires a decent amount of free space due to the large files it works with.

    Gravatar for Brian Barbour
    Brian Barbour 6 months ago

    @douglas, 300+ GB free... Did you happen to see it in any other circumstances?

    Gravatar for Douglas Sanchez
    Douglas Sanchez 6 months ago

    No, this was the only time I had a weird behavior. Any other time the script ran successfully. Another thing I could think of is that the build of window you are starting from might not be able to upgrade directly to 1709 ?

    Gravatar for Brian Barbour
    Brian Barbour 6 months ago

    That may be the issue. I was mostly testing on 1511 machines and a 1607. I ran it on a 1703 this morning and just checked in. Upon logging in, it give a full window splash saying an update was pending. It is installing 1709 now.

    Gravatar for Russ Stewart
    Russ Stewart 6 months ago

    This script relies on the provided files which someone made... i'd like to know a way to create my own in a compatible format for future scripts... can the process for creating the iso zip files be documented? Also, either as an add-on procedure or integrated, it would be great to be able to add the latest cumulative update to the automation.... I find if I update with the Microsoft wizard it automatically installs patches... but not so with kaseya.

    Gravatar for Justin
    Justin 5 months ago

    @Russ Stewart you can use 7Zip. Add to archive, specify Archive Format as zip and split to bytes. What I do is take the file size of the ISO and divide by 3. You will want to use Normal compression. Once the split archive is created you will see something like %archivename.zip.001%, %archivename.zip.002%, %archivename.zip.003 you can then point the UnzipFile command in your Kaseya procedures to %archivename.zip.001 to put the ISO back together as one.

    Gravatar for Justin
    Justin 5 months ago

    @Russ Stewart you can use 7Zip. Add to archive, specify Archive Format as zip and split to bytes. What I do is take the file size of the ISO and divide by 3. You will want to use Normal compression. Once the split archive is created you will see something like %archivename.zip.001%, %archivename.zip.002%, %archivename.zip.003 you can then point the UnzipFile command in your Kaseya procedures to %archivename.zip.001 to put the ISO back together as one.

    Gravatar for Justin
    Justin 5 months ago

    @Russ Stewart you can use 7Zip. Add to archive, specify Archive Format as zip and split to bytes. What I do is take the file size of the ISO and divide by 3. You will want to use Normal compression. Once the split archive is created you will see something like %archivename.zip.001%, %archivename.zip.002%, %archivename.zip.003% you can then point the UnzipFile command in your Kaseya procedures to %archivename.zip.001 to put the ISO back together as one.

    Gravatar for Lamond Venning
    Lamond Venning 5 months ago

    I have an issue, our instance is hosted in the cloud and we would like to use a local file share to host the ISO. Can you point me in the right direction about modifying the procedure to point to the local file server?

    Gravatar for Stephen Biasotto
    Stephen Biasotto 5 months ago

    Lamond, you will need to replace the writedirectory [line 3] in the procedure to one that copies the directory from your server.
    The copyFile function will not work with a directory, and there is no copyDirectory, so I would suggest using Windows native xcopy to do it.
    Replace line 3 in the procedure with something like this:

    executeFile
    C:\Windows\System32\xcopy.exe
    /Y /E \\SERVER\PATH\Windows ISO\ #vAgentConfiguration.AgentTempDir#\Windows ISO\
    Execute as System and Wait

    Gravatar for Stephen Biasotto
    Stephen Biasotto 5 months ago

    Lamond, you will need to replace the writedirectory [line 3] in the procedure to one that copies the directory from your server.
    The copyFile function will not work with a directory, and there is no copyDirectory, so I would suggest using Windows native xcopy to do it.
    Replace line 3 in the procedure with something like this:

    executeFile
    C:\Windows\System32\xcopy.exe
    /Y /E \\SERVER\PATH\Windows ISO\ #vAgentConfiguration.AgentTempDir#\Windows ISO\
    Execute as System and Wait

    Gravatar for Peter Jones
    Peter Jones 5 months ago

    Going to throw this out there as a different perspective on this.

    I am not interested in pushing out or having every endpoint download the iso and then run it. I wanted something more efficient and something I can use without much modification going forward with Windows 10 updates like these. I used the basics outlined in the procedures. I created another procedure that downloads the zip files to a machine on the local network. ISO file is unzipped from the files and then shared from that machine. I use a variable that is the path to the share on that machine and assign it to the machine group I need it for. I modified the procedure to mount the iso from the share - pulling the location from the managed variable for the group (you could copy the files from the share to the local machine as well) and run the rest of the procedure. I tweaked the cleanup procedure because I don't need it to clean up the iso or zip files on the local machine.

    In my case I am willing to set up the managed variable for the sites I need this for as I see it saving time overall. It allows for me to push out a new ISO to a single local machine in advance of the need. I can then run the procedure as needed on the local machines. At moment I have ~600 Windows 10 machines though not all of them need to have the update applied because they are current.

    Gravatar for Peter Jones
    Peter Jones 5 months ago

    Going to throw this out there as a different perspective on this.

    I am not interested in pushing out or having every endpoint download the iso and then run it. I wanted something more efficient and something I can use without much modification going forward with Windows 10 updates like these. I used the basics outlined in the procedures. I created another procedure that downloads the zip files to a machine on the local network. ISO file is unzipped from the files and then shared from that machine. I use a variable that is the path to the share on that machine and assign it to the machine group I need it for. I modified the procedure to mount the iso from the share - pulling the location from the managed variable for the group (you could copy the files from the share to the local machine as well) and run the rest of the procedure. I tweaked the cleanup procedure because I don't need it to clean up the iso or zip files on the local machine.

    In my case I am willing to set up the managed variable for the sites I need this for as I see it saving time overall. It allows for me to push out a new ISO to a single local machine in advance of the need. I can then run the procedure as needed on the local machines. At moment I have ~600 Windows 10 machines though not all of them need to have the update applied because they are current.

    Gravatar for Daniel Rhoden
    Daniel Rhoden 4 months ago

    @Douglas Sanchez
    We have the Kaseya SaaS offering, so no on-prem. We are trying to upload the three (3) Windows files to our Managed Files section but it keeps failing before 100%. We have tried using Chrome, Edge, & IE. We've even disabled AV and tried from another computer so we aren't sure what's going on. If it's a space limitation, can the space in Managed Files be raised to support this method?

    Gravatar for Daniel Rhoden
    Daniel Rhoden 4 months ago

    @Douglas Sanchez
    We have the Kaseya Cloud/SaaS offering, so no on-prem. We are trying to upload the three (3) Windows files to our Managed Files section but it keeps failing before 100%. We have tried using Chrome, Edge, & IE. We've even disabled AV and tried from another computer so we aren't sure what's going on. If it's a space limitation, can the space in Managed Files be raised to support this method? With Microsoft requiring an OS upgrade every 1.5~ years for Windows 10, it'd be even better if the upgrades were baked into the Kaseya Cloud/SaaS offering and we just selected the upgrade for agents, hopefully that's coming soon.

    Gravatar for Steve Healy
    Steve Healy 4 months ago

    @Daniel Rhoden - we just ran into this problem ourselves. Managed Files does have a size limit, which I was told is about 100MB but that was a couple years ago, so it could have changed, but not by much. So, no those zip files won't work in Managed Files. We have an amazon s3 bucket that I was able to store the files in and modified the script to use "getURL("https://s3.amazonaws.com/bucket/etc/Windows.zip.001") - you need one of these for each zip file of course (002, 003). If you have a server or something similar to store them on, that is your best bet. There are other methods too but this was the easiest for us. After that, the regular unzip command (only have to point it at 001, it will do the rest automatically) and rest of the script should work as normal.

    Gravatar for Steve Healy
    Steve Healy 4 months ago

    @Daniel Rhoden - we just ran into this problem ourselves. Managed Files does have a size limit, which I was told is about 100MB but that was a couple years ago, so it could have changed, but not by much. So, no those zip files won't work in Managed Files. We have an amazon s3 bucket that I was able to store the files in and modified the script to use "getURL("https://s3.amazonaws.com/bucket/etc/Windows.zip.001") - you need one of these for each zip file of course (002, 003). If you have a server or something similar to store them on, that is your best bet. There are other methods too but this was the easiest for us. After that, the regular unzip command (only have to point it at 001, it will do the rest automatically) and rest of the script should work as normal.

    Gravatar for Douglas Sanchez
    Douglas Sanchez 4 months ago

    @Daniel - I suggest exactly what Steve mentioned. Otherwise you can store the files in a local server and transfer them over as part of the agent procedure. Otherwise you might need to open a ticket with support so they can reach the Saas team and they might be able to help upload the files to your instance. About it being implemented in the product, I know this is in the works, it is just a bit more complicated than just patches so it takes longer.

    Gravatar for Daniel Rhoden
    Daniel Rhoden 4 months ago

    @Kaseya Team

    Thank you for the information. Would you update the article to reflect the limitation of Cloud/SaaS only customers and an example of how to get around the limitation for now (URL instead of File)?
    Thank you

    Gravatar for Daniel Rhoden
    Daniel Rhoden 4 months ago

    @Kaseya Team

    Thank you for the information. Would you update the article to reflect the limitation of Cloud/SaaS only customers and an example of how to get around the limitation for now (URL instead of File)?
    Thank you

    Gravatar for Daniel Rhoden
    Daniel Rhoden 4 months ago

    Separate comment but related: As you can see most people are doubling their posts. I posted the last post and waited until I received the error below, which then I assumed because of the error it didn't post... so now I have two posts :) Can you have someone look into why posts are erroring out and taking a long time, my apologies if this is the wrong location for this.

    "Application error"
    "An error occurred in the application and your page could not be served. If you are the application owner, check your logs for details."

    Gravatar for Douglas Sanchez
    Douglas Sanchez 4 months ago

    @Daniel, Hey I have been having the issues. We are working on getting it fixed in the backend but thanks a lot for the feedback.

    Gravatar for Isaac Bowley
    Isaac Bowley 4 months ago

    @Douglas, I can't find the Visit Website button to download the larger files. I have tried different browsers. I used the Download button to get the XML. What am I missing?

    Gravatar for Ralph Droesen
    Ralph Droesen 4 months ago

    I can't find the "visit website button" either. where is it hiding?

    Gravatar for Douglas Sanchez
    Douglas Sanchez 4 months ago

    We are working on getting it fixed. We pushed out an update Wednesday night which seem to have disabled that button.

    Gravatar for Daniel Rhoden
    Daniel Rhoden 4 months ago

    Is the download for Windows 10 1709 32-bit, 64-bit, or both? Would you mind updating the summary to clarify for others as well? We run 64-bit.
    Thank you

    Gravatar for Douglas Sanchez
    Douglas Sanchez 4 months ago

    It should work with both, but it was not tested on 32 bits machine.

    Gravatar for Josh Trump
    Josh Trump 4 months ago

    Also looking for this link, please advise or provide direction for manually creating/splitting the iso. Thanks

    Gravatar for Douglas Sanchez
    Douglas Sanchez 4 months ago

    Until we fix the link, I added it to the main listing's description. At the end of the description you should be able to click on "Here" to get the download started.

    Gravatar for Josh Trump
    Josh Trump 4 months ago

    Thanks Douglas. I was able to create yesterday and split the zip into several pieces and it seemed to work. Couple Qs:

    - Where do these uploaded files actually live? We're hosted I believe, are clients going out each time to your server or does this wind up on the probe server?

    - Anything in the works to automate this to the point it won't affect the end user beyond the back half of the update? This 'works' but still requires making sure the machine doesn't sleep and that the user has worked saved and away for at least a couple hours.

    Thanks!

    Gravatar for Douglas Sanchez
    Douglas Sanchez 4 months ago

    @Josh, The uploaded files reside on your VSA server. I am not sure about the specifics for Hosted, but they should just be part of all these files. I would advise cleaning them up once you're done or whenever you roll a newer build of Windows 10. As you can see from other comments in this discussions, some users edited the script so that it transfers from a local server or runs directly from there instead of having to download the files on each agent from the server.

    Gravatar for alex smith
    alex smith 4 months ago

    do you know the link for the ISO from Microsoft? so we can just pull it from them and not our server.

    Gravatar for Douglas Sanchez
    Douglas Sanchez 4 months ago

    @Alex, there is no direct link from Microsoft to download the ISO. If you review the previous comment you should be able to find the link to create the ISO you need.

    Gravatar for Jeff Ryer
    Jeff Ryer 3 months ago

    I tried this out for the first time, but I think the "prompt when procedure is scheduled" is preventing me from scheduling it. I'm not familiar with this command. I see that if I run the procedure I get the prompt, but if I schedule the procedure, I don't get the prompt and it doesn't get past that command. Although I like the idea of the prompt, t looks like I need to remove the prompt from the procedure and try again.

    Gravatar for Douglas Sanchez
    Douglas Sanchez 3 months ago

    @Jeff, it should be fairly straight forward to remove it, delete the first line of the script and push all the code back to the left to remove the indentation. Let me know if this helps.

    Gravatar for Eric Dowd
    Eric Dowd 3 months ago

    @jeff after selecting  "Schedule agent procedure"  the windows pops up. You should see a tab next to  "schedule agent procedure" called "script prompts". You can then type in True on that screen. I hope this helps.

    Gravatar for Paul Todd
    Paul Todd 2 months ago

    I did not see a powershell script when I unzipped the downloaded file.  Is it available somewhere else or does it get created automatically by Kaseya?

    Thanks.

    Gravatar for Jeff Ryer
    Jeff Ryer 2 months ago

    @Paul, the powershell script gets created by the procedure.

    @Douglas, thanks, I didn't notice the extra tab on the scheduling window!

    Gravatar for Lamond Venning
    Lamond Venning 2 months ago

    So made the change to line 3 and i can see the Unzip File then Execute Powershell Command under status but i don't see the ISO being mounted or the setup process running. Is there a way to monitor the procedure and see where it is failing??

    Gravatar for Douglas Sanchez
    Douglas Sanchez 2 months ago

    @Lamond, you can add some writeProcedureLogEntry() functions in between lines to write in the log. Then check the log in the Agent module, in Agent -> Agent Logs -> Agent Admin Logs -> Procedure History, You'll see the log entries you created as well as any feedback/errors from the procedure on that endpoint.