How Replications Work with the Tag


My question is about the behavior of the tag that I'm using on the "Destination Share" on my Replication task. I wanna know if this tag I have to use it on the Patch Task or is it enough having the tag on the Devices that need to use the repo replicated. For example, I have on the "Destination Share" the tag "A". I have some devices with this tag attached already. If I wanna apply a patch to a specific device inside A, and I create the patch task and I specify the device, when the patch is getting applied, is it going to use the repo that I replicated and specified the A tag? or I need to Specify the Tag A on the Patch task. My doubt is cause I don't want to apply the patch to all devices inside A.


0 Comments   [ + ] Show comments

Answers (1)

Answer Summary:
Posted by: Hobbsy 2 months ago
Red Belt

If you set a unique patch deployment to a single machine, and that machine is in a replication share, then only that machine will be patched.

So if you have a label D_Location_A for the replication share and Device _1 is a member of that label. Create a patch deployment schedule and select only Device_1 as the target, only Device_1 will patch.

  • It means that I only need to put Device_1 inside D_Location_A label and Everytime I patch it is going to use the repo attached to D_Location_A? I thought that I had to specify D_Location_A On the patch task, to use the repo for D_Location_A. - SoporteADPM 2 months ago
    • No the target device only has to be in the replication label, you do not need to specify it in the patch schedule. - Hobbsy 2 months ago

Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login


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