Systems Management Question

what is the cause of my replicates assigning themselves automatically to other label names?

10/13/2014 2031 views
i've created replicates before for all my branches but recently, my servers have been assigning themselves to incorrect label names. i even getting duplicate servers assigned to the same branch
10 Comments   [ + ] Show comments


  • What version of the k1000 are you on. If you are using ldap there was an issue with 6.0 that added ldap labels to everything

    if you aren't on 6.0 and upgraded to 6.2 I could check the smart labels. The only way it should be giving the labels out, sans issue, is if they met whatever criteria you setup for them.

    I am not understanding the duplicate servers? Do you mean you see multiple records for the same server? Does it have dual NICs?
  • im using version 6.0 of teh k1000. so what actually happens is, every new device that creating a replicate for is actually assigning itself to a replicate share and label that already exists and somehow kicks out teh existing device in that share. for example.lets say i have Barnets service which belongs to branch 3254 Alberton. this will be a new store opened and i need to create a replicate for it. label name, smart label, replicate download path have already being created. all i need to do is just create a replicate for it but now the problem is that when i save this replicate, it automatically assigns this device .e.g the SERVER to another existing replicate and the existing replicate becomes unassigned with no server to assign......
  • i cuurently have about 5 existing replicates unassigned and whenever i assign that replicate its correct server/device, it automatically assigns a different one.
  • i'm unable to send you a screenshot of what i talking about.
  • Just to make sure I understand...
    You are creating a NEW replication share for branch 3254 Alberton.
    Your server is Barnets with an IP of that is assigned as the server for that replication share.
    When that happens, the Barnets server gets reassigned to a different replication share and the 3254 Alberton branch replication share has no server associated with it.
    Is this correct?
    • hi h2polo25. that is correct. and the 3254 barnetts server is automatically deleted.
  • hi h2polo25. that is correct. and the 3254 barnetts server is automatically deleted in kace Inventory
  • the 3254 Alberton server is deleted automatically because when i search for it, it doesnt appear in inventory.
  • Wow so the server disappears not only from the Replication Share but also from the Inventory?
    Since both you and sskhoza are having the same issue I would create a ticket with KACE support to have them look at it since it's most likely a bug.

    Also post what specific version you are running. It might be due to a hotfix (like the LDAP hotfix) since I set up my replication shares in v6.0 before that hotfix was applied and have not had any issues with them.
  • thanks h20polo25. i'll be logging a ticket with kace support this morning
  • morning h2opolo25. im battling with a report that i need to create for all servers that have sql server installed and microsoft.net framework. would you perhaps have an idea how i could do this coz i'm only winning in getting the servers but when i add a query for the software it just gives me all the software installed instead of this specific ones i need. this report needs to be generated from system.

All Answers

Hi Tom,

I'm experiencing the same issue, searching for solutions too..
Answered 10/14/2014 by: sskhoza
White Belt

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