all right thanks everybody for uh for being here to the software asset management how-to clinic um my name is mike gomez i'm an itam sc uh so we got a packed house today and some people are still joining so this session is going to be recorded i'll make sure i send it out to all the participants um if you can try to ask questions in the q a panel i'm going to keep an eye on both but try to answer them in the q a and it's just me so i'll try to answer questions as i go and then i may have to follow up with you as well and then we also have some road map stuff uh some other sessions i'll explain that at the end with like a list of resources so i'll send you this deck as well um so hopefully you know at the end of this you'll be able to get your all your questions answered um maybe if not today then hopefully soon after um so great so let's kind of get rolling and um yeah and we'll kind of see where it goes so just a quick uh you know slide not too much that i'm going to be talking about is really confidential but you may hear other customers mention issues so just remember that this is a private basically session for servicenow customers and i'm not really going to be talking about too much on the roadmap but i might mention a few things in about san diego so that hasn't come out yet so what's the goal of the session what are we going to cover so basically this is all around just getting you started with sam um i'm going to spend most of the time in an instance talking through like some of the common issues that come up and things to keep in mind like as you get going and then at the end i'll have a list of slides and we can talk a little bit about like implementation and i'll try to just highlight best practices like as i go all right so just high level like what are the goals of sam um you know basically like i like to think of it in sort of three areas so we help you reduce your software spend uh we do this in like two ways one is helping you like we try to license everything as efficiently as we can so um any like you'll show up as being over licensed for some products and so that would be the opportunity like in the next renewal to potentially like revisit how many licenses you own uh the other way is around um like potential savings so this is like the unused licenses so if you p you have assigned licenses to people but they're not actually using them that's where like the potential savings and actual savings kind of comes in there's productivity so you can publish your software in the service catalog people can request it we're tied into your license position so we know um if you have enough licenses or not or if you need to purchase more if we're getting below a certain threshold and then the final piece is around risk so we're doing this um like licensed position it's weekly but you can do it on demand so the idea is like if your environment changes you'll have a sense of what changed and what the implications of that are so that you're not kind of surprised at your next the next time you look into you know a true up or look into a contract renewal um all right so as far as like turning on sam um there's not too many plugins that you need to worry about the first one is just this sam master plug-in um so you need to request this from support.servicenow.com and you just go into like activate a plugin and then you can just search for like you know it's just sam software asset management it'll say like all plugins uh you just activate that one that's gonna activate all of these um and you know including like the publisher packs which are basically just like specific uh um license metrics for these particular publishers and there's a few other features there and then the other thing is around from the store so there's a few apps on the store let's go ahead and just look at the store right now so there's one that's for the sas integrations um the reason they did this in the store is just like they're releasing integrations um every roughly every quarter so um you know you would uh you can just get an update for the new um integration when it comes out and you can do that separate from doing like a full um you know upgrade from like rome to san diego so that's the idea of the story i'm sorry let me just uh sign into the um to the servicenow store so that's um and the apps that are there are the integration the spend detection and there's also going to be the sccm service graph connector um that's for pulling stuff in from sccm uh let's see let's take a look at that one i'm going to be kind of demoing that a little bit in this session this is just like a really good one to get you started um it is free it doesn't require any additional licensing a lot of these service graph connectors require like itom or some some of them do um so if you search like service graph connector um you can see you know which ones like the idea is bringing in um software from different sources so you kind of see like what inventory tools do we have that collect software and you know what do we have for service craft connectors most of these do require an itom license but i know intune [Music] sccm and uh the workspace one uh they've changed it so if you just have itam uh then you're you know you're good to go this is like the new thing they added um so it's mainly like the end user stuff that if you have uh just sam you can you can get away with that but um a lot of the other ones require an iphone license so that's sort of it for plug-ins um so then you know so i showed you like searching in the store um so yeah just all things to consider sort of as you're as you're rolling yourself so this is kind of my last slide before we jump into an instance and i'm kind of just going to use it as like a map of what i'm going to cover today so you know to do sam we need data from two places right we need to know what you own uh i'm sorry what you own up here and then what we find out in the environment um so the way i like to approach it is to you know decide like we're not going to try and do everything at once when we're doing sam we want to like figure out what you can you can break it out different ways one way might be like by discovery source so maybe we just want to focus on sccm like what data can we get with sccm bring that into service now and then once we know what data's in there then we can look at our entitlements and see what what licenses do we need to kind of match up against what we bring in i'll show you how you can kind of approach that in your instance um and and so like you know as once we get a feel for doing some reconciliation then we can tackle more discovery sources and add in more entitlements and that sort of thing so so that's kind of one way you can approach it um so we take in that data we create a you know it gets normalized i'll show you that then we come up with like a license position so this is something that serves now basically calculates automatically we do it on a weekly basis um and then from there then we get into like optimization like how do we um say we're we're under licensed how do we you know potentially remove some unused licenses to avoid paying the full true up um so that's basically the approach here um and that's what i'm going to cover in the instance so yeah i'm not seeing any questions come in but just you know feel free to ask questions in the q a if you have anything and yeah i'll take it as it comes so uh when we get into an instance here so there's kind of like two views i guess is the first thing and it's gonna depend on what um instance of uh what instance you have for servicenow like what version you're on so right now i'm in rome um if you don't have rome yep you'll definitely get a copy of the powerpoint i'll send this out i'll send out the recording too um so i'm in rome right now so we have this like sort of different ui and it's going to change again in san diego so you know just be on the lookout for that i think in san diego it's going to be streamlined a little bit more where there won't be as much of a separation because usually the way i like to do it is like this ui looks really nice um and there's not a lot of data here because i intentionally kept this scarce so that you guys could kind of understand the way that reconciliation is working but i like to show a lot of the nice dashboards here but when i sort of do work i like to still use lists and forms that's and that's just me but in san diego it's kind of gonna consolidate a little bit more so and you're still gonna have a lot of the functionality that you have with this list and forms um so anyway just kind of keep an eye out for that um yeah um so let's see so uh so as far as like what i want to show um you know like i said the first thing i like to do is is think about so the first thing is like what tables do we want to look at and an important table that you should know about is this software install table it's not like one of the typical bookmarks that you get so it's not you wouldn't see it necessarily here in the menu um but it's that you know but it is it does exist and this is what it is here um and i'll just throw that in the chat why not but it's because it's a good one um so like you know you're going to be the different discovery sources are going to be populating this table and we'll just show you the default view um so we're going to we're going to sort of tweak this a little to get it to work the way that um that we needed to but what i wanted to show you in this first segment is just like how do we populate this table because everything a lot of a lot of the reconciliation is going to depend on this um just so you know the subscriptions and the sas stuff i'm not really gonna i wasn't planning on spending a lot of time on that today it gets populated in another table um we def i can definitely show you a couple things if you want to see it but um just so you know in rome they changed the reconciliation so that both the installs and the uh the subscriptions this is the table um they all get like captured in um in the reconciliation so that's like a new thing they changed in rome and it makes it really cool like when you're looking at your this is like a more production or more nicer looking uh view like you're gonna see all of your publishers in rome and san diego in this licensed um uh workbench we call it so let me just wait for it to load here um so just sort of be aware of that that's a change they made before in like quebec they had like a different dashboard that was just for sas but now you'll be able to see like all of your publishers in this one view which is really useful so anyway so getting back so how do we populate this table right so there's a bunch of different ways to do it and if you were going to look at like a populated one um if we go here on i'll show you like a more populated table um there is a discovery each this we're looking at these individual installation records and they're all going to have a discovery source so what's the thing the mechanism that created these um these records and so you'll be able to see that and you know so different different tools can populate this um the one i'm going to show you today is like sccm but you know you can see it's populated by all these different sources so that's import important thing to kind of call out so for this installation table how did we populate it so this is where i use the sccm service graph connector and basically the service graph connector is just a way of doing an import that that like servicenow it basically works with the cmdb to make sure everything gets put in like the right table um a lot of the service graph connectors i showed you in the store some of them are built by our partners some of them are built by servicenow um but they all kind of go through this vetting process of like making sure that they end up in the right tables so that's why we recommend them so whenever you have a service graph connector there's going to be like this nice guided setup i'm not going to walk through everything for it but for sccm basically you um let's go to the home or let's go to the beginning so basically like you need to have credentials um you have to set up like data source set up the credentials you'd like test it um you know run yeah this is kind of where you test it and then you then you'll set up like a schedule for when to um run it so this is kind of like what you end up with is each one of these data sources is going to put things in a different table and the way that so like by setting up the integration it generates these data sources and all they do is just put stuff in different tables and service now you can see for secm we create the computers we can put in like disk information no this is necessarily super important for sam but we can do software and if you set up usage metering in in an sccn we can pull that in and then you'll see this ai that stands for asset intelligence so like depending on if you have asset intelligence turned on in um in sccm you would choose one or the other i think i heard sccm is phasing this out just just be aware of that so anyway so these are the different um data sources that end up getting generated uh but really the way you'd work with it was with these import schedules so you do the computer identity and you set a schedule for that and then all of these will run afterwards [Music] yeah i see a question in the chat here about do we need to change anything for sam pro so you don't really need to change anything if you're already importing data with sccm uh you don't have to do anything special for servicenow other than maybe if you're not using some of these jobs uh you might want to turn them on you just set active true but if you're one thing is you might be using an older version of the secm integration and on the documentation or the the store app which i'll send you there's like a migration step um and we have a lot of different ways of doing it we have like an automated test that will run we'll just say hey if everything if the test is good then you can set it up i mean we recommend doing turning that turning on the store app like in a test instance connecting it to sccm doing the migration make sure it all works and then kind of moving the production but that's the biggest thing just make sure that try to make sure that you're using the new service graph connector that's where all the development work is going to be moving forward and just one other thing i'll mention is they did add support recently for like multiple sccm instances so if you have um uh oh yeah can you not share your picture oh no i can if you can't if you're oh sorry it sounds like somebody's having trouble seeing um yeah you should be able to see my screen kind of regardless of my picture i think um but uh yeah if you're having trouble seeing the screen let me know i can if if this if this helps people i can just stop sharing my my video it's fine um and but i'll zoom in a little bit too all right so anyway so that's just it about sccm sorry i'm trying i'll try to keep it moving um so we set up these jobs and then is it puts um it puts records into this table right so the the three things that are basically four things actually that we care about is the display name the publisher the version and then the device that it's installed on so any sort of data source bringing stuff into servicenow it needs for for sam it needs to have like we care those are the fields we care about sometimes you might not get like a publisher or a version and in some cases sam can still work with it um but ideally we have values for each one of those um so if we look at a particular device here um here all the here's all the software the sccm that we imported so that's kind of step one is like bringing in um uh so anyway that's that's like some of the stuff that we're bringing in um and so that's the first step so you have this initial view right this is kind of you that you get out of box so when we're thinking about like reconciliation um this is where um you would this is kind of where you want to make another view so to do another view you go here to configure list layout um the way i the reason i do it this way is because we need to be able to dot walk like so there's stuff on the discovery model that we need to get in order to really make sense of uh the reconciliation i'll kind of show you why this is beneficial so that's why i make a new view they did change it in san diego where you can just instead of making a view you can just use that gear icon and personalize the list and add and dot walk that is something that they did change but um it's not here yet so anyway so these are some really useful fields we want to look at the discovery model like we still want to look at the installation but we want to get information about the discovery model because that's going to help us as far as like figuring out normalization i'll show you where this comes in handy and then when we're looking at uh reconciliation we want to look at these fields too and it'll become obvious like why these are useful so that's the view that i made if we look at the data with this view like you know the first step is like figuring out what what's normalized and what's not so we can see here that most of this stuff is normalized which is great um and then we got a few that are partially normalized so and it's the discovery model that gets normalized so just to make this a little more concrete so you can see we had a bunch of installations for system center config manager they're all partially normalized but it's really the discovery model so if we these discovery models get generated automatically whenever you have a unique combination of publisher display name and version so you can see here all those individual records but they all kind of mean the same thing from like a sam perspective so this is what we do the normalization on so like you can see the versions missing that's why it's partially normalized this is going to happen you're just inevitably you're going to get stuff that doesn't normalize uh completely and it may like this may be fine from a compliance perspective if the version if you're licensed the version doesn't matter and i'll show you where you would look at that then this would work fine but you could come in here and manually normalize it you we can also like over time you can submit your partially normalized stuff to the through the content service you do have to opt in to that um and and then eventually you could get an automatic update so there's a few different ways of dealing with it but um that's kind of step one is you want some level of normalization because after that reconciliation like needs normalization to work basically so that's step one is is normalization and then step two is like what is licensable and what's not so on the discovery model view that i showed you one of the things was um product type let's just go back sorry um on the discovery model there's this product type field and that's going to tell you whether it's licensable or not so from the same perspective you know the the next thing you want to do is look okay of the stuff that i've normalized what's licensable and anything that's licensable is going to show up in the license workbench um so you know that's kind of that's step two and then let's just look at the licensable stuff and then let's look at the products there's probably a couple ways you can slice it so in this kind of demo instance we've got some crowdstrike software each one of the servers has crowdstrike we got some sql server stuff and then we've got uh you know the config the config manager and then each one of these has like windows standard so from like a sam perspective this is kind of what we want to work on from a normalization perspective um so you can look at there's a couple ways we could look at this if we go let's go to um the so if we go here i'm i'm in my this is like my test instance um but i'm showing you the nice you know workbench view here are the publishers that are that have licensable stuff in the environment or these are publishers that we have entitlements for so you can see microsoft and crowdstrike we go back um sorry okay so if we go back to our installations and we group it by publisher and we sorry let me do it by licensable and then if we group by publisher just trying to give you a sense of like how this works so you can see microsoft and crowdstrike and if we come here microsoft and crowdstrike and then docusign red hat and sap i just have entitlements for these so that's why they're showing up so um so that's like that's kind of the way it works anything that's licensable will show up there so the task now is like well how do we reconcile so let's try to match these up to an entitlement so um if we the next so that's kind of where doing the entitlement import comes in so if we go back to our license usage um you know so it's kind of like this part is very similar in the old list and forms ui um you know it's it just kind of has a different view but if you look if you're on quebec if you just search like entitlement import you're going to get a very similar screen um so what you're going to do is do a new import and this is where the entitlement import spreadsheet comes in so best practice is to always just download the template because like every time they update sam they you know at least in a major release they're gonna change the uh the template so um so you just want to take a quick look and go here and these are the different kind of fields now all you don't have to worry about filling out every one of these fields all right and i'm going to show you a completed one but that's kind of the first step and when you do your entitlements it's beneficial to try to use this um there's some automation around like publisher part numbers and and things like that and this is like a good first pass rather than just entering each entitlement in manually so let me show you what a more filled out spreadsheet would look like let me pull this up sorry okay so um so you put in your publisher part number now if you have a publisher part number you don't necessarily need um uh these values filled in yep entitlements is correct it's what you own um so so you don't necessarily need these filled in i just like to just fill these in just so i know what they are and if it's going to ignore these values if you have this filled in so but i just do that for me um you know you can see i've hidden a few of these fields um so you want as far as like mandatory fields and i'm going to send you a really good white paper that explains this uh in more detail but you know you're just going to want some sort of indicator of the type of agreement um the license type you know as a subscription as a perpetual um so how many rights did you purchase for some of the microsoft stuff like server stuff you want to leave that blank and just fill in these anything that you buy in like a pack of two or a pack of 16 you want to fill them out here and then if it's a subscription you just want to put in the period and the dates so we try to request like the minimum information that we need from the customers of course you can add other attributes that will get pulled into the entitlement and you can even do like custom fields i believe um so so that's like kind of the data that we're looking for and then you can see here i've got a couple of weird use cases that we can figure out the best way of handling it i got one that's got a weird skew and then i got one that is a blanks published part number with weird product names um so the way that i recommend the reason i recommend doing it this way is if you have the publisher part number it's going to create the software models um but i'll give you a feel of like how all the entitlement stuff kind of hangs together um so hopefully that'll answer your question um all right so let's go ahead and import this so i'm going to close this if i attach the file it's going to update the description okay so i got that set up i'm going to import it and then it's basically what this is going to do it's going to create a record for like the import and then it will create a record for attached to that record about the import it will attach any entitlements that it creates and then there's going to be a separate area for um for errors so if we come to license operations you can see here this is what it's doing so it imported most of those but there were some with errors um so if we go to the the import record we can see the entitlements that it created again like you'll this look this is going to look very similar in quebec um but you'll see that it created these entitlements it used the publisher part number and uh it it like basically imported a lot of that data um let's take a quick look at one of the ones that we imported uh just in the old listing forms view so if i come in here and just to make sure let's filter this by like created today all right so really any one of these is fine let's do uh let's see if we can do windows so windows server standard we're going to use this in reconciliation um so by going through that import process it created um it created the software model from our content like library basically it used this number to create the software model um and sometimes the published part numbers can fill in like some of these details like the uh license metric but in general i think it's best to just like include that in the spreadsheet but this is like and you'll see where these software models like in general using the the creating these manually um in some cases is what you need to do but if you can use the publisher part number that's really what the why the benefit is um so if we look at the software models um i've got 349 so if i filter and um so let's do created today and run it so you can see 270 of these were created basically just now because like some of the part numbers like a model might be related to other models for instance the all apps one is gonna have like a bunch of software models tied to it and so by using that import mechanism uh it's going to create the uh these like sweet components it's going to create all of these um so that's sort of the benefit of doing it you could also just use the discovery map i'll explain where discovery maps kind of fit in when we look at the errors um but that's sort of the benefit of using the publisher part number and the entitlement import um so when we look at let's go back to the errors so um if we're here in our details sorry license operations so if we go to entitlement import errors we got four of these so a couple of these are so publisher part number and software model not found we got uh software while not found duplicate entitlement and then publisher part number not found okay so they're kind of similar let's look at on the duplicate entitlement so you might get these because like the quantities and the uh the like the quantities match they're exactly the same as another entitlement and the dates are the same so like if we go back to my import um i'll just open it up like i have basically i have a perpetual license and then i have maintenance and this is for sql server um which is here yep so like it's just making sure that i meant to do that i didn't make a mistake so you know if i um you know if i'm fine with it see there's the 30 that i bought i can just do create entitlement and it will you know it'll create it anyway so it's just kind of a check um but there's some that uh you know we had issues with so if we refresh that one's going to get fixed let's look at this one for i was going to do let's see so this one is for microsoft it's going to show me here um the software that like this is what i put in the spreadsheet uh so actually in this case i didn't have for this one i didn't have a publisher part number but i did have these values and this is important thing so even if i have these and even if it's in the library it's not going to automatically create a um [Music] software model so there might be a software model for this in our library but it's not going to automatically create so that's an important point um so basically what i would do i don't know sometimes like for the more complicated ones i like to get out of this view but let's try to uh uh i think i may quickly not use it yeah all right um let's go back here and go to i'm just going to grab this all right so um here's the one for uh oh sorry i'm in the wrong instance okay so for this one so manually fixed this is the microsoft one so that you know for these um we can just come in this is where we look in the library so it's going to look oh sorry so no we need to create a software model so the first step is to create the software model um so yeah i'm just looking at time i think we're still doing okay so we'll go here go to new and this is where when you create a software model basically sort of under any circumstances this is you even if you don't have a publisher part number go into discovery map and come here and just search for the software so it was like advanced oh and it would help if i spelled advanced [Music] sorry it would help if i just i'm just going to grab it so try to search for the title here um and i think it's because it's missing yeah so we do have a discovery map for it we just don't have the software so um you want to create the software you have to create the software model um and so the benefit of using the publisher part numbers it's going to create the software model automatically and just you know as a caveat if this if this is painful and you have a lot of errors it might be worth like thinking through how to automate this so maybe towards the end we can talk about that um but i want you to understand at least understand the approach so okay so we created the software model um if we come in here it should exist now so it does so we fill that in and we should be able to import it now and it lets us do that so that's kind of like one use case um let's go back to our errors um and then so then for these so i got weird skew and then i've got no skew let's look at weird skew so it doesn't it didn't find a publisher part number and it's for crowdstrike device control six so that means we don't have a software model for it um this is kind of similar to like the one i showed you before so in the library we do have all um let's see so let's go to our software models and you can see i guess the easiest thing and we'll do a discovery map and so we in this case we have one for crowdstrike device control but we don't have one for that exact version so i wanted to show you this like you know what detail do we need so i think just having one at least from my perspective just having one for six is probably fine so if we do product we can rather than using the discovery map because the ones that we have in there don't quite meet my use case um so device control so let's do that so we're going to use the product we know it's licensable and then in my version condition i'm just going to say it starts with 6 and do save um so i saw a question like should we trust the provider the supplier provided publisher part numbers and i'd say yeah that makes sense like it's just a question of whether we have it in our library and if we do then great it's going to look everything up and if we don't it's probably correct i mean if you purchased it and the supplier gave it to you most likely it's valid so all right so i created the software model so if i go back to my error um i can use that and after i do this one i'm going to show you the re reconciliation just so i make sure we have enough time and i know i want to leave time for um you know the resources and stuff too um so oh yeah okay cool so right so we got that um so let's go back to our error i'm in the wrong okay so crowd strike and that was weird skew i believe um so some reason i'm not seeing the um i'm gonna guess i guess i'm gonna do it here i'm not seeing the software model field so it's because i have um it shouldn't matter because i have this part number filled on yeah i guess it was interesting um all right so in this case let's i think if i try to import it it's not gonna let me i think it must have looked up the fact that i created that model interesting i didn't know i've never i've never done that with like a custom sku so but anyway the bottom line is when you have these the bottom line here is you need to create the model first okay when you're doing the import yep and it looks like it look at the entitlement in a different view maybe it created it but it didn't create it with the model so we come back here and go to entitlements and we're going to use this one for uh the reconciliation yep so i looked up the model that i created and uh it just filled that in okay so we've got some entitlements in here let's run reconciliation a bunch of different ways you can do it you can do it from like the nicer view i'm just going to do it this way for speed so i don't have too many um actually this might take a little bit because i have a bunch of other entitlements um so let's while this is running let's do a quick uh talk about um like resources and then we can come back and check on what we found so as far as like implementation you know i sort of covered this but you want to bring in some inventory um do your normalization then look at what entitlements do i have that i think is going to line up against that inventory and then do my reconciliation so like on a bigger scale this right this might take a little while so this is sort of how it kind of makes sense and this time frame is like just generically it's totally going to depend on what your goals are um but basically once you have your compliance position then you can focus on the more advanced use cases like the usage metering you can do data center um optimization uh and or maybe you wanna you know tackle end user stuff and think about the service catalog um so a lot of different like ways you can go but i'd say at the base of it is just you know doing what we've been doing so far just figuring out your compliance position um and and like making sense of the data that we bring into service now um and you know here are just some of the roles that are typically involved um i won't say a ton about this but just i guess on the customer side right we want to have like somebody that understands the business like the entitlements and licensing and then we just need somebody on the more technical side to help us out with you know setting up some of the access and permissions and maybe helping out with bringing in some of the data into that install table um so kind of you know think about the kind of division of labor there where it makes sense for one person to focus and then um also let's talk about just resources while i'm on the subject so i'm gonna send you guys this out um you know in general as far as resources there is a community specific for itam um we do have this thing called office hours i'm not sure if they have any upcoming sessions but this is with like the product team um and you can also even if we don't have any upcoming sessions you can i think you should still register for this and indicate as part of the survey like what do you want to talk about that's going to help the product team see that there's demand for this um training make sure that you've taken if you're going to be like running sam or dealing with a partner that's going to be doing sam for you we recommend the fundamentals just so you have a little deeper understanding of um just how it works and you can you know like discuss about in a more detailed way about kind of what you want we also have some resources like in playbooks and stuff and now now create that has like more processed stuff um so resources there we get some upcoming road map stuff going on so there's a roadmap community that you can you have to register to join it but this will kind of let you work you basically with these sessions you can um have calls with like the product team and they can tell you sort of what's coming and get feedback about like what you'd like to see um and then you know i'll share these with you so what just what i want to point out here is like a lot of uh there's good stuff on now support not just for opening tickets which you can absolutely do especially open a ticket if it's like a very narrow thing that you have a question about that you know you can't get help on the community for um or if it's with normalization if you're really struggling with normalization um open a ticket and you feel like it's not getting resolved you know definitely open the ticket and they can they can kind of focus on that if you say it's for sam normalization it should get routed to the right team um but you know there's some good just like deep dive stuff on uh in in high support too that's worth looking here's a few useful useful links so anyway so you know these are some resources i'll share those with you um and you know hopefully this will be helpful so let's jump back to our instance here so if we refresh all right looks like recon is done so if we go back to our install table [Music] we should see some different results here so let's um anything that's one thing to call out is anything that's not licensable is not going to get so the way we do is first we match it to a model and then we match it to an entitlement but the model is kind of the first step so anything that's not licensable and like and it could be like a child too anything that does not meet the licensable type is not going to have like a it's not going to be considered a record still each so that's the first thing so if we filter this out by um we just see licensable stuff um that's you know we're only looking at this and then um the next piece is around like you know does a model get matched up to this record so that's where the software model result is going to help you with so let's group by this and see what we get so it looks like most of these did get matched up to a model the only ones that didn't were the config manager client and we'll we might need to troubleshoot a little bit why that didn't happen i think it's it's i'm not really sure so i'll have we'll be i don't know what time trouble shoot that but anyway you can see the crowd strike did get matched up and then the other thing is um does it get matched to a license so we go back to [Music] this is the one so license metric results so uh if we group let's see which ones are empty it might just be config manager no account there's some windows servers that didn't get matched up so um [Music] so just because it got tied to a model it might not have gotten tied to a license and there's different reasons for that um it may have to do with uh you know for windows server some of the data center the reasons can be a little complicated um it can have to do with like whether windows is is virtualized or not like um so usually when we do when we do like compliance for windows if it's like a virtu it's a vm uh it needs to know about like the vmware infrastructure below it and with sccm it's not going to know about that it's just gonna know that it's a device um so one thing that can be tricky is like why is this not filled in and there can be different sort of reasons for that um but let's look at let's just look at the you know the use case around the device control so for crowdstrike each one of these um [Music] matched up through 16 yep so probably actually probably a better way to do this would be to do crowdstrike so i guess my question is are there any of these that did not get matched to a license and it looks like they all did so so that's good so if all of this stuff is filled in then like reconciliation's working and we're gonna know that by checking a few different places so if we come here um let's look uh if we refresh this actually let me let me come here to uh the license workbench i kind of like there's a like i said there's a few different ways you can look at it you can look at it look at it um [Music] uh in that view i showed you before um or you can look at it here so um all of these showed up under licensed installs right because of that mapping that i showed you before and if we look at the individual metrics in that entitlement i own 20 it's consuming six and i have four available and it's just a per device so um you know that's what's giving me my license position so if i look at my entitlement for um for crowd strikes so that so the the dollar amount came in when i did my import i had like a unit cost basically that was in the spreadsheet and then it figured out like what's my total cost um and that's how it figured out like my and then it looked at how many rights am i using and that's how i figured out like am i over under license um so that's basically like how it came to that position um so yeah so like when you're so so anyway the bottom line is that like looking at reconciliation can be can be a little tricky because like i said there's a few things that are kind of involved um and this would this is like a useful way of approaching it i think is like what models what things are lining up to a model and then what things are lining up to a license given that we have a model um and and i think that's kind of how it makes sense to to approach it and so if you see something that doesn't line up to anything like if we look at windows for instance um if we go to windows server there's going to be like these things are getting matched to a model but they're not getting matched to a license so that's sort of why um you know that's kind of why we're having that problem and i think part of the issue is that i had some old demo data in here and one of the things i had was this like standard windows so maybe if i delete this model i might get like cleaner um cleaner results so it can be a little tricky as far as what um gets matched up to what also you'll see things that are compliant like it's not using any rights um and that's just because i have an entitlement for um for standards so basically my problem here with windows is i have licenses for it but they're not it's not getting consumed um and that has to do with like it could my suspicion is it has to do with the fact that these are virtual um cis so maybe um yeah so we don't have a ton of time left so i'm probably not gonna be able to dig into it but there is a switch here that says like is this virtual and that could be what's going on um let me just see um so i guess rather than diving into that um just another thing to consider is when you're doing your entitlements sometimes you'll find stuff that's like not even in there's no discovery map for it there's no publisher part number for it you might need to create like a product so if you were to do that you come in uh what you do is you do a new product and you choose a publisher and this is going to reference like the company table so you may not it may be that you don't even have the company in here in that case you create the company then create the product um and then once you do that let me just i'll just do something like really quick um so once you have your product then you can create a model um and you could create like a discovery map so like i showed you with the model um you know there's a place where you can put the discovery map in just like inline as part of the model um but you can also do it here so i'm gonna do that new um the new one i just did looks like i got a bunch so i think it was three yeah here's that one i just created so i could like i could put in the conditions this way um this is like another approach it's a little this might be you might need to not do this whole thing maybe just creating the the product and then tying the model to the product this way is how you want to do it and you don't want to create a discovery map um but if you do create the discovery map what that lets you do is create a custom part number and this is where you you know so you do like custom and then you pull in that one that you just created here and then you can put in the license type and the license metric so this this is a little more kind of detailed you don't have to do it this way maybe just creating the model would be enough but i just want you to be aware that this is another way you can do it but it always goes publish your product and then model and then tie the model to an infection um [Music] so yeah so i know i covered a lot i'm just trying to pack in as much as i can in like an hour um so the you know the bottom line is like why are we doing this we want a good licensed position right another thing that we have is this licensed position report that really that really breaks things out and easy to understand way we have your right zone your rights consumed and then your rights available so a lot of things insert like a lot of the dashboards and things that i showed you they all referenced this like underlying report and this gets generated as part of um this part of reconciliation so just you know be aware that this exists and we do you know all types of metrics here um and yeah so i'm just trying to think if there's anything else i want to cover let's i think that was it for the slides yep so let me just see um yeah so you know kind of moving forward just to wrap up um you know keep an eye out for what's coming in san diego you can get like early access for that um as far as like new features the main thing that's you know there's a lot of stuff coming out for sam and i'll actually be recording like a youtube video i'll do an overview for sam so um you know we can keep an eye out for that i could even send the list you know everybody here that video when it comes out i'll sort of recap that um so yeah keep an eye out for that um and yeah hopefully you found this helpful just trying to think um and he was trying to answer the questions that came in um so yeah i'm not seeing too many that we need to follow up with um [Music] so yeah hopefully hopefully this was helpful i'll definitely make sure i send out the recording um yeah and good luck with your with your standard implementation