So issue is with a windows server, When it got discovered by midserver it is classified as computer,

[MohitSaxena]

So issue is with a windows server, When it got discovered by midserver it is classified as computer, but through SCCM integration it is classified as Windows server. due to this it's class and few more fields are keep changing daily. What action I could take?

 

[cassieb_]

Is this with all Windows Servers are just a limited few?
I would look at the Discovery Pattern for Windows Servers and determine if there is something that is not recognizing it as a Windows Server as opposed to a computer.
If all else fails, you can put a reconciliation rule in place for SCCM to give it precedence over Discovery.

[Cassandra Kittl]

Double check the OS of the machine - if the OS is not a Server OS - then the Computer pattern is triggered. You can control the updates via the IRE.

[Shubham_Jain]

@MohitSaxena Normally Discovery data is correct because that directly comes from Target device. Hence, double check on target device and match your data with Discovered data. If it is the same, then retain only Discovered device and remove the SCCM device. Or maybe you can set the priority first to Discovery and second to SCCM for data refresh. So, if something does not come from Discovery will update from SCCM.