You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
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).
SCCM integration would be super simple. Just use powershell 'Get-CMDevice' to get all computers in a collection and use my JSM.Insight module to post to Insight.
We are toying with the idea of writing one anyway which I will share if it comes to pass. But as we have been moving our assets to InTune they might skip SCCM..