Unlike the previous dashboard which looks at all updates per operating system, this dashboard is more useful for organizations that use a whitelist\blacklist or baseline of updates to collections that they may not necessarily control.

This dashboard has many layers of “filters”.  Only updates that are applicable to managed systems in a specified collection and are contained in a specified SUG that fall into certain Categories will be reported on.

Here is how it works.  Each report has a set or parameters.  The parameters define what will be filtered on.  Only managed systems will be included at since it is very common to have outdated information in a Configuration Manager database. 

There are five different types of filters:

• Days Scanned
  • This parameter determines what systems will be included in the reports.  Only non-obsolete systems that have performed a successful scan within the last @DaysScanned (default is set to 14 days) will be reported on.
• SUG
  • Only updates that are contained in the SUG are reported on. 
• Collection
  • Only updates that are applicable to the systems in the collection will be reported on. 
• Category
  • Only updates matching the category will be reported on.
• Date\Time
  • Start Date (only applies to the SUG Compliance – Dashboard)
    • Only updates that have been released or revised before the Start Date and within a 12 month period of the Start Date will be reported on.
  • Start Date and End Date (only applies to the SUG Compliance – Software Update Information report)
    • Only updates that have been released or revised between the dates will be reported on.

Be aware that any update in the selected SUG that doesn’t apply to a system in the selected collection will not be reported on.

Using the Dashboard

When you first run the dashboard you will need to select the parameters to run the report.

After selecting the parameters click the View Report button and the dashboard will appear.  The dashboard contains a table listing the operating systems in the selected collection, a chart depicting systems missing a certain number of updates, and a chart showing the applicable updates on a monthly basis over a period of 12 months.  The last month is controlled by the @StartDate parameter. 

Assets

The Assets table list all operating systems detected in the specified collection as well as the number of managed or unmanaged systems.  Remember that all results returned by the reports are based on managed systems.

You can click on the Assets link to be redirected to a sub report which will show information on the assets.

Each computer name is a link to the built-in Discovery information for a specific computer report.

Systems Missing Software Updates

The Systems Missing Software Updates chart groups systems together depending on how many updates the they are missing.  This perspective can add a spotlight to problematic systems that could be missed if only looking at a patch compliance level.

You can click each bar to be directed to a sub report that will list each system per group.

Each computer name is a link to the built in Compliance 5 - Specific computer report.

SUG Overall Compliance

The SUG Overall Compliance column chart displays the overall patch compliance for each applicable updates in the SUG.  The column is clickable and will redirect you to the Compliance 1 - Overall compliance report.

Applicable Software Updates

The updates that meet the criteria previously describe are considered applicable and are display in the monthly chart.

The bar’s color depicts the compliance level.

• Green – 100%
• Yellow – 66% - 99%
• Orange – 33% - 65%
• Red – 0% - 32%

Under each bar contains 2 numbers. The top number is the unique applicable updates that has been released or revised that month and the bottom number is the number of systems that are affected by the applicable updates.

You can mouse over each bar to display the tooltip.  The tooltip will show the number of installed and missing updates.  These numbers are used to get the compliance percentage for that month.

You can click each bar to be directed to a sub report that will list the applicable updates for that month.

Each software update Title is a link to the built in Compliance 2 - Specific software update report.

Installing the Reports

The process of installing these reports is similar to my previous reports in past blogs. 

I've attached a zip file containing the .rdl files to this blog.  To install the dashboard, create a folder in the SSRS home page called Software Updates Compliance (If you installed my previous reports you should already have this folder) and place each .rdl file in it.  Modify each report with your data source. 

Change the site code in the Overall Compliance chart.

1. Right click each series (green and red bar) then select properties
2. Click Action
3. Change the Site code to your Configuration Manager site code
   1. (e.g. change /ConfigMgr_SI0/Software Updates - A Compliance/Compliance 1 - Overall compliance to /ConfigMgr_LS1/Software Updates - A Compliance/Compliance 1 - Overall compliance)

For each sub report right click the text box with the hyperlink then select Text Box Properties.  Perform the same steps as above to change the site code to your Configuration Manager site code.

Development

I have only tested this dashboard in my small lab.  Please ensure the accuracy of the reports and watch for SQL performance when running them in your environment.  Since I’m not able to use functions, stored procedures, external SQL tables, etc. the SQL queries are not as optimized as they could be.

Software Update Group Compliance v1.0.zip

https://blogs.technet.com/b/gary_simmons_mcs/archive/2013/12/09/creating-a-custom-report-for-system-center-2012-r2-configuration-manager-part-1.aspx

https://blogs.technet.com/b/gary_simmons_mcs/archive/2014/09/16/system-center-2012-r2-configuration-manager-software-update-compliance-dashboard-part-1.aspx

https://blogs.technet.com/b/gary_simmons_mcs/archive/2015/02/17/system-center-2012-r2-configuration-manager-software-update-compliance-compare-compliance-dashboard.aspx

I’ve received many requests for a software update compliance dashboard based on Software Update Groups and Collections since not everyone reports compliance based on Operating System or has a whitelist\blacklist of updates.

This Software Update Groups Dashboard displays the compliance for each Software Update Groups. The intention of this dashboard is to be displayed on a single screen and able to be printed on a 8” x 11” paper in landscape with no margins.  If you have more than 10 SUGs the chart will expand onto the next page.

Breaking down each SUG in a format similar to my previous blog (Month to month, etc) is very time consuming so it’s not included in this version of the dashboard.  I do plan on having additional sub reports in the future so stay tuned for those.

