Jump to content

Steve G

Hornbill Developer
  • Posts

    746
  • Joined

  • Last visited

  • Days Won

    30

Posts posted by Steve G

  1. Hello everyone,

    The latest update of Hornbill ITOM (27) has been released to live.

    The change log for this update is as follows:

    Change

    • Added [Manage Executed Runbooks] to application navigation
    • Plugged-in new application navigation using same style as new admin navigation
    • Moved the Runbooks and Installed Packages links from admin area to user application menu
    • Styling improvements across the application

    Fix

    • Issue with the job view console trying to scroll down on page load
    • Time zone selector of a scheduling job was missing
    • Unexpected error when opening scheduled runbook jobs
    • Issue when filtering the inventory by a list and then looking for unmanaged inventory
    • macOS package filtering issue
    • Issue where the breadcrumb was not visible on the site integration services panel
    • Issue when opening a job from a parent job
    • Unable to delete a job from the job list
    • Issue where the Hornbill package library button did not respond
    • Package command line cursor in Operation form mis-aligned
  2. @AndyHill,

    I've tested both operations in the PRTG package and they are working with our PRTG server. But to help with your diagnosis, we've just released an update to the PRTG package that outputs more debugging information.

    Let me know how you get on, and please post any errors here so we can investigate further if need be.

    Kind regards,

    Steve 

  3. Hi @davidrb84,

    Sure have :) Take a look at the example PVA here: https://github.com/hornbill/hornbillPowerVirtualAgent

    There are Power Automate flows contained within the solution that do exactly what you need. You need a subscription that allows for the use of premium connectors within Power Automate though, as the flows make use of the HTTP Request connector to make the calls into Hornbill, and this is a premium connector.

    Note: we're releasing an update to the PVA in the next few days, with an additional flow to assist in the identification of your chatbot users against your Hornbill users, so keep a look out for that.

    Let me know how you get on.

    Cheers,

    Steve

  4. @Kevin Allitt,

    As well as Keith's curl explanation, there are examples of how to make API calls using Python here:

    https://github.com/hornbill/pythonPowerBIHornbillDataSources

    And we also have a library for making API calls from Python easier, which lives here:

    https://github.com/hornbill/pythonApiLib

    Cheers,

    Steve

  5. Hi @Andy Gilbert,

    I've just had a look at what is required here, and the last logged on user data is currently only available in the beta version of the Intune Graph API and not v1.0. 

    In their beta API, the windowsManagedDevice collection returns an object called usersLoggedOn, which is a collection of loggedOnUser objects. Contained within each object in that collection is the userId (objectId) and lastLogOnDateTime properties. So you could use that, along with the Get-HB-User cmdlet from the HornbillHelpers PowerShell module to populate the appropriate columns when creating/updating asset records.

    Once Microsoft have moved their beta API to production, I'll make sure the above changes get added into the Intune import script.

    Cheers,

    Steve

    • Like 1
  6. Hi @lee mcdermott,

    Post To Channel is a deprecated operation (still there so as to not break existing workflows) that uses keysafe keys of type Microsoft, and has been replaced by: Microsoft > Teams > Channel > Send Message, which uses the Microsoft Teams keysafe key type. So if you switch over to the new operation, you will see your Teams key listed.

    See the Hornbill Wiki for more information.

    Cheers,

    Steve

  7. Hi @lukeb,

    I'd suggest using the -dryrun=true argument when running the tool, and check the resulting log. This will not delete any records, and will output details of each record that would have been deleted if you had run it without the dryrun argument...

    And as always - check twice, run once. :D 

    Thanks,

    Steve

    • Like 1
  8. Hi @Berto2002,

    1. The new Teams integrations that post to chats or channels in Teams do not require Azure/Office 365 admin access, so you can create a generic Service Desk account and use that account against the keysafe key that is performing your post operations. The required rights are: ChannelMessage.Send, User.Read, Chat.ReadWrite. And the iBridge operations that require these basic rights are: 
      1. Channel
        1. Reply to Message
        2. Send Message
      2. Chat
        1. Create Chat
        2. Send Message
    2. As per the description against the content box, HTML formatting tags are supported by the API that we use to make the calls into Teams so you should be able to format those messages as required: https://docs.microsoft.com/en-us/graph/api/channel-post-messages?view=graph-rest-1.0&tabs=http
    3. See 2 above, same formatting restrictions apply

    A very basic example of formatting:

    image.png

    Hope this helps,

    Steve 

    • Like 1
×
×
  • Create New...