Kaseya Community

Naming Policy challenge

This question is answered

We have a situation where a client has 2 separate companies running on 2 separate AD domains all running from the same LAN subnet and connection gateway. The naming policy moves all devices from ORG 2 to ORG 1 because of this. Manually moving the devices works only until the next agent check up.

Is there a better way to be allocating devices to organisations/groups/group ID's etc. without requiring the naming policy to do the work?

I considered that domain based discovery might be the better way however I don't think I can manage it from here or at least not to get a device into a subgroup (which is the main reason behind using the naming policy).

Verified Answer
  • Our strategy for putting client machines into the correct groups is to specify which group they go into when the agent is installed.  

    You can do this by going to Agent -> Install Agents -> Deploy Agents -> Create Package and then walking through the wizard.

    You'd then want to setup a separate agent installer on each domain as part of their startup scripts.

    This will throw each computer into the proper group at agent install.

    You'll need to stop using the Naming Policy settings to make that work consistently.

All Replies
  • Our strategy for putting client machines into the correct groups is to specify which group they go into when the agent is installed.  

    You can do this by going to Agent -> Install Agents -> Deploy Agents -> Create Package and then walking through the wizard.

    You'd then want to setup a separate agent installer on each domain as part of their startup scripts.

    This will throw each computer into the proper group at agent install.

    You'll need to stop using the Naming Policy settings to make that work consistently.

  • Sounds like you should just leave them in one group

    Then any reports your run use the Agents Domain name as a reference.

    One idea you can do is create separate agent packages for Domain (that will assign the machine to the correct group and mcconnell has said) then setup a group policy that installs the correct agent when the machine joins the domain.

    Not much to it, just convert the agent install into a msi and slap it into a software install gpo.

  • This sounds like a workable solution. Thanks

  • Another option is to define the scope of the Naming Policy using the internal IP ranges.  If they are coming from the same WAN that is okay, but internally are they on different networks, or perhaps range within a given scope?   If you so you narrow the naming policy down by that internal range.  So for example 192.168.1.1-100 is network A and group A, and 192.168.1.101-255 is network B, group B.  Hope that makes sense, we use this for similar clients we have.