Systems Management

I experienced a very similar issue with my 12 replication shares never completing successfully once I upgraded my K1000 to v5.5. The problem continued even after I upgraded to v6.0 My replication shares would either restart completely or the amount of files/data in the replication queue would fluctuate, increasing or decreasing randomly. Also, when attempting to perform a patch job on my desktops, it would fail with a "Error (Handshake Failed)" status.

I eventually resolved this issue on my own, even though I had worked with KACE support. In my replication share settings, under Destination Share > Path, I used a UNC path of \\ServerA\KACE_Share. I had a User and Password specified. The issue was resolved when I specified a local path of C:\KACE_Share (my replicating device was also storaging the replicated data) with no Username and no Password (neither are needed for local paths). Once I made this change, my replication completed successfully and patching from replication shares had no errors. Specifying a UNC path was never an issue before v5.5 and KACE support made no mention of it when they reviewed my replication share settings.

I hope that writing about my experience saves someone else a lot of time. 

I have experienced some odd behavior with replication since upgrading to 5.5. Everything replicates just fine, as it did prior to the upgrade. The issue I have is that I can not force replication outside of the time window that was previously set. Sometimes I do that to test a script or managed install. It will replicate fine in the evening when the scheduled window opens but I can no longer force replication in real-time. I have deleted and recreated one of my replication shares to see if that would resolve the issue and it has not. 

Try deleting the replication share all together and recreating it.  Also, upgrade the agent on the replication machine if you haven't already.