AndyGilly

+1 from us

Hi @Ricky just checking in on the next ITOM release progress?? thanks Andy

thanks @Graham understood we have built the error handling into the BPM that is triggering the request, it would have just been a nice visual in the job queue to see any failures in ITOM itself Andy

Would it be possible to have the Job 'Outcome' available on the Job Queue main screen Currently a 'failed' job just shows the 'status' which would be success as the process completed, even if it completed with a 'failed' outcome thanks Andy

Hi @Ricky by any chance did this one get accepted into the backlog? Just finding i am spending quite a lot of time during troubleshooting trying to find the matched jobs to request tickets e thanks Andy

Hi @Ricky appreciate an update thanks Andy

Hi @Ricky how we looking with this one?? thanks Andy

Would it be possible to have a column in the job queue for the source of the job EG the hornbill request reference or runbook process ID this would really help with trouble shooting many thanks Andy

Hi @Ricky any news on this one? its happened again post a SIS server reboot, we have had to log back in thanks Andy

I would like to make it possible for team members to amend the service and/or catalogue item against a request. I understand this will not impact the BPM but from a visibility and reporting perspective this would be helpful in some cases I have had a look at auto tasks and custom buttons but cannot see a way that the process could happen with the ability to select the appropriate service or catalogue item from a drop down of valid options have anybody implemented something similar?? thanks Andy

Hi @Ricky as an update: we are finding that in order for the Set-Execution policy job to work (it always states job successful but the policy has not changed) the server needs to be logged in as the Run As account and PowerShell open any other scenario - logged in but PowerShell closed, not logged in etc, the outcome is no change in the policy would appreciate any other thoughts you have thanks Andy

Morning @Ricky it would be great to get an update, we are holding off putting our automated new starter process live until this fix is in & and I would like to plan our release if possible please thanks Andy

thanks @Keith Stevenson, appreciated, I hadn't spotted that admin area

Morning Does anyone know of a way of checking if an email was sent when using the email - direct message send functionality? Should it still be visible in the sent folder of the system mailbox? Is there a way of getting the email onto the audit trail of the ticket? many thanks Andy

The service desk have been using the knowledge centre for a while with success We have found today that when logging a ticket in the agent portal using the 'New Request Process' that the knowledge centre suggestions that appear when you enter a summary or description do not represent the service portfolio subscription settings for the customer When using the knowledge centre in the Portal or in the agent portal under new incident or new request the correct catalogue items options are shown Can I check if this is by design or due to the process flow behind the 'new request approach' thanks Andy

Hi @Ricky, polite request for the latest on this one, thanks Andy

Hi @Ricky thanks for coming back, we have been using this view I was more after my options once we have a executed instance that has an error currently it seems we only have the re-run process option, but it very likely we dont want all steps to be re-run. Ideally, you would want the option for the runbook to restart from the failure point. hope that makes sense thanks Andy

Hi @Ricky is there an update on PM00166852 please??? we have been doing some new starter testing today and have found the issue to be appearing more frequently. We cannot see any logic to the error occurring (differing jobs etc) thanks Andy

Can I please ask for some guidance on supporting runbooks in ITOM I cannot find a way that if an instance of a runbook fails that you can resolve the issue and then ask the instance to restart from the point it has failed or from a given step Is there a way to do this?? thanks Andy

Hi @Stephen.whittle we are in a similar boat, we have had to build in quite a few error handling paths in the workflow to get the ticket reassigned to the Service Desk if the automation fails Managed By - not present, Managed By - disabled etc We have agreed internally that the Service Desk will fix the underlying data as tickets get raised for those AD Groups/ Dist lists and the data will improve over time. thanks Andy

Morning @Stephen.whittle primarily, this has allowed us to automate all of our approval process for any request that uses an AD Group We can now get the 'managed by' attribute from any on-prem AD group/ dist list etc and set it as the approver in the workflow thanks Andy

thanks @Ricky I have checked the native PowerShell. I manually set policy etc. Once i had done this on the box the automated job seemed to start working again I am not sure if it is a sequencing thing or what quite stopped it working but an end to end process was tested last night and seems to be working fine i am a little confused to why but we are back thanks Andy

PS C:\Users\svc-hbepcon-mgrauto> get-executionpolicy -list Scope ExecutionPolicy ----- --------------- MachinePolicy Undefined UserPolicy Undefined Process Undefined CurrentUser Undefined LocalMachine RemoteSigned

