Vipre enterprise stuck updating defs best taglines for online dating profiles
Close the console Stop the VIPRE Business Site service Go to C:\programdata\VIPRE business\Threat Db\Copy that folder to the desktop then delete everything in the original folder Start the service again Check site properlies under update and wait for it to say healthy again Then check to see if any machines start to update properly.In that case we will need to see the logs from the VIPRE server and one of the agents that is failing to updates.although I did successfully perform a full definition update push for those remote agents.However, this will become a serious problem if I have to check my servers every few hours to make sure the definition updates are being applied properly.I try to push the updates from the Vipre Console and I get an Updates Failed error. Then go to updates and make sure the throttling is not set about 1000 default is 100.
Also, 9.3 agents that bypassed the 4848 definitions appeared to update without any issues.
Port 8123 is a new port for updating the secondary engine that is now in VIPRE 9.3.
It is not configurable in any of the policy setting but is required for the updates to complete properly now.
However, I do have a couple of remote agents that report the version 7.5 definition 48408 and continue to fail both incremental and full definition updates to the current 48430-7.65044 definition update.
John, Yes, the remote agents are using port forwarding and I have now added port 8123 to the firewall rules.