
SrikantSingh123 asked a question.
We have a scenario , where we have dedicated hosts within each cluster for Windows VM . Since we don't have license for Software Assurance (It's expired long back) , we have restricted the vmotion through Windows VM Host Affinity Rule .
Now , SLM is calculating license against complete cluster , which are having atleast one Windows VM Host. We require licensing only against dedicated windows vm host since windows vm's are not moving across hosts within cluster.
How to reflect this restricted calculation in snow . Please help me out .@Heena Abbasi @Rakesh Sharma
Hi, do you have update regarding this issue? Thanks.
Guys need your suggestions , that's an interesting scenario.
I don't see the issue.
SLM does not "calculate licenses against" something. Speaking of Windows Server licenses: you assign the licenses.
It is up to you if you want to assign the license to a virtual machine, a host or the datacenter / cluster.
You decide.
@Axel Lamparth Hi Axel ,
Thanks for reply . We have option for Windows Server to license it against host/datacenter/virtual machine . I am assigning the licenses(Windows Server Datacenter) against Host .Now in license compliance calculation ,core count is calculated against cluster ,of which host is the part . I want that compliance calculation should include only host because in my case windows vm's over host is restricted to move across cluster.
P.S. Windows Server licensing never goes by virtual machine assignment . Always, we need to assign it by host or Cluster .
The Windows Server License Assessment reports should help you. Basically, the license requirement is already correct (counting VMs based on movement as recorded in the VH Host History report).
Maybe @Carola Iberl could correct me, she is quite expert with topics like this one based on the experience I had with her answers to my many questions! (don't want to put you on the spot :D)
Hi @Srikant Singh
Samuel is right, I also had a similar issue 😉
What you can always use to check how SLM calculates the Windows Server license requirement are the reports
License tracking report do show the amount of license requirement, Windows Server Assessment report will also show you why the requirement was calculated.
For a cluster that includes virtual Windows Servers and has activated DRS and/or HA SLM will always calculate the Windows Server requirement for all hosts in that cluster.
That is not wrong as default setting, but as you mentioned you can reduce the license requirement, when you fix the Windows Server VM's to some dedicated hosts, by using some VMware rules.
We also did this for some Windows servers in special clusters.
Snow cannot detect that rules automatically, so it will calculate the full requirement.
But you have the possibility to manually exclude some hosts from License requirement.
You can assign your licenses to the hosts that require the license in your opinion.
And then you can create a compliance exclusion for the other hosts in that cluster.
You need to go to Administration -> Compliance exclusions. Here you should create a good comment why you want to exclude a license requirement.
Then you can select in the next tabs the application(s) that should be excluded, the computers that should be excluded and then in the last tab you can see the result of your settings.
After activating the rule and a following compliance calculation the License tracking report will show you License requirement = 0 and Requirement adjustment reason = "Manually excluded"
And compliance report will not show that you are underlicensed any more.
I already did that for some hosts in a cluster and it worked, but I just can see that this compliance exclusion now is "hanging".
So I first need to check the reason, before I can confirm it works still with SLM 9.8
I will let you know in the next days.
Hope that may help you.
Hi, as well I like tosuggest the "License tracking per computer" report. You can adjust it to see the hosts to which you assigned licenses.
BR Michael
Hi @Srikant Singh
I do not know if you already tried to use that compliance exclusions?
As mentioned i validated that in my environment again and waited for 9.8.1 to recheck that.
But it seems there is a problem with the compliance exclusion now.
That rule does not work, when I want to exclude Windows Server license requirement from ESX hosts.
So I just created a ticket for that. In case you want to refer to that here the number: 04452049
Hello. Has this been resolved? Exactly on the same boat where we established affinity rules to restrict VM movement to specific licensed hosts. Any Microsoft experts who can help confirm if this is allowed by Microsoft? Appreciate the response!
Hi all,
I got following information from support for my ticket in June 2022 (after 2 years)
I have gotten information from our developers that they have rejected the problem report and instead raised it as an enhancement:
From developers:
"I will change the status of this ticket to Rejected as it’s not an actual bug but rather an enhancement.
An enhancement ticket was created for the Enhancements backlog.
Until it will be prioritized in our roadmap, there is no ETA that we could give on it."
Snow's idea was to improve SIM vSphere connector, so that connector would read and send the VMware rules that fix VM's to a host. But I do not have any idea when this will happen.
I finally gave up and closed the ticket. So I do live with a workaround since 2 years and presumably for further years.