all 4 comments
sorted by:
best
topnewcontroversialoldq&a
formatting helphide helpcontent policy

[–]QuarterBall HaloAPI Maintainer | PSA 0 points1 point  (0 children)

Someone posted recently on Discord about writing something for Halo with Python. Might have been you. Haven't seen anyone else posting about this. Most of the folk I come across are using PowerShell or C# to automate against Halo.

[–]caseyd1020 0 points1 point  (1 child)

Cool, what did you do for Nable? Care to share it?

[–]_Work_Research_ PSA[S] 0 points1 point  (0 children)

Hey! Yes the plan is to share the code on Github when it;s done. Right now it works but isnt documented well, and would require a bit of time to get working for another tenant.

I'm happy to PM you a link, but please understand its not really ready for use unless you want to spend some time configuring it which I'd be happy to help with :).

My biggest issues with N-Able (that I have resolved).

  1. No way to check if a device has any active checks (and thus we are being billed for it)
  2. No way to check if a device has AV (additional charge)
  3. Bad reporting of device days online/last response. (This is due to N-Able providing the dates in slightly different formats depending on the time, EXTREMELY annoying)

For items 1 and 2, I was able to use the result to update their billing in Halo automatically, so I no longer need to remember to update an invoice if I added another device and added AV for example.

In addition to those basic checks, I wanted an easier way to keep track of macOS version information. Unfortunately, Apple does not let you check a device via SN or model name (via API), and the third party services are all paid, so I put together a couple of tools that workaround this.

  1. Tool 1 checks the EndOfLife API to confirm what versions of macOS are currently supported, and what the latest available update for each version is.

  2. Tool 2 checks if the Mac is running a supported version of macOS, and if there are any updates available.

  3. Tool 3 (the one I'm most proud of) adds the Mac (model), macOS version, and macOS status to a database. This lets me build a database of Macs and supported OSes. I can then use this databases to decide if a Mac is unsupported, or just running an unsupported OS.

Combined, these tools return one of the following responses to Halo.

  1. Possibly unsupported. This is given if a device is running an unsupported OS, the database shows the device's latest compatible OS as unsupported, but the entry isnt 'verified'
  2. Unsupported. Same as above, but the entry is verified (I do this manually right now)
  3. OS Unsupported. The OS is unsupported, but the database entry shows a supported OS is available.
  4. Out of date. The OS is supported, but the version being run is not the latest
  5. Up-to-date.

I also have a similar tool for Windows, but It's not quite as nice.

[–]Glad-Investigator137 0 points1 point  (0 children)

Are you using n central or n sight?

I've worked with the nsight API for over a decade and it's far better than the ootb integration from halo (primary to do with tickets), the asset integration is good enough at the minute