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
Answers (1)
Please log in to answer
Posted by:
Nico_K
6 years ago
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 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.
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 6 years ago