SG-SCCM Operating System (OS)

[garyminnick]

We just implemented the new SCCM Service Graph Connector (SG-SCCM) in development, upgrading from the legacy process.  The new SG-SCCM import uses a different OS name than the legacy and causes it to flip back and forth with Discovery.  Before moving to the SG-SCCM, Server 2019 would show as "Windows 2019 Datacenter" for both the legacy SCCM and Discovery.  The new SG-SCCM will use "Windows Server 2019 Datacenter".  Looking at the legacy SCCM there is a Script Include, WindowsOSNameHelper, that seems to format the OS name.  After the first SG-SCCM run it added 9 new choices to Operating System field, all with the format that starts with "Windows Server".  Has anyone else seen this and are you creating a reconciliation rule to set either Discovery or SG-SCCM as the priority?

[SwarnadeepNandy]

Thanks for the acknowledgement.

But that said, I don't agree with your second point. Every day I learn and rely on and learn again a lot from these search engines and advanced versions of it. And I am sure everyone has some point in their life performed some kind of search whenever they stumble upon it and found a lot of useful content. So, what I am trying to do is mixing both my experience along with other persons expertise across the internet to provide the best possible result as an answer to the post.

I would suggest you should also try them. It will help enhance your response.

According to me the wealth of knowledge over the internet is enormous, so searching it is also a form of art.

And here I am trying my best to help others in my own way.

Regards,

Swarnadeep Nandy

[CMDB Whisperer]

Thanks @SwarnadeepNandy - hope it didn't come across too harsh.  I know it takes multiple perspectives and I don't claim to have the only one.  Just trying to do my part to combat a perceived trend in the Community where people are posting things that lack relevance and subject matter knowledge, in the interest of making the Community a better place for users.  Sorry if your post got caught in my net.  Peace.

[garyminnick]

I still do not understand the link to the Dell website.  It has no helpful information.  And given I was asking IF people were using reconciliation rules or something else should have indicated I know what a reconciliation rule is and do not need instructions on how to make one.  So, I admit, I also assumed this was a past and run job to get solution points.  It never really answered my question.  But if my question was not clear then I appreciate the time you took to post.

[garyminnick]

Hey @SwarnadeepNandy 

Thanks for the reply.  I have already created a rule for this.  I was asking if that is what others are doing or is there something else to consider given this was a non-issue in the SCCM legacy plugin and only presented itself with the SG-SCCM.  It is pulling the same data from SCCM but the SG-SCCM is doing something different than the legacy SCCM.  Either formatting differently or pulling the data from a different value.  That is what I was trying to find out.