Kace replication shares

Are there any success/horror stories about using replication shares for patching? Currently on version 7.2, having some issues with patching and it was recommended to us by support. 

3 Comments   [ + ] Show comments
  • We use it on a few dozen remote servers without much trouble. What issues are you running into? - DaveMT 3 years ago
    • We have had issues with patch labels failing, and numerous Kace issues on the service desk side during mass deployments. Support tells me this is because we can only push to 255 devices at a time, they suggested using replication shares to lighten the load. - tramiksim 3 years ago
  • we push to 300-800 at a time with a few different labels, but they are all spread out over 20+ repositories. A few things I can think of to check
    1 - If your repository is on a Windows OS and not a Windows server OS, it limits concurrent connections to 20. If you do not have failover enabled in the repository, the target PC will just fail.
    2 - Check to be sure the repositories are getting the updated replicated out to them completely prior to the patch deployment start. This can also cause them to error out.
    3 - If you are getting fails with Error but no other indication of the error. that could mean the Deployment Timeout setting in the schedule is too short. We had that with the high number of PCs we push to, so I set it to 5 hours and that made all the difference in the world. I will note however that if you just get the Error with no indication. that could just mean the PC didn't report complete in the deploy timeout window so it error. That PC MAY have actually patched, but just took longer than the timeout setting. - DaveMT 3 years ago
  • Lots of good advice there, thank you! - tramiksim 3 years ago

Answers (1)

Posted by: Nico_K 3 years ago
Red Belt
Replication Shares are always nice if setup correctly.
This means: if you patch the files are on location and not in another location.

What do you need?
1. machine which is always online (the local domain controller you setup because of the same issues )
2. a smart label which contains all machines on the location

Then simply fill out the fields and let it replicate and you are done.
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