What are the cascading rules when ServiceNow SAM finds SQL Server devices to license
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-08-2024 12:39 PM
I'm trying to make heads and tails out of the products shown as Licensed and Unlicensed in the Licensing Workbench for SQL Server. Can someone tell me if there are search/find rules that ServiceNow uses to identify Licensed devices and cascade down through some identification rules for licensing? Example: for Enterprise, would it find:
Enterprise Running SQL Servers with an active Listening Port
Enterprise Running SQL Servers without listening for connections (typically a local install)
<<missing Edition>> Running SQL Servers with an active Listening Port
Enterprise XXXXX Components
Enterprise YYYYY Components
etc....
What I'm seeing seems to be a bit of a shotgun blast, of what it's calling Licensed and then falls over to Unlicensed. Those CI's are then reflected in the LW data and LPR.
Thanks.