There has been much written about the issue (in particular Joel's Q&A) with Deploying Solutions on SharePoint 2007 after Daylight Savings started (and ended depending on where you are) this year and I have run into it several times. Most recently when I attempted to deploy and upgrade to a solution to a server I thought had the patch applied, but it had not.

So I kicked off the upgrade, saw the job sitting in deploying (scheduled...) status, banged my head and installed the patch, rebooted, re-ran the Configuration Wizard (and lamented the time it took on setp 8!).

However, after all that my job still said deploying and clicking on the Solution in Solution Management did not display the usual Cancel Deployment option. 

Sooo.... stsadm time!

To cancel the deployment:

stsadm -o canceldeployment -id ...

Of course I assumed that the ID parameter was the ID of the Solution - it's not. It's the ID of the deployment job. Incidentally, running stsadm -o enumsolutions gives you a nice list of the Solutions installed and their ID's.

stsadm -o enumdeployments gives you a list of the current deployment jobs and their ID's.

Plug the ID of the deployment job into the canceldeployment operation above and voila - cancelled deployment!

TechNet has some documentation of the operations available via stsadm. Interestingly canceldeployment is not on the list!

Mind you I much prefer to figure these things out on the fly and under pressure, don't you?