SG-Intune OS Field
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
5 hours ago
I recently installed the SG-Intune service graph connector in our dev environment. I have tried both the regular and advanced sources. The data it is pulling in for Windows devices includes client and server OSes. Initially, I had created a scripted transform to translate the version to Windows 10 or Windows 11 based on the number. However, when I did this, I originally did not see the server data and thus, the servers would be labeled with the same OS. Has anyone discovered a way to differentiate client vs. server OS? I am looking at the current fields imported and cannot seem to find anything I can use that is unique to one or the other.
I am relatively new to service graph connectors, and any assistance would be helpful.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
4 hours ago - last edited 4 hours ago
Hi @ctdemato,
You can’t reliably split Windows Client vs Server using only the Intune SG payload. Intune gives you operatingSystem = Windows and osVersion, and those build numbers overlap between client & server (e.g., 17763 = Win10 1809 and Server 2019; 26100 = Win11 24H2 and Server 2025). The Intune connector doesn’t send an edition flag.
Best practice is to use ETL Conditional Class Mapping + IRE precedence so a better source (SCCM/Discovery/Defender/ARG) sets the server class & OS, keep Intune for ownership/compliance. If you must do it in Intune, add a Script Parser step to derive u_is_server from naming/model/device category (and only weakly from builds), then map to cmdb_ci_win_server vs client. Expect some false positives until a richer source is added,
Please take a look at the documentation link.
https://www.servicenow.com/docs/bundle/zurich-servicenow-platform/page/product/configuration-managem...
Please don't forget to mark this helpful if it was, cheers,
Best regards,
Renat Akhmedov
