Jump to content

Ricky

Hornbill Product Specialists
  • Posts

    226
  • Joined

  • Last visited

  • Days Won

    5

Posts posted by Ricky

  1. @JanS2000, When you delete a user from within Hornbill, any Request, Asset, Service Subscriptions etc. that has been associated, you should assume that the link will be lost.  In some cases, if you re-import a user with the same User ID, then some associations to entities such as Requests, Assets Ownership and Service Subscriptions will be re-established, although this is not guaranteed.  If you have changed the User ID, all links must be established manually.

    To retain the links, you would NOT delete the record within Hornbill and modify the Import to use a different field to identify users uniquely, for example, the Login ID field.  Of course, if the login ID is also changed, you must manually modify this field in Hornbill to match the new login ID being imported. 

     

    • Thanks 1
  2. @JanS2000 The issue you are having where the Handle already exists is due to the modified field being used to populate the userId field within Hornbill, causing the import to attempt to create a new Hornbill Account.  This would then fail due to the original account that has the old UserId having the same Handle as the new account being created; the Handle is configured so that it is required to be unique.  To get around this error, you could delete the old account or modify the Handle on the old account (you may also have to do this with the Employee ID)so that it differs and set it as Archived.  As @SamS has mentioned above, a feature within the import enables you to utilise another field other than the userId. In the above cases, you must use another field, such as the loginId, which should resolve the errors you see.  Obviously, this option would re-use the existing Hornbill account, which may not be desirable in case of a role change unless you change the Roles, Teams, Groups, etc., that the account is a member of within Hornbill.

     

    • Thanks 1
  3. Hi Jim,  How the installed software entries are managed depends on the tool used to import the software details.  If you are using the Database Asset Import tool, the installed software list against each device will add and remove entries each time it is executed when a change has been detected.

    Specifically, I will need to look at your methods to populate the tables to better understand your particular issue.  You currently have request open with myself on the is subject I will schedule a session so that we can investigate this further.

     

    Ricky

  4. @QEHNick Unless you have enough licences within your ITOM subscription to enable all your computer devices to be categorised as managed, I would suggest that you keep using the import tool.  This will allow for more information to be captured against each device, which is most likely not currently supported within the ITOM inventory.

    Regards,

    Ricky

     

  5. Hi @QEHNick, thank you for your post.  The ITOM Inventory was not designed to be a Asset Management tool, its purpose is to provide a list of devices that can be targeted by an IT Automation.   However ITOM can be used to import Windows and Linux devices that have been classified as Managed within the ITOM inventory into the Service Manager Asset database.  Assuming the information captured within the inventory satisfies your requirements and the relevant subscription is in place then the ITOM Service Manager Import could replace the import from your asset management tool.

    Regards,

    Ricky

    Product Specialist

  6. Hi Adam,

    Thank you for your post.  Unfortunately it is still not possible for the SIS to communicate via a Proxy service currently.  I have asked our development team on the plans to provide this feature and will get back to you once I get a response.

    I am also not not sure that I understand what you are trying to achieve and why the requirement to utilise a proxy server for the secondary SIS.

    Regards,

    Ricky Fearon

  7. Hi@Francis von Stein, my apologies for the delay in responding to your post, this seems to have been left behind due to our investigations with another ITOM query.  We have looked at the issue and are not able to replicate the issue.    It looks the issue maybe related to the data that you are passing to the node.  Can you confirm that you are still experiencing the issue?

    Regards,

    Ricky

     

  8. Hi@Adam Toms,  thank you for your post. I can confirm that this is a known issue; relating to a later version of the unstalled SIS compared to that available on the live stream. Usually, due to a patched version of the SIS software, and will not cause any issues with the operation of your SIS. The problem will resolve itself once the latest SIS is release to the live stream; we will also be addressing the issue so that it no longer occurs for future patched releases.
     

    Regards,
     

    Ricky

    • Thanks 1
×
×
  • Create New...