STSADM

Microsoft Office SharePoint Server 2007 includes a very powerfull tool the Stsadm, stsadm is for command-line administration of Office SharePoint Server 2007/Moss 2007 you can use this sharepoint 2010 also. it can be used for server and sites stsadm can be used by command line or by using batch files or scripts. There are certain operations and certain parameters that are only available by using theStsadm command-line tool.

Where the STSADM is Located

Stsadm is located at the following path on the drive where SharePoint Products and Technologies is installed: %COMMONPROGRAMFILES%\microsoft shared\web server extensions\12\bin. You must be an administrator on the local computer to use Stsadm.Many a times people think of running stsadm.exe commands from any command prompt.  So here is the way:

1. Open command prompt
2. Type in the following command:  @set PATH=C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\BIN;%PATH% 
(This Command does not work on WSS 2.0)

In WSS 2.0
Try CD C:\Program Files\Common Files\Microsoft Shared\web server extensions\60\BIN
and run the below Commands.

3. You can now run the stsadm.exe commands from anywhere in the command prompt
_________________________________________________________________________________

To get the IDs of the Solutions use the below Command

stsadm -o enumdeployments
_________________________________________________________________

To CANCEL the deployment of the Solution use the below Power Shell Command.

stsadm -o canceldeployment -id "ae9d211d-83d2-47c4-a0c0-c6251a423675"
_________________________________________________________________

STUCK ON DEPLOYING

Make sure all deployments are set to DEPLOYING before stopping the services.
MY ENVIRONMENT
Command prompt, run as Admin on WFE and SQL if you are running SSRS integrated mode.
Stop the SharePoint Admin Service
Stop the SharePoint Timer service
1) Run stsadm -o execadmsvcjobs on your CA server.
2) Run stsadm -o execadmsvcjobs on all the farm members that have stsadm.
3) Restart the Timer Service on all farm members.
4) Restart the SharePoint Admin service
That should fix it.