Symptoms

When deploying patches, the deployment tracker shows 'Scheduled' or 'Executed' but never updates with a new status.

Cause

These are two of the most common causes for this issue:

• Port 3121 is blocked and Track traffic is not making to the Protect Console.
• The deployment failed to start..

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.

The ProPatches folder also might be full on the target machine and clearing out the old files may allow space for the patches to execute.

Affected Product(s)

Protect 9.X