Currently using Dell Kace K1000 in my organisation. Should My replication shares all be the same size?
Currently using Dell Kace K1000 in my organisation. Should My replication shares all be the same size. I currently have 22 rep shares with the same setup dotted around the globe but some of them have different sizes. What could be the reason for this?
| \\OAK01\KACE-Repository | 1.65 |
| \\OAK02\KACE-Repository | 800 |
| \\OAK03\KACE-Repository | 1.86 |
| \\OAK04\KACE-Repository | 1.92 |
| \\OAK05\KACE-Repository | 1.21 |
| \\OAK06KACE-Repository | 2.08 |
| \\OAK07\KACE-Repository | 1.6 |
| \\OAK08KACE-Repository | 1.57 |
| \\OAK09\KACE-Repository | 1.57 |
| \\OAK10\KACE-Repository | 1.63 |
| \\OAK11\KACE-Repository | 1.91 |
| \\OAK12\KACE-Repository | 1.61 |
| \\OAK13\KACE-Repository - slow | 915 |
| \\OAK14\KACE-Repository | 1.03 |
| \\OAK15\KACE-Repository | 1.61 |
| \\OAK16\KACE-Repository | No Acess |
| \\OAK17\KACE-Repository - slow | 1.66 |
| \\OAK18\KACE-Repository - slow | 1.89 |
| \\OAK19\KACE-Repository | 1.61 |
| \\OAK20\KACE-Repository | 1.61 |
| \\OAK21\KACE-Repository | 1.61 |
| \\OAK22\KACE-Repository | 1.4 |
Please help
3 Comments
[ + ] Show comments
Answers (1)
Please log in to answer
Posted by:
MacDude
10 years ago
Be aware that you can choose not to send some patch subscriptions to some of the replication shares. For instance if you know that you don't having any Windows XP systems at a remote site, you could unselect those patches in the Replication share and then it would have a different total size.
Are there items in the Queue for a given site that are not yet pushed?
1. Connection type (T1, VPN...etc)
2. High/Low bandwidth speeds
3. Schedules
4. Applications created but removed before next schedule
5. Patches replicated to certain sites but removed or deleted before another schedule kicked off to a different replication point. - nshah 10 years ago
Yes I believe they are on the same schedule. Please let me know if there are any additional info I can provide to help pin point the issue.
As for the OAK16, i figured out it wasnt shared and hence reason for being unable to access. - OAK 10 years ago