Ben Maddams

Hello all, We're looking at creating a set of scheduled requests for maintainance and checks against a set of custom asset types. These would trigger on a monthly or weekly basis. I had a few questions about the creation of the actual service requests and couldn't find the answers elsewhere. 1. Summary Name: Is is possibly to insert the current date/month into the summary upon the creation of the request? I'm assuming this would have to be done on the business process called by the scheduled request, not through the Description paramter in the scheduled requests config screen? 2. The Asset: When the details of this asset are passed to the newly created request, can the workflow call upon this again to insert the asset name into the summary field? Example: "Widget 102" has a cleaning task run upon it monthly, so when the scheduled request is created it would automatically have the summary "[WIDGET A] - Cleaning Request Required [JUNE]" Thanks for any advice. -Ben

Thanks Gareth, will give that a go and report back. -B

I'm having the same issue in - Just asking if a solution for the missing fields was ever provided. Thanks, Ben

Hello all, I'm trying to embed an autotask on our asset screen, when used all it is meant to do is send an email through to our support mailbox to log a ticket, containing information present in the asset. Can somebody please explain why all of the output params come up blank when I use them in a Direct Email Send node immediately after? All the fields come up blank, only the assetID is populated and this does not actually match our asset tags, so it useless for the purpose we want. How can I use the assetID in the autotask, to capture the relevent information from the reset of the asset table, and send this through? Any help much appreciated, have been banging my head against this one. Many thanks, Ben

+1 Same here.

@Jim Thanks so much for your assistance with this! Was exactly what I was looking for and you've been incredibly helpful!

Hello, I've recently been attempting to produce reports and widgets against the number of assignment bounces on incidents and SRs, and found the thread below: In this thread, there is reference to an admin instance we can use to look into example widgets, but the credentials dont appear to be working. Can you please clarify if this instance is still accessible and what login we should be using to look at it? At the moment I'm trying to create a report into our monthly most bounced tickets, and it would really help to look at some working examples. Thanks, Ben

@Victor Yes thats in MS 0365.. I wasn't aware Hornbill doubles up on sent emails, so it captures them both internally and also inside the sent/outbox folders on the mailbox in 0365? We never did anything directely to set this up this way. @Keith Stevenson How would I check this in Hornbill? We only anticipated using the internal HB mailboxes for archiving/retention, and now I'm worried our other capture mailboxes may be affected too.

Hello, I've been reviewing our support mailbox as we've been getting message limit alerts on it's Outbox folder. It looks like it is overflowing (950K) emails and after review the sent items folder hit the 1million mark a while back (I suspect this is why the messages are now stuck in Outbox). I was under the impression Hornbill handled mail internally after captuting the mailbox so can you please explain why the actual 0365 mailbox is being filled with "alert" emails (i.e X has been assigned o your team). Any information on this would be appreciated as it appears mail hasn't been leaving Hornbill properly? Slightly concerned engineers and users haven't been getting the mails we've been sending them from inside Service Manager. Many thanks, Ben

Hello, Please can we get the ability to modify and create asset information from inside workflows, at the moment the only entity option is to Get Information but we really need to be able to add custom workflows to buttons on the asset information screen to duplicate/create new assets from existing asset information. I've seen this come up multiple times during searches, and many people have +1'd this going back to 2021, but the current advice to export and reimport via CSV is extremely time consuming for individual items. Thanks,

@Berto2002 @Joshua Howitt Have eliminated the error message - Have compiled a test calendar entry against my own calendar, but it always returns a fail code. I've tried using both my Calendar ID and the User ID as the target. Is there any way to get more information out on why this is failing? The OAuth account in KeySafe for this action is both a global admin, and has full permissions to the mailbox I'm trying to change. Can you please provide the authorisation requirements for the account in KeySafe to be able to make these calendar entries, both on the tenant and to the calendars it is trying to alter? I sent the output from the automation task to the timeline after the automation node, and just get this back.

Same issue - But looking at permissions for the test calendar now, so might be a mistake we've made our side. -B

Hi @Joshua Howitt Has there been any movement on this one? We're experiencing the same issue. Many thanks, Ben

