hello everyone this is srinivas product manager software asset management and in today's demonstration we'll talk about a new feature that we're releasing in san diego which is called as sam virtualization adapter so let's see uh what this feature is all about so we know that you know uh software's like sql server windows server etc they can be deployed on different virtualization technologies some of these virtualization technologies include hyper-v red hat nutanix etc um although microsoft or you know others uh vendors do not have specific rules um for these different virtualization technologies um but from a sam product viewpoint these need to be reconciled correctly uh so that you know the correct license compliance uh can be provided to the customers so that's the future all about the feature is able to determine the license compliance uh of software's deployed on these different virtualization technologies notice that you know when discovery discovers these virtualization technologies owing to the different architectures on these technologies the relationships are discovered very differently and as as we know that software set management product depends a lot on the uh discovered relationships to determine the license compliance this feature provides a kind of a layer on which you know different virtualizing technologies uh reconciliation can be standardized so if you see here hyper-v has got a very different uh relationship view there is you know two different installs for example created red hat has got clusters members of relationship which is very different from what we have in vmware so um this feature is able to standardize uh these relationships through uh database views uh which we provide as part of this feature and uh through these database views servicenow is automatically able to reconcile these different virtualization technologies so we need to appreciate that the different virtualizing technologies uh are discovered differently uh and have got different relationships but at the same time they have got a very different architecture as well so vmware for example is a monolithic architecture as you can see that the uh the the vmware esx software is installed on the physical server however in hyper-v which is microsoft virtualizer technology the windows server is installed on the physical machine and then one of them becomes the parent vm and then that acts as the hypervisor in this case so you can see that the architectures are also different and this also needs to be considered when determining license compliance if i move ahead uh and provide a small demonstration of this feature uh but before demonstrating let's see the use case that we are going to demonstrate so we have got two different clusters there are about two servers in each cluster and a number of vms running on each of them and one of them has got the hypervisor as microsoft hyper-v and another one it has got red hat virtualization you can see that cluster b has got a high number of vms running on it it has got high density and hence windows server data center rights will be consumed here and in cluster a going to its low density windows server standard licenses will be consumed here also note that in hyper v as we just talked because of the architectural difference there is uh a windows server installed um which is present on the hyper-v but in red hat or you know in vmware for instance uh that there is no windows server installed on on these different virtualizing technologies so for hyper-v it's very important to not consider that software installed on on the hypervisor and you can see here that microsoft has made a provision for the same and it allows windows server standard edition to use one running instance of the server software in the physical osc on the license server in addition to the two osc's so that extra install that you find on the hypervisor for hyper-v is not considered for licensing so let's see that in action so i'm here uh and i can see to 2016 standard i can see the license required license phone and license required i can go to the license required pane and i can see that the device is because windows server licensing works on the device layer only i can see the licenses got consumed here and if i just go and i can see that 80 rights have been consumed in this case i can open the dependency view and i can see that this is a hypervisor uh having microsoft hyper-v so this is that cluster there is this hypervisor here and these are the two vms running on on them and uh i can just open up the form view of this hypervisor and you can see that that there is a software installed on this there's a windows server software installed on this uh hypervisor in addition there are uh installs on the virtual machines as well so you can see that the architecture uh is totally different here there are two installs and what what this feature does or what sam virtualization does is that it it does not consider the install on the hypervisor while calculating uh the license compliance and similar let's see a 2016 data center we can see that again the license phone license required i can go inside the license required i can see that again the host got consumed i can open up uh the machine which consumed data center licenses i can open up with the dependency view and i can see that this is also a hypervisor but it uses red hat virtualization and again there are 50 vms running on it and and this is a separate virtualization technology as we know about it i can open up the form view here and you can see that this is a red hat machine red hat hypervisor and uh there are no installations on this hypervisor so you can notice that there is difference in terms of architecture on both red hat and hyper-v so what servicenow does is that it abstracts this virtualization mechanisms from the sam managers and it will give you a right license compliance on these different virtualization technologies be it hyper-v be it red hat or the existing support that we already provide for vmware so that's about it thank you so much