CIS Datacenter (Windows Server Datacenter) optimal calculation

1__ElieB · ‎09-18-2024

Hello!

I have entitlements of both CIS Standard and Datacenter. Both are in Use, perpetual, with a Per Core (with CAL) license metric from Microsoft and the default DMAP already setup.

Our normalization is 100% completed, we see several thousands of Windows Server installations that are all normalized correctly.

Although I don't see any Licenses required calculated and no mapping errors nor any unlicensed installs.

Am I wrong to think that SAMPro is supposed to calculate the Rights needed automatically and optimally based on the number of virtualized machines per cluster or do we ABSOLUTELY need to tell the tool on which machines it needs to calculate the consumption by doing individual allocations on every single ESX host?

Please tell me SAMPro can do it automatically!

dreinhardt · ‎09-18-2024

Hi @1__ElieB,

Edit: Check out the following blog article and video by Srinivas from ServiceNow about the CIS Suite Components Setup: Software Suite Inference on ServiceNow SAM Pro - ServiceNow Community

we had a similar situation and solved it with the following adjustments.

Open your CIS Datacenter software model (same for Standard required)
Navigate to the "Suite Components" menu tab and check the following details (see screenshot)
(Inference percent must be 75)
Open the Suite child "Microsoft System Center Datacenter" software model
Navigate to the "Suite Components" menu tab and check the following details (see screenshot)
(Inference percent must be 0)
Run a MSFT reconcile and review the results

Why do we set the percentage from 75 to 0 for our System Center software model?

With the default setup of 75, 6 of 8 installations must be recognized so that the model is assigned and an installation of system center is recognized. I've never seen a server with all system center components installed and that's the reason to set it down to 0. In this way, we "force" any detected suite component to end up in a recognized System Center installation, so that our condition for CIS is fulfilled (Windows Server + System Center).

Best, Dennis

Should my response prove helpful, please consider marking it as the Accepted Solution/Helpful to assist closing this thread.

View solution in original post

1__ElieB · ‎09-23-2024

Hello Dennis,

I'm confused with your recommendations.

1: Healthcheck: There are recommendations, but none related to fixing anything related to Windows Server. Windows Server installations are clear cut in our environment and we see precisely on which VM they run.

2: Install actions required: There are 0 Installs that require actions for CIS Standard, 0 Unlicensed installations, all indicators are empty.

3: Check the Software Model recognition to ensure they're calculated as CIS Standard: How do you do that specifically? I thought SAMPro calculates and reconciles all of that automatically...? No?

dreinhardt · ‎09-23-2024

Hi @1__ElieB,

1: Healthcheck: this is great!

2: Install actions required: Please also check all required actions for your Windows Server Standard software models appearing in the workspace

3: Check the Software Model recognition: Please add the column "Software Model results" to your cmdb_sam_sw_install table to see the latest model the installation is assigned to.

For one of your servers in scope for CIS Std., the Windows Server and all System Center components should be linked to your CIS Std. software model

Best, Dennis

Should my response prove helpful, please consider marking it as the Accepted Solution/Helpful to assist closing this thread.