Similar to my previous dashboard the top displays the assets.  A managed system is defined as a non-obsolete system that has performed a successful scan within a period of time.  That time is defined in the @DaysScanned parameter with a default of 14 (days).  Feel free to change this.  Unlike my previous blog, the chart doesn’t distinguish between an unmanaged or managed system as the queries are using the built in views and the results are based off of a SUG and collection.  You are in control of what system and software update to report on.

The bottom half is the SUG compliance chart.  It displays the same information that can be found in the console by clicking on a SUG and looking at the bottom right hand corner under Statistics.  It will be displayed in a small Pie chart. By default the collection the chart uses is the All System collection.  This can be changed by modifying the default value in the CollectionID parameter.

Each Series in the chart is clickable and will open the Compliance 7 - Computers in a specific compliance state for an update group (secondary) report with the parameters prepopulated. 

The green arrow indicates the path in which the sub report is linked.  The orange arrows show the patch that sub reports are linked from my previous blog.

Attached to this blog is a zip file containing the reports from the Software Updates Compliance dashboard and the Software Update Groups dashboard.  Please use the instructions on my Software Updates Compliance blog on how to upload and modify those reports to work.

To install the Software Update Groups dashboard, similar to the previous reports upload the Software Updates Groups - Dashboard.rdl file to the Software Updates Compliance folder.  Open the Software Updates Groups - Dashboard.rdl with ReportBuilder (or Visual Studio) and change the datasource for your Configuration Manager server.

For each series (Green, Red, and Orange) in the chart, right click it and select Series Properties. Click Action then change the link to the report to include your site code.

Updated on 9-23-2015

• Changed the charts Dynamic Height to =(Count(Fields!Title.Value, "SUG_Status") /2) & " in"
• Changed the Title Property Auto Increment value to 1
  
• Incremented Version to 1.1
  

Software Updates Compliance v1.2.2.zip

The opinions and views expressed in this blog are those of the author and do not necessarily state or reflect those of Microsoft.

This report does not have any support and should be used as an example on enhancing your own reporting posture. I have not validated the results outside of my own lab so please verify the results in your environment.

To follow on with the Software Update Compliance dashboard for System Center 2012 Configuration Manager, this report compares software update compliance by displaying side by side results between two points in time.  The results are also presented within a 12 month period which allows for light trend analysis. Some of the steps needed in configure this report is described in the previous blog post.

Similar to the Software Update Compliance report there is no method to exclude updates and it looks for “All” applicable updates for managed systems.

Software Update Compliance– Compare Compliance

The Software Update Compliance – Compare Compliance report is broken into several parts; System Compliance, Software Update Compliance, and Monthly Compliance which is further separated between Servers and Workstations.

 Parameters

The System Compliance and Software Update Compliance charts are filtered on all parameters. The Start Date and End Date parameters will filter the overall charts to show results of the updates that were released\revised between those times.

When running the report it will default to comparing software update data between the top 2 most recent dates.  This can be changed by modifying the @DateCollected1 and @DateCollected2 parameters.

Overall System Compliance Charts

Each of the Overall charts are similar in that they are categorized by the operating system and show the compliance between two separate dates.  The Overall System Compliance charts displays the compliance of systems that are not missing any updates.

Overall Software Update Compliance

The Overall Software Update Compliance charts displays the percentage of applicable updates installed.

Monthly Charts

The Monthly charts are similar to the Overall charts except they only show a 12 month period starting from the @EndDate – 11 months to the @EndDate.  I didn’t include a monthly system compliance to limit the number of charts in the report.

Software Update Compliance Database

The intention of this report is to keep things very simple in SQL.  Because of this the SQL queries are not as optimal as they could be however, should still should perform adequately.

The information needed to compare results are basic device information, the applicable updates for each system, and the status of each update.  This information is then captured in a separate database which allow comparisons between two given dates.

Create the SQL Database

Although the database can be hosted on any SQL Server (2008 - 2012) with SSRS, for simplicity sake the database has been created on the SQL Server hosting the Configuration Manager database and SSRS.

1. Create a database called Software Update Compliance

2. Create 3 tables

   a. Devices
   

   Column	Data Type	Allow Null
   ResourceID	int	No
   Name0	nvarchar(50)	No
   Operating System	nvarchar(100)	No
   LastScanTime	smalldatetime	No
   DateCollected	smalldatetime	No

    b. Software Updates
   

   Column	Data Type	Allow Null
   CI_ID	int	No
   Title	nvarchar(513)	No
   ArticleID	nvarchar(64)	No
   BulletinID	nvarchar(64)	Yes
   DateRevised	smalldatetime	No
   Deployed	bit	No
   Category	nvarchar(50)	No
   DateCollected	smalldatetime	No

   c. Status
   

   Column	Data Type	Allow Null
   ResourceID	int	No
   CI_ID	int	No
   Status	nchar(10)	No
   DateCollected	smalldatetime	No

There are many ways to get data from one database to another.  SSIS would be the preferred method however, SSIS relies on the SQL Server Agent which may not be enabled for some.  The below method should work for the majority of people.

Create a Stored Procedure

The stored procedure collects the data needed and stores it in the Software Update Compliance database.

The diagram below shows what views the data is pulled from and where it is stored in the new database.

