Symptoms

When deploying patches, the deployment tracker shows 'Scheduled' but never updates with new statuses.

Cause

There are 2 causes for this issue:

• Port 3121 is not blocking transmissions for the Deployment Tracker.
• The Batch file on the target is never being executed.

Resolution

Verify that communication from the Target to the Console is open on port 3121.

Using Telnet to test ports

Port requirements for Shavlik Protect

When initiating a deployment, the patches and deployment files are copied to the target, then a job is created in the scheduler, which sets the Deployment status to 'Scheduled'. Once the deployment is running, it will send status updates to the console over port 3121. If that port is blocking traffic, the status will stay at 'Scheduled'.

If traffic is able to go through port 3121 from the target to the Console, the batch file may be failing to initiate and run. This can be caused by Anti Virus, or locked down security features on a machine.

Affected Product(s)

Shavlik Protect All