Client Health Report Support Webinar
Automatically Generated Transcript (may not be 100% accurate)
Hello and welcome to this week's support webinar. In this week's webinar we are focusing on the Client Health Report. Before we get started I want to make sure that everyone is comfortable with their virtual environments. In the navigation control window of the webinar you have the ability to ask questions. We will silence all communications during the webinar and use the questions window for primary interaction with the audience. We will conduct an overview then move into a demonstration followed by our live Q&A session. It is recommended to send in your questions as soon as you have them. Thanks for joining and let's get started. I would like to introduce our speaker for this weeks webinar, Bill Hennessey. Hello my name is bill Hennessey. And welcome to lab tech support webinar on the client health report. In this webinar we're gonna talk about how to update the current health -- Scripps. Will take a look at the health report overview. And we'll take a look at how the scores are compiled. Before we begin need to make sure the we have the right server control Centre version. In order to update to current script -- -- have version fifty point 170 install. You can find -- at support dot lab -- software dot com. Or I actually found mine on my RSS feed. In order to acquire the new. Daily health -- scripts and health reports will need to get them from the lab tech marketplace. To go to the marketplace you'll need to make sure that you're on your control center server. And go -- the tools. And lab tech marketplace. -- and it opens. So from here. Who wants you scroll down and highlight. Scripps. And look for. Now this is going -- -- to download other scripts that go along with that just go ahead and say yes. And you'll see them popularly down here. So now ready to update these scripts but we also need to make sure that we update. The results -- going to look a little bit different. So we'll go to. -- We need to walk grabbed. Each one of the -- to make sure we have all the updated Scripps. At our disposal. -- and you'll see that they as well population down here. From here you can go ahead and select update. I already have done this so I will. Move on. The first time your on the daily health check -- it creates all the new properties that dictate how the check performs. Once the health checks script runs increase the properties for even the dashboard. It's a good idea awaited near you -- -- the updated strip improperly gather the data. But for our example I'm obviously not going to wait so -- here will go ahead and schedule the health checks script. Will go to a group I'll select the all agents group. And go to scripts. As -- C area have -- scheduled. According to ignites it is a best practice to have this script scheduled. -- 6 AM. No need to add any parameters. You can't just go ahead and save this. Close that out. Now scheduled to report scripts. From the year will go to the dashboard. Go to management tabs. And -- is scheduled client Scripps. Once -- you can see add the schedule already. However according to lab tech ignites it is best practice to have the scheduled at 1:30 PM every day. This gives sufficient time in between both Scripps so you can get the most accurate data. Every day I need to repeat. And safe. See updates. Are close this out as it's ready. It'll open up my company. -- go to the info tab where these daily health check tab resides. On this -- you have many options. Server -- action workstations failed action. What these are asking is how you want the server workstation -- reacted if it gets a failing score in the health check. Do you want to do nothing do you want to record -- and raise alert or create ticket. It's best practice to at least record the stats that -- go back and add them to a report at some point. Some don't want the health -- record. AV or performance stats. For the servers. Here you can disable that. Same with the fire scanner. This works on both servers and workstations. Here you can decide which reports you want to run. And where you want -- -- to. Please note that it is important to have an email address. In putting heralds there will not be airport. Just some information for you. As you see -- several options here for reports. Full is not the most robust report. There's more information on all these reports individually it supports -- lab -- software dot com. However if you want the most robust report -- clearing now that is simply choose health report. And it's just another piece of information for you if reports -- days. -- tech will default to the most thorough report for instance if you have. Daily reports. Running and a monthly airports running the data at the monthly and the daily report -- -- It will default to the monthly. Make sure you save your work. And close out a client. Now we're gonna quickly go over the report itself. This is the first page in the client health report known -- the summary page. You'll notice the top left has overall client health score information for the day. Your top right has -- OS's. Middle left has what type of devices are detected. Mill rates at the -- -- space status. Bottom left is detected commands applications and alert information. And on the bottom right is the top five and the bottom five -- systems. Here you can see the detailed server report. On the top left is useful server information. Top rated CPU and ram usage and this is for the time period that the report -- Enron in this case it is -- the last 24 hours. In the middle is the record of the checks that -- run and the results. On the bottom left -- prevalence event log -- and next to that is available shares on the server. This is the workstation summary page and it gives summarized information on what workstations failed what checks. And the last page of the report -- a -- So where exactly do we get these scores from. Well -- based on properties their pre configured for you. The values can be modified to fit your needs. Each -- scores comprised of multiple checks each check is assigned a way to. The sum of all health check waits equals the health score. In these can be modified like I said at dashboard config configurations. Properties. And they will look like. What you see below you'll see script underscore DHC underscore and then the value. It does need to be noted that if you are. Making changes in the properties to not change the spelling of any of these properties because the check will -- not give you accurate results. If he do you go in and make changes to the properties I wanted -- -- Get an idea of what shall be looking at if you scroll down and find. The daily health check properties you'll notice that they look like this they'll say scripts underscored DHC -- begin with. Mod or -- and then followed by a value -- Mod stands for modify or and that's basically a -- -- -- threshold. And an example -- that would be a defrag percentage. And that value in there would be 15% so you didn't want to the defrag to go over 16%. And weights are used for compiling the actual score that goes in your reports -- an example of this would be if one of the checks is worth 50% -- the actual value of that property would be fifty and once again you can make changes to these. And it is important to note that if you do make changes to the weights. Make sure that if you have the health check weights and another health check way to make sure that -- equal 100. If you do not then -- report will return strange results. Now let's go through each check its weight and how it scored differently. -- start with the anti virus health Jack. This check will go looking for whether you have a virus scanner. Whether -- definitions are current and whether your fire Skinner auto protect. The feature is enabled. And you'll notice that to each one has a weight assigned to it to the -- scanner detected -- is worth 50%. So therefore if the check runs and it does not to detect -- scanner then your check is already down 60%. Next to it there's an example of the wait that is in the properties for this particular check script -- DHC underscore -- virus scanner found. Now like I said he could make changes to these. As long as with any -- they all equal 100% and as you can see in the -- -- fifty plus 25 plus 25 equals 100%. This chart explains the difference between the old way of scoring in the New York. You'll notice that computer one and -- were pretty self explanatory. Computer one passes all checks and to fails -- -- And in both methods -- new way of scoring and the old way of scoring they would either get 100%. Or a 1% failure. The difference comes in computer three. You'll notice that computers three has a scanner installed definitions are up to date to but the auto protect is not enabled. In the old message computer three would -- for the day with a 1%. In the new message -- you now have a 75%. Now let's say for example you didn't want auto protect and able to be part of the scoring. We would go to dashboard configured configurations. And properties. And redistribute this weight of 25%. As long as it equals 100% at the end of the day you can make changes in the properties. Another important note is that scores will not be applied retroactively when you update your health -- Scripps. Running the checks for weekly health report for instance. You'll have to have seven days of news scores to cycle out the old ones and receive accurate results. And we'll take a look at that here. You'll see that one and two produced the same results. If we take a look at day three we apply the new scoring. 3459%. The weekly however doesn't get the same bump yet because the scores are retroactive it's gonna take the rest of the week to cycle out the old scores. They'll take a look at the drive health check this one's a little bit more complicated. These are checked against each internal hard drive. For example the event -- drive check on a PC with three internal drives. Overall this check is -- 30%. With two out of three drives passing -- this check is only worth 20% -- The checks -- -- here are. Checking to see if there is a minimum drive space free and that's for a 15%. Is it below maximum amount of fragmentation and that's waited at 15%. Does it pass Smart tests and that's waited 40%. -- -- a recorded any dried -- errors. -- waited at 30%. They'll take another look at this chart. You'll notice that computer one and two pass and fail in both methods. Computer three has one drive that doesn't pass fragmentation check worth 15%. -- -- on computer three it's only going to receive half credits or seven point five for the frag check. In the old scoring the single drive would -- the entire computer for the entire day. Drive health checks are giving partial credit. All other -- checks like easier performance are pass fail or full or no credit. Now let's take a look at the virtual computer. Notice the big -- zero. The end to not get Smart checks in the old method this BM would return a sale on Smart and -- -- -- for the entire day. When the new health -- script runs it checks for -- If it returns true then the Smart check doesn't run and -- percentage for Smart is redistributed equally. Among the other checks. 13% is added to each of the other check waits for instance drive space is now worth twenty point 3% instead of fifteen. -- event errors is now worth 43 point 3% instead of just thirty. Here again you can see other weekly health scores applied. Computer three getting credit for the drives that passed and -- not taking Smart -- gives a significant bump once the new scoring has applied. You can see the weekly score slowly rise as we cycle out the old scores. Teachers and health Jack. This -- the event ID is representing a failed login attempt in the event log table. The default for this check is 25 which means that 26 would mean failure. -- you can adjust this in the properties that dashboard config configurations and properties. And there's a list of events that the lab tech looks for at support dot lab tech software dot com. Search how health scores are calculated. Now take a look at performance health. The first checked detects average CPU resource usage over a number of days and this is -- at 30%. The default number of days as -- there's another modify -- associated with this check and that's Max percentage threshold which is forty. So that means if average CPU usage over the last eight days is greater than forty but it fails. The next Jack is the number of hourly CPU spikes. And a CPU spike is defined as the Mac's CPU. Exceeding the average CPU by a certain percentage and this is weighted at 10%. -- -- -- CPU usage. And gets an average every hour -- -- CPU usage goes 10% over that hours average is defined as a spike the script counts how many of those have occurred in the past 24 hours. And if it's anything more than six and it equals the sale don't forget that these can be changed by going to the dashboard. Config configurations. And properties. Next check is to detect the average -- resource usage over a number of days. And this check is -- at 30% to. This works the same as the CPU and uses the same -- fire as CPU with an eight -- default. Again number of hourly -- spikes are rams -- is defined as Macs ran exceeding the average -- by certain percentage. And this is -- at 10% as well once again this works the same as the CPU spike. The last check done here is the minimum OS version and it's worth 20%. What this is looking for is operating systems at XP or 2003 server and above. Here's another example of how the new scoring is applied. Computer three -- checks one and two waited together at 40% -- the new score is 60%. Vs the old scoring which would fail them immediately. And get a 1% score. And again you can see how the -- scoring on. The service health check this checks for automatic critical service is not running since last -- -- Critical services are defined as windows services not drivers and not printers and not on the event blacklist. This check is on weighted so that means it's pass fail. -- take a look at the updates and health store. What this is looking for first is the outstanding critical patches that are not installs. Critical patches are defined. As critical updates and or anything with a critical severity rating. By Microsoft -- has a weight of 75%. It also looks for any outstanding elevated patches that are not install -- An elevated patch is defined as a security update or anything with the severity rating that is not listed -- critical this is listed at 20%. And lasting -- looks for -- any outstanding standard patches that are not installed. A standard patch is something that is not categorized as critical or a security and has no severity assigned to it. This has a weight of 5% to. The way that this is -- it is directly related to -- how many patches are available for each check. For instance if there -- ten standard patches available and you have nine of them installed. You automatically receive. 8090%. For that score because each -- is worth 10%. Here you can see the very large disparity between the old and the new scoring. Computers three has standard patches missing and it would resolve a failing score but not anymore now scores -- 95%. And you can also see what that does to your updated health scores over the course of a week. And as it has been said before the scores are not retroactive. So you see -- rising slowly. It'll take a look at the event health check. This is gonna look for any critical -- from the event logs that have been recorded from certain information gathering Scripps. This check is on waited so it's pass fail in any detected -- equals failing score. At this time I'd like to move to a question and answer session with one of our top developers Joseph Smith. Please feel free to type in your questions through the webinar and jolt you out. Would like to thank you for your participation -- my name's bill Hennessey and notes welcome Joseph Smith joked. This is Joseph Smith from the report developer with -- -- software and address and your culinary questions here we've already got a couple that we're gonna run through so let's go and jump into it. First question was when I go to get daily health checks for from the marketplace. It's listed as having local changes instead of update available how to update the script and that's -- -- Well but we can't do that is that you can just go ahead and check the daily health -- stripped. You'll load in all the dependency is the -- script go to the report you may see local changing on the air and set an update available go hand in just over -- -- and you'll and -- listen tomorrow and the marketplaces. -- update and a go ahead and update -- -- All right so our second question what is the difference between -- health and update helps this is a great question the -- we receive multiple terms -- the past that's part of the reason we update in the daily health check is that you could. Address the concerns that the existence of this difference between actual. It used to be that update -- was more focus on the number of critical patches that -- income on each individual system. If you had at least one credible patch outstanding would -- -- check automatic. Patch help is more focused on the number of hot fixes and patches are available for your windows systems. And we separate them out into three individual levels of critical elevated standard -- this has been -- -- of last year -- -- health impact review reports critic of the -- -- -- see -- patch was not installed and so -- So -- with this release we decided that. Wanted to fix that disparity between up to health -- parent -- partial -- same way. Update health now scores. The same exact message every day that passion health -- so for instance you look at your parents help on Monday that -- seventy check your update help for that day from -- computer is also gonna be at 70%. Instead of a 100% or 1% so you're gonna receive the same exact or that you see on her patch also TC that you're scores low. You insult you catch is you run the -- health reported in -- -- review reported in on that computer you get it up -- -- 95%. For that day the update health will be 95%. So now up to help his shifts from. Running measure of what your parents health has been over the time period for that report. All right so question at three. Hello I just the day of the week in the day of the month -- the health report is emailed us a great question we've had this several times through support channels. You look in the properties list that we direct you to earlier what you believe is the from the dashboard -- you. -- -- And then the properties -- you'll see that there are two properties there -- one is called health report email. -- month and health report -- -- week. Understood it to number values. Of those first one month is gonna be basically matching up -- in -- so if you set that value to -- it's gonna set it on the -- -- she said it's a fifteen minutes instead of on the fifteenth. You have to be careful about when you modify that number is it she said it's just -- 31. Because you want to -- at the end of the month won't not every month has 31 days so she tried to -- -- -- in September on the September 31 that it doesn't exist so people just skip over that instead of nailing it the next day so it's very important that you try to set back to mediate between the first of the twenty. The weekly email day it is a number based off of basic and that number can be sent anywhere between -- range of zero in 60. Representing Monday. So if you set that date due to which can mail it out on Tuesday she said to sixty may hold out on Sunday so on and so. All right so and so the next question. I assume that the updated scripts are already loaded for cloud version of lab -- we actually have not updated the cloud version of web -- for the daily health -- script hasn't yet he's been trying to make sure that a cloud installs are having universalist and that there -- affecting everybody the same time so to make sure that happens right from the -- first so we've held off on that on that version being installed and I believe it will be on the first of them. -- month I will need to double check that so if you have any questions on that you can contact support. The next question was why would you disabled EGM performance section of the reports costs a great question. That would disable section lets you choose for servers only whether you want to cover -- Eighty checks and performance -- throughout the -- process. There are some servers that you would want to disable the -- checks on their some servers he wanted to see what form -- -- excellent. -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- System automation folder search let's underscore -- daily health check folder open up the daily health. -- -- And there'll be to have on the right -- you can click on -- -- what you foreign scripts. Will pop up window rebels say do you want to include. All groups in this or something similar to -- question you click yes there until list out all the groups that are calling the script. I think this question might have actually come from an ignore user. You vignali. Agent automation scripts as -- actually calls the daily health -- script it's automated as part of the process within it so. -- questions idea of them. Reports sent email to different people but we've never received -- now what could be causing it not to -- we've had this question coming to support several times it's really difficult for us to tell without taking a closer look at the system it may be something as simple as the way that we entered emails into the health -- email parameters. Or could be something more complicated like -- connection issue with your change server. So in that situation I would recommend contacting support at lab tech and they'll be able to invest -- system walk through with you and see what would be causing them. Station. What can we do about the services war. I'm assuming that -- question is referring to what kind of changes that we make to the properties to table for model fires and waits for services services are pretty much set up the same way that they were before where -- -- service fails the entire -- fails for that day. Now if you have a service says that continues to reappear in your list you can have that service European blacklist. And that'll prevent it from firing your service pork. All right so the next question some of the health reports used to include back up in the health report is that still included if so how -- -- this from the report. Sure in the past is that the report shows 0% for back -- and some clients and are using a back up service from -- that's a great question the backup section of the health report has not been modified from the previous version that's been out for the past year. So we still include this is the way that we have back -- set -- is that that section only runs when we are actually collecting back up data via scripts. I believe there are stats gathering Scripps. In the -- section that you can run that will go ahead and gather that information to -- -- stats table the daily health check is designed to check -- -- and associate with each computer that has a back -- running that's what's actually given us the score for Beckham's successor backup fail. Report that showed a 0% -- backup and some clients -- -- -- -- of service may wanna contact support about that to see if we can find out if there's a script that's pushing the value in for backup health that you may not necessarily want to be pushing in the next question how can we exclude VH DS from health reports. -- is for virtual hard drives. But only exclusion were doing were virtual hard drives this through virtual machines so if we detect that key -- and machine that is a virtual machine system which she conceived fuel into the computer -- screen and in the operating quarter will be about shift to talks -- there's one of -- says virtual machine if that flag is checked -- we -- exclude. Around that virtual machine from the Smart checks are running against the drive. -- We actually don't exclude -- Smart checks we we distribute the -- waiting for that check across to the other three checks so we're basically saying okay you don't wanna run -- its virtual machine because you're gonna come back with false positive so word -- just re distributed and make everything else a little bit easier so that it compensates for the lost amount on that a Smart check. If you have suggestions for other ways that we can detect virtual hard drives or other -- them are being affected by our virtual hard drive for hidden contact customer support and will take that as a feature -- -- access into will be able to change its future. Okay next question daily health check is no longer running after updates. We have any ideas property security missing as well from the dashboard. Like a little bit of follow as we wanna look into that -- I wanna call tech support for this issue if you have downloaded and the newest version of the daily health check and -- Has stopped running those properties are not visible and that means of calling have a problem with the script itself from going through now the properties only appear in the dashboard. After the first time you run the daily health -- scripts what's actually happening in the first couple lines he call me another script called -- properties stashed daily health check. And -- -- goes through and -- the properties table to see if there are any additional properties that need to be added in that may have been deleted the previous day. It also checks to see if you if you have the properties in their at all if it sees the properties in there it's not -- updated policy if it doesn't see that property name listed as an added in. As if she's there with default values so hmmm if you're looking to -- properties you can go in and run the -- properties daily health -- script -- -- that you'll be able to find that under system automation. -- dysfunction is -- of another question do you have a list of services are checked for the service -- we actually do what I can tell you that we filter that list by whether it's -- driver or not it's it's it's it's a windows driver we excluded if its printer we excluded. And finally we look. Look for the of -- blacklist. This is -- blacklist just -- Even 2012 might have been a little bit earlier this event blacklist which you need that the service steps should be automatically running and is coming up the -- -- you run the check so any service that's on that list it is going to be skipped over as part of the -- process. Under tools reporting configure manage risk for. We can change weeks yours well does this do the same things change and in the properties there's also an update client health scores option here to. -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- teaching -- some questions user friendly -- the executive summary report in management report are also are actually health reports as part of -- health reports that the executive summary report it is actually the same as the monthly summary report in the management report is actually the same as the Motley -- reports so if you're looking to get those ports are -- scheduled you can go ahead and select those that names won't be the same but they are basically providing the same information. -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- Scroll all the way down you should see script underscored THE underscore -- -- And there should be a total of five waits for the performance section. Obi -- -- CPU spikes memory -- Memory average CPU average and -- OS version costs you can go in. And and reduces CPU spikes. And 20 and the memory -- -- -- zero. A gesture -- three up bounce between them so that they all add up to a hundred. And at that point you'll have effectively remove the CPU spikes in memory -- from Europe for performance health -- checks will still be performed but they will not impact your overall score for performance. I want to thank everyone for attending this week's webinar. This webinar will be made available both on the forum under Lindsey corner, and on LabTech TV under support webinars. I also wanted to remind everyone about the resources we have available for you online. By going to support.labtechsotware.com we have a variety of educational resources, including documentation, Knowledge Base articles, and LabTech TV. On behalf of LabTech I want to thank everyone for attending and hopefully we see you at a future webinar.