[Music] hi my name is Sean Walker and I'm a principal product success architect and part of the Ranger team here at service now today I'm going to be talking to you about the health check application this video is part five of five of a video series I'm doing on the success portal so make sure you watch the other videos to see how all the components of the success portal relate to each other and really help you mature your Sam program so today we're going to cover the itam health check we are going to discuss site checks and scan results and then I'm going to go into a demo and run a couple scans for you and make some modifications so you can see those results so what is the itam health check the health check it's a service now store application and it's going to give you an overview of your Sam configurations and give you recommendations on things to correct uh the Sam manager Sam analysts and implementation Partners they can all use the health check at any point during the deployment of Sam or as you're kind of going through the life of Sam uh you can continually run the health check they really help you keep an eye on any errors within the application so for example you know configuration errors like incomplete setups of in tement or software models or maybe missing data attributes in the cmdb that Discovery is not populating the health check can really help identify those issues so just make sure that since since this is a store application it does update more frequently so you're going to want to make sure that you're periodically checking to make sure you have the latest um health check application installed so the health check runs a series of checks in your instance and there's currently 12 suites available so there's you know a general dat General check on the database there's uh Microsoft Microsoft 365 Suites that it checks also a bunch of SQL server and Windows Server Suites that are built into the product today there'll be more sweet checks coming out in the future so hence the reason that you know you want to make sure you stay up to date on their plugins so as future checks are released they automatically get included as part of your health check application so each Suite check has multiple checks to run that's going to identify those particular configuration or data issues about that specific product so if you look at for example the SQL Server it does a check for things like um software software Assurance doeses some downgrade checks it checks your rights per uh pack and it also does things like check the environment field Etc so there's a bunch of Suites uh checks included in each Suite so be sure to go through each different suite and you can kind of see all the different checks that are run automatically in your instance so the health check runs a scan every week and that's triggered by a scheduled job Sam trigger full scan and this is what's going to do that weekly full scan of your environment to check for any errors you can initiate individual scans or full scans even yourself um at any given time but it's just set to run weekly by default the scan results are can be found right on the dashboard and it takes the results and it groups them by priority so some obviously our bigger concern um so high you know critical those are something you're going to want to take it take a look at right away it also gives you um the number of scan results per suite and it also breaks them down by categor so you can have different people may be looking at different components if you need to so this is just an example of one of the scan results and so the scan results are are really helpful because they provide you not only the category and the priority but they do give you that short description but also that resolution detail so here are some of the things that you can do specific to that issue it found so this one was for SQL Server CPU count core count core thread um and it's a discovery check so what this basically is is hey as all your Discovery information coming in for this particular installation record um so for this example right it could very well be an installation record exists and the Machine it's installed on doesn't have any CPU information so if we don't have CPU information we're not going to be able to end core information we're not going to be able to calculate the number of cores required to license this particular uh installation of SQL Server so that's just one of the many checks so now what I'm going to do is I'm going to jump into a Washington instance and we're going to go through um the health check we're going to trigger a scan and maybe make some updates to see the results okay so now I'm in my Washington instance uh of service now with Sam installed and I'm on the success portal so I'm going to go into the health check application now and on the health check dashboard here we can see all the different site checks that are available so I can click on this and see all the different sweet checks and I can dig into specific Suites and see which checks they're going to run um and then I can also take a look at any checks issues by priority I can see kind of My overall health check score see you know if there's any open issues for a specific Suite so if I wanted to see you know my SQL Ser my database server errors here I could filter on that by status and also by uh by category so if you remember what we did in the last video and that was run through the product setup for SQL Server one of the steps of the setup was to trigger the scan for SQL Server so what I'm going to do now is I'm going to show you how to trigger a scan manually so again this will run weekly so all these numbers are coming from the weekly job but I can actually trigger a scan for SQL Server independently just by clicking on the execute scan and here's where it's going to ask me which Suite do I want to execute the scan for So today we're just going to play with the SQL Server scan and we're going to actually scan our instance and then see what kind of results come out so it's simple as C selecting SQL server and then clicking on execute and this in the background is going to go ahead and run those checks against my cmdb against my models against my entitlements and it's really going to see what issues um came at so we can click on The View results and we can see here's all the specific results that it found um now it did find 692 issues um and these are more maybe these are all related to to this particular scan or maybe there's some old ones so what I'm going to do is quickly grab take a look this was scan result 87 I'm just going to come back and I'm going to show you the view one of the views I kind of like taking a look at um now I can come through here and I can see maybe SQL Server cmdb I can just open this up and this is going to kind of give me a list of all the scan results um but you see it's got all the scan results from every scan it's done but let's just take a look at the scan results um from scan number 87 which was my last scan the one I just triggered and let's just make sure there's no other filters on there and I'll be able to see absolutely everything it's just a good way to show you so I'm going to take off this sweet check for SQL Server cmdb because I want to see all the SQL Server scans that ran but I still want to keep this result 87 so I'm just going to filter this and now what I like to do personally is I like to sort these um or group these I should say by check so this will kind of group together all the issues it found by that specific check category so here we go so now we can see we've got 285 uh CPU errors that we should be looking at uh we can see here that some the developer and express configurations we should be looking at there's environment Fields etc etc and so these are all the different issues that we probably want to make sure we address um before we can say our our SQL Server license compliance position is is even accurate because if we don't have the CPUs cores it's going to be wrong our reconciliation is going to be wrong and our compliance position is going to be wrong uh if we don't take care of these uh developer and express configurations we could be consuming licenses when we shouldn't be so let me just jump into that one that's a good example to show maybe go through and we'll fix some of this um to show you how to fix some of these issues again some you're going to be able to fix yourself as a Sam manager others might have to like all these Discovery issues these might have to go back to your Discovery team to have to go to them and say hey why am I missing this data on these machines so this one here I'm just going to open up the check and it says SQL Server developer and express Edition configuration so it says ensure SQL Server developer and express editions have license under management set to false and that's a really good idea because SQL Server developer and SQL Server Express are not licensable products so you'll see these come into your instance quite often people install a piece of software and it might have Express loaded and you don't even know it's there um and that's part of this other installation packet so you're not paying it for it and developer you don't need to pay for as well um or there're separate licensing for kind of concept um so what you probably want to do is you want to set these to license under management equals false and what that will do by setting this particular model so what I'm did now is I clicked on that and it opened up that very specific software model that it detected that didn't have this attribute unchecked and it's telling me to uncheck the license under management and so what this will do by unchecking this is this particular software model and all its related installations will no longer be uh counted during the reconciliation process so you're not managing this product you don't want to manage this product you don't have to worry about it so you can say license under management is false so unchecking that equals false I'm going to hit [Music] update and it's going to think about updating there we go and now I can come into the next one I'm just going to do a couple here and I'm going to set this one oops this one to fall and update it that's SQL 2019 developer and we'll do one more here uh SQL 2005 developer we're just going to un whoops uncheck that and now we've fixed three of those nine errors right so we had nine uh configur sorry configuration check for that so we fixed three of them um environment field is empty I'm probably not going to go ahead and modify that CU that's really something you're going to want to do probably in bulk and that's making sure you have on your CI your server based CIS that environment feel feel populated um this is another one here missing relationship for on premise VM uh this means probably it's a discovery issue where your Discovery team is going to probably need to take a look at it but here's another good one that me as a s manager should be taking a look at um and if you look at the description is rights per license pack should be two for SQL Server right so it's saying here if I take a look at the entitlement go back a screen here and I take a look at this particular entitlement so the entitlement is uh Microsoft SQL Server 2019 Enterprise and if we look at the license metric it's a per core license metric right um and we know that SQL Server is licensed in two core p packs so um we see here that we only have rights per pack equals one when it's actually two and so that's what that error is talking about is it's saying you should go through an update this to two because that is the correct for SQL Server okay go back here okay so now we fixed one of these and we fixed three of these so now what I can just quickly do is go back into my success portal and I can run this scan again for SQL server and I can execute it again it shouldn't take very long okay it's already done this was result 88 so I just go back to this let's just maybe update that filter so we're looking at the scan results for 88 so remember we had nine developer and express and we had six of these so let's just change this to the other scan and see what happened and we're just going to run this filter give it a second and look at that we had fixed three of these and the total was nine before so now it's down to six and then we had we this was at six before and we fixed one of them so it's down to five so again this is all the different health checks um that you can run is obviously you can you can just look at all the results um on the success portal and you can look at them by category whatever and go through you can maybe look at these say for example these Discovery issues and send some of these issues to your Discovery teams to resolve um and making sure you have all of these particular um results fixed um is a really really important thing for Sam to make sure you're getting the best compliance position and the best reconciliation possible again I can just remove any those filters group it you can see all the different things that are going on in this instance so there's quite a bit going on but what do I really need to be concerned with well I'm working on a SQL Server license compliance position so I really want to make sure my SQL Server um issues have been resolved there we go so now you can see all the different checks it's done and all the different results that it's done throughout all of its scans of the environment so there are quite a few issues but again focus on the ones that are specific to your specific use case in this case I was doing SQL Server so that's really what I want to focus on and then if I'm doing window Ser Windows Server I'd want to focus on those if they're doing some SAS stuff I'd want to take a look at that Etc and then there's some general ones as well too so that concludes includes the um Health Scan portion of this demo in this video we discussed the health check application we talked a little bit about the suits and the scan results and the resolution details then I went into an instance and demonstrated you know how to initiate that specific scan we did SQL Server we reviewed the the results of that scan and some of the resolution details that were provided with that scan and then we went through and actually remediated a couple of issues and reran the scan to just kind of show you how you can remediate some of them yourselves and then maybe some of the ones that actually do need to go to other teams to resolve so for more information on this particular topic you can go to the service now product documentation site and there's a couple of really good things to check out one is software Asset Management health check and the other one is run a health check scan for Sam um those again both on the service now product documentation site so this was the last video in a five-part series on the success portal so I really do encourage you to watch the other videos to really uh look at how the success portal all the components can be used together to really improve your Sam program I hope you found all of these videos helpful and I'll talk to you on the next one