- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-31-2023 08:55 PM
Colleagues
I am unable to get a Microsoft CA discovery schedule working correctly. Debugging the pattern shows that:
- Step 3 - Run certutil command produces an empty template_arry variable.
- Step 4 - Failover step for run certutil has the output: response attribute does not exist in the table.
- Step 8 - Populate certificate table has the output: Line attribute does not exist in the table.
The end result is an empty CertResults variable which means nothing is discovered and the discovery fails. I have confirmed the Windows credentials in the instance work on the target server. The Discovery Schedule is configured like this:
- Name: [Name]
- Discover: Certificates
- Certificate Discovery Type: CA Trust Discovery
- MID Server selection method: Specific MID Server
- MID server: [MID Server].
The Serverless Execution Pattern is configured like this:
- template_list: All or a specific OID (no change is results)
- IP: IP address of the CA server
- start_offset:1.
I'd be grateful for any assistance.
Solved! Go to Solution.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-26-2023 06:59 PM
I had the same issue and had to add the server as a proxy host as per this work instruction
https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB1096137
This is missing from all the documentation...
ServiceNow Nerd
ServiceNow Developer MVP 2020-2022
ServiceNow Community MVP 2019-2022
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-05-2023 07:32 AM
I am currently encountering the same issue.
it seems to fail already at:
"tasklist /SVC | findstr /I certsrv"
Error in debug states it cannot connect using SSH, which seems odd as it is a window server.
Did you ever get this working?

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-26-2023 06:59 PM
I had the same issue and had to add the server as a proxy host as per this work instruction
https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB1096137
This is missing from all the documentation...
ServiceNow Nerd
ServiceNow Developer MVP 2020-2022
ServiceNow Community MVP 2019-2022
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-26-2023 11:13 PM
I'm sorry I didn't respond earlier with an update. The SN Nerd's advice is the correct solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-26-2023 11:31 PM
Thanks for the update.
I will try this next time I'm at the customer.