This document will provide details of an issue where the Tracker never updates past Scheduled and the deployment never runs on the target machine. This document is specifically related to port 5120 being used by another application thus preventing Protect from schedule the deployment job.
You perform a deployment against a machine(s), the Tracker status never updates past Scheduled and the patches never install. The patches copy to the target machine and the .bat and .cfg copy to the C:\Windows\ProPatches\Install directory. The .bat file never renames itself to .his indicating the job either didn't start or never finished. (the .bat file renames itself to .his after the deployment process is complete)
It's possible another application installed on the target machine is using 5120. You can open the scheduler log from C:\Windows\ProPatches\Scheduler\Scheduler.log and search for 'Error 10048'.
The full error is: SchedulerServer.cpp:51: Bind failed on port 5120: Error 10048: Only one usage of each socket address (protocol/network address/port) is normally permitted.
You can use netstat -b from a CMD prompt which will show a list of ports and what program is using those ports.
This can be solved by changing the other application's port or change Shavlik's Scheduler port. This is done by going to Tools-Options-Scheduler and choosing a new port.
In many case, the Tracker update issue when stuck at Scheduled can be attributed to port 3121 being blocked from the target machine back to the Protect console. This port is needed for all Tracker communication from the target machine.