[Music] hi everyone this is Shas product manager SRO in today's session we'll talk about swet inference and SRO so let's look at the agenda we'll start with an introduction to swet inference the basics on S pro we look at the configuration that is required for swed inference and then we'll end with some use cases and demonstration of this feature so let's get started introduction to Sweden friends before we start let's understand what a suite is a software suite is a group of related software that is offered as a unit now organizations or Publishers like Microsoft VMware Oracle offer Suites which is a group of softwares Microsoft offers M365 E3 as an example which is a suite of office EMS Windows Enterprise Defender for endpoint it also offers server software Suites like core infrastructure Suite which is a combination of Windows server and system Center Software now these software components can be purchased individually as well or as a suite but organizations do purchase it because of the cost efficiencies that they get from sweets now these site components can itself be a suite too a good example here is M365 E3 which has got Office 365 E3 and office is 36 E3 is itself a suite for M365 apps for Enterprise Microsoft team SharePoint online Jammer Etc so these individual software components can also be a suite in their own right similar example is system center which is a combination of configuration manager orchestrator client management and so on now what is the advantages why do organizations buy software Suites first of all cost savings software Suites are sold at a lower price than individual software components they offer integrated functionality they provide comprehensive support So Publishers like Microsoft provide comprehensive support for the suite U as a whole product they provide a consistent user interface and better scalability and hence sweets are a preferred way for purchase of many many Enterprise level softwares now what is sweet inference now sweet inference is a s Pro feature that helps remine if the software that is installed or subscribed is a part of a software suite so that it can be licensed efficiently what it means is that if you have got a deployment of a particular component of software for example Windows server using service now's Suite inference you could infer that install to be part of the core infrastructure Suite so that it can be licensed under the core infrastructure Suite uh license or entitlement so we'll understand this in more detail as we go along but a small example here is you have got entitlements of core infrastructure Suite standard now these entitlements as you know come with Publisher part number so when you enter it uh it would automatically create software models on service now now the S software models on service now would have automated content Services activated which would automatically add the requisite Suite components like Windows Server system center uh in this case and then um there is something known as U suet inference which is what we'll talk about but they help determine the inference for these deployments so we'll come to that so imagine that there is a software deployment or install for Windows Server standard in this case there is so it will be inferred to the core infrastructure Suite standard software model which will then help it get licensed by the core infrastructure Suite standard entitlement so this is just a very basic overview of how Suite inference works as it's rightly said the software deployment of Windows Server standard was inferred to core infrastructure Suite standard and this will ensure that Windows Server standard installs will be licensed with the CIS standard entitlements that's the basics of sweet inference now what are the challenges that Sam managers face first of all how to configure it how to check whether it's working and are there any real life examples that can help me understand so we'll dive into all of them the basics are that uh if you have got a publisher part number uh it will automatically create a software model and that software model will have a discovery map and this discovery map will help you automatically populate the suite components in this case you can see that there is a Microsoft Visual Studio which is another uh Suite it has got you know a lot of components SQL Server Windows Server uh and and many many more components so that you don't have to add it it comes automatically as part of content services in SRO and then of course you know these uh sweet components have their own parents now as we know that uh you know they could be a lot of different uh sweet parents for uh the same software so that relationship is also managed by S pro cont and services now how to check if SE inference was applied now a very easy way to check is that uh you go into software installs list View and check the infert suite and infert Suite product column and it will check tell you that uh you know this install was inferred to this Suite software model and you can see that the inferred Suite column will show you exactly where that inference is happened this will help you determine if inference has been uh working correctly or not and U uh one more thing to understand here is that uh you know the inferred Suite will help you determine which software model that installed was inferred to but there's another column known as software model result and that will ultimately tell you where this was licensed on um in this case uh you know the the inferred suite and the software model result suite are the same but in many cases it may not be the case it could be that your inferred Suite is inferred to a particular software model and then uh the licensing happens on another software model because uh inference uh is just a way to efficiently infer to the right software model but then the licensing could happen in a more efficient software model and we'll come to more details about it so that's uh a detail about inference and Licensing now coming to configurations uh these are some of the steps right so first of all set up your Suite inference uh so that it helps infer correctly you know you have to use the right PPN because the PPN would help you you know create the entitlement which would automatically create the software model with the right discovery map and Discovery Maps as we just saw autop populate the components use the right inference percentage or number u in some cases this is autop populated by content automatically and thereby select mandatory optional or part of mandatory group these are some of the steps that would help you set up suet inference select the property you know there is this uh very important property that uh uh is part of the feature which you will help you to use of component licenses so what that means is that let's say you have got a a license for a suite but also a license for an individual product for example you have got license for CIS suite and a license for Windows Server product now uh if there are Windows Server installs they would be inferred to CIS but you would want that let's say the CIS licenses are exhausted then it moves moves to and consumes the Windows Server license so using this property will help you achieve that and we'll see that in a demonstration and then in some cases you require product install conditions uh for example you know in case of uh Visual Studio you would want to have product install conditions because you would want your installs uh in your Dev environment to be only inferred to visual studio so if you have got product installed conditions configured that will help you achieve that so these are some of the steps so you can see here that you know we've listed these steps um you start with setup of uh Suite inference you see that uh the suite components are autop populated you just have to then determine the inference uh percent or number uh in some cases this percent or number are autofilled but in some cases you have to just uh you know uh just add the number uh inference number uh means that the minimum number of components present to be considered as site inference percentage means the minimum percentage of components present to be considered as a suite so either ways you know you could use a number or a percent whichever is uh more convenient for you and then determine if uh the component is mandatory or optional to be considered as part of The Suite so if you do that uh your Suite inference uh setup is complete thereby you can go to the properties and then if you want to use your component licenses just check the optimized compliance for Microsoft Suite with component licenses to yes and then what will happen is as it's mentioned when your Suite licenses are exhausted it will move to your component licenses and consume it you can set up your product install conditions in case of products like uh visual studio so that your licensing happens uh only on the dev environment and that's about it now we come to the use cases now there are several use cases we'll not go into all the use cases we'll talk about some common ones now these are the two common ones uh which I've taken when one is for Microsoft Windows Server um and CIS so uh in this case uh you know you have got Windows Server standard installations and uh you'd want those Windows Server standard installations to be uh inferred and consumed by CIS entitlement and in the Second Use case you have got uh Windows Server standard installs and then uh you would have them inferred to CIS Suites but the difference here is that once that CIS Suite entitlements are exhausted then the installs uh get consumed assumed by the component license in this case Windows Server standard and we'll see a demonstration of that um the first use case you know is U Can Be depicted like this right you have got software entitlements they Auto create the software model now these software models as we know have got Suite components in this case system center and Windows Server standard and what happens is that you know based on the installation that uh comes through inventory and discovery uh the software installs are created which create the discovery models they're normalized and licensed and this software install of Windows Server 2022 standard matches to one of the suite components of CIS standard and that means that now it can be inferred and so inference happens uh of that software installs to CIS 2022 standard and thereby the license is consumed by CIA standard now if you want to understand this in more detail uh just look at these steps you know whatever I mentioned has been documented here the first and second step are the PPN and the software model creation three four five step is for your deployments the installs uh which are getting uh discovered creation of installs and then the Discovery Model creation and thereby the last step is inference and then the consumption so that's how a usual uh inference works now if you take it this Notch further and we just talked about it what happens if you have got a CIS entitlement and a Windows Server entitlement youve got Windows Server installs U and these get inferred to CIS and then uh the CIS entitlements get fully consumed or exhausted now in this case if you have got the system property true or set up uh those installs would then start getting uh licensed by your uh Windows Server entitlements once the CI entitlements are totally exhausted we'll see a demonstration of that but before that uh let's look at the bigger picture how it works so the same case uh you have got two U entitlements now these entitlements autocreate the software models CIS and Windows Server 2022 standard and then you have got deployments now these deployments come from install uh uh to Discovery models which get normalized and licensable and in this case as we know this Windows Server 20122 standard software model matches to uh install matches to the uh software model and thereby inference happens for the 2022 standard now what is different here is uh that first of all this Windows Server uh uh installs starts consuming the license for CIS standard and then by when that is completely exhausted moves over and starts consuming the Windows Server entitlement and all these steps are listed here so that was all said and done let's move to demonstration so I've got uh my installs here as I mentioned you know uh we've got Windows Server installs you can see here that um you know we've got about 50 installs of Windows Server 2017 standard and Theo Suite here is uh CIA standard and I can just uh Group by and uh you can see that you know a lot of inferences happened now um I can also see the software model result here and I can see here that uhu there are two software Model results basically means that the consumption has happened on two different entitlements if I go to the licens workbench I can um go to mic soft go to core infrastructure site standard um look at the entitlements and thereby uh look at the software model for 2017 standard I see the license metric result I see that there are U 700 licenses and about everything was consumed and because everything was consumed the licensing started then consuming the Windows server entitlements as you can see here so there were 200 licenses of Windows server and you can see that uh the license required is 112 that means that the installs for Windows Server started consuming here as well so they first moved to CIS they consumed the CIS entitlements you can see the installs here thereby they moved and uh started consuming the Windows Server entitlements you can see the license required here and the installs here so 43 + 7 50 so all those 50 installs that we just saw were consumed effectively by both CIS entitlements and Windows Server entitlements so that was a short demonstration of how uh Suite inference works of course you know suet inference is a very complex topic and uh it has got a lot of use cases some of these use cases are listed here uh we do in for SQL Server component Services uh so you know if you have got SQL Server component services like integration Service uh analysis service they would be inferred to SQL Server Enterprise or standard depending on the Edition uh if you have got SQL server deployments on your development environment and you have set the product install conditions they would be inferred to visual studio and um all all of these are just examples of how those things work now there there are more complex use cases uh what happens if you know there are multiple sqls of component services on the same VM um or you have got SQL Server component services and database on the same same virtual machine so in these cases as well inference works there is a particular logic but uh overall uh you know the uh the solution remains uh similar um and you know we we can discuss this in the next session uh you can see here that there are more use cases inference of SQL Server component service installs windows and system center installs infer to CIS but there are not enough licenses then what happens um what happens if there is Windows Server installs inferred to CIA standard but there are not enough licenses for CIA standard so you know in the same way those licenses will then start consuming CIS dat Center uh what happens in inference for M365 cases subscription inference so all are uh these are uh you know some more advanced topics that we'll cover in our next session but for now this session was just to provide an overview of suet inference go through some of the uh configuration topics hope that was helpful thank you