Hi All, I have added the information that SLM 8.2.2 is not available on SUS at the moment. As soon as I know more I will let you know. Please have a little patience. Thank you, Myrja
SLM 8.2.3 is now deployed in SUS and available to all Customers. This version introduce the fix for the Critical issues: Manual connection between Agreements and computers that users have added to the system will not be lost when the DUJ runs The new licensing rules that Microsoft added for Windows Sever 2016 will no longer apply to processor metric when calculating the license requirements Please see new release news here:
UPDATE We will be planning to issue a release to resolve this issue today. The release will also include a fix for SLM - Windows Server 2016 known issue. Cause When making the changes to optimize the performance of the organisation auto-connect rules in the Data Update Job a change was made to the step that performed the automatic attaching of computers to agreements. When processing any updates to the mapping between computers and agreements based on the Auto attach settings, the change inadvertently deleted both the manually added and auto attach links in the mapping table. This results in all links between Agreements and computers to be lost. Fix For platforms that have already upgraded to 8.2.2 and run the data update job, we are investigating the possibility of restoring that data from tblcontractcomputers from a backup of the SQL database prior to the 8.2.2 update. For now, we have halted the rollout of 8.2.2 and will release it as well as 8.2.3 that will contain a fix to prevent this issue as soon as we safely can.
Hi Myrja, thanks for the updates. Unfortunately the Link regarding the Windows Server 2016 known issue seems to lead to another system where my account is not know? Many thanks and best regards Sebastian
Great point Sebastian - Myrja posted a link to an internal note whcih of course you can't access - please find the relevant details here: "Customers that are licensing Windows Sever 2016 based on the processor metric are seeing the new minimum requirements and VM use rights calculations being applied, which are only applicable when using the processor core metric. Cause The changes made to support the new processor core rules did not take into account that customers that purchase Windows 2016 server license during their current agreement can continue to use the processor based rules until their next renewal. This resulted in the new rules being applied when either the processor core or processor metric are used for a license, rather than just when the processor core metric is used. Fix We are actively working on verifying a fix for this issue. Due to the potential impact this can have on our partners, and customers, we have decided to perform a dedicated release for the fix as soon as it is verified, which will be rolled out to all customers. This is of high priority and will be as soon as possible."
Hi Dennis, i got the information this update was stopped because of a bug. Support should be able to provide more information. maybe the blog post about this update should be updated? We have applied the update before but are not hit by that bug. Best regards Sebastian