Discovery Stopped working after Windows Update 22H2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-15-2023 10:27 AM
Hello,
Our discovery stopped discovering workstation's after updating to 22H2. It's something to do with KB5004442 that hardens DCOM. Here is the error message: "Adding target to blacklist. No valid credential found for type [Windows]" or/and "Adding target to blacklist. No valid credential found for type [BASIC_AUTH]". ServiceNow tech has been trying to help us for a month now and still no solution. ServiceNow tech wants us to open ports but nothing specific.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-15-2023 02:12 PM
Does the MID Server Service still run on the hosted machine? I've faced this issue but it's seems the connection between the ServiceNow instance and the hosted machine was down due to the credential has lost in the config file (in the hosted machine).
I submitted a HI Ticket, ServiceNow support help us with these solution:
1. reset password of MID Server user.
2. added the password the config file (on the hosted machine). Line <paramter value="PASSWORD" name="mid.instance.password" encrypt="true"/>
3.go to <MID server directory>\agent open config file and delete <parameter name="keypairs.mid_id" value=""/>
Then start the MID Server service again. Validate and Rekey (in the ServiceNow MID Server).
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-15-2023 02:21 PM
Yes. The Mid Server Still runs on the hosted machine. So, when we run our discovery, it goes through our Credential Manager. We can see in our Discovery, that all of the workstations that are Windows Build 1903 are being discovered with no issue. But when we update the workstation to Windows Build 22H2, it fails the discovery.
