/build/static/layout/Breadcrumb_cap_w.png
12/21/2018 347 views

Hi!

So I have this problem (solved by right now with manual work).   There are a lot of smaller customers that really don't have anything I can successfully Filter on when they come in as a new device.

The normal company have a domain or some sort of name standard that I can pick up.


The ones I have now have nothing specific about them. Random names or ex Laptop - 000 or Mikes Computer.  

Is there any good way I could add something when deploying the agent or get these computers into a specific (not the default org) org directly without needing to move them after they come in?

Messing with the KUID would be a thing but then the agent just break and it cant be something to intrusive like changing their names at that point.

1 Comment   [ + ] Show comment

Comments

  • What version are you running on the KACE SMA.
    If you are on 9.0, you will need to open a support ticket to have a fix applied for Org Filters.

All Answers

1

What version are you running on the KACE SMA.
If you are on 9.0, you will need to open a support ticket to have a fix applied for Org Filters.

Answered 12/21/2018 by: KevinG
Second Degree Blue Belt

  • Is there a known issue with Org Filters not working in 9.0? We've been seeing issues with new machines not correctly showing up in our KACE Org recently.
    • This may be the resolution for me: https://support.quest.com/kace-as-a-service/kb/265755/org-filters-no-longer-place-devices-in-the-correct-organization
      • Correct, apply the kbin attached to the knowledgebase article to a 9.0.270 SMA
1

There are several filter criteria available under org filter to help you determine how to filter the devices. If you have an AD where the devices are connected, you may use an ldap filter as well. Agent doesn't have an ability to point the device to a specific org within the K1 appliance.


Answered 12/26/2018 by: AbhayR
Red Belt

0

*** warning - this post relates to KACE MSP admins with orgs that have no domain ***

BTW - Many kace competitors already have a decent download portal for agents that already identify the tenant\org it should report to :-(

This is how we hacked this (works at 80% of the cases)

Option 1.

1. Systemui> Organizations > Filters > Configure org filter with IP. add the internal LAN ip range of the client office.


2. Adminui (relevant org)> settings > General settings > under "ignored Client IP Address settings" add the company`s Gateway IP address.

This assign devices coming from an internal client network to their org. the downside however, is that you need to make sure the agent is installed while inside the network and that there are no overlapping addresses between orgs including generic 10.0.0.x (that can pop-up for home users...). 

Option 2. : with some clients we urge them to change the device system name to a generic name prior to agent install.

hope that can give more ideas.

Answered 12/26/2018 by: mulimotola
Senior White Belt