DST issue Pt. 2: SharePoint jobs don't immediately propagate
As of Sunday (Oct 28) it seems that server farms with uneven Windows Server patches are once again seeing issues with deployment jobs. The symptom is that deployment of x takes up to an hour to execute or propagate to all servers in the farm. For example, a web content deployment will be delayed, Forms uploaded to Forms Server aren't marked Ready for an hour, etc.
As a workaround, this issue can be solved from the command line with the usual:
stsadm -o execadmsvcjobs
The fix is to get all servers in the farm up to the same patch levels. Windows Server SP2 solves the issue, it includes the Feb 2007 cumulative time zone update. There is an additional patch for WSS 2.0 and SPS 2003 (previously described here), while O12 products (WSS 3.0 and MOSS) should behave correctly if the server itself is patched. If you're back in the stone or bronze ages, this is the authoritative article, note that it only addresses SP&T 2001 and 2003:
[Updated Nov 1 with links to Windows Server SP2 and the SP&T Team Blog article]