Hello,
This same issue is actually covered in a recent community post: http://communities.vmware.com/thread/437267?tstart=0
Here is what to check (with some clarification included):
If you deploy and see it sitting at scheduled - go to the target system, C:\Windows\Propatches\Install. Of the newest files in this folder do you have a .bat or .HIS file here?
.bat will still exist if the deployment job has not run - Indicates a scheduler problem.
.HIS will exist if the deployment job has run and completed - Indicates the 'scheduled' status is due to a deployment tracker problem.
If the issue is a deployment tracker problem:
The tracker uses port TCP 3121 to communicate with the Protect console - the most important thing is to verify this port is open from the target system back to the console system.
Also check that your tracker address is set to the correct address in case the console system has multiple NICs or addresses that could be used. You can verify the address the tracker uses in Protect under Tools > Options > Deployment.
If the issue is due to a scheduler problem, go through the following:
-Verify your settings in Tools > Options > Scheduler. Ensure that the scheduler port configured is open for communication from you Protect system to all target systems.
-Verify that you have proper credentials set on the machine(s), machine group(s), and for default credentials.
Try reinstalling the scheduler service to see if it helps resolve the issue:
I hope this helps. If it does not, it may be best to contact support directly for further assistance with troubleshooting.