1. Using SQL Management Studio open sp_CollectSoftwareUpdateStatus.sql which is located in the attached zip file.  Replace each instance of [CM_<SITECODE>] with your CM Sitecode and exec the script.  This will create a stored procedure in the Software Update Compliance database.
   

   (example: Replace [CM_<SITECODE>] with [CM_HQ1]

    

Manage the SQL Database

Managing the SQL database won’t be covered in this blog as there are many scenarios to cover.  Consult with your SQL DBA to find the right method to back up the SQL Database.

If you don’t have a SQL DBA and little SQL experience then understand that other than having a good backup of the database, overtime the transaction logs may grow and need to be managed separately.  See https://technet.microsoft.com/en-us/library/ms191429(v=sql.110).aspx for more information.

Trigger the SQL Stored Procedure

There are many ways to get the stored procedure to run.  A SQL Server Job would be a good method but this too is dependent on the SQL Server Agent.  A scheduled task or System Center Orchestrator could be used but I'll describe a method to leverage native Configuration Manager capabilities after each successful software update sync using the Status Filter Rules.

Be cautious with this method.  If you have an aggressive sync schedule and a large amount of devices this will quickly grow the database. 

1. Copy Get-SoftwareUpdateStatus.ps1 to C:\Tools

   1. The location doesn’t need to be C:\Tools and could be anywhere on the server

2. In the CM Console click Administration from the Wonder Bar

3. Expand Site Configuration --> Click Sites

4. Click Status Filter Rules from the Ribbon

5. Click the Create button

6. Give the filter rule a name (e.g. Get Software Update Compliance Information)

7. Check Component

8. Select SMS_WSUS_SYNC_MANAGER

9. Check Message ID

10. Enter 6702

11. Click Next

12. (Optional) Check Report to the event log

13. Check Run a program

14. Enter C:\Windows\system32\WindowsPowerShell\v1.0\powershell.exe -file "C:\Tools\Get-SoftwareUpdateStatus.ps1" –noprofile

    1. Change the location of the file if you stored it somewhere else on the server

    2. Modify the file and change the DaysScanned value as needed

15. Click Next

16. Click Close

Upload the RDL File

1. Upload the RDL file to the SSRS server.

   1. The rdl file could be uploaded anywhere however, it’s recommended to place it in the Sofware Updates Compliance folder describe in my previous blog post

2. Modify the report to include your datasource.  You will need to at least modify the connection string with your SQL Server that is hosting the Software Updates Compliance database.

Software Updates Compliance - Compare Compliance.zip

I created this blog due to the responses I’ve received from my previous blog (https://blogs.technet.com/b/gary_simmons_mcs/archive/2013/12/09/creating-a-custom-report-for-system-center-2012-r2-configuration-manager-part-1.aspx) on creating custom SSRS dashboard for Configuration Manager.  I used a Software Update dashboard just as an example but it seems there is a lot of interest in Software Update dashboards.

Reporting on Software Updates can be tricky because depending on the organization different people or groups may want to see numbers in different ways.  Executives or Senior Management may just want to know if they are “good” and look at percentages while mid-level management may want to know what part of their enterprise is good.  Security groups tend to want to know what updates are missing while looking at trending data, System Administrators want to know what systems are missing updates and CM Administrator’s what to know how the updates are being managed.

The default Software Update reports are based off of Software Update Groups (SUG) and collections that need to be managed.  It’s good for the System\CM Administrators but usually requires someone creating custom charts either in Excel or PowerPoint to brief on the Software Update posture to security or management. Additionally, they don’t give a quick timeline view on when updates were released or allow for trend analysis.

This blog describes a Software Update Compliance dashboard with Security in mind.  It is formatted in a way that should appease management while giving detailed information to administrators managing the systems or deployments.  It doesn’t rely on SUG’s, collections, or unmanaged systems and allows CM Administrators to deploy updates however they choose.

Software Update Compliance Dashboard – Part 2

The Software Update Compliance dashboard is broken into three main sections; Assets, Software Update Information, and Compliance separated between servers and workstations.

By default, the dashboard displays information for each operating system within a 12 month period starting from the month the report was run on.  You can change the default behavior by modifying the @StartDate or just change the Start Date after the report has run.

Each report allows the type (Category) of update to be filtered on.  By default, each report has Security Updates defined.  You can change the default behavior by modifying the @Category parameter.

The software update information is gathered from each managed system.  A managed system is defined as a non-obsolete client that has performed its software update scan within the last 14 days.  The number of days is defined with the @DaysScanned parameter.

A couple things to note are the exclusions of Windows XP, Vista, and Windows 8. The results seen in this dashboard include all applicable updates for the devices.  There isn't a method to include or exclude specific updates to the report.

Section 1 – Assets

The top of the dashboard sets the stage for each chart as it displays the number of systems that are being reported on for each operating system.

It is very important to understand that unmanaged systems will not be reflected in the dashboard.  All compliance and applicable data seen in the dashboard is derived from the v_Update_ComplianceStatus view from systems that have performed a successful scan within the defined parameter.

This means that all the system objects that can be seen in the Configuration Manager console aren’t being reported on since it is very common to have outdated information in the CM Database.

The Operating System value is pulled from Operating_System_Name_and0 column in the v_r_system view.  This information is populated from AD discovery so the dashboard isn’t dependent on hardware inventory to complete.  The issue with the Operating_System_Name_and0 view is that it isn’t a friendly name for non-technical people so it is translated in each SQL query.  This means that “Microsoft Windows NT Workstation 6.3 (Tablet Edition)” and “Microsoft Windows NT Workstation 6.3” are converted to “Windows 8.1”.  Also “Microsoft Windows NT Server 6.3” and “Microsoft Windows NT Advanced Server 6.3” are converted to “Windows Server 2012 R2” since the applicable patches are the same and it just makes it easier to understand.

In the Assets section it is possible to click Servers or Workstations to drill down into the systems that make up the numbers.

Section 2 – Software Update Information

The Software Update Information section shows the number of applicable software updates that were released or revised during the 12 month reporting period.  It also shows the compliance for updates released that month.
Each chart has a link to a sub report that will display more detailed software update information.

Section 3 – Compliance

This section is separated between Servers and Workstations with four different charts; Overall Compliance, Systems missing a certain amount of updates, Operating System Compliance, and Operating Systems missing at least 1 update.

The Servers link will run a sub report showing more detailed information regarding server operating systems.

Sub Reports - Part 3

The Software Update Compliance dashboard contains links to sub reports that allow you to drill down into specific information.

The orange arrows indicate the path in which the sub reports are linked.

Assets

The Software Update Compliance – Assets sub report displays the systems where the Last Software Update scan falls within the managed parameter @DaysScanned.

Software Update Information

The Software Update Compliance – Software Update Information sub report shows information pertaining to software updates that are applicable to managed systems within a period of time, operating system, and type of Software Update.

System Information

The Software Update Compliance – System Information sub report shows information on each managed system.  The report can be filtered within a period of time, by operating system, and by the type of software update.

I've attached a zip file containing 4 .rdl files to this blog.  To install the dashboard create a folder in the SSRS home page called Software Updates Compliance and place each .rdl file in it.  Modify each report with your data source.  For each sub report right click the text box with the hyperlink then select Text Box Properties. 

Click Action then change the link to the report to  have your site code in it.  for example, Change /ConfigMgr_SIM/Software Updates - A Compliance/Compliance 5 - Specific computer to /ConfigMgr_SI1/Software Updates - A Compliance/Compliance 5 - Specific computer

If you place the .rdl files anywhere else you'll need to change the link locations for the sub reports.

This dashboard is still being developed so if you plan on using it make sure to validate the accuracy of it in your environment. I have not tested updates imported with System Center Updates Publisher however, it should work with those updates.

When time permits, I plan on updating the dashboard to allow each bar in the charts clickable to a sub report.  I also plan on capturing the data to a separate database to allow for trend analysis or comparisons between different time periods.

Updates
28 Jan 2015 - v1.1

• Updates to the Dashboard

  • Most Column charts are clickable and link to a sub report

• System Information

  • Added parameter for the group of missing updates

  • Added a Filter to limit the results based on a computer name

  • Modified the dataset to display systems that didn’t have a top user

  • Modified the Chassis column to display the chassis number

  • Changed Chassis type 3 from Server to Desktop

  • Modified the dataset to correctly display if a system is a VM

• Assets

  • Added a Filter to limit the results based on a computer name

 5 Aug 2015 - v1.2

• Added support for Windows 10
• Removed support for Server 2003
• Included Version number in footer

Software Updates Compliance v1.2.zip

DECLARE @StartDate datetime, @EndDate datetime

Set @StartDate = CAST(@StartMonth as varchar) + '/1/' + CAST(@StartYear as varchar)

Set @EndDate = CAST(@EndMonth as varchar) + '/1/' + CAST(@EndYear as varchar)

Set @EndDate = DATEADD(s,-1,DATEADD(mm, DATEDIFF(m,0,@EndDate)+1,0))

Select distinct ucs.ci_id, count(ucs.status)[Count],

Ui.BulletinID, ui.ArticleID, ui.Title,

CASE(ui.IsSuperseded)

When 0 Then 'No' Else 'Yes' End as 'Superseded',

Ui.DatePosted,

CASE (ucs.status)

When 3 Then 'Installed' When 2 Then 'Required' Else 'Not Applicable' End as 'Status',

Case (ui.IsDeployed)

When 0 Then 'No' Else 'Yes' End as 'Deployed',

Case(ui.IsExpired)

When 0 Then 'No' Else 'Yes' End as 'Expired',

cica.CategoryInstanceName,

CASE(ui.Severity)

When 2 Then 'Low' When 6 Then 'Moderate' When 8 Then 'Important' When 10 Then 'Critical' Else 'NA' End as 'Severity'

From v_Update_ComplianceStatus ucs

JOIN v_FullCollectionMembership fcm on ucs.ResourceID = fcm.ResourceID

JOIN v_UpdateInfo ui on ui.CI_ID = ucs.CI_ID

JOIN v_CICategoryInfo_All cica JOIN v_CategoryInfo ci on cica.CategoryInstanceID = ci.CategoryInstanceID AND cica.CategoryTypeName = 'UpdateClassification' on ucs.CI_ID = cica.CI_ID

Where fcm.CollectionID = @ColID AND ui.DatePosted BETWEEN @StartDate AND @EndDate

Group by ucs.CI_ID, ucs.status, ui.BulletinID, ui.ArticleID, ui.Title, ui.DatePosted, ui.IsDeployed, ui.IsSuperseded, ui.IsExpired, cica.CategoryInstanceName, ui.Severity

Creating a Custom Report for System Center 2012 R2 Configuration Manager – Part 1
Creating a Custom Report for System Center 2012 R2 Configuration Manager – Part 2
Creating a Custom Report for System Center 2012 R2 Configuration Manager – Part 3
Creating a Custom Report for System Center 2012 R2 Configuration Manager – Part 4
Creating a Custom Report for System Center 2012 R2 Configuration Manager – Part 5

Software Updates Summary.rdl

If you have worked with the PowerShell Set-CMSiteMaintenanceTask and Get-CMSiteMaintenanceTask you most likely have already mapped the task name parameter to the actual task name. 

At this time the Get-CMSiteMaintenanceTask reference page on TechNet doesn’t list the Maintenance Task name however, you can reference the SMS_SCI_SQLTask Server WMI Class of the Configuration Manager SDK to get them.

For those that haven’t used the Set-CMSiteMaintenanceTask and Get-CMSiteMaintenanceTask you can use this table for the task names to save some time instead of figuring it out with a trial and error process.  I wouldn’t be surprised if these were changed in the future to use a common set of task names for each cmdlet.

Current Bugs

Currently, there are a couple of bugs with each cmdlet.  The Get-CMSiteMaintenanceTask doesn’t retrieve the BeginTime and LatestBeginTime properties.  The Set-CMSiteMaintenanceTask requires the –DeviceName argument set although it only applies to the BackupSiteServer.  You can set the argument to “ “ as a workaround to the bug. (e.g. –DeviceName “ “)

Getting  BeginTime and LatestBeginTime

To get the BeginTime and LatestBeginTime properties of a task you can query the SMS_SCI_SQLTask Server WMI Class then convert the DateTime value to a hh:mm string format.

This is a sample wmi query to get the Delete Obsolete Alerts tasks:

$MT =  gwmi -Namespace root\sms\site_<SiteCode> -Query "Select * from SMS_SCI_SQLTask Where SiteCode='<SiteCode>' and TaskName = 'Delete Obsolete Alerts'" -ComputerName <computername>
To output the begintime run($MT).BeginTime

When displaying either the BeginTime and LatestBeginTime properties it’ll be returned in a WMI datetime format such as 00000000050000.000000+*** however, when using the[System.Management.ManagementDateTimeConverter]::ToDateTime()method to convert it, it will throw an error.  One way of getting the hours and minutes needed is parse it as a string.  This function will take the datetime format and return an hh:mm string format.

Function Convert-WMITime{
     [CmdletBinding()] 
     Param(
     [Parameter(Mandatory=$true)]
     [Alias("WT")] [string]$CIMdatetime)
     return $CIMdatetime.Substring(8,2)+":"+$CIMdatetime.substring(10,2)
}

Getting the Days of Week

The DaysOfWeek for each task is stored as a UInt32 value however, the name of the days is represented as binary.  The name of the days are required for the Set-CMSiteMaintenanceTask cmdlet and is just easier to read. 

One method of getting the day names is to convert the decimal value to binary then iterate the binary bits to create an array of day names. 

This table can help visualize the tasks that need to be done.

Converting the decimal to binary can be used with the .Net Convert method.  Since we are working with up to 7 bits (one for each day of the week) it should be padded to the left and included 0’s for empty spaces.  For instance, Thursday is the decimal value of 16 and binary value of 10000.  Extra zero’s will be added to the left to ensure there are 7 values.  This will in turn become 0010000. 

$bDays = [Convert]::ToString($MT. DaysOfWeek,2).PadLeft(7,'0')

Match 0010000 with the above table, wherever the bit is set to 1 then add that day to an array.

$aDays = @()
$aDayNames =  @("Saturday", "Friday", "Thursday", "Wednesday", "Tuesday", "Monday", "Sunday")
$bDays = $bDays[0..$bDays.length]

for($i=0;$i -lt $bDays.Length;$i++){
     if($bDays[$i] -eq "1"){$aDays = $aDays + $($aDayNames[$i])}
{

This is a complete function that can be used to return the DaysOfWeek UInt32 value and return an array of day names:

Function Convert-DecimaltoDays{
     [CmdletBinding()] 
     Param(
     [Parameter(Mandatory=$true)]
     [Alias("D")]
     [string]$Days
     )
     $aDays = @()
     $aDayNames = @("Saturday", "Friday", "Thursday", "Wednesday", "Tuesday", "Monday", "Sunday")

     $bDays = [Convert]::ToString($Days,2).PadLeft(7,'0')
     $bDays = $bDays[0..$bDays.length]
     for($i=0;$i -lt $bDays.Length;$i++){
          if($bDays[$i] -eq "1"){$aDays = $aDays + $($aDayNames[$i])}
     }
     return $aDays
}

In Part 3 the dataset were created.  We’ll now take the data and place them into the tables and charts.

1. Click the Insert tab --> click Table --> Insert Table
2. Draw a table below the title

1. A default table with 3 columns will appear

• Hover over the bottom row of the first column
  and click the little notepad icon symbol that appears
• Select the Dataset --> Select Collection_Details --> Select Name
• Click Next
• Add Devices to the next column and the scanned_last_30_days to the last column
• Right click the top of the last column --> Select Insert Column --> Select Right
• Add Inventory_last_30_Days to the last column
• Right click the bottom row in the Devices column
• Select fx Expression
• Change the expression from =Fields!Devices.Value to =SUM(Fields!Devices.Value)
• Repeat this step for the Scanned_last_30_Days
  and Inventory_last_30_Days column
• Right click the bottom row of any column

1. Notice the orange bracket in the first column

• Select Row Group --> Delete Group
• Select Delete group only--> Click OK
  1. This disables the looping ability of the table and the orange bracket will disappear

The table should look like this:

Press F5 to run the report to see if it is working properly

1. Create another table and place it under the one just created
2. Right click the bottom row of any column
3. Select Row Group --> Delete Group
4. Select Delete group only --> Click OK
5. Hover over the bottom row of the first column and click the little notepad icon symbol that appears
6. Select the Dataset-> Software_Update_Details -->  Title
7. Hover over the bottom row of the second column and click the little notepad icon symbol that appears
8. Select Software_Update_Details --> Status
9. Hover over the bottom row of the third column and click the little notepad icon symbol that appears
10. Select Software_Update_Details --> Status
11. Create a new column
12. Hover over the bottom row of the forth column and click the little notepad icon symbol that appears
13. Select Software_Update_Details --> Deployed
14. Hover over the bottom row of the forth column and click the little notepad icon symbol that appears
15. Create a new column
16. Select Software_Update_Details --> Deployed
17. Right click the last row in the first column -->  Select fx Expression
18. Change the expression to =Count(Fields!Title.Value)
19. Right click the last row in the second column --> Select fx Expression
20. Change the Expression to =SUM(IIF(Fields!Status.Value = "Required",1,0))
21. Right click the last row in the third column --> Select fx Expression
22. Change the expression to =SUM(IIF(Fields!Status.Value = "Installed",1,0))
23. Right click the last row in the fourth column --> Select fx Expression
24. Change the expression to =Sum(IIF(Fields!Deployed.Value = "Yes", 1, 0))
25. Right click the last row in the fifth column --> Select fx Expression
26. Change the expression to =Sum(IIF(Fields!Deployed.Value = "No", 1, 0))

The table should look like this:

Press F5 to run the report to see if it is working properly

Creating the Operating System Pie Chart

1. Click the Insert tab --> Click Chart --> Chart Wizard
   1. The New Chart window will appear
2. Select the All_OperatingSystems dataset
3. Click Next
4. Select the Pie Chart
5. Click Next
6. Place Operating_System in the Series
7. Place Number_of_Systems in Values
8. Click Next
9. Select the Ocean style
10. Click Finish
11. Right click the Pie chart --> Select Show Data Labels
12. Rename the Chart Title to Operating Systems

Press F5 to run the report to see if it is working properly

Creating the Line Chart

1. Click the Insert tab --> Click Chart --> Chart Wizard
   1. The New Chart window will appear
2. Select the Software_Update_Details dataset
3. Click Next
4. Click the Line Chart
5. Click Next
6. Add Count(DatePosted) in Values
7. Add Status in Series
8. Add DatePosted in Categories
9. Click Next
10. Select the Ocean style
11. Click Finish
12. Right click the chart --> Select Show Data Labels
13. Click off the chart then right click it again
    1. The Chart Data Properties should appear next to it
14. Under Category groups right click DatePosted
15. Select Category Group Properties…
16. Click the Fx button for the Label
17. Change the Expression to =Format(Fields!DatePosted.Value, "MMM yy")
18. Click OK
19. Click the fx button for the group
20. Change the Expression to =MonthName(Month(Fields!DatePosted.Value))

Press F5 to run the report to see if it is working properly

To make the Required line red follow these steps:

1. Click the View tab
2. Select Properties
3. Click off then back on to the chart
4. In the properties pane under Chart look for CustomPaletteColors
5. Click the … button for the CustomPaletteColors collection
   

6. Change the color in row #1 (it starts at 0) to Red

Press F5 to run the report to see if it is working properly

Creating the Severity Chart

1. Click the Insert tab --> Click Chart --> Chart Wizard
   1. The New Chart window will appear
2. Select the Software_Update_Details dataset
3. Click Next
4. Click the Column Chart
5. Click Next
6. Add Status in Series
7. Add Severity in Categories
8. Add Count(Severity) in Values
9. Click Next
10. Select the Ocean style
11. Click Finish
12. Right click the chart --> Select Show Data Labels

Creating the Category Chart

1. Click the Insert tab --> Click Chart --> Chart Wizard
   1. The New Chart window will appear
2. Select the Software_Update_Details dataset
3. Click Next
4. Click the Column Chart
5. Click Next
6. Add Status in Series
7. Add Count(CategoryInstanceName) in Values
8. Add CategoryInstanceName in Categories
9. Click Next
10. Select the Ocean style
11. Click Finish
12. Right click the chart -->Select Show Data Labels

Creating the Software Update Table

Adding in the list of all applicable updates doesn’t fit in with the concept of a dashboard but it is good information to see.

1. Create another table and place it under the charts
2. Hover over the bottom row of the first column and click the little notepad icon symbol that appears
3. Select the Dataset --> Software_Update_Details --> Count
4. Continue to add in the columns for each field returned from the dataset

To add sorting to the columns follow these steps:

1. Right click a column header --> Select Text Box Properties…

1. The Text Box Properties window will appear

• Select Interactive Sorting
• Check Enable interactive sorting on this text box
• Select the column to be sorted in the Sort by selection
• Repeat this for each column you want to allow sorting on

Press F5 to run the report to see if it is working properly

You should now have a dashboard to give you a quick view of overall software update status.  Although you may not use this dashboard in its entirety, you can create your own custom queries to satisfy your own requirements and gain more out of one the most powerful but underused  features of ConfigMgr 2012.

I purposely didn't update the top right text box.  Based on the steps within this demonstration, see if you can have it display the start month, start year, end month and end year.

Creating a Custom Report for System Center 2012 R2 Configuration Manager – Part 1
Creating a Custom Report for System Center 2012 R2 Configuration Manager – Part 2
Creating a Custom Report for System Center 2012 R2 Configuration Manager – Part 3
Creating a Custom Report for System Center 2012 R2 Configuration Manager – Part 4
Creating a Custom Report for System Center 2012 R2 Configuration Manager – Part 5

For the Collection parameter, the dashboard will display the collections name but will pass its Unique ID to the datasets in a variable called ColID. 

To create this parameter, a dataset needs to be created.  To create the dataset, a data source is required.

Creating the Data Source

1. In the Report Data pane right click Data Sources--> Click Add Data Source
   1. The Data Source Properties window will appear
2. Change the Name to CM
3. Select Use a connection embedded in my report
4. Select Microsoft SQL Server as the connection type
5. Click the Build… button
6. Enter the Server name to the SQL server
7. Select the ConfigMgr database
8. Click Test Connection to ensure that a connection could be established
9. Click OK
10. Click OK

Creating the All_Collections Data Set

1. In the Report Data pane right click Datasets --> Click Add Dataset
   1. The Dataset Properties window will appear
2. Change the Name to All_Collections
3. Select Use a dataset embedded in my report
4. Select the CM Data source
5. In the Query box enter the following:
    select distinct c.CollectionID, c.Name from v_Collection c order by c.Name
6. Click OK

Creating the ColID Parameter 

1. In the Report Data pane right click the Parameters folder --> Click Add Parameter.
   1. The Report Parameter Properties window will appear
2. Change the Name to ColID (this is spelled colid)
3. Change the prompt to Select a collection
4. Click Available Values
5. Select Get values from a query from the dataset
6. Select CollectionID for the Value field
7. Select Name for the Label field
8. Click Default Values
9. Select Specify values
10. Click the Add button
11. Enter SMS00001 for the Value
    1. This is the Collection ID for the All Systems collection.
12. Click OK

Your Report data pane should look like this:

Creating the other parameters

Month Parameters

Although it is possible to create datasets for the other parameters, this demonstration will use static entries.

1. In the Report Data pane right click the
   Parameters folder --> Click Add Parameter.

1. The Report Parameter Properties window will appear

• Change the Name to StartMonth
• Change the prompt to Select a month that the report will start from
• Change the Data type to Integer
• Click Available Values
• Select Specify values
• Click the Add button 12 times
• Enter January for the Label and 1 for the Value
• Repeat this until you have December for the Label and 12 for the Value
• Click Default Values
• Select Specify values
• Click the Add button
• Click the fx button

1. The Expression window will appear

• Enter =Month(today()) for the expression value

1. This will get the number value of the month for day the report is run

• Click OK
• Click OK 

Repeat these steps for the EndMonth parameter with the prompt of Select a month the report will end with

Year Parameters

Similar to the Month parameter the dashboard will create static year parameters with the starting year having a slight twist to its default value.

1. In the Report Data pane right click the Parameters folder --> Click Add Parameter.

1. The Report Parameter Properties window will appear

• Change the Name to StartYear
• Change the prompt to Select a year that the report will start from
• Change the Data type to Integer
• Click Available Values
• Select Specify values
• Click the Add button 10 times
• Enter 2004 for both the Label and Value
• Repeat this until you have 2014for both the Label and Value

1. You may add or remove in more entries if you want to report update older or newer than 2004

• Click Default Values
• Select Specify values
• Click the Add button
• Click the fx button

1. The Expression window will appear

• Enter =Year(today()) -1 to default the report to the year previous to when it is run
• Click OK
• Click OK

Repeat these steps for the EndYear parameter with the prompt of Select a year that the report will end with and a default value of =Year(today())

Your Report Data pane should now look like this:

Creating Other Datasets

1. Similar to how the All_Collections dataset was created, create the All_OperatingSystems Dataset with the query of:
   select distinct c.Name [Collection Name], gsos.Caption0 [Operating System], count(gsos.Caption0) [Number of Systems]
   from v_R_System rs
   JOIN v_FullCollectionMembership fcm on rs.ResourceID = fcm.ResourceID
   JOIN v_Collection c on c.CollectionID = fcm.CollectionID
   JOIN v_GS_OPERATING_SYSTEM gsos on gsos.ResourceID = fcm.ResourceID
   WHERE c.CollectionID = @ColID
   group by c.Name, fcm.collectionID, gsos.Caption0
2. Create another Dataset called Collection_Details with the query of:
   select distinct c.Name, count(rs.ResourceID) [Devices], (Select Count(LastScanTime) from v_UpdateScanStatus uss where datediff("d",LastScanTime, getdate()) <= 30) [Scanned last 30 Days],(Select Count(LastHWScan) from v_GS_WORKSTATION_STATUS gsws where datediff("d",LastHWScan, getdate()) <= 30) [Inventory last 30 Days]
   from v_FullCollectionMembership fcm
   JOIN v_Collection c on c.CollectionID = fcm.CollectionID
   JOIN v_R_System rs on rs.ResourceID = fcm.ResourceID
   LEFT JOIN v_GS_WORKSTATION_STATUS gsws on gsws.ResourceID = fcm.ResourceID
   where fcm.CollectionID = @ColID
   group by  c.Name
3. Create the final dataset called Software_Update_Details with the query of:
   DECLARE @StartDate datetime, @EndDate datetime
   Set @StartDate = DATEFROMPARTS(@StartYear,@StartMonth,1)
   Set @EndDate = DATEFROMPARTS(@EndYear,@EndMonth,1)
   Select ucs.CI_ID, count(ucs.CI_ID) [Count],
   CASE((status))
   When 3 Then 'Installed' When 2 Then 'Required' Else 'Not Applicable' End as 'Status', BulletinID, ArticleID,
   CASE((IsDeployed))
   When 0 Then 'No' Else 'Yes' End as 'Deployed',
   CASE((ui.IsSuperseded))
   When 0 Then 'No' Else 'Yes' End as 'Superseded',
   CASE((ui.IsExpired))
   When 0 Then 'No' Else 'Yes' End as 'Expired',
   ui.Title, ui.DatePosted, cica.CategoryInstanceName,
   CASE((ui.Severity))
   When 2 Then 'Low'
   When 6 Then 'Moderate'
   When 8 Then 'Important'
   When 10 Then 'Critical'
   Else 'NA' End as 'Severity'
   From v_Update_ComplianceStatusReported ucs
   JOIN v_UpdateInfo ui on ucs.CI_ID = ui.CI_ID
   JOIN v_CICategoryInfo_All cica JOIN v_CategoryInfo ci on cica.CategoryInstanceID = ci.CategoryInstanceID AND cica.CategoryTypeName = 'UpdateClassification' on ucs.CI_ID = cica.CI_ID
   Where resourceid IN(Select ResourceID from v_FullCollectionMembership where CollectionID = @ColID) AND ui.DatePosted BETWEEN @StartDate AND @EndDate AND ucs.status <> 1
   GROUP BY ucs.CI_ID, ucs.status, BulletinID, ArticleID, IsDeployed, ui.Title, DatePosted, cica.CategoryInstanceName, cica.CategoryInstanceID,ui.IsSuperseded, ui.Severity, ui.IsExpired
   ORDER BY ucs.status, BulletinID, ArticleID

Your Report Data pane should now look like this:

Creating a Custom Report for System Center 2012 R2 Configuration Manager – Part 1
Creating a Custom Report for System Center 2012 R2 Configuration Manager – Part 2
Creating a Custom Report for System Center 2012 R2 Configuration Manager – Part 3
Creating a Custom Report for System Center 2012 R2 Configuration Manager – Part 4
Creating a Custom Report for System Center 2012 R2 Configuration Manager – Part 5

Ensure you can browse to both the Reports (e.g. https://<ConfigMgr>/Reports) and ReportServer (e.g. https://<ConfigMgr>/ReportServer) web pages on your server hosting SQL Reporting services.

Launch Report Builder 3.0 elevated (“Run as Administrator”) using and an account that has admin credentials to both the SQL server and ConfigMgr.  Although the account doesn’t need to be an administrator, for simplicity sake an admin account will be used in this demonstration.

Close the Getting Started screen.  On the left hand pane there are 5 folders to get familiar with.  If you don’t see the pane click the view tab then check Report Data.

• The Built-in Fields won’t be used
• The Parameters are variables that will be passed to the Datasets
• The images will contain the system center logo
• The Data Sources is the connection to the ConfigMgr database
• The Datasets are the SQL queries

For more information view the Report Data Pane on Technet.

1. Let’s start with the layout first.  Select the View tab then check  Properties. Click the center of the report then change the size in the Properties pane to 12.7in, 9.48in or your own custom size.
2. Click the line in for the title text box.  In the Properties pane change the Location to 1in, 0in and the Size to 4.15in, 1in. Click the Home tab then change the font to Calibri 20 Bold. Click inside the Textbox and enter Software Updates Dashboard. 
3. Click the Insert tab then click Text Box. Draw a textbox next to the Software Updates Dashboard textbox to the edge of the report.  Click the border of the textbox and change the size to 7.37833in, 1in and the location to 5.32167in, 0in. You may need to adjust the width to ensure it  isn’t off the report.  When resizing the textbox it should snap to the edge.
4. Within the Insert tab click Image.  Draw the image in the upper left hand corner.  When the Image Properties box appears, click the Import button then select an image.
5. The top of your report should look like this:
   
6. Scroll to the bottom of the report and delete the textbox with the Execution Time.

You should now have a basic layout for your dashboard and can change it to meet your needs.   

To view what the report will look like press F5 or click the Run button in the Home tab.

Creating a Custom Report for System Center 2012 R2 Configuration Manager – Part 1
Creating a Custom Report for System Center 2012 R2 Configuration Manager – Part 2
Creating a Custom Report for System Center 2012 R2 Configuration Manager – Part 3
Creating a Custom Report for System Center 2012 R2 Configuration Manager – Part 4
Creating a Custom Report for System Center 2012 R2 Configuration Manager – Part 5

For a practical demonstration, a dashboard for software updates will be created that uses tables, a pie chart, a line chart, and a column chart.

The built in reports for software updates contain a large quantity of information however, there isn’t a dashboard to provide a quick overview of update status.  In its given state, you would have to drill down into multiple reports, export the data, and then manipulate it in a spreadsheet to present it in a dashboard form.  It is possible to run SQL queries from within Excel or PowerPoint to display a dashboard but that’s beyond the scope of this blog.

Since there are so many different angles to display software update statuses, this dashboard will contain a query that will display data based on the v_Update_ComplianceStatusReported view.  This view contains the status of each software update for each system that has successfully performed a scan. It is important to note this as if you want a query based off a list of updates (software update groups) or a success rate to include inactive systems then this dashboard won’t work for you although you could use the examples and create your own dashboard.

The v_Update_ComplianceStatusReported view contains a column called “Status” to indicate if an update is Installed, Required, or Not Applicable.  Since we are only concerned about installed or required updates, the not applicable status will be filtered out and significantly reduce the number of data queried on.

The dashboard will allow filtering by collection and a duration (a start date and an end date) to display the following:

• A table with the collection name, number of devices, number of devices that performed a software update scan in the last 30 days, number of systems that performed a hardware inventory in the last 30 days
• A table that displays each required or installed update with the number of applicable systems, the article ID, the Bulletin ID, the Title, whether it is superseded, the Date the update was posted, whether it is deployed or not, the category, and the severity of the update.
• A Pie chart that displays each inventoried operating system
• A Line chart that displays the number of required and installed updates by month (or every couple months to fit in the graph)
• A table with the total number of updates, the count or required updates, the count of installed updates, the count of deployed updates, and the count of updates not deployed
• A Column chart that displays the number of updates installed or required by severity
• A Column chart that displays the number of updates installed or required by category

This screenshot is what the dashboard will look like

Creating a Custom Report for System Center 2012 R2 Configuration Manager – Part 1
Creating a Custom Report for System Center 2012 R2 Configuration Manager – Part 2
Creating a Custom Report for System Center 2012 R2 Configuration Manager – Part 3
Creating a Custom Report for System Center 2012 R2 Configuration Manager – Part 4
Creating a Custom Report for System Center 2012 R2 Configuration Manager – Part 5