HaloPSA - RMM Integration Setup (NinjaOne)

Поділитися
Вставка
  • Опубліковано 9 лис 2024

КОМЕНТАРІ • 4

  • @jforceX
    @jforceX 6 місяців тому

    Thank you for the deep dive into the topic! What I still haven't sorted out, is the asset number thing. I think asset numbers should be an identifier that - in an ideal world - matches the clients inventory number. Any thoughts on this? Just filling it out with the ninjaOne's hostname doesn't seem to bring me closer to this objective... The tips regarding dedicated top level and dedicated client as control bucket are worth its weight in gold.

    • @risingtidegroup
      @risingtidegroup  6 місяців тому +1

      It's really up to you on how you want to use it, the key is what value you want to see as the title of the asset. In most cases this will be the hostname/computername of the computer (for assets that are computers), but you can make this whatever you want, including swapping out other Key Fields onto a different field such as the Name or even a brand new asset field that's used for tracking the customer inventory number.

  • @iConk3r
    @iConk3r 25 днів тому

    You walk through setting up unmappned Ninja clients to land in the NinjaOne Top Level, but then you never revisit that thought to show how to resolve clients that land there.
    Do you delete the auto-imported client, then go back into mappings and map that client to the true Halo org?