SSRS – Client Health Dashboard

, , , , ,
Client Health Dashboard
In previous posts I was speaking about soon to be releasing a series of SSRS reports based on troubleshooting. The first in the series I am trying to have is a focus on Client Health Overview. This dashboard will later be include drill down functionality to multiple other reports as soon as I can finish making and validating them. This dashboard is something that I put together for my current customer to get a brief overview of client health. There will be a few more items added to the home page at a later time which will be focused on count vulnerable/unpatched systems
Currently we can see in this report Active clients, MP information, Client version counts, OS version counts. There are even a few top level items you should keep an eye on like duplicate systems, mac addresses, systems running out of space, or why clients failed to install/re-evaluate. These will all be further expaneded on when the full client health troubleshooting series wraps up over the next few weeks.

Link to the Report: https://gallery.technet.microsoft.com/SSRS-Client-Health-6bfb794f

Some code used from: Greg Ramsey and Eswor Koneti

Future Dashboards w/ drilldowns coming soon.

– Client Health (will be finished soon)

  • This will also include drill downs into several other reports

– Software Deployment (For Packages / For Apps)

  • This will also include how to troubleshoot just like this other report
– Infrastructure health (Primary/DP/SQL/DP etc health focused)
  • This will also include how to troubleshoot just like this other report
  • This will also include drill downs into several other reports
– Windows Migration Summary

 

– Collection evaluation

 

SSRS Client Installation Troubleshooting

, , , , , , ,

This will be the first part of many in a series of reports that I will offer for free to the community. The reports will cover wide range of items from OS Migration dashboards, Bit locker reports, SCCM Infrastructure health, Client health, Collection evaluation, etc. In each report I intent on there to be plenty of visuals to provide the tech a clean overview of what is happening in the environment. There will also be several troubleshooting notes included in this report to be a 1 stop shop for troubleshooting tool. Some reports during this series will have troubleshooting guides available as well. So far I am intending to release troubleshooting guides for OSD, client install, and software updates as I have already written several of them for previous customers.

The first report to be released will have a focus on identifying problems with client installation and providing some good.  This will eventually grow into a “Client Health Assessment” where there will be multiple reports all focused on client install/health/active etc.

Below we are able to get an overview of the client install failures within the last 30 days, and keep an eye on how many clients we currently have in the environment.

I’m leveraging several CASE WHEN statements to translate the error codes to something the tech can easily troubleshoot.

Please not that if your total systems number is off from what you see in your SCCM Console then look into your maintenance tasks/discovery items. It is not uncommon for me to see customers environments that do not have AD cleaned up…so long story short make sure your AD environment is cleaned up too.

Future Revision of this report will be released as part of client health Dashboard, with a few other reports.

Link to Report:
https://gallery.technet.microsoft.com/SSRS-SCCM-Client-Install-3bd9e6e6

 

USMT Estimation Report

, , , , , ,

USMT Estimation Report:

One of the deliverable items at a customers site was to identify the amount of data each machine would would have to backup. This is important data to capture to help plan your estimated migration times as well as identify systems that will not be able to successfully perform a backup. This data is not something that SCCM will automatically absorb, but Jason Sandy already has a solution for that. We used his script here with a few mods for our environment we were able to capture this information.

let me point out that if you look inside of the MDT Toolkit for ZTIUserState.wsf you will see that it is estimated to need 1.1 times the size of the data you are trying to catpure. This is something that was pointed out from a co-worker.
OLD Report Visuals

New Report Visuals

 

 

The new report allows you to look up specific computers, interactive sorting, better visuals, graphs, and more efficient SQL logic.

you will have to modify the CASE WHEN statements to fit your own environment. Please do some testing and then modify for the “USMT Only Time Estimate” column. Several factors go into consideration for determining this value. These are things such as server specs, amount of systems running the task concurrently, bandwidth, etc.

THE RDL: https://gallery.technet.microsoft.com/USMT-Space-Estimator-2c5d728b