don't inadvertently make this happen. it's pretty silly...
inside the dsuw, you probably recall being presented with the option to force installations to comply to a window for advanced clients only. this setting is nearly useless if you're using dsuw the way it was intended (as in reoccurring schedules). it's also useless if you're forcing package download and execute instead of running from a remote distribution point.
the window that is specified uses the advertisement start time as its beginning marker. this means if you set an early start time to make sure your clients downloaded this month's patches and then a mandatory execution 3 days later, your advertisement would fail. why?
well, going on the default setting of 90 minutes, by the time the execution fires, you've already long lapsed that install window. you'll get an error in patchinstall.log that reads:
cannot start updates installation due to install window violation.
if you've already setup dsuw this way, don't waste time going back through the wizard. instead, remove the /l:[time] switch from the program command line. something like this...
PatchInstall.exe /n /z:ws /l:90 /s /q /c:5 /p /t:30 /m:"PatchAuthorize.xml"
PatchInstall.exe /n /z:ws /s /q /c:5 /p /t:30 /m:"PatchAuthorize.xml"