Liongard Ideas Portal

I am guessing by this quite old idea that there is still no way to automatically have the assets and the configurations for the exact same device either be overlaid like the RMM does or solve it in some other way.

It is no fun seeing a list of 600 configurations knowing that there is only 300 physical devices.

Relational documentation is key - the flexible assets we are populating need to be linked with existing configurations in ITG wherever possible. Most of these assets can be matched with existing configurations based on device name alone. Many script based documentation solutions have this capability.

Users/Group level tagging:

https://www.cyberdrain.com/documenting-with-powershell-chapter-6-documenting-active-directory-groups/

Computer/device level tagging:

https://www.cyberdrain.com/documenting-with-powershell-chapter-2-documenting-bitlocker-keys/

From an AM feedback session:
if we could structure flexible assets as we want and push roar's data into the places we want in it glue how they are already trained, then that would be ideal! we also have equal breakfix customers - there wasn't a standard because for some customers we told them to go to roar's FAs and for others they had to go to manual FAs. Our team consistently said it would be nice if we could pull in Roar's data to IT Glue where we want it (in our own FAssets in your fields).

I would like to see pushing the status updates Liongard sees for servers and workstatoions. So if you see in the AD inspector a "Stale" machine, it would automatically update IT Glue's Configuration with an "Inactive" status.

Relating is all well and good, but it���s inefficient and a ton of ongoing work. We already have our ITGlue organized where specific information is in a specific page. The idea being all information in the right place. We don���t want to have to click through to related pages to find more information among a lot of included info when all we need is specific information where we need it. Not to mention, Related pages are a manual update. We���d have to go through 50 clients and manually add related pages any time we add something to Liongard, which is silly. I���d rather do the work once to point to a specific flex asset on a specific page for that agent so everything is where it belongs to begin with, and this is the same regardless of the client. I can see your method working for new users of ITGlue who can build their documentation around Roar���s assets, or single users with only their own company to worry about, but for existing ITGlue clients who happen to be MSP���s, this just won���t do.

Mike Bohde
Support Services Team Lead

[cid:image001.png@01D5B1C7.C88C64F0]
Happy Holidays to You and Yours!

Help Desk: (919) 459-0128
Hours: 7:30am-5:30pm
Email: support@technologyassociates.net
Follow us on Twitter: @techassociateNC
Please Note: After hours emergencies should be initiated by phone , press option 2 to be connected with our on call Engineer.

[FB] [Twitter] [LinkedIn]

yes please.  Flex Assets chock full of info is nice, but still need the configs to link to other Flex Assets unrelated to Roar.

In addition to Configs, also the ability to send Liongard's data to existing flex assets, instead of the built in Liongard flex assets.