Jump to content

Ricky

Hornbill Product Specialists
  • Content Count

    130
  • Joined

  • Last visited

Everything posted by Ricky

  1. Hi Dan, sorry to hear that your access has not been enabled I will inform the team, and get someone to look into it for you. Regards, Ricky
  2. Hi Andy, I believe this issue has been resolved, sorry for any inconvenience, I will get the team to have a look and get this sorted in your instance asap. Regards Ricky
  3. Hi @AndyGilly The issue is with the Runbook Process, in that the Human Task node will suspend the Runbook Process, waiting for user input. There was a design decision to remove all actions that have the protentional to suspend Runbook processes. I have been looking at possible workarounds that can be put in place, by moving the creation of tasks into a business process. This would involve temporarily storing the task details in a custom field and using the details to populate the Human Task from within the Requests Business Process. This would of course link the task to the BPM w
  4. Hi Andy, I noticed this issue late last week, and have asked our development team to have a look at it, which hopefully will be today, and will get back to you with an update as soon as I have further details. Regards, Ricky
  5. @AndyGilly Unfortunately it is not possible to use the Human Task node as provided within the BMP as it would block the process from completing until the task was completed. I will have look to see if there are any other methods that can used to do something similar. Ricky
  6. @AndyGilly I have asked the question internally, and it looks like currently that feature is not available via a Runbook. I am waiting from a response from the development teams with regards to enabling this feature, and will get back to you once i have further details. Ricky
  7. Hi Andy, apologies it looks like in my previous post I am referring to logging a request and assigning it to an existing request, to log a new request you need to use the Cloud Automation Node and select the method highlighted in the image below: Mot sure myself with regards to creating tasks, I will ask one of the Service Manager team to have look and see if its possible. Ricky
  8. Hi Andy, From within the runbook process you should be able to add a Hornbill Automation node, where you will be able to select the Service manager and specify a Request entity:
  9. Hi Andy, This usually occurs when the Job has not reached the SIS, can you check that the SIS is online and able to connect to the cloud. You should be able to check this via the SIS Status web page on the SIS server http://127.0.0.1:11117 Ricky
  10. Hi Andy, I have received feedback from our development teams with regards to browser related issues. We currently have no issues outstanding relating to any of the following browsers; Google Chrome, Firefox, Safari, Edge (Chromium) or IE. Regards, Ricky
  11. Hi Andy, thank you for your post. I can confirm that I have been using Edge with the ITOM Admin tool and have not found any browser related issues, however I believe that you may be requiring a more broader answer relating to testing against the Hornbill platform. I therefore asked our development team to look into this and will get back to you as soon as I have been received a response. Regards, Ricky
  12. Hi Dan, you should now have access to the Free ITOM offering. Regards, Ricky.
  13. Hi Dan, due to the ITOM preview closing, and moving into an Early Adopter stage, a new licensing mechanism is now being implemented which is the cause of the ITOM feature being temporarily removed from your instance. ITOM will re-appear once the licensing mechanism has been put in place and is pushed to live, and access will be enabled with some restrictions put in place for all unlicensed users. The Free (unlicensed) access will be available for all active Hornbill customers and will provide limited access to ITOM and all of its features, ideal for those that wish to try it out before co
  14. Hi Dan, Sorry to hear that you are experiencing this issue I will have a look into it and get back to you as soon as possuble. Regards, Ricky Fearon.
  15. Hi Andy, If you created input parameters when you created the package they should show within the properties of the IT Automation / Runbook nodes: If you do not see these then they need to be configured in the package Regards, Ricky Fearon
  16. @AndyGilly I can now confirm that the fixes have now been applied to the live stream and should now be available for your usage. Regards Ricky
  17. HI @AndyGilly We have found and corrected the issue that you have been experiencing when attempting to configure a IT Automation Job within the Scheduled Jobs and via a BPM process. This and a number of other issues are now being put through testing before being released to the live stream. I will let you know as soon as I am able when these are available for live usage. Regards Ricky
  18. Hi @AndyGilly, Currently then the solution for the Password reset is yet to be finalised however it is one of our priorities. Earmarked as part of the ITOM offering, due to the specific behaviour it is envisaged that some features are developed independently from the ITOM feature set. The feature provides a mechanism for a standard password reset via a simple service request utilising an ITOM automation, and for users that have been locked out or require a password change without logging in first. One or more, the following could be provided: Service request via the Mobile App
  19. HI @AndyGilly Have not had anything back from development as yet, but will be discussing this with them this morning so should have some further information for you today, and will get back to you asap with some further details. Regards, Ricky
  20. Hi @AndyGilly, Sorry for the delay, only just noticed the post. It looks like there is an issue with the Scheduled Job configuration which I believe has been raised with the development team who are looking into the issue. I will discuss the progress with resolving this issue, and get back to you ASAP. Regards, Ricky
  21. @AndyGilly We have identified an issue with the SIS Service when attempting to impersonate the account provided by the Admin Context, configured when creating a IT Automation Job. Our development team have now been able to replicate this issue, and are currently investigating the root cause. A workaround has been identified that involves using the account that is currently provided via the Hornbill KeySafe for the Admin Context to be used as the Log On Account for the EspSisService. This can be set via the Services MMC (services.msc): Applying directly to the service no long
  22. There are details of these requirements within the Package documentation that you may already be aware of, these details are mentioned in Target Environment Details section with a link for further details: https://wiki.hornbill.com/index.php/Active_Directory_Group_Management The Full list of Package Documentation can be found here: https://wiki.hornbill.com/index.php/ITOM_Package_Library
  23. Hi @AndyGilly Looks like you may not have installed the Powershell module for Active Directory Web Services. you can check this by running the following on the SIS server from within the Powershell CLI: Get-Module -List This will list all the modules and you should see Active Directory in the output, if this is not the case then you can add it by entering: Add-WindowsFeature RSAT-AD-Powershell
  24. @AndyGilly that looks like the issue is with the server that’s hosting SIS, does not have the Remote Server Administration Tools (RSAT) installed. They can be installed from Server Manager, Add Roles and Features. Ricky
  25. Thanks for the reply @AndyGilly did you receive the Powershell script that I sent you via Daniel Riley? If so would it be possible to execute the script on the SIS server? If this script executes correctly then it would finally prove that the issue is with the deployment. Also could you send me a copy of the error message, if it differs from that which we experienced yesterday. Cheers
×
×
  • Create New...