/build/static/layout/Breadcrumb_cap_w.png
04/15/2019 139 views

We have a site with low bandwidth so we set up a working replication share. However I noticed we can only assign one device label to one replication share. Since we have 3 device label groups with 3 different schedules, I created a single device label and nested the 3 device groups into the single label. I then set the single label to the replication share. Will this work as in should all the devices (With multiple device labels now) use the same replication share for their schedules?  The worry is that since the devices have more than one device label, how does it know to use the share and not try to go over the WAN?

0 Comments   [ + ] Show comments

Comments


All Answers

1

We create a site label based on IP (something that is unique). Assigned that label to the replication share.  When one of the patching jobs come time to run.  The job will use the device labels tied to it to tell those machines to patch    The SMA will initiate patching and when they check in with the SMA it will tell them to go the share based on the site label assigned to the share to get the files.

You should be able to create a site smart label "if the machine has Label X assign it to the site label" and they will run when scheduled and get the patches from the replication share.

Answered 04/15/2019 by: SMal.tmcc
Red Belt

1

This will work.
Any machine can be linked to 0 to unlimited device labels.
The Repl Share label just says that this machines download from the repl share, nothing else.
All jobs are working on the device labels which are assigned to it.

A nice example:
You have 3 sites:
Main
R1
R2
R1+R2 have a repl share with a smart label containing all machines which are logged in with a local IP address.

Miss Superboss is normally in the main site and so her notebook gets updates from the appliance itself directly.
If she visits R1 and joins the local network the normal update task she is having is fulfilling the updates from the repl share R1.
If she comes back to main, the updates will be delivered by the KACE itself.
And as you may assume, if she visits R2 the updates will be delivered by repl share R2.

Answered 04/15/2019 by: Nico_K
Red Belt

0

So what we noticed was that bandwidth increased significantly b/w the SMA and a target server when we ran a patch job. I noticed on the replication share setting, it started to downloading files during this time as well. So did the server detect missing patches, did not see them on the Share, then went to the SMA to get them? The replication share is set to "failover" to the appliance. How can we see where the server is getting the patches from?  

Answered 04/18/2019 by: lama01
Senior Yellow Belt