Windows Server 2019 and 2022 not showing in the Workspace
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎12-21-2023 08:43 AM
We are using the CIS suite for our Windows server Licensing, The entitlements are set to Per Core (with Cal), We can't get the Workspace to show compliance for our Windows Server 2019 or 2022. I also notice that the software models for Windows Server 2019 and 2022 do not have any Metric attributes assoctiated to them. Trying to figure out what I am missing!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎12-26-2023 01:14 PM
Hi @norm kalish,
thanks for all the details! Please keep in mind, that a inference percentage of 50% means, that "System Center" or "Windows Server" (1 out of 2) is enough to end up in a CIS consumption. The System Center model and his Child Components are not edition specific (no separation between DC / Std) based on the installation data. This will end in a best guess by the reconciliation engine and the allocation will switch between DC / Std - I would suggest to increase up to 50+ or 75 as the default value is.
I'm wondering about the amount of software model results per CIS software models (108, 89). By default, the reconcile generates one software model results which can include multiple license metric results based on different metrics per entitlement for the same software model, Could you please share more details about the model results.
Please revert all manually added downgrade rights - this seems to be one of the root causes why the reconcile is not able to calculate any license balance. The default setting for e.g., the CIS DC model is - please remove all models with source "Internal". All your Windows Server installations are covered by the suite components of the CIS suite - the generic "Windows Server DC/Std" model.
Best, Dennis
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎12-27-2023 12:27 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎12-27-2023 02:51 PM
Hi @norm kalish,
thanks, the next steps are:
- Software Model CIS Standard : Remove the Suite Component for "Windows Server Enterprise", because this is covered by default with the model for "Windows Server Standard"
- Enable "License under management" flag for both models "Windows Server Standard" and "Windows Server Datacenter", as it is by default. Please also revert all other changes you've made to any other Windows Server Software Model. One reason is, when the flag is disabled the recon engine ignores the model, as we've seen in your other document. The suite detection is based on multiple steps - 1. detect basic software model, e.g., Windows Server Standard, 2. check if it's part of a suite and all requirements are met (inference, .etc.)
- It looks like you're using an older ServiceNow release, if possible please upgrade to min. Utah or the latest Vancouver, while ServiceNow did a lot of enhancements for SAM Pro.
Best, Dennis
