I wanted to share a bit of behaviour I noticed with the service pack definitions for Windows 10 1803.
I am currently testing an update process for moving our clients from v1709 to v1803. We have a multi lingual environment, so I have created a custom definition using a clone of the standard patch W10V1803 definition in Patch Manager.
I have customised my ISO image by adding the language packs we require in our build using DISM. I then tested the upgrade by mounting the custom ISO manually and then using the standard setup commands as included in the patch definition, minus the /noreboot switch:
setup /auto upgrade /quiet /dynamicupdate disable
Every time I run this patch manually on a client it works first time.
However, when I try to push the patch out using the custom definition (bearing in mind the script has not been modified from the original W10V1803 definition) I am getting very intermittent results. In many instances, the update appears to run but when the system reboots, nothing happens and it just reboots back in to Windows 1703 with no error prompts or failed update warnings. As far as Ivanti is concerned, I am getting a report that the patch has been successful.
On further investigation I have found that the definition script appears to be finishing before the upgrade has actually completed, causing Ivanti to request a reboot. I monitored one client and could clearly see that the setup.exe and setuphost.exe files were still running in the background.
I notice in the definition there is a time out script:
Option Explicit
Sleep 1800*1000
SetRebootRequired
ReportRepairResult True, "Restart successfully."
I am guessing I will need to modify this script, but I am curious does anyone know why this is included in the definition?