you could embed this worklet to the existing to start the scan when finished.

Have you ever needed to run a scan from the client side?
There are times when you may want to trigger a scan from the device as part of an automation rather than from the console (or waiting for the next scheduled scan to run). One example is to automatically update the Automox inventory when a Windows 10 in-place upgrade successfully completes.
Luckily, @Nic recently published a topic to clean up inactive devices - 

One thing to note is that after any patching policies run, a scan is automatically triggered, so you only need to worry about the worklet use case.

Hey @Nic, it should run a full scan after a Worklet policy runs as well. @it_stuck, Win10 feature upgrade is problematic as the Worklet’s end just after the upgrade starts. It runs it’s scan at this point rather than after the upgrade completion.


The best way I can think of to work around the way that works, is to add the script as a custom action script (I suggest Run Once to clean up the script after upgrade). This would only work on manageable versions of Win10 (pro, ent, edu).


https://docs.microsoft.com/en-us/windows-hardware/manufacture/desktop/windows-setup-enable-custom-actions