Monitor Supervisory processing for RunAs processing started as WWCORP\svc-hbadauto. PID: 9276 Package processing started as WWCORP\SVC-HBEPCON-MGRAUTO. PID: 9068 Payload processing started as WWCORP\SVC-HBEPCON-MGRAUTO. PID: 3132 #< CLIXML Bypass : Bypass {{SISJobOutputParameterStart:outcome}}OK{{SISJobOutputParameterEnd}} <Objs Version="1.1.0.1" xmlns="http://schemas.microsoft.com/powershell/2004/04"><Obj S="progress" RefId="0"><TN RefId="0"><T>System.Management.Automation.PSCustomObject</T><T>System.Object</T></TN><MS><I64 N="SourceId">1</I64><PR N="Record"><AV>Preparing modules for first use.</AV><AI>0</AI><Nil /><PI>-1</PI><PC>-1</PC><T>Completed</T><SR>-1</SR><SD> </SD></PR></MS></Obj><Obj S="progress" RefId="1"><TNRef RefId="0" /><MS><I64 N="SourceId">2</I64><PR N="Record"><AV>Preparing modules for first use.</AV><AI>0</AI><Nil /><PI>-1</PI><PC>-1</PC><T>Completed</T><SR>-1</SR><SD> </SD></PR></MS></Obj></Objs> The job was executed successfully.

