Jump to content

Ben Maddams

Hornbill Users
  • Posts

    75
  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

Ben Maddams's Achievements

Enthusiast

Enthusiast (6/14)

  • First Post
  • Collaborator
  • Conversation Starter
  • Week One Done
  • One Month Later

Recent Badges

7

Reputation

  1. 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,
  2. @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.
  3. Same issue - But looking at permissions for the test calendar now, so might be a mistake we've made our side. -B
  4. Hi @Joshua Howitt Has there been any movement on this one? We're experiencing the same issue. Many thanks, Ben
  5. @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
  6. @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.
  7. @Graham As the target has had a recent job attempted on it I'm going to have to wait for the time-out period to expire, as I can't unmanage a device that has recently had a run attempt on it. I'll try a little later today.
  8. @Graham Same results on the SIS server. I've only got the one target I can run against - We've got our admin box (hosting SIS) and the DC as the target. Selecting our admin box as the target provides the same error code.
  9. @Graham I'm getting this back: IdentifyResponse ProtocolVersion = http://schemas.dmtf.org/wbem/wsman/1/wsman.xsd ProductVendor = Microsoft Corporation ProductVersion = OS: 10.0.14393 SP: 0.0 Stack: 3.0
  10. @Graham @Steve G The machine is on (its our main DC) and returns the following: WinRM service is already running on this machine. WinRM is already set up for remote management on this computer. I don't believe anything has changed on our side. Cheers, Ben
  11. Just to add some troubleshooting: The target machines for the job are both show as available under the ping/DNS checks under the managed device inventory. The authorising account hasn't changed since running succesfull jobs. The EpSis Service is running as normal and the SIS server is up and contactable.
  12. Hi all, We had working jobs being processed until just recently, I've attempted to run them and receive the following: Package is not cached, downloading package from library: /secure-content/download/YVPbyO8puhB2A2VOqiOzw3MP3JT2XpjTVer_ZwEODw3owP7pTYcK1u-CYP1Khdw47B7318y3hdCQRwkFHffL_ftMfZxVewXLhty-BC3O--Iu90Fu3Y_dPb0dKlpxgxqs9gwa839TcBEC46K1MSM7-_leOcv_aGtuBnBCtfAgvXumnTUIfD9IviHeyLtDinoHzLBZpGFnkMSfcMu7XYMe12_RrSBuynY6fEr4ZlDel4KP Remote job creation failed. It was not possible to connect to the remote system. HRESULT: 0x80338005. Deferred until 2024-04-25 11:53:17Z Can anyone suggest a reason for this? I couldn't find a reference to the error code in the ITOM documentation, and the log files don't appear to have anything regarding this job run attempt in them. Many thanks, Ben
  13. Hi all, We had working jobs being processed until just recently, I've attempted to run them and receive the following: Package is not cached, downloading package from library: /secure-content/download/YVPbyO8puhB2A2VOqiOzw3MP3JT2XpjTVer_ZwEODw3owP7pTYcK1u-CYP1Khdw47B7318y3hdCQRwkFHffL_ftMfZxVewXLhty-BC3O--Iu90Fu3Y_dPb0dKlpxgxqs9gwa839TcBEC46K1MSM7-_leOcv_aGtuBnBCtfAgvXumnTUIfD9IviHeyLtDinoHzLBZpGFnkMSfcMu7XYMe12_RrSBuynY6fEr4ZlDel4KP Remote job creation failed. It was not possible to connect to the remote system. HRESULT: 0x80338005. Deferred until 2024-04-25 11:53:17Z Can anyone suggest a reason for this? I couldn't find a reference to the error code in the ITOM documentation, and the log files don't appear to have anything regarding this job run attempt in them. Many thanks, Ben
  14. @Steve G Hi Steve, much appreciated! Tested and passing the right info now.
  15. @Berto2002 Yes absolutely, I've heard nothing back about this since I posted weeks ago. -Ben
×
×
  • Create New...