@Graham Looks like the original job completed using WinRM without issue. I'm checking the credentials now. (EDIT Looks like one of our AD admins changed some account details - I've just re-run this under a new keysafe entry and it has worked. Testing onpremAD change jobs now) Standalone processing started. Process ID: 15672 Payload processing started as Local System. PID: 88280 15:51:12 Starting Hornbill Discovery Tool (build 3381, x64) run at 2024-02-23 15:51:12Z 15:51:13 Using SIS context (instance=rbgkew, sis=Hornbill SIS Integrations) 15:51:13 Discovery job ID: 1 15:51:13 Scan mode: list 15:51:13 Using dynamic threading 15:51:14 List discovery: XXXXXx 15:51:14 Ping required for scan: Yes (hop count=30, timeout=5) 15:51:14 Discovery probe protocol: WinRM 15:51:14 Discovery username: XXXXXX 15:51:14 Scan found 1 computers for detailed discovery 15:51:15 Performing DNS lookups on 1 computers 15:51:15 Using 1 threads 15:51:15 DNS lookups complete. checked=1, resolved=1, failed=0 15:51:16 Running ping check on 1 computers, timeout=5000ms, hops=30) 15:51:16 Using 1 threads 15:51:16 Pinging XXXXX => 10.4.1.1 15:51:16 Ping checks complete. checked=1, responded=1, failed=0 15:51:18 Performing discovery of 1 computers 15:51:18 Using 1 threads 15:51:18 Performing WMI probe for XXXXXX 15:51:25 Discovery information probe for XXXXXX completed OK (time taken 7s) 15:51:26 Merging discovery results 15:51:27 Discovery results merged 15:51:27 Discovery time taken: 9 seconds 15:51:27 Starting discovery data upload 15:51:27 Generating discovery log 15:51:28 Adding discovery log 15:51:28 Adding computers 15:51:28 Adding hardware vendors 15:51:28 Adding software vendors 15:51:29 Archived discovery data: 1 computers, 1 hardware vendors, 5 software vendors 15:51:29 Starting discovery data upload 15:51:29 Discovery data archive is 4823 bytes 15:51:29 Uploading discovery data to /sis/discovery/job_1.zip 15:51:30 Discovery data uploaded 15:51:30 Notified instance to initiate data discovery import process 15:51:30 Generating summary Summary ======= Successful Discovery -------------------- XXXXXX All Computers ------------- XXXXXXX: Success The discovery was executed successfully. The results are now being imported. 15:51:40 Starting the discovery import process 15:51:41 Opening import archive 15:51:41 Data discovery source: sis:Hornbill SIS Integrations 15:51:41 Device XXXXXX is being added to the inventory 15:51:43 Deleting discovery import file 15:51:43 Added: 1 15:51:43 Updated: 0 15:51:43 Skipped: 0 15:51:44 Missing: 0 15:51:44 Failed: 0 15:51:44 Discovery import complete

@Graham I reran Discovery on both machines, the admin box updated fine, but this was the result from the DC. Standalone processing started. Process ID: 18500 Payload processing started as Local System. PID: 27948 09:58:42 Starting Hornbill Discovery Tool (build 3381, x64) run at 2024-04-26 08:58:42Z 09:58:42 Using SIS context (instance=rbgkew, sis=Hornbill SIS Integrations) 09:58:43 Discovery job ID: 63 09:58:43 Scan mode: list 09:58:43 Using dynamic threading 09:58:43 List discovery: XXXXXX 09:58:43 Ping required for scan: Yes (hop count=30, timeout=5) 09:58:43 Discovery probe protocol: Auto 09:58:44 Discovery username: XXXXXXX 09:58:44 Scan found 1 computers for detailed discovery 09:58:44 Performing DNS lookups on 1 computers 09:58:44 Using 1 threads 09:58:44 DNS lookups complete. checked=1, resolved=1, failed=0 09:58:45 Running ping check on 1 computers, timeout=5000ms, hops=30) 09:58:45 Using 1 threads 09:58:45 Pinging XXXXXX => 10.4.1.1 09:58:45 Ping checks complete. checked=1, responded=1, failed=0 09:58:47 Performing discovery of 1 computers 09:58:47 Using 1 threads 09:58:47 Performing WMI probe for XXXXXXXX 09:58:47 Performing SSH probe for XXXXXXXX 09:59:08 Discovery information probe for XXXXXXX failed (time taken 21s) 09:59:08 Merging discovery results 09:59:09 Discovery results merged 09:59:09 Discovery time taken: 22 seconds 09:59:09 Starting discovery data upload 09:59:09 Generating discovery log 09:59:09 Adding discovery log 09:59:09 Adding computers 09:59:09 Adding hardware vendors 09:59:10 Adding software vendors 09:59:10 Archived discovery data: 1 computers, 0 hardware vendors, 0 software vendors 09:59:10 Starting discovery data upload 09:59:10 Discovery data archive is 946 bytes 09:59:10 Uploading discovery data to /sis/discovery/job_63.zip 09:59:11 Discovery data uploaded 09:59:11 Notified instance to initiate data discovery import process 09:59:11 Generating summary Summary ======= Information Acquisition Failure ------------------------------- XXXXXX: WinRM: HRESULT: 0x80338005. DCOM: Access is denied. SSH: Failed to connect. Failed to establish initial TCP/IP connection All Computers ------------- XXXXXX: WinRM: HRESULT: 0x80338005. DCOM: Access is denied. SSH: Failed to connect. Failed to establish initial TCP/IP connection The discovery was executed successfully. The results are now being imported.