Object ID in windows server not populating after discovery

[SNOW44]

Hi Excepts,

1. Object ID for windows servers(isVirtual=true) are not populating by IP Address based discovery, where as VMware instance of same Windows CI's are getting populating Object ID.

2. Object ID for windows servers(isVirtual=false) are getting populated.

I just want to know why same windows server class are having object id for few CI's but not for all. Is there a way to populate for all?

[Rahul Priyadars]

Object ID for windows servers(isVirtual=true) are not populating by IP Address based discovery, where as VMware instance of same Windows CI's are getting populating Object ID.---> This seems for me expected behavior in case of IP based discovery. VM instance are created using Vcenter discovery and Object Id is the indetification key for Vm Instance CI Class, similarly it's used for hyperv, ec2 or azure instances too.

Object ID for windows servers(isVirtual=false) are getting populated--> This is Physical server run discovery in debug mode and see where its set.

Regards

RP

[SNOW44]

Hi Rahul,

Thanks for reply.

I have debug the Windows server(isVirtual=false) CI and below is image, I see no Object ID brought.

Is there any Article that supports the above scenario like where Object Id not retrieved for Physical Windows Server?

[Rahul Priyadars]

is it possible that Object_id is populated/updated manually for those CIs?

Check audit log once.

Regards

RP

[SNOW44]

Object ID were not populated via discovery and no manual update happened on CI record(checked the audit also, no luck)

Is there any Article that supports the above scenario?