I got sick of waiting for Insight to come up with a viable solution to scraping info from workstations and importing it into JSM. The discovery tool is just such a mess in a large environment that I felt it was just not worth it and as Jira still hasn't given an ETA (or even said if it is on the roadmap) I decided to just skip them and do it myself.
So I rebuilt the windows discovery agent in PowerShell.
It is running on PowerShell 7 and as such is cross-platform, however, I have only designed it for Windows at this time with Mac\Linux coming further down the line.
I will be rolling this out to my 5000 workstations shortly so will keep this function updated with any changes that I see.
Inside JSM I used a copy of the schema that Insight discovery makes and made just a few changes to the way that the fields are named so you all should be able to work that out fairly easy.
My solution to the issue with JSMs import needing to be done manually is to have the output converted to JSON and then pushed to an azure blob directly from the workstation, and then all the files are downloaded on a schedule and imported into Insight via my main JSM.Insight module all via a scheduled task (run on one of our servers).
If you are not looking for updates as often or have fewer workstations then you could simply do a Get-InsightObjectByIQL (store the returned ID in the registry so you don't have to look it up every time) against the CMDB for that device and then Set-InsightObject right from the host (after a network check).
Hi everyone - in case you haven’t heard, we’re hosting the show of the century on November 10th: High Velocity: ITSM World Tour. This virtual, concert-themed experience...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events