AndyGilly

ok @Daniel Dekel understood

Thanks for the quick reply @Steve G i will have a chat with the dev

We are trying to put some error handling into our PowerShell scripts that are making packages in ITOM. When the script is processing it does not seem to be able to step from a 'try' statement into a 'catch' The try is processed successfully if everything is valid but if its not then falling into the catch does not happen. The Powershell script itself seems to run OK in Powershell ISE would appreciate any thoughts or guidance thanks Andy

thanks @Steve G, i have used that package and it is all working perfectly, thanks for the help

Hi @Ricky did this item get accepted onto the list?? thanks Andy

Hi @Ricky @Steve G for some reason the PowerShell cmdlet did not enable local execution globally, just for the local user context The answer was to go into the Local Group Policy Editor -> Local Computer Policy -> Administrative Templates -> Windows Components -> Windows PowerShell and double-click on 'Turn on Script Execution'. This then let me change it to 'Enabled' and then execution policy of "Allow all scripts" I would need to check with our security team to see if i can enable this policy on that machine fulltime Is this something you have seen in any testing??? Would you say this is WW environment specific? the Active Directory Package library scripts run fine, so it must be something about this specific ECM requirements i guess thanks Andy

thank you appreciated @James Ainsworth

thanks @Steve G - appreciated, i will take a look

thanks for the quick reply @Ricky, appreciated

within a runbook I would like to use the output of a PowerShell script as the description of a service manager ticket. Can you help with the best way to achieve this?? thanks Andy

Hi @Daniel Dekel our use case is that the separation of domain is used to enable reporting on domains of IT work. For us IT (customer facing SLA) & IT - Operational Maintenance (internal IT requests for back office maintenance of services) From a customer request perspective it would be great for the requestor not to have to understand which IT domain the request type is in , they could just hit an IT home page with both IT domain services visible thanks Andy

Hi @James Ainsworth did this use case get reviewed any further thanks Andy

Hi @Ricky we have moved on a bit but are now getting an error of: Error trying to add Device to Collection: This command cannot be run from the current drive. To run this command you must first connect to a Configuration Manager drive. appreciate any help thanks Andy

morning @Daniel Dekel thanks for the reply, thanks a shame. I understand that each domain creates its own page. But i didnt think that page had any filtering applied to its widgets until it was configured i was thinking the filter by service domain functionality could be enhanced to be able to take multiple options rather than one in a drop down thanks Andy

apologies, raised in the incorrect place, i have raised a copy in the subforum

could I please add this service to the list of integrations for review we are looking at a number of efficiencies an integration to this service could help with List of Open API (samsungknox.com) many thanks Andy

Hi @Daniel Dekel I was thinking anywhere the filtering is possible. Ideally i would like for a single employee portal page to represent more than one domain but not all like company home In our use case we have a Customer Facing Service Catalogue that is the IT domain & then a second manually created domain called IT - Operational Maintenance which represents other BAU activities like backups, environment restores but this work does not full as part of the customer SLA Ideally IT & a small number of specialist customers would be subscribed to services in both domains but have visibility of both domains of work in one portal page

please could you have a look at the possibility of the widget filtering to be enhanced to be able to select multiple domains from the list rather just 1 many thanks Andy

thanks @Ricky. we are working though this now

thanks @Ricky

Afternoon we have our first attempt to use the device collection process this morning. The ITOM job was a success but the output was a failure msg Failure to import SCCM/ConfMan/ECM Cmdlets:Cannot bind argument to parameter 'Path' because it is null. the debug log looks to be happy that it has all the items it needs. I cannot find what this msg means please can someone have a look?? thanks Andy

please could you consider adding a ITOM job for capturing the 'managed by' attribute of the on prem AD group many thanks Andy

Afternoon the new update asset functionality that has been added as a hornbill automation is great could we look at the possibility of there being a 'create asset' automation. this would really save the team time and allow us to add the cmdb update element fully in to our BPMs it would be great to be able to capture the required fields in the ticket and then use the create automation to generate the CI thanks Andy

apologies i missed the package rebuild step, that is now complete but still get the same error. new debug log below

Hi @Ricky have got around this by installing the most recent version of powershell on the SIS server but now get an output parameter error, here is the debug thanks Andy