Discovery of Windows servers is not going beyond identification phase

[Rakesh16i]

Hi,

We have two MID servers, with same version and same reach-ability to the IP ranges with configured to use same credentials. However discovery of Windows servers is not successful with one MID server (getting completed with status "classified"), but when discovery happens thru other MID, it could able to successfully create the CI.

I can see the following error message

'MultiProbe script error for probe `Windows - Network`: ReferenceError: "related_data" is not defined.'

Please suggest what needs to be done to resolve this issue.

Regards,

Rakesh

[natem]

That's exactly what I ended up having to do!

[johnnyjava]

We have our MID instances running as domain account that is a member of the local administrators group on all machines.

During one of our upgrade tests, security had removed this permission from our account and it caused issues with the mid server upgrade process which requires the privilege to install another service on the machine. Once it was restored and the instances restarted (to ensure permissions were validated) we didn't have as much trouble.

I asked SN to document the auto-upgrade process, including this other service installation, a bit better.

[natem]

You're right Glenn. The MID Server didn't upgrade correctly. Tried to restart them... modify the config file... but something happened. We ended up just installing a new MID and everything is working fine now. Thanks!

[natem]

Thanks for the video links Glenn! Very helpful... and timely. We are getting ready to move to performing Discoveries in prod and there is a lot of concern that we are going to create duplicates and/or overwrite asset records. You're videos are focused on the cmdb_ci tables. It would be helpful to understand at a detail level the rules that occur (and the reconcilation options available) for CI creation in tandem with Asset (alm_asset) record creation upon discovery... which is further complicated when the hardware assets have been manually imported and maintained in the system (i.e., the serial numbers may have been fat fingered).