Debug Log - post library update applied Standard -------- 2021-04-07 13:50:50Z Package filename: C:\Users\SVC-HB~1.WWC\AppData\Local\Temp\Hornbill\SIS Package Processor\2416f7c9-5bc8-40c7-abff-9e9db0132671\Alternate\Package.pkg 2021-04-07 13:50:50Z Operation: Set Execution Policy 2021-04-07 13:50:50Z Analysing input parameters 2021-04-07 13:50:50Z Parameter: Name: ExecPolicy Value: Bypass 2021-04-07 13:50:50Z Parameter: Name: Scope Value: LocalMachine 2021-04-07 13:50:50Z Target platform: win3264 2021-04-07 13:50:50Z Command Type: ps1 2021-04-07 13:50:50Z Timeout: 300 2021-04-07 13:50:50Z Using executable C:\Windows\system32/WindowsPowerShell\v1.0\PowerShell.exe 2021-04-07 13:50:50Z Plain text arguments: .\"SetExecutionPolicy.ps1" -ExecPolicy "Bypass" -Scope "LocalMachine" 2021-04-07 13:50:50Z Base64 arguments: LgBcACIAUwBlAHQARQB4AGUAYwB1AHQAaQBvAG4AUABvAGwAaQBjAHkALgBwAHMAMQAiACAAIAAgAC0ARQB4AGUAYwBQAG8AbABpAGMAeQAgACIAQgB5AHAAYQBzAHMAIgAgAC0AUwBjAG8AcABlACAAIgBMAG8AYwBhAGwATQBhAGMAaABpAG4AZQAiAA== 2021-04-07 13:50:53Z Processing result: Exit Success Full ---- 2021-04-07 13:50:50Z Log filename: C:\Users\SVC-HB~1.WWC\AppData\Local\Temp\Hornbill\SIS Package Processor\2416f7c9-5bc8-40c7-abff-9e9db0132671\Alternate\Processing.log 2021-04-07 13:50:50Z Local computer name: WXAPSHRNBP01-01 2021-04-07 13:50:50Z Package filename: C:\Users\SVC-HB~1.WWC\AppData\Local\Temp\Hornbill\SIS Package Processor\2416f7c9-5bc8-40c7-abff-9e9db0132671\Alternate\Package.pkg 2021-04-07 13:50:50Z Operation: Set Execution Policy 2021-04-07 13:50:50Z XML result filename: C:\Users\SVC-HB~1.WWC\AppData\Local\Temp\Hornbill\SIS Package Processor\2416f7c9-5bc8-40c7-abff-9e9db0132671\Alternate\Result.xml 2021-04-07 13:50:50Z Timeout: 300 2021-04-07 13:50:50Z Encoded parameters: okpfR9fnZEwMovC0_-G_42TYE2Mo5b75u0qQUTTgsa6mx5GSj7HFkit8--pAYT5phA0eaL4rLSF7-3SCmrveB88s8xKb5-G-lMfC9j6TxgZXoUwhTMf_mdvM_z73Sjb42106Z5uqOk84806NBTr5CB_Oe8XkOYuiEvh8NJT522TiVA31MFvyLciT5kFnhyQ0RcMGoZEp348pQkaqxhwATscYYxVbmFkrHtihtTIN0vw1Cdxpho0h83HgbQ2rJx6Y8s689i9nBA3Hhb_ORRrN2JLAgCXKjukUDc8PNsabogxHOD24nH0md1ABPJOwYN0BB_opryI5gp1xd_3cPn6yQOV5ZZOezxgqBZispQeazTc1zcE8BXhRqxd6LuXGvYyzO17F 2021-04-07 13:50:50Z Encoded credentials: RMFrQFMVdXvfl5MRvBNLUrH8QwNHF3CeioK1TGCfUO-TsWEwS2TMFuHY3OOAs3M7Mgq8vdFJC199A6O_Uo8PwbVVTFdj1yJ7nuuxlW9NJptUGcD6rMj31AMw5pL6eDSMR_WfyFOSzKIVriMBRsWjsj-88gOAdA8oQUBgY59jRNNYzgQD3gJmt5PWxrxc7ieL-M9mQpzz4QGVc4qMymp2qFPUIHDqdWv4UeTtNZolE11GmemlrtxlP4KPuH-e_NPal14pyn3AUsk-Y-ZMmlgV3Ohzjy8obbToDuemCoztyU5G2-0xArYCRfhQ-J6V08tSEfRH5l8fNUbJNHJ3lC3ZT11eCfiFRbGWhToIHtH9gL0Nad-mCq3p8CKEDuSySg 2021-04-07 13:50:50Z Callback context: zEmgs7Gp31vYr23mB4kYjIXvYis_uEMG51ke4_KbXAx8MWKJORKBIh9faqQ8-6QZ9gAStYQpeveDemPQAVNc43aDJVxhZ58fzWR3xjTTIlsxBLxMfsmH4lcUKqIZgqi0hpYAvH18106iU5pLA3R3e26PxlK1ZEE18mlo_EBV3as0nS67I-bYNKva_CFZvR8ZGIRIiZdui5T5sPpG6EVywAyc6LkiiXxAUv0q7ZR9AASyBUu483CLFc1Cn006jbKvYfOAu8ZXl9kqRa4I8Q48Y47kuT38ikTVAxj-5G6WzfRHYZxM3j0kjQ9TTLYQAJgfEPvdXsFaeAYJD4zgjNtWGc32aO9q0u1bMH3SuFqWUcFcyhbTDW8 2021-04-07 13:50:50Z Log line prefix: P 2021-04-07 13:50:50Z Package processing started as WWCORP\SVC-HBEPCON-MGRAUTO. PID: 9068 2021-04-07 13:50:50Z Analysing input parameters 2021-04-07 13:50:50Z Parameter: Name: ExecPolicy Value: Bypass 2021-04-07 13:50:50Z Parameter: Name: Scope Value: LocalMachine 2021-04-07 13:50:50Z Target platform: win3264 2021-04-07 13:50:50Z Command Type: ps1 2021-04-07 13:50:50Z Timeout: 300 2021-04-07 13:50:50Z Using the native variant of PowerShell 2021-04-07 13:50:50Z Using executable C:\Windows\system32/WindowsPowerShell\v1.0\PowerShell.exe 2021-04-07 13:50:50Z Plain text arguments: .\"SetExecutionPolicy.ps1" -ExecPolicy "Bypass" -Scope "LocalMachine" 2021-04-07 13:50:50Z Base64 arguments: LgBcACIAUwBlAHQARQB4AGUAYwB1AHQAaQBvAG4AUABvAGwAaQBjAHkALgBwAHMAMQAiACAAIAAgAC0ARQB4AGUAYwBQAG8AbABpAGMAeQAgACIAQgB5AHAAYQBzAHMAIgAgAC0AUwBjAG8AcABlACAAIgBMAG8AYwBhAGwATQBhAGMAaABpAG4AZQAiAA== 2021-04-07 13:50:50Z Console Output: C:\Users\SVC-HB~1.WWC\AppData\Local\Temp\Hornbill\SIS Package Processor\b29ba7c8-38de-473d-8a45-a35d7b19d2c7\Output/Output.txt 2021-04-07 13:50:53Z Processing result: Exit Success