Mastering Configuration Manager Patch Compliance Reporting

Published May 25 2020 04:45 AM 34.5K Views
Microsoft

Hi, Jonas here!

Or as we say in the north of Germany: "Moin Moin!"
I am a Microsoft Customer Engineer (CE formerly known as PFE) and a while back (years in fact) I was asked to analyze the update compliance status of a SCCM/ConfigMgr/MECM environment. I will use the current name: "Microsoft Endpoint Configuration Manager" (MECM) in the rest of the blog.
I used different reports to look for clients not installing the necessary updates, but it was time consuming and I was missing a general overview with some meaningful KPIs. I ended up with a comprehensive SQL query and an Excel sheet, but changed that to a SQL Server Reporting Services (SSRS) report. I than made that available to several departments in the organization.
As mentioned before, it's been a while since I created the report. If I were to start now it would be a PowerBI version or I would simply grab one of the PowerBI reports available from the MECM community. But since I still use the report and find it quite helpful, I decided to share that with the rest of the world.

 

Updated version

I recently updated the whole solution and changed it significantly. I added descriptive text to each column header, added ~400 common WSUS errors and changed the overall compliance criteria for example. I also updated this blog to reflect those changes. So, if you read it before, you might need to read it again ;)
(Use the table of contents to jump to the summary of changes directly if you want)

 

Table of contents:

TR:DR
The report explained
1st sub-reports (list of systems)
2nd sub-report (per system)

3rd sub-report (errorlist)

4th sub-report (deployments per system)

5th sub-Report (updates approved)
Some key facts and prerequisites:
How to install
Script Parameters
Script Examples

Activate report data caching
Additional report
Disclaimer
Resources
Changes

 

TL;DR

The following report should help you identify update problems within a specific collection and a group of systems and is designed to work well for a few thousand clients. The query might run longer in bigger environments and you might need to improve it or run it not within business hours to show results.
The installation guide for the custom update reporting can be found at the end of this post but you should at least start with the "Some key facts and prerequisites" section.
If you're just looking for the SQL statement behind the report, copy the query from the "UpdatesSummary.sql" file and use it in SQL directly.
The whole solution can be found on GitHub: https://github.com/jonasatgit/updatereporting
Feel free to improve the SQL queries or some of the reports on Github.
If you are a Premier customer and if you are looking for a more complete reporting solution, ask your Microsoft contact about the following offerings:
"Microsoft Endpoint Configuration Manager: Advanced Dashboards"
"Microsoft Endpoint Manager: PowerBI Dashboard Integration"

"Modern Workplace Compliance Reporting"

 

The report explained:

The main report dashboard looks like this:

Figure 1: Main update compliance dashboardFigure 1: Main update compliance dashboard

 

I used different KPIs to measure update compliance and the report combines all that into one dashboard. The main KPI is the first bar and all the others should simply help identify patch problems or flaws in your deployment strategy.

The report also has five sub-reports. One to show you a list of systems in a specific state (1st sub-report). One for a list of missing updates for a single system (2nd sub-report).  One sub-report (3rd sub-report) to show you a list of update installation errors or WSUS scan errors. One sub-report for all update deployment-states per system (deployments per system) and the last report (Updates Approved) shows you the NOT deployed / approved updates a system is still missing.

Figure 2: Simplified view of report dependenciesFigure 2: Simplified view of report dependencies

 

1st sub-reports (list of systems)

Almost each bar or pie chart links to a sub-report to show compliance state of that subset of systems to give you better visibility. This is an example of all the uncompliant systems from the first bar in the dashboard and is basically what the Excel list looked like in the early days:

Figure 3: List of all uncompliant systemsFigure 3: List of all uncompliant systems

If you click on different bar or pie charts, the same sub-report will be opened, but the data will be filtered depending on which bar or pie chart you clicked.

 

2nd sub-report (per system)

If you click on a system name a system specific report will open. The list of updates of that report will be filtered for the specific need. For example, if you click on “missing updates approved” just the approved and missing updates will be visible. The report also shows installations errors if any happened. Each error will link to a Bing search with the hex value of the error. The search string looks like this: https://www.bing.com/search?q=error+0x80070005
The report is basically a copy of one of the default MECM reports with some adjustments and some custom filters to filter for “Deployed and missing updates”, “Not deployed but missing”, "Missing updates with errors", “All missing updates deployed or not” or just “All updates per device.

It also contains update collections and maintenance windows to help identify missing or wrong collection memberships:

Figure 4: Per device update compliance reportFigure 4: Per device update compliance report

 

3rd sub-report (errorlist)

If you either click on the “WSUS-Scan Error” or “Systems with install error” bar a list with errors will be visible as shown in the screenshot below:

Figure 5: List of WSUS scan errorsFigure 5: List of WSUS scan errors

The report contains around 400 possible WSUS errors, tips and links to give you a troubleshooting starting point. It might not be a complete list, but it should cover the most common errors.

 

4th sub-report (deployments per system)

The fourth sub-report is a simple list of update deployments and their state and some other useful information per system. 

It can be either be opened directly or if you click on the "Deployments non compliant" row of the first sub-report.

Figure 6: Update deployment-states per deviceFigure 6: Update deployment-states per device

 

5th sub-report (updates approved)

If you click on the yellow “Updates Approved” bar a report shows you all the updates the selected systems are still missing, which are NOT yet approved / deployed.

The report should help identify problems with the selection of updates in your deployments.

Figure 7: Report of missing updates not yet approvedFigure 7: Report of missing updates not yet approved

 

Some key facts and prerequisites:

  • The report is made to show the update compliance status of members of a collection or multiple collections no matter what type of systems are a member or which or how many updates are deployed to each individual system. So, it can be a combined view over multiple deployments and not just one deployment.
  • The report combines multiple deployments into one single view.
    If you have a simple group of systems and deploy every necessary update with one deployment, the deployment status might be enough, but if you have a more complex setup, you might want to see details based on a specific group of systems no matter if, how or how many updates are deployed to each system.
  • I have defined "compliant" to be a system which has:
    • all enabled update deployments set to compliant (see changes down below. Column: "Deployments Non Compliant")
    • the last security update installation in Win32_Quickfixengineering was in the current month (or the monthly security rollup. Column: "Month Since Last Update Install")
    • The last or current security rollup is installed (see changes down below. Column: "Last Rollup Status")
  • The report will all updates no matter if deployed as "available" or "required".
  • The report consists of multiple KPIs to indicate the update compliance or update/client health state and should give you an overview from different viewpoints to help identify problematic systems or a flaw in your patch strategy.
  • The report will use data from WMI class Win32_QuickFixEngineering which needs to be enabled in the hardware inventory client settings. The class is only used to determine the latest or last cumulative update or A security update installation to identify systems which seem to be fine but actually have never installed anything.
  • The report is also uses LastLogonTimeStamp from AD System Discovery to visually show systems which have not logged on to the domain in a while and which might be disposed of already and could be deleted from the MECM database. If you don't use AD system discovery the report will show all systems of the specified collection as not compliant in the pie chart "Last ADDS logon" .
    • AD system discovery is no hard requirement to run the report
  • The report does not show historical data and will always show the current status. So, if you change a deployment in the middle of the month, the compliance percentage will drop almost immediately as it does with the deployment in MECM.
  • The report has multiple sub-reports to drill further down and almost each report will use the same dataset
    • Read more about data caching down below
  • The SQL query of the dataset is made to filter out Defender Update Deployments, because they normally will be changed every x hours and could interfere with the overall compliance state and should be monitored with other reports.
    You can change that via the available report parameters.  
  • The 2nd Level sub-report per system will also show Defender updates, even if they are filtered out on the dashboard
  • The SQL query might run longer in bigger environments depending on SQL performance and SQL maintenance. In some cases one of the “ForceLegacyCardinality” parameters can help to speed up the queries. (See parameter description down below)
  • There are several sub-reports with the same look and feel, because it was simpler to copy the report and just change the filter for the specific need.
  • Most sub-reports will be hidden in SSRS to avoid direct use and keep the folder as clean as possible.
  • The reports are made on SSRS 2017 but can be converted to the older format using the "ForceLegacyFormat" parameter.
  • The reports can be used on PowerBI Reporting Services if you upload them manually. Start with the “rsd” files from the “work” folder to avoid any errors. 

 

How to install:

  1. In case you used an older version of the solution before, delete and re-create the report folder in SSRS (or create a new one) and run the latest script again.
  2. Make sure you have Win32_Quickfixengineering enabled in the client settings for hardware inventory
  3. You could also use AD System Discovery to have further data, but that's no hard requirement.
  4. Either clone the repository or download the whole content.
  5. Copy the whole content to the SQL Server Reporting Services Server (SSRS)
  6. Create a new folder on the report server website where the reports should be imported to.
    1. The folder should be under the normal MECM folder (normally called ConfigMgr_[SITECODE]), but it can also be at the root level of your Reporting Services Server. But keep in mind that report subscriptions are only visible in the MECM console, if the report, you have subscribed for, is below the normal MECM folder. The subscription will not be visible in the MECM console if the report was placed at the root level.
  7. Start a PowerShell session as admin.
    1. The user running PowerShell also needs to have admin rights on the SQL Reporting Services Server to upload the reports
  8. Change the directory to the folder were the import script "Import-SSRSReports.ps1" can be found.
  9. Start the script ".\Import-SSRSReports.ps1" with the appropriate parameters (see below or run “Get-Help .\Import-SSRSReports.ps1 -Full”)
    1. The script will copy each RDL and RSD file from the "Sourcefiles" folder to a new "work" folder in the same directory the script resides.
    2. The script will then simply replace some values with the parameter values you provided
    3. The script will then upload the datasets and the reports to the server and the folder you provided as parameters
    4. The files in the "work" folder will not be deleted and can be used as a backup or for manual uploads if necessary and will contain the data you provided as parameters to the script
    5. IMPORTANT: If you need to re-run the script, delete the SSRS website folder with all its content first an re-create the folder in SSRS. It is possible to overwrite the reports automatically, but I faced some issues with some settings not being overwritten as desired and I don't use that method anymore. That's why everything should be deleted first to avoid errors.

 

Script parameters:

Parameter

Required

Example value / Description

ReportServerURI

Yes

Value:
http://reportserver.domain.local/reportserver

 

Description:
The URL of the SQL Reporting Services Server.
Can be found in the MECM Console under "\Monitoring\Overview\Reporting" -> "Report Server" or in the "Report Server Configuration Manager" under "Web service URL"

TargetFolderPath

Yes

Value:
ConfigMgr_P11/Custom_UpdateReporting

 

Description:
The folder where the reports should be placed in. I created a folder called "Custom_UpdateReporting" below the default MECM reporting folder. My sitecode is P11, so the default folder is called "ConfigMgr_P11".
Like this for example: "ConfigMgr_P11/Custom_UpdateReporting"
IMPORTANT: Use '/' instead of '' because it's a website.

TargetDataSourcePath

Yes

Value:
ConfigMgr_P11/{5C6358F2-4BB6-4a1b-A16E-8D96795D8602}

 

Description:
The path should point to the default ConfigMgr/MECM data source.
In my case the Sitecode is P11 and the default data source is therefore in the folder "ConfigMgr_P11" and has the ID "{5C6358F2-4BB6-4a1b-A16E-8D96795D8602}"
The path with the default folder is required. Like this for example: "ConfigMgr_P11/{5C6358F2-4BB6-4a1b-A16E-8D96795D8602}"

IMPORTANT: Use '/' instead of '\' because it's a website.

DefaultCollectionID

No

Value:
SMS00001

 

Description:
The report can show data of a default collection when it will be run, so that you don't need to provide a collection name each time you run the report.
The default value is "SMS00001" which is the CollectionID of "All Systems", which might not be the best choice for bigger environments.

DefaultCollectionFilter

No

Value:

All%

 

Description:

The filter is used to find the collection you are interested in and the value needs to match the name of the collection you choose to be the default collection for the parameter "defaultCollection".
In my case "S%" or “Servers%” or "Servers of%" to get the "Servers of the environment" collection for example.

DoNotHideReports

No

Value:

'Software Updates Compliance - Overview','Compare Update Compliance'

 

Description:

Array of reports which should not be set to hidden. You should not use the parameter unless you really want more reports to be visible.

DoNotUpload

No

Description:

Switch parameter to not directly upload the reports to SRRS. That might be helpful if you do not have the rights to upload and need to give the files to another person for example. In that case, just use the report files in the work folder and upload them manually. (Was called "Upload" in the first script version)

ReportSourcePath

No

Value:
"C:\Temp\Reports"

 

Description:
The script will use the script root path to look for a folder called "Sourcefiles" and will copy all the report files from there. But you could also provide a different path where the script should look for a "Sourcefiles" folder

ForceLegacyFormat

No

Description:

Switch parameter to change the xml definition 
of each report to the older pre SSRS 

2016 format. That way the reports also 

work with SSRS 2014 for example.

ForceLegacyCardinalitySQL2016SP1AndHigher

No

Description:
Switch parameter to change some SQL queries to use legacy cardinality
(More information can be found in the sources list below)

IMPORTANT: Can only be used if the SQL Server hosting the MECM database is at least running SQL Server 2016 SP1.

ForceLegacyCardinalityOlderThanSQL2016SP1

NO

Description:
Switch parameter to change some SQL queries to use legacy cardinality.
More information can be found here.

IMPORTANT: Can only be used if the SQL Server hosting the MECM database is OLDER than 2016 SP1.

 

 

Script examples:

Get the full list of parameters by running:

 

Get-Help .\Import-SSRSReports.ps1 -Full

 

Upload all reports with the minimum required parameters

 

.\Import-SSRSReports.ps1 -ReportServerURI "http://reportserver.domain.local/reportserver" -TargetFolderPath "ConfigMgr_P11/Custom_UpdateReporting" -TargetDataSourcePath "ConfigMgr_P11/{5C6358F2-4BB6-4a1b-A16E-8D96795D8602}"

 

Upload all reports with the minimum required parameters and force legacy format

 

.\Import-SSRSReports.ps1 -ReportServerURI "http://reportserver.domain.local/reportserver" -TargetFolderPath "ConfigMgr_P11/Custom_UpdateReporting" -TargetDataSourcePath "ConfigMgr_P11/{5C6358F2-4BB6-4a1b-A16E-8D96795D8602}" -ForceLegacyFormat

 

Just change the report files and do not upload them

 

.\Import-SSRSReports.ps1 -ReportServerURI "http://reportserver.domain.local/reportserver" -TargetFolderPath "ConfigMgr_P11/Custom_UpdateReporting" -TargetDataSourcePath "ConfigMgr_P11/{5C6358F2-4BB6-4a1b-A16E-8D96795D8602}" -DoNotUpload

 

Upload all reports and change the default CollectionID and Collection-Filter

 

.\Import-SSRSReports.ps1 -ReportServerURI "http://reportserver.domain.local/reportserver" -TargetFolderPath "ConfigMgr_P11/Custom_UpdateReporting" -TargetDataSourcePath   "ConfigMgr_P11/{5C6358F2-4BB6-4a1b-A16E-8D96795D8602}" -DefaultCollectionID "P1100012" -DefaultCollectionFilter "All Servers of Contoso%"

 

Activate report data caching:

Activate report data caching to increase report render speed. As mentioned before almost every report retrieves data from the same dataset. By activating report data caching you can increase report render speed especially for the compliance sub-reports (like the first sub-report). 

First you need to show all hidden items of your report folder by clicking on "Tiles" and "Show hidden items".

Figure 8: Show hidden itemsFigure 8: Show hidden items

 

Choose the "UpdatesSummary" dataset and click on the three dots "..." and choose "Manage".

Click on "Caching" and "Cache copies of this dataset and use them when available" and "Apply".

Figure 9: Activate data source cachingFigure 9: Activate data source caching

 

Additional report:

Also, a while ago I created a report to compare the patch status of a maximum of six systems which will also be upload to your SSRS if you run the install script. It should just help to have a fast and simple way to spot differences.
The report has a filter to limit the amount of systems returned by name and you can choose a maximum of six systems to compare them. You could also choose to only view required updates to limit the view and complexity of the report.

Figure 10: Compare update compliance reportFigure 10: Compare update compliance report

 

I hope you like the report solution and I hope it is a good extension of what you are using right now. 

 

Stay safe and healthy!

 

Best regards

Jonas Ohmsen

Senior Customer Engineer - Microsoft Germany

 

Disclaimer:

This posting is provided "AS IS" with no warranties, and confers no rights

 

Resources:

Download the whole solution or clone the repository here:
https://github.com/jonasatgit/updatereporting

Other blogs:

https://aka.ms/JonasOhmsenBlogs

https://aka.ms/StefanRoellBlogs

Slow ConfigMgr console:

https://support.microsoft.com/en-us/help/3196320/sql-query-times-out-or-console-slow-on-certain-conf...

 

 

Changes:

(The version number can be found in the lower left corner of the dashboard. No version number means v1.0)

 

2021-07-02 v3.5:

  • Changed the overall compliance state from "all approved and missing updates" + "a security update installation happend within one month" to "All deployments are compliant" + "either the last or the current cumulative update is installed" + "a security update installation happend within one month" (based on Win32_QuickFixEngineering)
  • Added help text to all report column headers
  • Added Update install errors bar graph to dashboard (below WSUS scan errors)
  • Changed filter for top 10 systems on dashboard to be more accurate
  • Added top 10 update install errors to dashboard
  • Added new report with details about install errors and WSUS scan errors
    • Contains around 400 common windows update related errors with possible actions on how to fix them
  • Added new parameter to exclude deployments containing Microsoft Defender and System Center Endpoint Protection updates
    • Was previously part of the SQL query and not easily changeable nor visible to the report user
  • Removed Server 2008 specific parts
  • Added new filter to "per device" report called: "Missing updates with errors" and “All missing updates deployed or not”
  • Added more details about errors to "per device" report
  • Added update collection and maintenance window list to “per device” report
  • Added column: “Earliest Deadline” to “per device” report
  • Changed first sub-report name from “all uncompliant” to “compliance list”
  • Changed default sort order from "count of missing updates" to "month since last update install"
  • Changed "WSUS version" to "OS build version". Easier to determine actual OS version and patch level
  • Changed "Defender Pattern Version" to "Defender Pattern Age" to be able to spot systems with older pattern more easily
  • Added column "WSUS scan error" to system list
  • Added column count of "Updates with install error" to system list
  • Added column number of "Deployments non compliant" to system list
    • Helps to determine any problems with deployments when all updates are installed, but deployments are still marked as uncompliant
  • Added new report to list all update deployments and their states per device
  • Made "Per device" and “compliance list" report visible to be able to schedule subscriptions without the dashboard
  • Fixed several minor issues with each report
  • Changed SQL query for deployed updates to work better in larger environments
  • Changed import script to also handle SSRS folder path with spaces in it
  • Changed import script to delete existing contents of "work" folder from a previous run
  • Changed import script parameter name "Upload" to "DoNotUpload". Function is the same.
  • Removed import script parameter "UseViewForDataset". (To much work to keep the view consistent with regular query)
  • Added new import script parameters: "ForceLegacyCardinalitySQL2016SP1AndHigher" and "ForceLegacyCardinalityOlderThanSQL2016SP1" Read more about it here

2020-12-09 v2.1:

  • Fixed language and QFE problem
  • Added new parameter -ForceLegacyFormat,
  • Fixed minor issues and linked all reports to the per device sub-report

2020-11-03 v1.0:

  • Fixed wrong parameter name, updated repository with several fixes

 

 

36 Comments

Hi Jonas, impressive article and a great solution with a lot of useful information. Thanks for putting it together!

Thank you @jonasoh for the Awesome blogpost for the Community :cool:

I have Shared it on my Social media Channels ;)

 

Visitor

Hi Jonas,  
This is really helpful, however I am facing some errors when running the PS script - the definition of this report is not valid or supported by this version of Reporting Services

 

Any ideas?

Microsoft

Hi @MarkB35.

I only tested SSRS 2017, so it might not work with older versions. Which version you are running? Can you share the exact error message?

Download link for SSRS 2017: https://www.microsoft.com/en-us/download/details.aspx?id=55252 Just in case :)

Best regards

Jonas

Visitor

HI @jonasoh 

I managed to resolve this.

We was on SQL 2014, I updated to SQL 2017 and it now works.

Occasional Visitor

This looks very useful, but I am running into issues during installation.  I am receiving the error below for every RDL file that attempts to install.  Any help would be appreciated.


Uploading: UpdatesSummaryView.rsd...

'/1Patch_Compliance_Reports/UpdatesSummaryView' cannot be found. --->
Microsoft.ReportingServices.Diagnostics.Utilities.ItemNotFoundException: The item
'/1Patch_Compliance_Reports/UpdatesSummaryView' cannot be found.
at Microsoft.ReportingServices.Library.ReportingService2005Impl.GetProperties(String Item, Property[] Properties,
ItemNamespaceEnum itemNamespace, Property[]& Values)
at Microsoft.ReportingServices.WebServer.ReportingService2010.GetProperties(String ItemPath, Property[] Properties,
Property[]& Values)"
At E:\Reports\updatereporting-master\Import-SSRSReports.ps1:233 char:21
+ $Properties = $ReportServerConnection.GetProperties("$target ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : NotSpecified: (:) [], MethodInvocationException
+ FullyQualifiedErrorId : SoapException

The property 'Value' cannot be found on this object. Verify that the property exists and can be set.
At E:\Reports\updatereporting-master\Import-SSRSReports.ps1:235 char:21
+ $prop.Value = $true
+ ~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : InvalidOperation: (:) [], RuntimeException
+ FullyQualifiedErrorId : PropertyNotFound

Exception calling "SetProperties" with "2" argument(s): "System.Web.Services.Protocols.SoapException: The value for
parameter 'Properties' is not specified. It is either missing from the function call, or it is set to null. --->
Microsoft.ReportingServices.Diagnostics.Utilities.MissingParameterException: The value for parameter 'Properties' is
not specified. It is either missing from the function call, or it is set to null.
at Microsoft.ReportingServices.Library.ReportingService2005Impl.SetProperties(String Item, Property[] Properties,
Guid batchId)
at Microsoft.ReportingServices.Library.ReportingService2005Impl.SetProperties(String Item, Property[] Properties)
at Microsoft.ReportingServices.WebServer.ReportingService2010.SetProperties(String ItemPath, Property[] Properties)"
At E:\Reports\updatereporting-master\Import-SSRSReports.ps1:236 char:21
+ $ReportServerConnection.SetProperties("$targetPath/$reportNa ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : NotSpecified: (:) [], MethodInvocationException
+ FullyQualifiedErrorId : SoapException

Microsoft

Hi @riche10it which SSRS version you are using? I tested SSRS 2017 which will work with older SQL versions. 
Some reports should be set to hidden and that seems to be failing in your case. Those reports are only used as a sub-report for the dasboard and hiding them makes therefore sens. 
You can always try to upload the reports manually from the "work" folder by clicking the "upload" button in the SSRS folder you which to have the reports in. Make sure to upload the two ".rsd" files first. Hope this helps. 

Senior Member

Hi Jonas

thnx for this dashboard :)

Frequent Visitor

I am receiving the following error when trying to publish your report. Any guidance would be appreciated.

 

writeErrorStream : True
PSMessageDetails :
Exception : System.InvalidOperationException: The HTML document does not contain Web service discovery
information.
at System.Web.Services.Discovery.DiscoveryClientProtocol.DiscoverAny(String url)
at Microsoft.PowerShell.Commands.NewWebServiceProxy.GenerateWebServiceProxyAssembly(String
NameSpace, String ClassName)
TargetObject : http://servername/reports/ReportService2010.asmx?wsdl
CategoryInfo : InvalidOperation: (http://servername...e2010.asmx?wsdl:Uri) [New-WebServiceProxy],
InvalidOperationException
FullyQualifiedErrorId : InvalidOperationException,Microsoft.PowerShell.Commands.NewWebServiceProxy
ErrorDetails :
InvocationInfo : System.Management.Automation.InvocationInfo
ScriptStackTrace : at <ScriptBlock>, C:\Temp\updatereporting-master\Import-SSRSReports.ps1: line 191
at <ScriptBlock>, <No file>: line 1
PipelineIterationInfo : {0, 0}

Senior Member

Hi @jonasoh,

 

Thank you for this great report. But I'm receiveing the following error when I try to run the report:

 

Une erreur s'est produite lors du traitement du rapport. (rsProcessingAborted)
L'exécution a échoué pour le jeu de données partagé « ClientSecurityOverview ». (rsDataSetExecutionError)
Impossible de lire la ligne de données suivante pour le dataset UpdatesSummary. (rsErrorReadingNextDataRow)
Erreur de conversion du type de données nvarchar en varbinary.

 

Could you please help me to solve this issue ?

 

Regards,

Youssef

Regular Visitor

I did all the prep work and ran the PowerShell. The reporting works, but I have a problem accessing the sub-report. I try to click on an individual machine to get the sub-report and it attempts to open: /ConfigMgr_XYZ/Custom_UpdateReporting/_Computer Dashboard_2 (I replaced our site code with XYZ)

 

Should I just use Report Builder to map it to one of the hidden reports? If so, which one? 

 

[EDIT: I customized the link for the machine names to use Software Updates Compliance - Per device with a filter value of 0. I'm not sure if that's what you intended, but I like it that way.]

Microsoft

@jdurlewanger looks like you are trying to upload the report to the PowerBI Report Server. The script is not able to do that yet, but you could manually upload each file to the server. You might need to change the data source and path manually for each report via Report Builder.

Changing the script to be PowerBI Report Server aware is still in my backlog.  

Microsoft

@gadgetz I removed the link from the report and updated the Git repository.  That was just a test and I seem to have forgotten to remove the link. 

Microsoft

@youssefsaad I changed to SQL query to not rely on the SQL Server install language. 

More details can be found here: https://github.com/jonasatgit/updatereporting/issues/1
Just download the latest version and the report should run. 

Frequent Visitor

@jonasoh I am not trying to upload to powerbi, I am trying to upload to SSRS report server hosting the configmgr db.

Microsoft

@gadgetz great idea changing the link to the per device report. I did that for all the links and updated the repository.

 

@youssefsaad I had to change the query again to fix the language issue, but it should work now. Just grab the latest files from the repository.

 

@riche10it I added a new switch parameter called "ForceLegacyFormat" to convert the files to the older format. The reports should work now on older SSRS versions as well. But updating to the latest SSRS version should be the first step, as you already did.

Occasional Visitor

Hi, Jonasoh. First thank you very much for the reports and script to load reports.

I have sccm 2016

powershell script completed without any error.

but  I am having a weird error.  First, after run the script. I am only seeing two reports:

compare update compliance and software updates compliance-overview.

pagenated reports(17)

datasets(2)

The other problem is I got following error when trying to run report, including any existing report from ssrs install:

 

 

xp620303_1-1613776971019.png

 

I have to retype in password on datasource security as on this screen. but after run one repport, problem come back again:

xp620303_2-1613777103519.png

 

any idea what's going on?

 

thanks

Steven

 

Occasional Visitor

never mind, figured out what went wrong regarding issue on my post. thanks

Occasional Visitor

Hi, Jonasoh! I followed the instructions you provided for this custom report but I am receiving this warning message "Warning: The dataset ‘UpdatesSummaryView’ refers to the shared data source ‘/coh/{5C6358F2-4BB6-4a1b-A16E-8D96795D8602}’, which is not published on th
e report server. The shared data source ‘/coh/{5C6358F2-4BB6-4a1b-A16E-8D96795D8602}’ must be published before this shared dataset can run." What can I do to correct this error? 

Microsoft

Hi @xp620303 you might need to type in the password for the reporting user in the SCCM console under: "Administration\Security\Accounts" instead of using SSRS directly. 

Hi @NewMem2022 have you provided the full path to ConfigMgr datasource like this?

-TargetDataSourcePath "ConfigMgr_P11/{5C6358F2-4BB6-4a1b-A16E-8D96795D8602}"

In my case the SiteCode is P11 and the default ConfigMgr reporting folder is called: "ConfigMgr_P11". I am assuming your SiteCode is "COH" which means the folder might be called: "ConfigMgr_COH" and you schould use that for the TargetDataSourcePath parameter. 
Delete and re-create the folder on the reporting services website before re-uploading the reports to avoid any errors. 
Hope this helps.  

Best regards
Jonas

Occasional Visitor

Hi @jonasoh ,

 

Thank you for the report

 

I am trying to run the PS script but I am getting the following error can you help me in this.

 

.\Import-SSRSReports.ps1 -ReportServerURI "http://clhqsm217/Reports
/browse/ConfigMgr_EUC" -TargetFolderPath "ConfigMgr_EUC/Custom_UpdateReporting" -TargetDataSourcePath "ConfigMgr_EUC/{5C
6358F2-4BB6-4a1b-A16E-8D96795D8602}"
Copy "E:\updatereporting-master\updatereporting-master\SourceFiles\*" to "E:\updatereporting-master\updatereporting-master\work\"
Found 19 .rdl and .rsd files in "E:\updatereporting-master\updatereporting-master\work"
Working on: Compare Update Compliance.rdl
Working on: Software Updates Compliance - Overview ABC Last ADDS Logon.rdl
Working on: Software Updates Compliance - Overview ABC Last Policy Update.rdl
Working on: Software Updates Compliance - Overview ABC Last Reboot.rdl
Working on: Software Updates Compliance - Overview ABC Last Update Install.rdl
Working on: Software Updates Compliance - Overview all compliant.rdl
Working on: Software Updates Compliance - Overview all uncompliant.rdl
Working on: Software Updates Compliance - Overview current rollup compliant.rdl
Working on: Software Updates Compliance - Overview current rollup uncompliant.rdl
Working on: Software Updates Compliance - Overview last rollup compliant.rdl
Working on: Software Updates Compliance - Overview last rollup uncompliant.rdl
Working on: Software Updates Compliance - Overview Pending Reboot.rdl
Working on: Software Updates Compliance - Overview subreport template.rdl
Working on: Software Updates Compliance - Overview Updates missing not deployed.rdl
Working on: Software Updates Compliance - Overview WSUSScanError.rdl
Working on: Software Updates Compliance - Overview.rdl
Working on: Software Updates Compliance - Per device.rdl
Working on: UpdatesSummary.rsd
Working on: UpdatesSummaryView.rsd
Connecting to: http://clhqsm217/Reports/browse/ConfigMgr_EUC...
New-WebServiceProxy : The HTML document does not contain Web service discovery information.
At E:\updatereporting-master\updatereporting-master\Import-SSRSReports.ps1:223 char:35
+ ... onnection = New-WebServiceProxy -Uri $ReportServerUriFull -Namespace ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : InvalidOperation: (http://clhqsm21...e2010.asmx?wsdl:Uri) [New-WebServiceProxy], Invalid
OperationException
+ FullyQualifiedErrorId : InvalidOperationException,Microsoft.PowerShell.Commands.NewWebServiceProxy

Problem with connection...
End of script!

Microsoft

Hi @Navajyoti the report server URI parameter should point to the report server API instead of the ConfigMgr reports folder.
Not like: -ReportServerURI "http://clhqsm217/Reports/browse/ConfigMgr_EUC"

Instead like: -ReportServerURI "http://clhqsm217/reportserver"

The URI might be different if you changed it in: "Report Server Configuration Manager".

You will find the actual URI in "Report Server Configuration Manager" under "Web Service URL".

Visitor

Hi Jonasoh, 

 

Thank you for creating this report and it's looking great. I uploaded this report to my MECM system without any problem, when I run compliance report against specified collection, I found out some client with same status as compliant clients (no red section) but they are located in uncompliant section. I couldn't figure out what causing the two client with same patches installation and compliance status but one is compliant and another isn't. 

I reviewed your "patching" compliance definition and believe the uncompliant machine should be in compliance client group instead of uncompliant. Do you have any idea?

 

Thanks a lot,

Gloria 

Occasional Visitor

Hello Jonasoh,

 

Can you tell me what the required version of SSRS is for these to work? I get the following error when trying to install them via PowerShell.

 

Exception calling "CreateCatalogItem" with "7" argument(s): "System.Web.Services.Protocols.SoapException: The definition of this report is not valid
or supported by this version of Reporting Services. The report definition may have been created with a later version of Reporting Services, or
contain content that is not well-formed or not valid based on Reporting Services schemas. Details: The report definition has an invalid target
namespace 'http://schemas.microsoft.com/sqlserver/reporting/2016/01/reportdefinition' which cannot be upgraded.
at Microsoft.ReportingServices.Library.ReportingService2010Impl.CreateReport(String Report, String Parent, Boolean Overwrite, Byte[] Definition,
Property[] Properties, ItemType ItemType, CatalogItem& ItemInfo, Warning[]& Warnings)
at Microsoft.ReportingServices.Library.ReportingService2010Impl.CreateCatalogItem(String ItemType, String Name, String Parent, Boolean Overwrite,
Byte[] Definition, Property[] Properties, CatalogItem& ItemInfo, Warning[]& Warnings)
at Microsoft.ReportingServices.WebServer.ReportingService2010.CreateCatalogItem(String ItemType, String Name, String Parent, Boolean Overwrite,
Byte[] Definition, Property[] Properties, CatalogItem& ItemInfo, Warning[]& Warnings)"
At C:\Users\da_mpeterson.HSHSAD\Desktop\updatereporting-master\updatereporting-master\Import-SSRSReports.ps1:246 char:17
+ $null = $ReportServerConnection.CreateCatalogItem(
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : NotSpecified: (:) [], MethodInvocationException
+ FullyQualifiedErrorId : SoapException

 

Any help would be appreciated, thanks!

Microsoft

Hi @webcat123 I will release a new version of the report framework in a few days. That should give you more details about why a system is marked as uncompliant. 

 

Hi @Agr8lemon the reports are build with Report Builder version 2016 and 2017 and contain a mix of those two schemas: 

'http://schemas.microsoft.com/sqlserver/reporting/2010/01/reportdefinition'

'http://schemas.microsoft.com/sqlserver/reporting/2016/01/reportdefinition'

As stated in the "Some key facts and prerequesites" section (last two lines) you can force the older schema (2010) by using the "-ForceLegacyFormat" parameter.
In case you want to upload the reports to PowerBI report server you have to do that manually as the upload script is not PowerBI aware at the moment.

Occasional Visitor

Hi Jonasoh,

 

Great report but the statistic I am having issues with is the top bar graph (Update Compliance) which is showing 100% uncompliant but I know this should be partially compliant, where is it pulling this information from?

 

Thanks

MECM.JPG

Microsoft


Hi @famelton you should see a description for each bar or column header if you hover over it with your mouse.
I described the compliance state in the: "Some key facts and prerequisites:" section. But to be honst it was easy to miss. So, I highlighted each fact and put that specific one on the third position.
But my guess would be column: "Month Since Last Update Install" (see first sub-report) because that is based on WMI class Win32_QuickFixEngineering which is not enabled in Hardware Inventory by default.

Visitor

Thank you Jonasoh for the update, looking forward to seeing the new version of report

 

Thanks,

Occasional Visitor

Thanks @jonasoh that was exactly what it was. As soon as Win32_QuickFixEngineering was enabled and the hardware inventory task run, the compliance started increasing. Thanks for your swift assistance.

Microsoft

Hi @webcat123 I hope you saw the new version (v3.5) already. I listed all the changes here: https://techcommunity.microsoft.com/t5/core-infrastructure-and-security/mastering-configuration-mana...

 

Regular Visitor

Hey Jonas,

Great work!

Whenever I run the script, I get the following error:
At C:\Scripts\SSRS_Reports\Import-SSRSReports.ps1:211 char:21
+ Sign&nbsp;up
+ ~
The ampersand (&) character is not allowed. The & operator is reserved for future use; wrap an ampersand in double quotation marks ("&") to pass it as part of a string.
At C:\Scripts\SSRS_Reports\Import-SSRSReports.ps1:223 char:18
+ </button> </div>
+ ~
The '<' operator is reserved for future use.
At C:\Scripts\SSRS_Reports\Import-SSRSReports.ps1:237 char:16
+ </button> </div>
+ ~
The '<' operator is reserved for future use.
At C:\Scripts\SSRS_Reports\Import-SSRSReports.ps1:250 char:189
+ ... ata-ga-click="(Logged out) Header, go to Features">Features <span cla ...
+ ~
The '<' operator is reserved for future use.
At C:\Scripts\SSRS_Reports\Import-SSRSReports.ps1:250 char:269
+ ... nk-symbol float-right text-normal color-text-tertiary pr-3">&rarr;</s ...
+ ~
The ampersand (&) character is not allowed. The & operator is reserved for future use; wrap an ampersand in double quotation marks ("&") to pass it as part of a string.
At C:\Scripts\SSRS_Reports\Import-SSRSReports.ps1:254 char:167
+ ... ck Link--secondary no-underline f5 Bump-link--hover">Mobile <span cla ...
+ ~
The '<' operator is reserved for future use.
At C:\Scripts\SSRS_Reports\Import-SSRSReports.ps1:254 char:247
+ ... nk-symbol float-right text-normal color-text-tertiary pr-3">&rarr;</s ...
+ ~
The ampersand (&) character is not allowed. The & operator is reserved for future use; wrap an ampersand in double quotation marks ("&") to pass it as part of a string.
At C:\Scripts\SSRS_Reports\Import-SSRSReports.ps1:255 char:178
+ ... k Link--secondary no-underline f5 Bump-link--hover">Actions <span cla ...
+ ~
The '<' operator is reserved for future use.
At C:\Scripts\SSRS_Reports\Import-SSRSReports.ps1:255 char:258
+ ... nk-symbol float-right text-normal color-text-tertiary pr-3">&rarr;</s ...
+ ~
The ampersand (&) character is not allowed. The & operator is reserved for future use; wrap an ampersand in double quotation marks ("&") to pass it as part of a string.
At C:\Scripts\SSRS_Reports\Import-SSRSReports.ps1:256 char:184
+ ... ink--secondary no-underline f5 Bump-link--hover">Codespaces <span cla ...
+ ~
The '<' operator is reserved for future use.
Not all parse errors were reported. Correct the reported errors and try again.
+ CategoryInfo : ParserError: (:) [], ParseException
+ FullyQualifiedErrorId : AmpersandNotAllowed

 

Any idea what I'm doing wrong?

Microsoft

Hi @Zirigo my guess would be that you copied too much from the GitHub page here: https://github.com/jonasatgit/updatereporting/blob/master/Import-SSRSReports.ps1
The easiest way to download the whole solution is to use the "Code" and "Download ZIP" button on the following GitHub page: https://github.com/jonasatgit/updatereporting

 

Regular Visitor

Hi Jonasoh,

Thank you so much for promptly answering my inquiry.

Yes, you were right, I copied too much from the GitHub page.

Using the link you provided, I was able to get the right code and run successfully the PowerShell script.

 

Thank you a million!

Regular Visitor

Hi Jonasoh,

Sorry to send you this second request.

What would be the best way to send this report to an IT VP that cannot access the SSRS report but could read it in any other format?

Thank you.

Microsoft

Hi @Zirigo I normally create a report subscription to send the report via email and use the report format appropriate for the audience. 

Read more about it here: https://docs.microsoft.com/en-us/sql/reporting-services/subscriptions/subscriptions-and-delivery-rep...

Or here: https://techcommunity.microsoft.com/t5/configuration-manager-archive/configuring-email-notification-...

I tend to create the subscription via the SQL Server Reporting Services website instead of the ConfigMgr console, but both ways are appropriate. 

Regular Visitor

Thank you so much Jonasoh, this is great.
I will read the document and implement it into my environment.

Again, thank you!

 

%3CLINGO-SUB%20id%3D%22lingo-sub-1416117%22%20slang%3D%22en-US%22%3ERe%3A%20Mastering%20Configuration%20Manager%20Patch%20Compliance%20Reporting%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1416117%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20Jonas%2C%20impressive%20article%20and%20a%20great%20solution%20with%20a%20lot%20of%20useful%20information.%20Thanks%20for%20putting%20it%20together!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1417149%22%20slang%3D%22en-US%22%3ERe%3A%20Mastering%20Configuration%20Manager%20Patch%20Compliance%20Reporting%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1417149%22%20slang%3D%22en-US%22%3E%3CP%3EThank%20you%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F268468%22%20target%3D%22_blank%22%3E%40jonasoh%3C%2FA%3E%26nbsp%3Bfor%20the%20Awesome%20blogpost%20for%20the%20Community%26nbsp%3B%3CIMG%20class%3D%22lia-deferred-image%20lia-image-emoji%22%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Fhtml%2Fimages%2Femoticons%2Fcool_40x40.gif%22%20alt%3D%22%3Acool%3A%22%20title%3D%22%3Acool%3A%22%20%2F%3E%3C%2FP%3E%0A%3CP%3EI%20have%20Shared%20it%20on%20my%20Social%20media%20Channels%20%3B)%3C%2Fimg%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1417979%22%20slang%3D%22en-US%22%3ERe%3A%20Mastering%20Configuration%20Manager%20Patch%20Compliance%20Reporting%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1417979%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20Jonas%2C%26nbsp%3B%26nbsp%3B%3CBR%20%2F%3EThis%20is%20really%20helpful%2C%20however%20I%20am%20facing%20some%20errors%20when%20running%20the%20PS%20script%20-%26nbsp%3Bthe%20definition%20of%20this%20report%20is%20not%20valid%20or%20supported%20by%20this%20version%20of%20Reporting%20Services%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAny%20ideas%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1418628%22%20slang%3D%22en-US%22%3ERe%3A%20Mastering%20Configuration%20Manager%20Patch%20Compliance%20Reporting%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1418628%22%20slang%3D%22en-US%22%3E%3CP%3EHi%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F679981%22%20target%3D%22_blank%22%3E%40MarkB35%3C%2FA%3E.%3C%2FP%3E%0A%3CP%3EI%20only%20tested%20SSRS%202017%2C%20so%20it%20might%20not%20work%20with%20older%20versions.%20Which%20version%20you%20are%20running%3F%20Can%20you%20share%20the%20exact%20error%20message%3F%3C%2FP%3E%0A%3CP%3EDownload%20link%20for%20SSRS%202017%3A%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fwww.microsoft.com%2Fen-us%2Fdownload%2Fdetails.aspx%3Fid%3D55252%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttps%3A%2F%2Fwww.microsoft.com%2Fen-us%2Fdownload%2Fdetails.aspx%3Fid%3D55252%3C%2FA%3E%26nbsp%3BJust%20in%20case%20%3A)%3C%2Fimg%3E%3C%2FP%3E%0A%3CP%3EBest%20regards%3C%2FP%3E%0A%3CP%3EJonas%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1423009%22%20slang%3D%22en-US%22%3ERe%3A%20Mastering%20Configuration%20Manager%20Patch%20Compliance%20Reporting%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1423009%22%20slang%3D%22en-US%22%3E%3CP%3EHI%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F268468%22%20target%3D%22_blank%22%3E%40jonasoh%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20managed%20to%20resolve%20this.%3CBR%20%2F%3E%3CBR%20%2F%3EWe%20was%20on%20SQL%202014%2C%20I%20updated%20to%20SQL%202017%20and%20it%20now%20works.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1577161%22%20slang%3D%22en-US%22%3ERe%3A%20Mastering%20Configuration%20Manager%20Patch%20Compliance%20Reporting%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1577161%22%20slang%3D%22en-US%22%3E%3CP%3EThis%20looks%20very%20useful%2C%20but%20I%20am%20running%20into%20issues%20during%20installation.%26nbsp%3B%20I%20am%20receiving%20the%20error%20below%20for%20every%20RDL%20file%20that%20attempts%20to%20install.%26nbsp%3B%20Any%20help%20would%20be%20appreciated.%3C%2FP%3E%3CP%3E%3CBR%20%2F%3EUploading%3A%20UpdatesSummaryView.rsd...%3C%2FP%3E%3CP%3E'%2F1Patch_Compliance_Reports%2FUpdatesSummaryView'%20cannot%20be%20found.%20---%26gt%3B%3CBR%20%2F%3EMicrosoft.ReportingServices.Diagnostics.Utilities.ItemNotFoundException%3A%20The%20item%3CBR%20%2F%3E'%2F1Patch_Compliance_Reports%2FUpdatesSummaryView'%20cannot%20be%20found.%3CBR%20%2F%3Eat%20Microsoft.ReportingServices.Library.ReportingService2005Impl.GetProperties(String%20Item%2C%20Property%5B%5D%20Properties%2C%3CBR%20%2F%3EItemNamespaceEnum%20itemNamespace%2C%20Property%5B%5D%26amp%3B%20Values)%3CBR%20%2F%3Eat%20Microsoft.ReportingServices.WebServer.ReportingService2010.GetProperties(String%20ItemPath%2C%20Property%5B%5D%20Properties%2C%3CBR%20%2F%3EProperty%5B%5D%26amp%3B%20Values)%22%3CBR%20%2F%3EAt%20E%3A%5CReports%5Cupdatereporting-master%5CImport-SSRSReports.ps1%3A233%20char%3A21%3CBR%20%2F%3E%2B%20%24Properties%20%3D%20%24ReportServerConnection.GetProperties(%22%24target%20...%3CBR%20%2F%3E%2B%20~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~%3CBR%20%2F%3E%2B%20CategoryInfo%20%3A%20NotSpecified%3A%20(%3A)%20%5B%5D%2C%20MethodInvocationException%3CBR%20%2F%3E%2B%20FullyQualifiedErrorId%20%3A%20SoapException%3C%2FP%3E%3CP%3EThe%20property%20'Value'%20cannot%20be%20found%20on%20this%20object.%20Verify%20that%20the%20property%20exists%20and%20can%20be%20set.%3CBR%20%2F%3EAt%20E%3A%5CReports%5Cupdatereporting-master%5CImport-SSRSReports.ps1%3A235%20char%3A21%3CBR%20%2F%3E%2B%20%24prop.Value%20%3D%20%24true%3CBR%20%2F%3E%2B%20~~~~~~~~~~~~~~~~~~~%3CBR%20%2F%3E%2B%20CategoryInfo%20%3A%20InvalidOperation%3A%20(%3A)%20%5B%5D%2C%20RuntimeException%3CBR%20%2F%3E%2B%20FullyQualifiedErrorId%20%3A%20PropertyNotFound%3C%2FP%3E%3CP%3EException%20calling%20%22SetProperties%22%20with%20%222%22%20argument(s)%3A%20%22System.Web.Services.Protocols.SoapException%3A%20The%20value%20for%3CBR%20%2F%3Eparameter%20'Properties'%20is%20not%20specified.%20It%20is%20either%20missing%20from%20the%20function%20call%2C%20or%20it%20is%20set%20to%20null.%20---%26gt%3B%3CBR%20%2F%3EMicrosoft.ReportingServices.Diagnostics.Utilities.MissingParameterException%3A%20The%20value%20for%20parameter%20'Properties'%20is%3CBR%20%2F%3Enot%20specified.%20It%20is%20either%20missing%20from%20the%20function%20call%2C%20or%20it%20is%20set%20to%20null.%3CBR%20%2F%3Eat%20Microsoft.ReportingServices.Library.ReportingService2005Impl.SetProperties(String%20Item%2C%20Property%5B%5D%20Properties%2C%3CBR%20%2F%3EGuid%20batchId)%3CBR%20%2F%3Eat%20Microsoft.ReportingServices.Library.ReportingService2005Impl.SetProperties(String%20Item%2C%20Property%5B%5D%20Properties)%3CBR%20%2F%3Eat%20Microsoft.ReportingServices.WebServer.ReportingService2010.SetProperties(String%20ItemPath%2C%20Property%5B%5D%20Properties)%22%3CBR%20%2F%3EAt%20E%3A%5CReports%5Cupdatereporting-master%5CImport-SSRSReports.ps1%3A236%20char%3A21%3CBR%20%2F%3E%2B%20%24ReportServerConnection.SetProperties(%22%24targetPath%2F%24reportNa%20...%3CBR%20%2F%3E%2B%20~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~%3CBR%20%2F%3E%2B%20CategoryInfo%20%3A%20NotSpecified%3A%20(%3A)%20%5B%5D%2C%20MethodInvocationException%3CBR%20%2F%3E%2B%20FullyQualifiedErrorId%20%3A%20SoapException%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1586858%22%20slang%3D%22en-US%22%3ERe%3A%20Mastering%20Configuration%20Manager%20Patch%20Compliance%20Reporting%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1586858%22%20slang%3D%22en-US%22%3E%3CP%3EHi%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F754258%22%20target%3D%22_blank%22%3E%40riche10it%3C%2FA%3E%20which%20SSRS%20version%20you%20are%20using%3F%20I%20tested%20SSRS%202017%20which%20will%20work%20with%20older%20SQL%20versions.%26nbsp%3B%3CBR%20%2F%3ESome%20reports%20should%20be%20set%20to%20hidden%20and%20that%20seems%20to%20be%20failing%20in%20your%20case.%20Those%20reports%20are%20only%20used%20as%20a%20sub-report%20for%20the%20dasboard%20and%20hiding%20them%20makes%20therefore%20sens.%26nbsp%3B%3CBR%20%2F%3EYou%20can%20always%20try%20to%20upload%20the%20reports%20manually%20from%20the%20%22work%22%20folder%20by%20clicking%20the%20%22upload%22%20button%20in%20the%20SSRS%20folder%20you%20which%20to%20have%20the%20reports%20in.%20Make%20sure%20to%20upload%20the%20two%20%22.rsd%22%20files%20first.%20Hope%20this%20helps.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1622806%22%20slang%3D%22en-US%22%3ERe%3A%20Mastering%20Configuration%20Manager%20Patch%20Compliance%20Reporting%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1622806%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20Jonas%3C%2FP%3E%3CP%3Ethnx%20for%20this%20dashboard%20%3A)%3C%2Fimg%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1724837%22%20slang%3D%22en-US%22%3ERe%3A%20Mastering%20Configuration%20Manager%20Patch%20Compliance%20Reporting%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1724837%22%20slang%3D%22en-US%22%3E%3CP%3EI%20am%20receiving%20the%20following%20error%20when%20trying%20to%20publish%20your%20report.%20Any%20guidance%20would%20be%20appreciated.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EwriteErrorStream%20%3A%20True%3CBR%20%2F%3EPSMessageDetails%20%3A%3CBR%20%2F%3EException%20%3A%20System.InvalidOperationException%3A%20The%20HTML%20document%20does%20not%20contain%20Web%20service%20discovery%3CBR%20%2F%3Einformation.%3CBR%20%2F%3Eat%20System.Web.Services.Discovery.DiscoveryClientProtocol.DiscoverAny(String%20url)%3CBR%20%2F%3Eat%20Microsoft.PowerShell.Commands.NewWebServiceProxy.GenerateWebServiceProxyAssembly(String%3CBR%20%2F%3ENameSpace%2C%20String%20ClassName)%3CBR%20%2F%3ETargetObject%20%3A%20%3CA%20href%3D%22http%3A%2F%2Fservername%2Freports%2FReportService2010.asmx%3Fwsdl%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3Ehttp%3A%2F%2Fservername%2Freports%2FReportService2010.asmx%3Fwsdl%3C%2FA%3E%3CBR%20%2F%3ECategoryInfo%20%3A%20InvalidOperation%3A%20(%3CA%20href%3D%22http%3A%2F%2Fservername...e2010.asmx%3Fwsdl%3AUri%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3Ehttp%3A%2F%2Fservername...e2010.asmx%3Fwsdl%3AUri%3C%2FA%3E)%20%5BNew-WebServiceProxy%5D%2C%3CBR%20%2F%3EInvalidOperationException%3CBR%20%2F%3EFullyQualifiedErrorId%20%3A%20InvalidOperationException%2CMicrosoft.PowerShell.Commands.NewWebServiceProxy%3CBR%20%2F%3EErrorDetails%20%3A%3CBR%20%2F%3EInvocationInfo%20%3A%20System.Management.Automation.InvocationInfo%3CBR%20%2F%3EScriptStackTrace%20%3A%20at%20%3CSCRIPTBLOCK%3E%2C%20C%3A%5CTemp%5Cupdatereporting-master%5CImport-SSRSReports.ps1%3A%20line%20191%3CBR%20%2F%3Eat%20%3CSCRIPTBLOCK%3E%2C%20%3CNO%20file%3D%22%22%3E%3A%20line%201%3CBR%20%2F%3EPipelineIterationInfo%20%3A%20%7B0%2C%200%7D%3C%2FNO%3E%3C%2FSCRIPTBLOCK%3E%3C%2FSCRIPTBLOCK%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1763285%22%20slang%3D%22en-US%22%3ERe%3A%20Mastering%20Configuration%20Manager%20Patch%20Compliance%20Reporting%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1763285%22%20slang%3D%22en-US%22%3E%3CP%3EHi%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F268468%22%20target%3D%22_blank%22%3E%40jonasoh%3C%2FA%3E%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThank%20you%20for%20this%20great%20report.%20But%20I'm%20receiveing%20the%20following%20error%20when%20I%20try%20to%20run%20the%20report%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EUne%20erreur%20s'est%20produite%20lors%20du%20traitement%20du%20rapport.%20(rsProcessingAborted)%3CBR%20%2F%3EL'ex%C3%A9cution%20a%20%C3%A9chou%C3%A9%20pour%20le%20jeu%20de%20donn%C3%A9es%20partag%C3%A9%20%C2%AB%20ClientSecurityOverview%20%C2%BB.%20(rsDataSetExecutionError)%3CBR%20%2F%3EImpossible%20de%20lire%20la%20ligne%20de%20donn%C3%A9es%20suivante%20pour%20le%20dataset%20UpdatesSummary.%20(rsErrorReadingNextDataRow)%3CBR%20%2F%3EErreur%20de%20conversion%20du%20type%20de%20donn%C3%A9es%20nvarchar%20en%20varbinary.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ECould%20you%20please%20help%20me%20to%20solve%20this%20issue%20%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ERegards%2C%3C%2FP%3E%3CP%3EYoussef%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1846092%22%20slang%3D%22en-US%22%3ERe%3A%20Mastering%20Configuration%20Manager%20Patch%20Compliance%20Reporting%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1846092%22%20slang%3D%22en-US%22%3E%3CP%3EI%20did%20all%20the%20prep%20work%20and%20ran%20the%20PowerShell.%20The%20reporting%20works%2C%20but%20I%20have%20a%20problem%20accessing%20the%20sub-report.%20I%20try%20to%20click%20on%20an%20individual%20machine%20to%20get%20the%20sub-report%20and%20it%20attempts%20to%20open%3A%20%2FConfigMgr_XYZ%2FCustom_UpdateReporting%2F_Computer%20Dashboard_2%20(I%20replaced%20our%20site%20code%20with%20XYZ)%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EShould%20I%20just%20use%20Report%20Builder%20to%20map%20it%20to%20one%20of%20the%20hidden%20reports%3F%20If%20so%2C%20which%20one%3F%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%5BEDIT%3A%20I%20customized%20the%20link%20for%20the%20machine%20names%20to%20use%26nbsp%3BSoftware%20Updates%20Compliance%20-%20Per%20device%20with%20a%20filter%20value%20of%200.%20I'm%20not%20sure%20if%20that's%20what%20you%20intended%2C%20but%20I%20like%20it%20that%20way.%5D%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1848053%22%20slang%3D%22en-US%22%3ERe%3A%20Mastering%20Configuration%20Manager%20Patch%20Compliance%20Reporting%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1848053%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F813485%22%20target%3D%22_blank%22%3E%40jdurlewanger%3C%2FA%3E%26nbsp%3Blooks%20like%20you%20are%20trying%20to%20upload%20the%20report%20to%20the%20PowerBI%20Report%20Server.%20The%20script%20is%20not%20able%20to%20do%20that%20yet%2C%20but%20you%20could%20manually%20upload%20each%20file%20to%20the%20server.%20You%20might%20need%20to%20change%20the%20data%20source%20and%20path%20manually%20for%20each%20report%20via%20Report%20Builder.%3C%2FP%3E%0A%3CP%3EChanging%20the%20script%20to%20be%20PowerBI%20Report%20Server%20aware%20is%20still%20in%20my%20backlog.%26nbsp%3B%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1848054%22%20slang%3D%22en-US%22%3ERe%3A%20Mastering%20Configuration%20Manager%20Patch%20Compliance%20Reporting%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1848054%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F711432%22%20target%3D%22_blank%22%3E%40gadgetz%3C%2FA%3E%26nbsp%3BI%20removed%20the%20link%20from%20the%20report%20and%20updated%20the%20Git%20repository.%26nbsp%3B%20That%20was%20just%20a%20test%20and%20I%20seem%20to%20have%20forgotten%20to%20remove%20the%20link.%26nbsp%3B%3CBR%20%2F%3E%3CBR%20%2F%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1849600%22%20slang%3D%22en-US%22%3ERe%3A%20Mastering%20Configuration%20Manager%20Patch%20Compliance%20Reporting%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1849600%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F566883%22%20target%3D%22_blank%22%3E%40SaadYoussef0%3C%2FA%3E%26nbsp%3BI%20changed%20to%20SQL%20query%20to%20not%20rely%20on%20the%20SQL%20Server%20install%20language.%26nbsp%3B%3C%2FP%3E%0A%3CP%3EMore%20details%20can%20be%20found%20here%3A%20%3CA%20href%3D%22https%3A%2F%2Fgithub.com%2Fjonasatgit%2Fupdatereporting%2Fissues%2F1%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttps%3A%2F%2Fgithub.com%2Fjonasatgit%2Fupdatereporting%2Fissues%2F1%3C%2FA%3E%3CBR%20%2F%3EJust%20download%20the%20latest%20version%20and%20the%20report%20should%20run.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1849805%22%20slang%3D%22en-US%22%3ERe%3A%20Mastering%20Configuration%20Manager%20Patch%20Compliance%20Reporting%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1849805%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F268468%22%20target%3D%22_blank%22%3E%40jonasoh%3C%2FA%3E%26nbsp%3BI%20am%20not%20trying%20to%20upload%20to%20powerbi%2C%20I%20am%20trying%20to%20upload%20to%20SSRS%20report%20server%20hosting%20the%20configmgr%20db.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1971392%22%20slang%3D%22en-US%22%3ERe%3A%20Mastering%20Configuration%20Manager%20Patch%20Compliance%20Reporting%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1971392%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F711432%22%20target%3D%22_blank%22%3E%40gadgetz%3C%2FA%3E%26nbsp%3Bgreat%20idea%20changing%20the%20link%20to%20the%20per%20device%20report.%20I%20did%20that%20for%20all%20the%20links%20and%20updated%20the%20repository.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F566883%22%20target%3D%22_blank%22%3E%40youssefsaad%3C%2FA%3E%26nbsp%3BI%20had%20to%20change%20the%20query%20again%20to%20fix%20the%20language%20issue%2C%20but%20it%20should%20work%20now.%20Just%20grab%20the%20latest%20files%20from%20the%20repository.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F754258%22%20target%3D%22_blank%22%3E%40riche10it%3C%2FA%3E%26nbsp%3BI%20added%20a%20new%20switch%20parameter%20called%20%22ForceLegacyFormat%22%20to%20convert%20the%20files%20to%20the%20older%20format.%20The%20reports%20should%20work%20now%20on%20older%20SSRS%20versions%20as%20well.%20But%20updating%20to%20the%20latest%20SSRS%20version%20should%20be%20the%20first%20step%2C%20as%20you%20already%20did.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2150785%22%20slang%3D%22en-US%22%3ERe%3A%20Mastering%20Configuration%20Manager%20Patch%20Compliance%20Reporting%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2150785%22%20slang%3D%22en-US%22%3E%3CP%3EHi%2C%20Jonasoh.%20First%20thank%20you%20very%20much%20for%20the%20reports%20and%20script%20to%20load%20reports.%3C%2FP%3E%3CP%3EI%20have%20sccm%202016%3C%2FP%3E%3CP%3Epowershell%20script%20completed%20without%20any%20error.%3C%2FP%3E%3CP%3Ebut%26nbsp%3B%20I%20am%20having%20a%20weird%20error.%26nbsp%3B%20First%2C%20after%20run%20the%20script.%20I%20am%20only%20seeing%20two%20reports%3A%3C%2FP%3E%3CP%3Ecompare%20update%20compliance%20and%20software%20updates%20compliance-overview.%3C%2FP%3E%3CP%3Epagenated%20reports(17)%3C%2FP%3E%3CP%3Edatasets(2)%3C%2FP%3E%3CP%3EThe%20other%20problem%20is%20I%20got%20following%20error%20when%20trying%20to%20run%20report%2C%20including%20any%20existing%20report%20from%20ssrs%20install%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%22xp620303_1-1613776971019.png%22%20style%3D%22width%3A%20400px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F256210i3ED2C85970455A00%2Fimage-size%2Fmedium%3Fv%3D1.0%26amp%3Bpx%3D400%22%20role%3D%22button%22%20title%3D%22xp620303_1-1613776971019.png%22%20alt%3D%22xp620303_1-1613776971019.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20have%20to%20retype%20in%20password%20on%20datasource%20security%20as%20on%20this%20screen.%20but%20after%20run%20one%20repport%2C%20problem%20come%20back%20again%3A%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%22xp620303_2-1613777103519.png%22%20style%3D%22width%3A%20400px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F256211i90340EA3CD9A2FC9%2Fimage-size%2Fmedium%3Fv%3D1.0%26amp%3Bpx%3D400%22%20role%3D%22button%22%20title%3D%22xp620303_2-1613777103519.png%22%20alt%3D%22xp620303_2-1613777103519.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3Eany%20idea%20what's%20going%20on%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3Ethanks%3C%2FP%3E%3CP%3ESteven%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2162671%22%20slang%3D%22en-US%22%3ERe%3A%20Mastering%20Configuration%20Manager%20Patch%20Compliance%20Reporting%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2162671%22%20slang%3D%22en-US%22%3E%3CP%3Enever%20mind%2C%20figured%20out%20what%20went%20wrong%20regarding%20issue%20on%20my%20post.%20thanks%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2175749%22%20slang%3D%22en-US%22%3ERe%3A%20Mastering%20Configuration%20Manager%20Patch%20Compliance%20Reporting%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2175749%22%20slang%3D%22en-US%22%3E%3CP%3E%3CSPAN%3EHi%2C%20Jonasoh!%20I%20followed%20the%20instructions%26nbsp%3Byou%20provided%20for%20this%20custom%20report%20but%20I%20am%20receiving%20this%20warning%20message%20%22Warning%3A%20The%20dataset%20%E2%80%98UpdatesSummaryView%E2%80%99%20refers%20to%20the%20shared%20data%20source%20%E2%80%98%2Fcoh%2F%7B5C6358F2-4BB6-4a1b-A16E-8D96795D8602%7D%E2%80%99%2C%20which%20is%20not%20published%20on%20th%3CBR%20%2F%3Ee%20report%20server.%20The%20shared%20data%20source%20%E2%80%98%2Fcoh%2F%7B5C6358F2-4BB6-4a1b-A16E-8D96795D8602%7D%E2%80%99%20must%20be%20published%20before%20this%20shared%20dataset%20can%20run.%22%20What%20can%20I%20do%20to%20correct%20this%20error%3F%26nbsp%3B%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2202141%22%20slang%3D%22en-US%22%3ERe%3A%20Mastering%20Configuration%20Manager%20Patch%20Compliance%20Reporting%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2202141%22%20slang%3D%22en-US%22%3E%3CP%3EHi%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F610351%22%20target%3D%22_blank%22%3E%40xp620303%3C%2FA%3E%26nbsp%3Byou%20might%20need%20to%20type%20in%20the%20password%20for%20the%20reporting%20user%20in%20the%20SCCM%20console%20under%3A%20%22Administration%5CSecurity%5CAccounts%22%20instead%20of%20using%20SSRS%20directly.%26nbsp%3B%3CBR%20%2F%3E%3CBR%20%2F%3EHi%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F982624%22%20target%3D%22_blank%22%3E%40NewMem2022%3C%2FA%3E%26nbsp%3Bhave%20you%20provided%20the%20full%20path%20to%20ConfigMgr%20datasource%20like%20this%3F%3C%2FP%3E%0A%3CPRE%20class%3D%22lia-code-sample%20%20language-powershell%22%3E%3CCODE%3E-TargetDataSourcePath%20%22ConfigMgr_P11%2F%7B5C6358F2-4BB6-4a1b-A16E-8D96795D8602%7D%22%3C%2FCODE%3E%3C%2FPRE%3E%0A%3CP%3EIn%20my%20case%20the%20SiteCode%20is%20P11%20and%20the%20default%20ConfigMgr%20reporting%20folder%20is%20called%3A%20%22ConfigMgr_P11%22.%20I%20am%20assuming%20your%20SiteCode%20is%20%22COH%22%20which%20means%20the%20folder%20might%20be%20called%3A%20%22ConfigMgr_COH%22%20and%20you%20schould%20use%20that%20for%20the%20TargetDataSourcePath%20parameter.%26nbsp%3B%3CBR%20%2F%3EDelete%20and%20re-create%20the%20folder%20on%20the%20reporting%20services%20website%20before%20re-uploading%20the%20reports%20to%20avoid%20any%20errors.%26nbsp%3B%3CBR%20%2F%3EHope%20this%20helps.%26nbsp%3B%26nbsp%3B%3CBR%20%2F%3E%3CBR%20%2F%3EBest%20regards%3CBR%20%2F%3EJonas%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2278714%22%20slang%3D%22en-US%22%3ERe%3A%20Mastering%20Configuration%20Manager%20Patch%20Compliance%20Reporting%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2278714%22%20slang%3D%22en-US%22%3E%3CP%3EHi%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F268468%22%20target%3D%22_blank%22%3E%40jonasoh%3C%2FA%3E%26nbsp%3B%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThank%20you%20for%20the%20report%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20am%20trying%20to%20run%20the%20PS%20script%20but%20I%20am%20getting%20the%20following%20error%20can%20you%20help%20me%20in%20this.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E.%5CImport-SSRSReports.ps1%20-ReportServerURI%20%22%3CA%20href%3D%22http%3A%2F%2Fclhqsm217%2FReports%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3Ehttp%3A%2F%2Fclhqsm217%2FReports%3C%2FA%3E%3CBR%20%2F%3E%2Fbrowse%2FConfigMgr_EUC%22%20-TargetFolderPath%20%22ConfigMgr_EUC%2FCustom_UpdateReporting%22%20-TargetDataSourcePath%20%22ConfigMgr_EUC%2F%7B5C%3CBR%20%2F%3E6358F2-4BB6-4a1b-A16E-8D96795D8602%7D%22%3CBR%20%2F%3ECopy%20%22E%3A%5Cupdatereporting-master%5Cupdatereporting-master%5CSourceFiles%5C*%22%20to%20%22E%3A%5Cupdatereporting-master%5Cupdatereporting-master%5Cwork%5C%22%3CBR%20%2F%3EFound%2019%20.rdl%20and%20.rsd%20files%20in%20%22E%3A%5Cupdatereporting-master%5Cupdatereporting-master%5Cwork%22%3CBR%20%2F%3EWorking%20on%3A%20Compare%20Update%20Compliance.rdl%3CBR%20%2F%3EWorking%20on%3A%20Software%20Updates%20Compliance%20-%20Overview%20ABC%20Last%20ADDS%20Logon.rdl%3CBR%20%2F%3EWorking%20on%3A%20Software%20Updates%20Compliance%20-%20Overview%20ABC%20Last%20Policy%20Update.rdl%3CBR%20%2F%3EWorking%20on%3A%20Software%20Updates%20Compliance%20-%20Overview%20ABC%20Last%20Reboot.rdl%3CBR%20%2F%3EWorking%20on%3A%20Software%20Updates%20Compliance%20-%20Overview%20ABC%20Last%20Update%20Install.rdl%3CBR%20%2F%3EWorking%20on%3A%20Software%20Updates%20Compliance%20-%20Overview%20all%20compliant.rdl%3CBR%20%2F%3EWorking%20on%3A%20Software%20Updates%20Compliance%20-%20Overview%20all%20uncompliant.rdl%3CBR%20%2F%3EWorking%20on%3A%20Software%20Updates%20Compliance%20-%20Overview%20current%20rollup%20compliant.rdl%3CBR%20%2F%3EWorking%20on%3A%20Software%20Updates%20Compliance%20-%20Overview%20current%20rollup%20uncompliant.rdl%3CBR%20%2F%3EWorking%20on%3A%20Software%20Updates%20Compliance%20-%20Overview%20last%20rollup%20compliant.rdl%3CBR%20%2F%3EWorking%20on%3A%20Software%20Updates%20Compliance%20-%20Overview%20last%20rollup%20uncompliant.rdl%3CBR%20%2F%3EWorking%20on%3A%20Software%20Updates%20Compliance%20-%20Overview%20Pending%20Reboot.rdl%3CBR%20%2F%3EWorking%20on%3A%20Software%20Updates%20Compliance%20-%20Overview%20subreport%20template.rdl%3CBR%20%2F%3EWorking%20on%3A%20Software%20Updates%20Compliance%20-%20Overview%20Updates%20missing%20not%20deployed.rdl%3CBR%20%2F%3EWorking%20on%3A%20Software%20Updates%20Compliance%20-%20Overview%20WSUSScanError.rdl%3CBR%20%2F%3EWorking%20on%3A%20Software%20Updates%20Compliance%20-%20Overview.rdl%3CBR%20%2F%3EWorking%20on%3A%20Software%20Updates%20Compliance%20-%20Per%20device.rdl%3CBR%20%2F%3EWorking%20on%3A%20UpdatesSummary.rsd%3CBR%20%2F%3EWorking%20on%3A%20UpdatesSummaryView.rsd%3CBR%20%2F%3EConnecting%20to%3A%20%3CA%20href%3D%22http%3A%2F%2Fclhqsm217%2FReports%2Fbrowse%2FConfigMgr_EUC%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3Ehttp%3A%2F%2Fclhqsm217%2FReports%2Fbrowse%2FConfigMgr_EUC%3C%2FA%3E...%3CBR%20%2F%3ENew-WebServiceProxy%20%3A%20The%20HTML%20document%20does%20not%20contain%20Web%20service%20discovery%20information.%3CBR%20%2F%3EAt%20E%3A%5Cupdatereporting-master%5Cupdatereporting-master%5CImport-SSRSReports.ps1%3A223%20char%3A35%3CBR%20%2F%3E%2B%20...%20onnection%20%3D%20New-WebServiceProxy%20-Uri%20%24ReportServerUriFull%20-Namespace%20...%3CBR%20%2F%3E%2B%20~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~%3CBR%20%2F%3E%2B%20CategoryInfo%20%3A%20InvalidOperation%3A%20(%3CA%20href%3D%22http%3A%2F%2Fclhqsm21...e2010.asmx%3Fwsdl%3AUri%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3Ehttp%3A%2F%2Fclhqsm21...e2010.asmx%3Fwsdl%3AUri%3C%2FA%3E)%20%5BNew-WebServiceProxy%5D%2C%20Invalid%3CBR%20%2F%3EOperationException%3CBR%20%2F%3E%2B%20FullyQualifiedErrorId%20%3A%20InvalidOperationException%2CMicrosoft.PowerShell.Commands.NewWebServiceProxy%3C%2FP%3E%3CP%3EProblem%20with%20connection...%3CBR%20%2F%3EEnd%20of%20script!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2327673%22%20slang%3D%22en-US%22%3ERe%3A%20Mastering%20Configuration%20Manager%20Patch%20Compliance%20Reporting%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2327673%22%20slang%3D%22en-US%22%3E%3CP%3EHi%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F1031087%22%20target%3D%22_blank%22%3E%40Navajyoti%3C%2FA%3E%26nbsp%3Bthe%20report%20server%20URI%20parameter%20should%20point%20to%20the%20report%20server%20API%20instead%20of%20the%20ConfigMgr%20reports%20folder.%3CBR%20%2F%3ENot%20like%3A%26nbsp%3B%3CSPAN%3E-ReportServerURI%20%22%3CA%20href%3D%22http%3A%2F%2Fclhqsm217%2FReports%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3Ehttp%3A%2F%2Fclhqsm217%2FReports%3C%2FA%3E%3C%2FSPAN%3E%3CSPAN%3E%2Fbrowse%2FConfigMgr_EUC%22%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%3CSPAN%3EInstead%20like%3A%26nbsp%3B-ReportServerURI%20%22%3CA%20href%3D%22http%3A%2F%2Fclhqsm217%2Freportserver%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3Ehttp%3A%2F%2Fclhqsm217%2Freportserver%3C%2FA%3E%22%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%3CSPAN%3EThe%20URI%20might%20be%20different%20if%20you%20changed%20it%20in%3A%20%22Report%20Server%20Configuration%20Manager%22.%20%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%3CSPAN%3EYou%20will%20find%20the%20actual%20URI%20in%20%22Report%20Server%20Configuration%20Manager%22%20under%20%22Web%20Service%20URL%22.%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2376985%22%20slang%3D%22en-US%22%3ERe%3A%20Mastering%20Configuration%20Manager%20Patch%20Compliance%20Reporting%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2376985%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20Jonasoh%2C%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThank%20you%20for%20creating%20this%20report%20and%20it's%20looking%20great.%20I%20uploaded%20this%20report%20to%20my%20MECM%20system%20without%20any%20problem%2C%20when%20I%20run%20compliance%20report%20against%20specified%20collection%2C%20I%20found%20out%20some%20client%20with%20same%20status%20as%20compliant%20clients%20(no%20red%20section)%20but%20they%20are%20located%20in%20uncompliant%20section.%20I%20couldn't%20figure%20out%20what%20causing%20the%20two%20client%20with%20same%20patches%20installation%20and%20compliance%20status%20but%20one%20is%20compliant%20and%20another%20isn't.%26nbsp%3B%3C%2FP%3E%3CP%3EI%20reviewed%20your%20%22patching%22%20compliance%20definition%20and%20believe%20the%20uncompliant%20machine%20should%20be%20in%20compliance%20client%20group%20instead%20of%20uncompliant.%20Do%20you%20have%20any%20idea%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks%20a%20lot%2C%3C%2FP%3E%3CP%3EGloria%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2620955%22%20slang%3D%22en-US%22%3ERe%3A%20Mastering%20Configuration%20Manager%20Patch%20Compliance%20Reporting%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2620955%22%20slang%3D%22en-US%22%3E%3CP%3EHello%20Jonasoh%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ECan%20you%20tell%20me%20what%20the%20required%20version%20of%20SSRS%20is%20for%20these%20to%20work%3F%20I%20get%20the%20following%20error%20when%20trying%20to%20install%20them%20via%20PowerShell.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EException%20calling%20%22CreateCatalogItem%22%20with%20%227%22%20argument(s)%3A%20%22System.Web.Services.Protocols.SoapException%3A%20The%20definition%20of%20this%20report%20is%20not%20valid%3CBR%20%2F%3Eor%20supported%20by%20this%20version%20of%20Reporting%20Services.%20The%20report%20definition%20may%20have%20been%20created%20with%20a%20later%20version%20of%20Reporting%20Services%2C%20or%3CBR%20%2F%3Econtain%20content%20that%20is%20not%20well-formed%20or%20not%20valid%20based%20on%20Reporting%20Services%20schemas.%20Details%3A%20The%20report%20definition%20has%20an%20invalid%20target%3CBR%20%2F%3Enamespace%20'%3CA%20href%3D%22http%3A%2F%2Fschemas.microsoft.com%2Fsqlserver%2Freporting%2F2016%2F01%2Freportdefinition%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttp%3A%2F%2Fschemas.microsoft.com%2Fsqlserver%2Freporting%2F2016%2F01%2Freportdefinition%3C%2FA%3E'%20which%20cannot%20be%20upgraded.%3CBR%20%2F%3Eat%20Microsoft.ReportingServices.Library.ReportingService2010Impl.CreateReport(String%20Report%2C%20String%20Parent%2C%20Boolean%20Overwrite%2C%20Byte%5B%5D%20Definition%2C%3CBR%20%2F%3EProperty%5B%5D%20Properties%2C%20ItemType%20ItemType%2C%20CatalogItem%26amp%3B%20ItemInfo%2C%20Warning%5B%5D%26amp%3B%20Warnings)%3CBR%20%2F%3Eat%20Microsoft.ReportingServices.Library.ReportingService2010Impl.CreateCatalogItem(String%20ItemType%2C%20String%20Name%2C%20String%20Parent%2C%20Boolean%20Overwrite%2C%3CBR%20%2F%3EByte%5B%5D%20Definition%2C%20Property%5B%5D%20Properties%2C%20CatalogItem%26amp%3B%20ItemInfo%2C%20Warning%5B%5D%26amp%3B%20Warnings)%3CBR%20%2F%3Eat%20Microsoft.ReportingServices.WebServer.ReportingService2010.CreateCatalogItem(String%20ItemType%2C%20String%20Name%2C%20String%20Parent%2C%20Boolean%20Overwrite%2C%3CBR%20%2F%3EByte%5B%5D%20Definition%2C%20Property%5B%5D%20Properties%2C%20CatalogItem%26amp%3B%20ItemInfo%2C%20Warning%5B%5D%26amp%3B%20Warnings)%22%3CBR%20%2F%3EAt%20C%3A%5CUsers%5Cda_mpeterson.HSHSAD%5CDesktop%5Cupdatereporting-master%5Cupdatereporting-master%5CImport-SSRSReports.ps1%3A246%20char%3A17%3CBR%20%2F%3E%2B%20%24null%20%3D%20%24ReportServerConnection.CreateCatalogItem(%3CBR%20%2F%3E%2B%20~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~%3CBR%20%2F%3E%2B%20CategoryInfo%20%3A%20NotSpecified%3A%20(%3A)%20%5B%5D%2C%20MethodInvocationException%3CBR%20%2F%3E%2B%20FullyQualifiedErrorId%20%3A%20SoapException%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAny%20help%20would%20be%20appreciated%2C%20thanks!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2693728%22%20slang%3D%22en-US%22%3ERe%3A%20Mastering%20Configuration%20Manager%20Patch%20Compliance%20Reporting%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2693728%22%20slang%3D%22en-US%22%3E%3CP%3EHi%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F1060338%22%20target%3D%22_blank%22%3E%40webcat123%3C%2FA%3E%26nbsp%3BI%20will%20release%20a%20new%20version%20of%20the%20report%20framework%20in%20a%20few%20days.%20That%20should%20give%20you%20more%20details%20about%20why%20a%20system%20is%20marked%20as%20uncompliant.%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EHi%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F1122387%22%20target%3D%22_blank%22%3E%40Agr8lemon%3C%2FA%3E%26nbsp%3Bthe%20reports%20are%20build%20with%20Report%20Builder%20version%202016%20and%202017%20and%20contain%20a%20mix%20of%20those%20two%20schemas%3A%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSPAN%3E'%3C%2FSPAN%3E%3CA%20href%3D%22http%3A%2F%2Fschemas.microsoft.com%2Fsqlserver%2Freporting%2F2016%2F01%2Freportdefinition%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttp%3A%2F%2Fschemas.microsoft.com%2Fsqlserver%2Freporting%2F%3CSTRONG%3E2010%3C%2FSTRONG%3E%2F01%2Freportdefinition%3C%2FA%3E%3CSPAN%3E'%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%3CSPAN%3E'%3CA%20href%3D%22http%3A%2F%2Fschemas.microsoft.com%2Fsqlserver%2Freporting%2F2016%2F01%2Freportdefinition%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttp%3A%2F%2Fschemas.microsoft.com%2Fsqlserver%2Freporting%2F%3CSTRONG%3E2016%3C%2FSTRONG%3E%2F01%2Freportdefinition%3C%2FA%3E'%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3EAs%20stated%20in%20the%26nbsp%3B%22Some%20key%20facts%20and%20prerequesites%22%20section%20(last%20two%20lines)%20you%20can%20force%20the%20older%20schema%20(2010)%20by%20using%20the%20%22-ForceLegacyFormat%22%20parameter.%3CBR%20%2F%3EIn%20case%20you%20want%20to%20upload%20the%20reports%20to%20PowerBI%20report%20server%20you%20have%20to%20do%20that%20manually%20as%20the%20upload%20script%20is%20not%20PowerBI%20aware%20at%20the%20moment.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2752018%22%20slang%3D%22en-US%22%3ERe%3A%20Mastering%20Configuration%20Manager%20Patch%20Compliance%20Reporting%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2752018%22%20slang%3D%22en-US%22%3E%3CP%3EHi%26nbsp%3B%3CSPAN%3EJonasoh%2C%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EGreat%20report%20but%20the%20statistic%20I%20am%20having%20issues%20with%20is%20the%20top%20bar%20graph%20(Update%20Compliance)%20which%20is%20showing%20100%25%20uncompliant%20but%20I%20know%20this%20should%20be%20partially%20compliant%2C%20where%20is%20it%20pulling%20this%20information%20from%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%22MECM.JPG%22%20style%3D%22width%3A%20999px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F310526i1902969F9BDB527A%2Fimage-size%2Flarge%3Fv%3Dv2%26amp%3Bpx%3D999%22%20role%3D%22button%22%20title%3D%22MECM.JPG%22%20alt%3D%22MECM.JPG%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1415088%22%20slang%3D%22en-US%22%3EMastering%20Configuration%20Manager%20Patch%20Compliance%20Reporting%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1415088%22%20slang%3D%22en-US%22%3E%3CH3%20id%3D%22toc-hId-1168509738%22%20id%3D%22toc-hId-1168509761%22%20id%3D%22toc-hId-1168509761%22%20id%3D%22toc-hId-1168509761%22%20id%3D%22toc-hId-1168509761%22%20id%3D%22toc-hId-1168509761%22%20id%3D%22toc-hId-1168509761%22%20id%3D%22toc-hId-1168509761%22%20id%3D%22toc-hId-1168509761%22%20id%3D%22toc-hId-1168509761%22%20id%3D%22toc-hId-1168509761%22%20id%3D%22toc-hId-1168509761%22%20id%3D%22toc-hId-1168509761%22%20id%3D%22toc-hId-1168509761%22%20id%3D%22toc-hId-1168509761%22%20id%3D%22toc-hId-1168509761%22%3E%3CSTRONG%3EHi%2C%20Jonas%20here!%3C%2FSTRONG%3E%3C%2FH3%3E%0A%3CP%3EOr%20as%20we%20say%20in%20the%20north%20of%20Germany%3A%26nbsp%3B%3CSTRONG%3E%22%3CSPAN%3EMoin%3C%2FSPAN%3E%20%3CSPAN%3EMoin%3C%2FSPAN%3E!%22%3C%2FSTRONG%3E%3CBR%20%2F%3EI%20am%20a%20Microsoft%20Customer%20Engineer%20(CE%26nbsp%3Bformerly%20known%20as%20PFE)%20and%20a%20while%20back%20(years%20in%20fact)%20I%20was%20asked%20to%20analyze%20the%20update%20compliance%20status%20of%20a%20SCCM%2F%3CSPAN%3EConfigMgr%3C%2FSPAN%3E%2FMECM%20environment.%20I%20will%20use%20the%20current%20name%3A%20%22Microsoft%20Endpoint%20Configuration%20Manager%22%20(MECM)%20in%20the%20rest%20of%20the%20blog.%3CBR%20%2F%3EI%20used%20different%20reports%20to%20look%20for%20clients%20not%20installing%20the%20necessary%20updates%2C%20but%20it%20was%20time%20consuming%20and%20I%20was%20missing%20a%20general%20overview%20with%20some%20meaningful%20KPIs.%20I%20ended%20up%20with%20a%20comprehensive%20SQL%20query%20and%20an%20Excel%20sheet%2C%20but%20changed%20that%20to%20a%20SQL%20Server%20Reporting%20Services%20(SSRS)%20report.%20I%20than%20made%20that%20available%20to%20several%20departments%20in%20the%20organization.%3CBR%20%2F%3EAs%20mentioned%20before%2C%20it's%20been%20a%20while%20since%20I%20created%20the%20report.%20If%20I%20were%20to%20start%20now%20it%20would%20be%20a%20%3CSPAN%3EPowerBI%3C%2FSPAN%3E%20version%20or%20I%20would%20simply%20grab%20one%20of%20the%20%3CSPAN%3EPowerBI%3C%2FSPAN%3E%20reports%20available%20from%20the%20MECM%20community.%20But%20since%20I%20still%20use%20the%20report%20and%20find%20it%20quite%20helpful%2C%20I%20decided%20to%20share%20that%20with%20the%20rest%20of%20the%20world.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CH3%20id%3D%22toc-hId--638944725%22%20id%3D%22toc-hId--638944702%22%20id%3D%22toc-hId--638944702%22%20id%3D%22toc-hId--638944702%22%20id%3D%22toc-hId--638944702%22%20id%3D%22toc-hId--638944702%22%20id%3D%22toc-hId--638944702%22%20id%3D%22toc-hId--638944702%22%20id%3D%22toc-hId--638944702%22%20id%3D%22toc-hId--638944702%22%20id%3D%22toc-hId--638944702%22%20id%3D%22toc-hId--638944702%22%20id%3D%22toc-hId--638944702%22%20id%3D%22toc-hId--638944702%22%20id%3D%22toc-hId--638944702%22%20id%3D%22toc-hId--638944702%22%3E%3CSPAN%3E%3CSTRONG%3EUpdated%20version%3C%2FSTRONG%3E%3C%2FSPAN%3E%3C%2FH3%3E%0A%3CP%3E%3CSPAN%3EI%20recently%20updated%20the%20whole%20solution%20and%20changed%20it%20significantly.%20I%20added%20descriptive%20text%20to%20each%20column%20header%2C%20added%20~400%20common%20WSUS%20errors%20and%20changed%20the%20overall%20compliance%20criteria%20for%20example.%20I%20also%20updated%20this%20blog%20to%20reflect%20those%20changes.%20So%2C%20if%20you%20read%20it%20before%2C%20you%20might%20need%20to%20read%20it%20again%20%3B)%3C%2Fimg%3E%3CBR%20%2F%3E(Use%20the%20table%20of%20contents%20to%20jump%20to%20the%20summary%20of%20changes%20directly%20if%20you%20want)%3CBR%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CH3%20id%3D%22toc-hId-1848568108%22%20id%3D%22toc-hId-1848568131%22%20id%3D%22toc-hId-1848568131%22%20id%3D%22toc-hId-1848568131%22%20id%3D%22toc-hId-1848568131%22%20id%3D%22toc-hId-1848568131%22%20id%3D%22toc-hId-1848568131%22%20id%3D%22toc-hId-1848568131%22%20id%3D%22toc-hId-1848568131%22%20id%3D%22toc-hId-1848568131%22%20id%3D%22toc-hId-1848568131%22%20id%3D%22toc-hId-1848568131%22%20id%3D%22toc-hId-1848568131%22%20id%3D%22toc-hId-1848568131%22%20id%3D%22toc-hId-1848568131%22%20id%3D%22toc-hId-1848568131%22%3E%3CSTRONG%3ETable%20of%20contents%3A%3C%2FSTRONG%3E%3C%2FH3%3E%0A%3CP%3E%3CA%20href%3D%22%23TRDR%22%20target%3D%22_self%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3ETR%3ADR%3C%2FA%3E%3CBR%20%2F%3E%3CA%20href%3D%22%23ReportExplained%22%20target%3D%22_self%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3EThe%20report%20explained%3C%2FA%3E%3CBR%20%2F%3E%3CA%20href%3D%22%23FirstSubReport%22%20target%3D%22_self%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3E1st%20sub-reports%20(list%20of%20systems)%3C%2FA%3E%3CBR%20%2F%3E%3CA%20href%3D%22%23SecondSubReport%22%20target%3D%22_self%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3E2nd%20sub-report%20(per%20system)%3C%2FA%3E%3C%2FP%3E%0A%3CP%3E%3CA%20href%3D%22%23ThirdSubReport%22%20target%3D%22_self%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3E3rd%20sub-report%20(errorlist)%3C%2FA%3E%3C%2FP%3E%0A%3CP%3E%3CA%20href%3D%22%23FourthSubReport%22%20target%3D%22_self%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3E4th%20sub-report%20(deployments%20per%20system)%3C%2FA%3E%3C%2FP%3E%0A%3CP%3E%3CA%20href%3D%22%23UpdatesApproved%22%20target%3D%22_self%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3E5th%20sub-Report%20(updates%20approved)%3C%2FA%3E%3CBR%20%2F%3E%3CA%20href%3D%22%23KeyFacts%22%20target%3D%22_self%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3ESome%20key%20facts%20and%20prerequisites%3A%3C%2FA%3E%3CBR%20%2F%3E%3CA%20href%3D%22%23HowToInstall%22%20target%3D%22_self%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3EHow%20to%20install%3C%2FA%3E%3CBR%20%2F%3E%3CA%20href%3D%22%23ScriptParameters%22%20target%3D%22_self%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3EScript%20Parameters%3C%2FA%3E%3CBR%20%2F%3E%3CA%20href%3D%22%23ScriptExamples%22%20target%3D%22_self%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3EScript%20Examples%3C%2FA%3E%3C%2FP%3E%0A%3CP%3E%3CA%20href%3D%22%23DataCaching%22%20target%3D%22_self%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3EActivate%20report%20data%20caching%3C%2FA%3E%3CBR%20%2F%3E%3CA%20href%3D%22%23AdditionalReport%22%20target%3D%22_self%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3EAdditional%20report%3C%2FA%3E%3CBR%20%2F%3E%3CA%20href%3D%22%23Disclaimer%22%20target%3D%22_self%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3EDisclaimer%3C%2FA%3E%3CBR%20%2F%3E%3CA%20href%3D%22%23Resources%22%20target%3D%22_self%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3EResources%3C%2FA%3E%3CBR%20%2F%3E%3CA%20href%3D%22%23Changes%22%20target%3D%22_self%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3EChanges%3C%2FA%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CH3%20id%3D%22TRDR%22%20id%3D%22toc-hId-41113645%22%20id%3D%22toc-hId-41113668%22%20id%3D%22toc-hId-41113668%22%20id%3D%22toc-hId-41113668%22%20id%3D%22toc-hId-41113668%22%20id%3D%22toc-hId-41113668%22%20id%3D%22toc-hId-41113668%22%20id%3D%22toc-hId-41113668%22%20id%3D%22toc-hId-41113668%22%20id%3D%22toc-hId-41113668%22%20id%3D%22toc-hId-41113668%22%20id%3D%22toc-hId-41113668%22%20id%3D%22toc-hId-41113668%22%20id%3D%22toc-hId-41113668%22%20id%3D%22toc-hId-41113668%22%20id%3D%22toc-hId-41113668%22%3E%3CSPAN%3E%3CSTRONG%3ETL%3BDR%3C%2FSTRONG%3E%3C%2FSPAN%3E%3C%2FH3%3E%0A%3CP%3EThe%20following%20report%20should%20help%20you%20identify%20update%20problems%20within%20a%20specific%20collection%20and%20a%20group%20of%20systems%20and%20is%20designed%20to%20work%20well%20for%20a%20few%20thousand%20clients.%20The%20query%20might%20run%20longer%20in%20bigger%20environments%20and%20you%20might%20need%20to%20improve%20it%20or%20run%20it%20not%20within%20business%20hours%20to%20show%20results.%3CBR%20%2F%3EThe%20installation%20guide%20for%20the%20custom%20update%20reporting%20can%20be%20found%20at%20the%20end%20of%20this%20post%20but%20you%20should%20at%20least%20start%20with%20the%20%22Some%20key%20facts%20and%20prerequisites%22%20section.%3CBR%20%2F%3EIf%20you're%20just%20looking%20for%20the%20SQL%20statement%20behind%20the%20report%2C%20copy%20the%20query%20from%20the%20%22%3CSPAN%3EUpdatesSummary.sql%3C%2FSPAN%3E%22%20file%20and%20use%20it%20in%20SQL%20directly.%3CBR%20%2F%3EThe%20whole%20solution%20can%20be%20found%20on%20GitHub%3A%20%3CA%20href%3D%22https%3A%2F%2Fgithub.com%2Fjonasatgit%2Fupdatereporting%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttps%3A%2F%2Fgithub.com%2Fjonasatgit%2Fupdatereporting%3C%2FA%3E%3CSPAN%3E%3CBR%20%2F%3E%3C%2FSPAN%3EFeel%20free%20to%20improve%20the%20SQL%20queries%20or%20some%20of%20the%20reports%20on%20%3CSPAN%3EGithub%3C%2FSPAN%3E.%20%3CBR%20%2F%3EIf%20you%20are%20a%20Premier%20customer%20and%20if%20you%20are%20looking%20for%20a%20more%20complete%20reporting%20solution%2C%20ask%20your%20Microsoft%20contact%20about%20the%20following%20offerings%3A%3CBR%20%2F%3E%22Microsoft%20Endpoint%20Configuration%20Manager%3A%20Advanced%20Dashboards%22%3CBR%20%2F%3E%22Microsoft%20Endpoint%20Manager%3A%20PowerBI%20Dashboard%20Integration%22%3C%2FP%3E%0A%3CP%3E%22Modern%20Workplace%20Compliance%20Reporting%22%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CH3%20id%3D%22ReportExplained%22%20id%3D%22toc-hId--1766340818%22%20id%3D%22toc-hId--1766340795%22%20id%3D%22toc-hId--1766340795%22%20id%3D%22toc-hId--1766340795%22%20id%3D%22toc-hId--1766340795%22%20id%3D%22toc-hId--1766340795%22%20id%3D%22toc-hId--1766340795%22%20id%3D%22toc-hId--1766340795%22%20id%3D%22toc-hId--1766340795%22%20id%3D%22toc-hId--1766340795%22%20id%3D%22toc-hId--1766340795%22%20id%3D%22toc-hId--1766340795%22%20id%3D%22toc-hId--1766340795%22%20id%3D%22toc-hId--1766340795%22%20id%3D%22toc-hId--1766340795%22%20id%3D%22toc-hId--1766340795%22%3E%3CSTRONG%3EThe%20report%20explained%3A%3C%2FSTRONG%3E%3C%2FH3%3E%0A%3CP%3EThe%20main%20report%20dashboard%20looks%20like%20this%3A%3C%2FP%3E%0A%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%22Dashboard-B.png%22%20style%3D%22width%3A%20952px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F306293i456F684E76E4FA80%2Fimage-size%2Flarge%3Fv%3Dv2%26amp%3Bpx%3D999%22%20role%3D%22button%22%20title%3D%22Dashboard-B.png%22%20alt%3D%22Figure%201%3A%20Main%20update%20compliance%20dashboard%22%20%2F%3E%3CSPAN%20class%3D%22lia-inline-image-caption%22%20onclick%3D%22event.preventDefault()%3B%22%3EFigure%201%3A%20Main%20update%20compliance%20dashboard%3C%2FSPAN%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSPAN%20style%3D%22font-family%3A%20inherit%3B%22%3EI%20used%20different%20KPIs%20to%20measure%20update%20compliance%20and%20the%20report%20combines%20all%20that%20into%20one%20dashboard.%20The%20main%20KPI%20is%20the%20first%20bar%20and%20all%20the%20others%20should%20simply%20help%20identify%20patch%20problems%20or%20flaws%20in%20your%20deployment%20strategy.%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3EThe%20report%20also%20has%20five%20sub-reports.%20One%20to%20show%20you%20a%20list%20of%20systems%20in%20a%20specific%20state%20(1st%20sub-report).%20One%20for%20a%20list%20of%20missing%20updates%20for%20a%20single%20system%20(2nd%20sub-report).%26nbsp%3B%20One%20sub-report%20(3rd%20sub-report)%20to%20show%20you%20a%20list%20of%20update%20installation%20errors%20or%20WSUS%20scan%20errors.%20One%20sub-report%20for%20all%20update%20deployment-states%20per%20system%20(deployments%20per%20system)%20and%20the%20last%20report%20(Updates%20Approved)%20shows%20you%20the%20NOT%20deployed%20%2F%20approved%20updates%20a%20system%20is%20still%20missing.%3C%2FP%3E%0A%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%22UpdateReporting001-level.PNG%22%20style%3D%22width%3A%20999px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F194166i7338894301E8AF68%2Fimage-size%2Flarge%3Fv%3Dv2%26amp%3Bpx%3D999%22%20role%3D%22button%22%20title%3D%22UpdateReporting001-level.PNG%22%20alt%3D%22Figure%202%3A%20Simplified%20view%20of%20report%20dependencies%22%20%2F%3E%3CSPAN%20class%3D%22lia-inline-image-caption%22%20onclick%3D%22event.preventDefault()%3B%22%3EFigure%202%3A%20Simplified%20view%20of%20report%20dependencies%3C%2FSPAN%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CH3%20id%3D%22FirstSubReport%22%20id%3D%22toc-hId-721172015%22%20id%3D%22toc-hId-721172038%22%20id%3D%22toc-hId-721172038%22%20id%3D%22toc-hId-721172038%22%20id%3D%22toc-hId-721172038%22%20id%3D%22toc-hId-721172038%22%20id%3D%22toc-hId-721172038%22%20id%3D%22toc-hId-721172038%22%20id%3D%22toc-hId-721172038%22%20id%3D%22toc-hId-721172038%22%20id%3D%22toc-hId-721172038%22%20id%3D%22toc-hId-721172038%22%20id%3D%22toc-hId-721172038%22%20id%3D%22toc-hId-721172038%22%20id%3D%22toc-hId-721172038%22%20id%3D%22toc-hId-721172038%22%3E%3CSTRONG%3E1%3CSUP%3Est%3C%2FSUP%3E%20sub-reports%20(list%20of%20systems)%3C%2FSTRONG%3E%3C%2FH3%3E%0A%3CP%3EAlmost%20each%20bar%20or%20pie%20chart%20links%20to%20a%20sub-report%20to%20show%20compliance%20state%20of%20that%20subset%20of%20systems%20to%20give%20you%20better%20visibility.%20This%20is%20an%20example%20of%20all%20the%20uncompliant%20systems%20from%20the%20first%20bar%20in%20the%20dashboard%20and%20is%20basically%20what%20the%20Excel%20list%20looked%20like%20in%20the%20early%20days%3A%3C%2FP%3E%0A%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%22ComplianceList-B.png%22%20style%3D%22width%3A%20999px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F306295i0A77DA709EED1433%2Fimage-size%2Flarge%3Fv%3Dv2%26amp%3Bpx%3D999%22%20role%3D%22button%22%20title%3D%22ComplianceList-B.png%22%20alt%3D%22Figure%203%3A%20List%20of%20all%20uncompliant%20systems%22%20%2F%3E%3CSPAN%20class%3D%22lia-inline-image-caption%22%20onclick%3D%22event.preventDefault()%3B%22%3EFigure%203%3A%20List%20of%20all%20uncompliant%20systems%3C%2FSPAN%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3EIf%20you%20click%20on%20different%20bar%20or%20pie%20charts%2C%20the%20same%20sub-report%20will%20be%20opened%2C%20but%20the%20data%20will%20be%20filtered%20depending%20on%20which%20bar%20or%20pie%20chart%20you%20clicked.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CH3%20id%3D%22SecondSubReport%22%20id%3D%22toc-hId--1086282448%22%20id%3D%22toc-hId--1086282425%22%20id%3D%22toc-hId--1086282425%22%20id%3D%22toc-hId--1086282425%22%20id%3D%22toc-hId--1086282425%22%20id%3D%22toc-hId--1086282425%22%20id%3D%22toc-hId--1086282425%22%20id%3D%22toc-hId--1086282425%22%20id%3D%22toc-hId--1086282425%22%20id%3D%22toc-hId--1086282425%22%20id%3D%22toc-hId--1086282425%22%20id%3D%22toc-hId--1086282425%22%20id%3D%22toc-hId--1086282425%22%20id%3D%22toc-hId--1086282425%22%20id%3D%22toc-hId--1086282425%22%20id%3D%22toc-hId--1086282425%22%3E%3CSTRONG%3E2%3CSUP%3End%3C%2FSUP%3E%20sub-report%20(per%20system)%3C%2FSTRONG%3E%3C%2FH3%3E%0A%3CP%3EIf%20you%20click%20on%20a%20system%20name%20a%20system%20specific%20report%20will%20open.%20The%20list%20of%20updates%20of%20that%20report%20will%20be%20filtered%20for%20the%20specific%20need.%20For%20example%2C%20if%20you%20click%20on%20%E2%80%9Cmissing%20updates%20approved%E2%80%9D%20just%20the%20approved%20and%20missing%20updates%20will%20be%20visible.%20The%20report%20also%20shows%20installations%20errors%20if%20any%20happened.%20Each%20error%20will%20link%20to%20a%20Bing%20search%20with%20the%20hex%20value%20of%20the%20error.%20The%20search%20string%20looks%20like%20this%3A%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fwww.bing.com%2Fsearch%3Fq%3Derror%2B0x80070005%22%20target%3D%22_blank%22%20rel%3D%22noopener%20nofollow%20noreferrer%22%3E%3CSTRONG%3E%3CEM%3Ehttps%3A%2F%2Fwww.bing.com%2Fsearch%3Fq%3Derror%2B0x80070005%3C%2FEM%3E%3C%2FSTRONG%3E%3C%2FA%3E%3CBR%20%2F%3EThe%20report%20is%20basically%20a%20copy%20of%20one%20of%20the%20default%20MECM%20reports%20with%20some%20adjustments%20and%20some%20custom%20filters%20to%20filter%20for%20%E2%80%9CDeployed%20and%20missing%20updates%E2%80%9D%2C%20%E2%80%9CNot%20deployed%20but%20missing%E2%80%9D%2C%20%22Missing%20updates%20with%20errors%22%2C%20%E2%80%9CAll%20missing%20updates%20deployed%20or%20not%E2%80%9D%20or%20just%20%E2%80%9CAll%20updates%20per%20device.%3C%2FP%3E%0A%3CP%3EIt%20also%20contains%20update%20collections%20and%20maintenance%20windows%20to%20help%20identify%20missing%20or%20wrong%20collection%20memberships%3A%3C%2FP%3E%0A%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%22PerDevice-B.png%22%20style%3D%22width%3A%20999px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F306296i198E4DF89B05042C%2Fimage-size%2Flarge%3Fv%3Dv2%26amp%3Bpx%3D999%22%20role%3D%22button%22%20title%3D%22PerDevice-B.png%22%20alt%3D%22Figure%204%3A%20Per%20device%20update%20compliance%20report%22%20%2F%3E%3CSPAN%20class%3D%22lia-inline-image-caption%22%20onclick%3D%22event.preventDefault()%3B%22%3EFigure%204%3A%20Per%20device%20update%20compliance%20report%3C%2FSPAN%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CH3%20id%3D%22ThirdSubReport%22%20id%3D%22toc-hId-1401230385%22%20id%3D%22toc-hId-1401230408%22%20id%3D%22toc-hId-1401230408%22%20id%3D%22toc-hId-1401230408%22%20id%3D%22toc-hId-1401230408%22%20id%3D%22toc-hId-1401230408%22%20id%3D%22toc-hId-1401230408%22%20id%3D%22toc-hId-1401230408%22%20id%3D%22toc-hId-1401230408%22%20id%3D%22toc-hId-1401230408%22%20id%3D%22toc-hId-1401230408%22%20id%3D%22toc-hId-1401230408%22%20id%3D%22toc-hId-1401230408%22%20id%3D%22toc-hId-1401230408%22%20id%3D%22toc-hId-1401230408%22%20id%3D%22toc-hId-1401230408%22%3E%3CSTRONG%3E3%3CSUP%3Erd%3C%2FSUP%3E%20sub-report%20(errorlist)%3C%2FSTRONG%3E%3C%2FH3%3E%0A%3CP%3EIf%20you%20either%20click%20on%20the%20%E2%80%9CWSUS-Scan%20Error%E2%80%9D%20or%20%E2%80%9CSystems%20with%20install%20error%E2%80%9D%20bar%20a%20list%20with%20errors%20will%20be%20visible%20as%20shown%20in%20the%20screenshot%20below%3A%3C%2FP%3E%0A%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%22WSUSScanError-B.png%22%20style%3D%22width%3A%20999px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F306298iFD151AAB1E887E22%2Fimage-size%2Flarge%3Fv%3Dv2%26amp%3Bpx%3D999%22%20role%3D%22button%22%20title%3D%22WSUSScanError-B.png%22%20alt%3D%22Figure%205%3A%20List%20of%20WSUS%20scan%20errors%22%20%2F%3E%3CSPAN%20class%3D%22lia-inline-image-caption%22%20onclick%3D%22event.preventDefault()%3B%22%3EFigure%205%3A%20List%20of%20WSUS%20scan%20errors%3C%2FSPAN%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3EThe%20report%20contains%20around%20400%20possible%20WSUS%20errors%2C%20tips%20and%20links%20to%20give%20you%20a%20troubleshooting%20starting%20point.%20It%20might%20not%20be%20a%20complete%20list%2C%20but%20it%20should%20cover%20the%20most%20common%20errors.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CH3%20id%3D%22FourthSubReport%22%20id%3D%22toc-hId--406224078%22%20id%3D%22toc-hId--406224055%22%20id%3D%22toc-hId--406224055%22%20id%3D%22toc-hId--406224055%22%20id%3D%22toc-hId--406224055%22%20id%3D%22toc-hId--406224055%22%20id%3D%22toc-hId--406224055%22%20id%3D%22toc-hId--406224055%22%20id%3D%22toc-hId--406224055%22%20id%3D%22toc-hId--406224055%22%20id%3D%22toc-hId--406224055%22%20id%3D%22toc-hId--406224055%22%20id%3D%22toc-hId--406224055%22%20id%3D%22toc-hId--406224055%22%20id%3D%22toc-hId--406224055%22%20id%3D%22toc-hId--406224055%22%3E%3CSTRONG%3E4th%20sub-report%20(deployments%20per%20system)%3C%2FSTRONG%3E%3C%2FH3%3E%0A%3CP%3EThe%20fourth%20sub-report%20is%20a%20simple%20list%20of%20update%20deployments%20and%20their%20state%20and%20some%20other%20useful%20information%20per%20system.%26nbsp%3B%3C%2FP%3E%0A%3CP%3EIt%20can%20be%20either%20be%20opened%20directly%20or%20if%20you%20click%20on%20the%20%22Deployments%20non%20compliant%22%20row%20of%20the%20first%20sub-report.%3C%2FP%3E%0A%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%22PerDeviceDeployments-B.png%22%20style%3D%22width%3A%20999px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F306303i320EAE23D9A0E3ED%2Fimage-size%2Flarge%3Fv%3Dv2%26amp%3Bpx%3D999%22%20role%3D%22button%22%20title%3D%22PerDeviceDeployments-B.png%22%20alt%3D%22Figure%206%3A%20Update%20deployment-states%20per%20device%22%20%2F%3E%3CSPAN%20class%3D%22lia-inline-image-caption%22%20onclick%3D%22event.preventDefault()%3B%22%3EFigure%206%3A%20Update%20deployment-states%20per%20device%3C%2FSPAN%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CH3%20id%3D%22UpdatesApproved%22%20id%3D%22toc-hId-2081288755%22%20id%3D%22toc-hId-2081288778%22%20id%3D%22toc-hId-2081288778%22%20id%3D%22toc-hId-2081288778%22%20id%3D%22toc-hId-2081288778%22%20id%3D%22toc-hId-2081288778%22%20id%3D%22toc-hId-2081288778%22%20id%3D%22toc-hId-2081288778%22%20id%3D%22toc-hId-2081288778%22%20id%3D%22toc-hId-2081288778%22%20id%3D%22toc-hId-2081288778%22%20id%3D%22toc-hId-2081288778%22%20id%3D%22toc-hId-2081288778%22%20id%3D%22toc-hId-2081288778%22%20id%3D%22toc-hId-2081288778%22%20id%3D%22toc-hId-2081288778%22%3E%3CSTRONG%3E5th%20sub-report%20(updates%20approved)%3C%2FSTRONG%3E%3C%2FH3%3E%0A%3CP%3EIf%20you%20click%20on%20the%20yellow%20%E2%80%9CUpdates%20Approved%E2%80%9D%20bar%20a%20report%20shows%20you%20all%20the%20updates%20the%20selected%20systems%20are%20still%20missing%2C%20which%20are%20NOT%20yet%20approved%20%2F%20deployed.%3C%2FP%3E%0A%3CP%3EThe%20report%20should%20help%20identify%20problems%20with%20the%20selection%20of%20updates%20in%20your%20deployments.%3C%2FP%3E%0A%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%22ApprovedUpdates-B.png%22%20style%3D%22width%3A%20999px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F306299i32701BFA0DA96C12%2Fimage-size%2Flarge%3Fv%3Dv2%26amp%3Bpx%3D999%22%20role%3D%22button%22%20title%3D%22ApprovedUpdates-B.png%22%20alt%3D%22Figure%207%3A%20Report%20of%20missing%20updates%20not%20yet%20approved%22%20%2F%3E%3CSPAN%20class%3D%22lia-inline-image-caption%22%20onclick%3D%22event.preventDefault()%3B%22%3EFigure%207%3A%20Report%20of%20missing%20updates%20not%20yet%20approved%3C%2FSPAN%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CH3%20id%3D%22KeyFacts%22%20id%3D%22toc-hId--421329187%22%20id%3D%22toc-hId--421329164%22%20id%3D%22toc-hId--421329164%22%20id%3D%22toc-hId--421329164%22%20id%3D%22toc-hId--421329164%22%20id%3D%22toc-hId--421329164%22%20id%3D%22toc-hId--421329164%22%20id%3D%22toc-hId--421329164%22%20id%3D%22toc-hId--421329164%22%20id%3D%22toc-hId--421329164%22%20id%3D%22toc-hId--421329164%22%20id%3D%22toc-hId--421329164%22%20id%3D%22toc-hId--421329164%22%20id%3D%22toc-hId--421329164%22%20id%3D%22toc-hId--421329164%22%20id%3D%22toc-hId--421329164%22%3E%3CSTRONG%3ESome%20key%20facts%20and%20prerequisites%3A%3C%2FSTRONG%3E%3C%2FH3%3E%0A%3CUL%3E%0A%3CLI%3E%3CSTRONG%3EThe%20report%20is%20made%20to%20show%20the%20update%20compliance%20status%20of%20members%20of%20a%20collection%20or%20multiple%20collections%3C%2FSTRONG%3E%20no%20matter%20what%20type%20of%20systems%20are%20a%20member%20or%20which%20or%20how%20many%20updates%20are%20deployed%20to%20each%20individual%20system.%20%3CSPAN%3ESo%2C%3C%2FSPAN%3E%20it%20can%20be%20a%20combined%20view%20over%20multiple%20deployments%20and%20not%20just%20one%20deployment.%3C%2FLI%3E%0A%3CLI%3E%3CSTRONG%3EThe%20report%20combines%20multiple%20deployments%20into%20one%20single%20view.%3C%2FSTRONG%3E%3CBR%20%2F%3EIf%20you%20have%20a%20simple%20group%20of%20systems%20and%20deploy%20every%20necessary%20update%20with%20one%20deployment%2C%20the%20deployment%20status%20might%20be%20enough%2C%20but%20if%20you%20have%20a%20more%20complex%20setup%2C%20you%20might%20want%20to%20see%20details%20based%20on%20a%20specific%20group%20of%20systems%20no%20matter%20if%2C%20how%20or%20how%20many%20updates%20are%20deployed%20to%20each%20system.%3C%2FLI%3E%0A%3CLI%3E%3CU%3E%3CSTRONG%3EI%20have%20defined%20%22compliant%22%20to%20be%20a%20system%20which%20has%3A%3C%2FSTRONG%3E%3C%2FU%3E%3CUL%3E%0A%3CLI%3Eall%20enabled%20update%20deployments%20set%20to%20compliant%20(see%20changes%20down%20below.%20Column%3A%20%22Deployments%20Non%20Compliant%22)%3C%2FLI%3E%0A%3CLI%3Ethe%20last%20security%20update%20installation%20in%20Win32_Quickfixengineering%20was%20in%20the%20current%20month%20(or%20the%20monthly%20security%20rollup.%20Column%3A%20%22Month%20Since%20Last%20Update%20Install%22)%3C%2FLI%3E%0A%3CLI%3EThe%20last%20or%20current%20security%20rollup%20is%20installed%20(see%20changes%20down%20below.%20Column%3A%20%22Last%20Rollup%20Status%22)%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3C%2FLI%3E%0A%3CLI%3E%3CSTRONG%3EThe%20report%20will%20all%20updates%20no%20matter%20if%20deployed%20as%20%22available%22%20or%20%22required%22.%3C%2FSTRONG%3E%3C%2FLI%3E%0A%3CLI%3E%3CSTRONG%3EThe%20report%20consists%20of%20multiple%20KPIs%3C%2FSTRONG%3E%20to%20indicate%20the%20update%20compliance%20or%20update%2Fclient%20health%20state%20and%20should%20give%20you%20an%20overview%20from%20different%20viewpoints%20to%20help%20identify%20problematic%20systems%20or%20a%20flaw%20in%20your%20patch%20strategy.%3C%2FLI%3E%0A%3CLI%3E%3CSTRONG%3EThe%20report%20will%20use%20data%20from%20WMI%20class%20Win32_QuickFixEngineering%3C%2FSTRONG%3E%20which%20needs%20to%20be%20enabled%20in%20the%20hardware%20inventory%20client%20settings.%20The%20class%20is%20only%20used%20to%20determine%20the%20latest%20or%20last%20cumulative%20update%20or%20A%20security%20update%20installation%20to%20identify%20systems%20which%20seem%20to%20be%20fine%20but%20%3CSPAN%3Eactually%20have%3C%2FSPAN%3E%20never%20installed%20anything.%3C%2FLI%3E%0A%3CLI%3E%3CSTRONG%3EThe%20report%20is%20also%20uses%26nbsp%3BLastLogonTimeStamp%3C%2FSTRONG%3E%20from%20AD%20System%20Discovery%20to%20visually%20show%20systems%20which%20have%20not%20logged%20on%20to%20the%20domain%20in%20a%20while%20and%20which%20might%20be%20disposed%20of%20already%20and%20could%20be%20deleted%20from%20the%20MECM%20database.%20If%20you%20don't%20use%20AD%20system%20discovery%20the%20report%20will%20show%20all%20systems%20of%20the%20specified%20collection%20as%20not%20compliant%20in%20the%20pie%20chart%20%22Last%20ADDS%20logon%3CSPAN%3E%22%20.%3C%2FSPAN%3E%3CUL%3E%0A%3CLI%3EAD%20system%20discovery%20is%20no%20hard%20requirement%20to%20run%20the%20report%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3C%2FLI%3E%0A%3CLI%3E%3CSTRONG%3EThe%20report%20does%20not%20show%20historical%20data%3C%2FSTRONG%3E%20and%20will%20always%20show%20the%20%3CSPAN%3Ecurrent%20status%3C%2FSPAN%3E.%20So%2C%20if%20you%20change%20a%20deployment%20in%20the%20middle%20of%20the%20month%2C%20the%20compliance%20percentage%20will%20drop%20almost%20immediately%20as%20it%20does%20with%20the%20deployment%20in%20MECM.%3C%2FLI%3E%0A%3CLI%3E%3CSTRONG%3EThe%20report%20has%20multiple%20sub-reports%3C%2FSTRONG%3E%20to%20drill%20further%20down%20and%20almost%20each%20report%20will%20use%20the%20same%20dataset%3CUL%3E%0A%3CLI%3ERead%20more%20about%20data%20caching%20down%20below%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3C%2FLI%3E%0A%3CLI%3E%3CSTRONG%3EThe%20SQL%20query%20of%20the%20dataset%20is%20made%20to%20filter%20out%20Defender%20Update%20Deployments%3C%2FSTRONG%3E%2C%20because%20they%20normally%20will%20be%20changed%20every%20x%20hours%20and%20could%20interfere%20with%20the%20overall%20compliance%20state%20and%20should%20be%20monitored%20with%20other%20reports.%3CBR%20%2F%3EYou%20can%20change%20that%20via%20the%20available%20report%20parameters.%20%26nbsp%3B%3C%2FLI%3E%0A%3CLI%3E%3CSTRONG%3EThe%202nd%20Level%20sub-report%20per%20system%20will%20also%20show%20Defender%20updates%3C%2FSTRONG%3E%2C%20even%20if%20they%20are%20filtered%20out%20on%20the%20dashboard%3C%2FLI%3E%0A%3CLI%3E%3CSTRONG%3EThe%20SQL%20query%20might%20run%20longer%20in%20bigger%20environments%3C%2FSTRONG%3E%20depending%20on%20SQL%20performance%20and%20SQL%20maintenance.%26nbsp%3BIn%20some%20cases%20one%20of%20the%20%E2%80%9CForceLegacyCardinality%E2%80%9D%20parameters%20can%20help%20to%20speed%20up%20the%20queries.%20(See%20parameter%20description%20down%20below)%3C%2FLI%3E%0A%3CLI%3E%3CSTRONG%3EThere%20are%20several%20sub-reports%20with%20the%20same%20look%20and%20feel%3C%2FSTRONG%3E%2C%20because%20it%20was%20simpler%20to%20copy%20the%20report%20and%20just%20change%20the%20filter%20for%20the%20specific%20need.%3C%2FLI%3E%0A%3CLI%3E%3CSTRONG%3EMost%20sub-reports%20will%20be%20hidden%20in%20SSRS%3C%2FSTRONG%3E%20to%20avoid%20direct%20use%20and%20keep%20the%20folder%20as%20clean%20as%20possible.%3C%2FLI%3E%0A%3CLI%3E%3CSTRONG%3EThe%20reports%20are%20made%20on%20SSRS%202017%3C%2FSTRONG%3E%20but%20can%20be%20converted%20to%20the%20older%20format%20using%20the%20%22ForceLegacyFormat%22%20parameter.%3C%2FLI%3E%0A%3CLI%3E%3CSTRONG%3EThe%20reports%20can%20be%20used%20on%20PowerBI%20Reporting%20Services%3C%2FSTRONG%3E%20if%20you%20upload%20them%20manually.%20Start%20with%20the%20%E2%80%9Crsd%E2%80%9D%20files%20from%20the%20%E2%80%9Cwork%E2%80%9D%20folder%20to%20avoid%20any%20errors.%26nbsp%3B%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3CH3%20id%3D%22toc-hId-2066183646%22%20id%3D%22toc-hId-2066183669%22%20id%3D%22toc-hId-2066183669%22%20id%3D%22toc-hId-2066183669%22%20id%3D%22toc-hId-2066183669%22%20id%3D%22toc-hId-2066183669%22%20id%3D%22toc-hId-2066183669%22%20id%3D%22toc-hId-2066183669%22%20id%3D%22toc-hId-2066183669%22%20id%3D%22toc-hId-2066183669%22%20id%3D%22toc-hId-2066183669%22%20id%3D%22toc-hId-2066183669%22%20id%3D%22toc-hId-2066183669%22%20id%3D%22toc-hId-2066183669%22%20id%3D%22toc-hId-2066183669%22%20id%3D%22toc-hId-2066183669%22%3E%26nbsp%3B%3C%2FH3%3E%0A%3CH3%20id%3D%22HowToInstall%22%20id%3D%22toc-hId-258729183%22%20id%3D%22toc-hId-258729206%22%20id%3D%22toc-hId-258729206%22%20id%3D%22toc-hId-258729206%22%20id%3D%22toc-hId-258729206%22%20id%3D%22toc-hId-258729206%22%20id%3D%22toc-hId-258729206%22%20id%3D%22toc-hId-258729206%22%20id%3D%22toc-hId-258729206%22%20id%3D%22toc-hId-258729206%22%20id%3D%22toc-hId-258729206%22%20id%3D%22toc-hId-258729206%22%20id%3D%22toc-hId-258729206%22%20id%3D%22toc-hId-258729206%22%20id%3D%22toc-hId-258729206%22%20id%3D%22toc-hId-258729206%22%3E%3CSPAN%3E%3CSTRONG%3EHow%3C%2FSTRONG%3E%3C%2FSPAN%3E%3CSTRONG%3E%20to%20install%3A%3C%2FSTRONG%3E%3C%2FH3%3E%0A%3COL%3E%0A%3CLI%3EIn%20case%20you%20used%20an%20older%20version%20of%20the%20solution%20before%2C%20delete%20and%20re-create%20the%20report%20folder%20in%20SSRS%20(or%20create%20a%20new%20one)%20and%20run%20the%20latest%20script%20again.%3C%2FLI%3E%0A%3CLI%3EMake%20sure%20you%20have%26nbsp%3B%3CSTRONG%3EWin32_Quickfixengineering%3C%2FSTRONG%3E%26nbsp%3Benabled%20in%20the%20client%20settings%20for%20hardware%20inventory%3C%2FLI%3E%0A%3CLI%3EYou%20could%20also%20use%20AD%20System%20Discovery%20to%20have%20further%20data%2C%20but%20%3CSPAN%3Ethat's%3C%2FSPAN%3E%20no%20hard%20requirement.%3C%2FLI%3E%0A%3CLI%3EEither%20clone%20the%20repository%20or%20download%20the%20whole%20content.%3C%2FLI%3E%0A%3CLI%3ECopy%20the%20whole%20content%20to%20the%20SQL%20Server%20Reporting%20Services%20Server%20(SSRS)%3C%2FLI%3E%0A%3CLI%3ECreate%20a%26nbsp%3B%3CSTRONG%3E%3CEM%3Enew%20folder%20on%20the%20report%20server%20%3CU%3Ewebsite%3C%2FU%3E%3C%2FEM%3E%3C%2FSTRONG%3E%26nbsp%3Bwhere%20the%20reports%20should%20be%20imported%20to.%3COL%3E%0A%3CLI%3EThe%20folder%20should%20be%20under%20the%20normal%20MECM%20folder%20(normally%20called%20%3CSPAN%3EConfigMgr%3C%2FSPAN%3E_%5BSITECODE%5D)%2C%20but%20it%20can%20also%20be%20at%20the%20root%20level%20of%20your%20Reporting%20Services%20Server.%20But%20keep%20in%20mind%20that%20report%20subscriptions%20are%20only%20visible%20in%20the%20MECM%20console%2C%20if%20the%20report%2C%20you%20have%20subscribed%20for%2C%20is%20below%20the%20normal%20MECM%20folder.%20The%20subscription%20will%20not%20be%20visible%20in%20the%20MECM%20console%20if%20the%20report%20was%20placed%20at%20the%20root%20level.%3C%2FLI%3E%0A%3C%2FOL%3E%0A%3C%2FLI%3E%0A%3CLI%3EStart%20a%20PowerShell%20session%20as%20admin.%3COL%3E%0A%3CLI%3EThe%20user%20running%20PowerShell%20also%20needs%20to%20have%20admin%20rights%20on%20the%20SQL%20Reporting%20Services%20Server%20to%20upload%20the%20reports%3C%2FLI%3E%0A%3C%2FOL%3E%0A%3C%2FLI%3E%0A%3CLI%3EChange%20the%20directory%20to%20the%20folder%20were%20the%20import%20script%26nbsp%3B%3CSTRONG%3E%22Import-SSRSReports.ps1%22%3C%2FSTRONG%3E%26nbsp%3Bcan%20be%20found.%3C%2FLI%3E%0A%3CLI%3EStart%20the%20script%26nbsp%3B%3CSTRONG%3E%22.%5CImport-SSRSReports.ps1%22%3C%2FSTRONG%3E%26nbsp%3B%3CSTRONG%3Ewith%20the%20appropriate%20parameters%3C%2FSTRONG%3E%20(see%20below%20or%20run%20%E2%80%9CGet-Help%20.%5CImport-SSRSReports.ps1%20-Full%E2%80%9D)%3COL%3E%0A%3CLI%3EThe%20script%20will%20copy%20each%20RDL%20and%20RSD%20file%20from%20the%26nbsp%3B%3CSTRONG%3E%22%3CSPAN%3ESourcefiles%3C%2FSPAN%3E%22%3C%2FSTRONG%3E%26nbsp%3Bfolder%20to%20a%20new%26nbsp%3B%3CSTRONG%3E%22work%22%3C%2FSTRONG%3E%26nbsp%3Bfolder%20in%20the%20same%20directory%20the%20script%20resides.%3C%2FLI%3E%0A%3CLI%3EThe%20script%20will%20then%20simply%20replace%20some%20values%20with%20the%20parameter%20values%20you%20provided%3C%2FLI%3E%0A%3CLI%3EThe%20script%20will%20then%20upload%20the%20datasets%20and%20the%20reports%20to%20the%20server%20and%20the%20folder%20you%20provided%20as%20parameters%3C%2FLI%3E%0A%3CLI%3EThe%20files%20in%20the%26nbsp%3B%3CSTRONG%3E%22work%22%3C%2FSTRONG%3E%26nbsp%3Bfolder%20will%20not%20be%20deleted%20and%20can%20be%20used%20as%20a%20backup%20or%20for%20manual%20uploads%20if%20necessary%20and%20will%20contain%20the%20data%20you%20provided%20as%20parameters%20to%20the%20script%3C%2FLI%3E%0A%3CLI%3E%3CP%3E%3CSTRONG%3EIMPORTANT%3A%3C%2FSTRONG%3E%26nbsp%3BIf%20you%20need%20to%20re-run%20the%20script%2C%20delete%20the%20SSRS%20website%20folder%20with%20all%20its%20content%20first%20an%20re-create%20the%20folder%20in%20SSRS.%20It%20is%20possible%20to%20overwrite%20the%20reports%20automatically%2C%20but%20I%20faced%20some%20issues%20with%20some%20settings%20not%20being%20overwritten%20as%20desired%20and%20I%20%3CSPAN%3Edon't%3C%2FSPAN%3E%20use%20that%20method%20anymore.%20%3CSPAN%3EThat's%3C%2FSPAN%3E%20why%20everything%20should%20be%20deleted%20first%20to%20avoid%20errors.%3C%2FP%3E%0A%3C%2FLI%3E%0A%3C%2FOL%3E%0A%3C%2FLI%3E%0A%3C%2FOL%3E%0A%3CH3%20id%3D%22toc-hId--1548725280%22%20id%3D%22toc-hId--1548725257%22%20id%3D%22toc-hId--1548725257%22%20id%3D%22toc-hId--1548725257%22%20id%3D%22toc-hId--1548725257%22%20id%3D%22toc-hId--1548725257%22%20id%3D%22toc-hId--1548725257%22%20id%3D%22toc-hId--1548725257%22%20id%3D%22toc-hId--1548725257%22%20id%3D%22toc-hId--1548725257%22%20id%3D%22toc-hId--1548725257%22%20id%3D%22toc-hId--1548725257%22%20id%3D%22toc-hId--1548725257%22%20id%3D%22toc-hId--1548725257%22%20id%3D%22toc-hId--1548725257%22%20id%3D%22toc-hId--1548725257%22%3E%26nbsp%3B%3C%2FH3%3E%0A%3CH3%20id%3D%22ScriptParameters%22%20id%3D%22toc-hId-938787553%22%20id%3D%22toc-hId-938787576%22%20id%3D%22toc-hId-938787576%22%20id%3D%22toc-hId-938787576%22%20id%3D%22toc-hId-938787576%22%20id%3D%22toc-hId-938787576%22%20id%3D%22toc-hId-938787576%22%20id%3D%22toc-hId-938787576%22%20id%3D%22toc-hId-938787576%22%20id%3D%22toc-hId-938787576%22%20id%3D%22toc-hId-938787576%22%20id%3D%22toc-hId-938787576%22%20id%3D%22toc-hId-938787576%22%20id%3D%22toc-hId-938787576%22%20id%3D%22toc-hId-938787576%22%20id%3D%22toc-hId-938787576%22%3E%3CSTRONG%3EScript%20parameters%3A%3C%2FSTRONG%3E%3C%2FH3%3E%0A%3CTABLE%20style%3D%22width%3A%20640px%3B%22%20width%3D%22755px%22%3E%0A%3CTHEAD%3E%0A%3CTR%3E%0A%3CTD%20width%3D%22337.812px%22%3E%3CP%3E%3CSTRONG%3EParameter%3C%2FSTRONG%3E%3C%2FP%3E%0A%3C%2FTD%3E%0A%3CTD%20width%3D%2278.7031px%22%3E%3CP%3E%3CSPAN%3E%3CSTRONG%3ERequired%3C%2FSTRONG%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3C%2FTD%3E%0A%3CTD%20width%3D%22340.75px%22%3E%3CP%3E%3CSPAN%3E%3CSTRONG%3EExample%3C%2FSTRONG%3E%3C%2FSPAN%3E%3CSTRONG%3E%20%3CSPAN%3Evalue%20%2F%20Description%3C%2FSPAN%3E%3C%2FSTRONG%3E%3C%2FP%3E%0A%3C%2FTD%3E%0A%3C%2FTR%3E%0A%3C%2FTHEAD%3E%0A%3CTBODY%3E%0A%3CTR%3E%0A%3CTD%20width%3D%22337.812px%22%3E%3CP%3E%3CSPAN%3EReportServerURI%3C%2FSPAN%3E%3C%2FP%3E%0A%3C%2FTD%3E%0A%3CTD%20width%3D%2278.7031px%22%3E%3CP%3EYes%3C%2FP%3E%0A%3C%2FTD%3E%0A%3CTD%20width%3D%22340.75px%22%3E%3CP%3E%3CSTRONG%3EValue%3A%3C%2FSTRONG%3E%20%3CBR%20%2F%3E%3CA%20href%3D%22http%3A%2F%2Freportserver.domain.local%2Freportserver%22%20target%3D%22_blank%22%20rel%3D%22noopener%20nofollow%20noreferrer%22%3Ehttp%3A%2F%2Freportserver.domain.local%2Freportserver%3C%2FA%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSTRONG%3EDescription%3A%3C%2FSTRONG%3E%3CBR%20%2F%3EThe%20URL%20of%20the%20SQL%20Reporting%20Services%20Server.%3CBR%20%2F%3ECan%20be%20found%20in%20the%20MECM%20Console%20under%20%22%5CMonitoring%5COverview%5CReporting%22%20-%26gt%3B%20%22Report%20Server%22%20or%20in%20the%20%22Report%20Server%20Configuration%20Manager%22%20under%20%22Web%20service%20URL%22%3C%2FP%3E%0A%3C%2FTD%3E%0A%3C%2FTR%3E%0A%3CTR%3E%0A%3CTD%20width%3D%22337.812px%22%3E%3CP%3E%3CSPAN%3ETargetFolderPath%3C%2FSPAN%3E%3C%2FP%3E%0A%3C%2FTD%3E%0A%3CTD%20width%3D%2278.7031px%22%3E%3CP%3EYes%3C%2FP%3E%0A%3C%2FTD%3E%0A%3CTD%20width%3D%22340.75px%22%3E%3CP%3E%3CSTRONG%3EValue%3A%3C%2FSTRONG%3E%20%3CBR%20%2F%3EConfigMgr_P11%2FCustom_UpdateReporting%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSTRONG%3EDescription%3A%3C%2FSTRONG%3E%3CBR%20%2F%3EThe%20folder%20where%20the%20reports%20should%20be%20placed%20in.%20I%20created%20a%20folder%20called%20%22Custom_UpdateReporting%22%20below%20the%20default%20MECM%20reporting%20folder.%20My%20sitecode%20is%20P11%2C%20so%20the%20default%20folder%20is%20called%20%22ConfigMgr_P11%22.%3CBR%20%2F%3ELike%20this%20for%20example%3A%20%22ConfigMgr_P11%2FCustom_UpdateReporting%22%3CBR%20%2F%3EIMPORTANT%3A%20Use%20'%2F'%20instead%20of%20''%20because%20it's%20a%20website.%3C%2FP%3E%0A%3C%2FTD%3E%0A%3C%2FTR%3E%0A%3CTR%3E%0A%3CTD%20width%3D%22337.812px%22%3E%3CP%3E%3CSPAN%3ETargetDataSourcePath%3C%2FSPAN%3E%3C%2FP%3E%0A%3C%2FTD%3E%0A%3CTD%20width%3D%2278.7031px%22%3E%3CP%3EYes%3C%2FP%3E%0A%3C%2FTD%3E%0A%3CTD%20width%3D%22340.75px%22%3E%3CP%3E%3CSTRONG%3EValue%3A%3C%2FSTRONG%3E%3CBR%20%2F%3EConfigMgr_P11%2F%7B5C6358F2-4BB6-4a1b-A16E-8D96795D8602%7D%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSTRONG%3EDescription%3A%3C%2FSTRONG%3E%3CBR%20%2F%3EThe%20path%20should%20point%20to%20the%20default%20ConfigMgr%2FMECM%20data%20source.%3CBR%20%2F%3EIn%20my%20case%20the%20Sitecode%20is%20P11%20and%20the%20default%20data%20source%20is%20therefore%20in%20the%20folder%20%22ConfigMgr_P11%22%20and%20has%20the%20ID%20%22%7B5C6358F2-4BB6-4a1b-A16E-8D96795D8602%7D%22%3CBR%20%2F%3EThe%20path%20with%20the%20default%20folder%20is%20required.%20Like%20this%20for%20example%3A%20%22ConfigMgr_P11%2F%7B5C6358F2-4BB6-4a1b-A16E-8D96795D8602%7D%22%3C%2FP%3E%0A%3CP%3EIMPORTANT%3A%20Use%20'%2F'%20instead%20of%20'%5C'%20because%20it's%20a%20website.%3C%2FP%3E%0A%3C%2FTD%3E%0A%3C%2FTR%3E%0A%3CTR%3E%0A%3CTD%20width%3D%22337.812px%22%3E%3CP%3E%3CSPAN%3EDefaultCollectionID%3C%2FSPAN%3E%3C%2FP%3E%0A%3C%2FTD%3E%0A%3CTD%20width%3D%2278.7031px%22%3E%3CP%3E%3CSPAN%3ENo%3C%2FSPAN%3E%3C%2FP%3E%0A%3C%2FTD%3E%0A%3CTD%20width%3D%22340.75px%22%3E%3CP%3E%3CSTRONG%3EValue%3A%3C%2FSTRONG%3E%3CBR%20%2F%3ESMS00001%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSTRONG%3EDescription%3A%3C%2FSTRONG%3E%3CBR%20%2F%3EThe%20report%20can%20show%20data%20of%20a%20default%20collection%20when%20it%20will%20be%20run%2C%20so%20that%20you%20don't%20need%20to%20provide%20a%20collection%20name%20each%20time%20you%20run%20the%20report.%3CBR%20%2F%3EThe%20default%20value%20is%20%22SMS00001%22%20which%20is%20the%20CollectionID%20of%20%22All%20Systems%22%2C%20which%20might%20not%20be%20the%20best%20choice%20for%20bigger%20environments.%3C%2FP%3E%0A%3C%2FTD%3E%0A%3C%2FTR%3E%0A%3CTR%3E%0A%3CTD%20width%3D%22337.812px%22%3E%3CP%3E%3CSPAN%3EDefaultCollectionFilter%3C%2FSPAN%3E%3C%2FP%3E%0A%3C%2FTD%3E%0A%3CTD%20width%3D%2278.7031px%22%3E%3CP%3E%3CSPAN%3ENo%3C%2FSPAN%3E%3C%2FP%3E%0A%3C%2FTD%3E%0A%3CTD%20width%3D%22340.75px%22%3E%3CP%3E%3CSTRONG%3EValue%3A%3C%2FSTRONG%3E%3C%2FP%3E%0A%3CP%3EAll%25%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSTRONG%3EDescription%3A%3C%2FSTRONG%3E%3C%2FP%3E%0A%3CP%3EThe%20filter%20is%20used%20to%20find%20the%20collection%20you%20are%20interested%20in%20and%20the%20value%20needs%20to%20match%20the%20name%20of%20the%20collection%20you%20choose%20to%20be%20the%20default%20collection%20for%20the%20parameter%20%22defaultCollection%22.%3CBR%20%2F%3EIn%20my%20case%20%22S%25%22%20or%20%E2%80%9CServers%25%E2%80%9D%20or%20%22Servers%20of%25%22%20to%20get%20the%20%22Servers%20of%20the%20environment%22%20collection%20for%20example.%3C%2FP%3E%0A%3C%2FTD%3E%0A%3C%2FTR%3E%0A%3CTR%3E%0A%3CTD%20width%3D%22337.812px%22%3E%3CP%3E%3CSPAN%3EDoNotHideReports%3C%2FSPAN%3E%3C%2FP%3E%0A%3C%2FTD%3E%0A%3CTD%20width%3D%2278.7031px%22%3E%3CP%3E%3CSPAN%3ENo%3C%2FSPAN%3E%3C%2FP%3E%0A%3C%2FTD%3E%0A%3CTD%20width%3D%22340.75px%22%3E%3CP%3E%3CSTRONG%3EValue%3A%3C%2FSTRONG%3E%3C%2FP%3E%0A%3CP%3E'Software%20Updates%20Compliance%20-%26nbsp%3BOverview'%2C'Compare%26nbsp%3BUpdate%20Compliance'%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSTRONG%3EDescription%3A%3C%2FSTRONG%3E%3C%2FP%3E%0A%3CP%3EArray%20of%20reports%20which%20should%20not%20be%20set%20to%20hidden.%20You%20should%20not%20use%20the%20parameter%20unless%20you%20really%20want%20more%20reports%20to%20be%20visible.%3C%2FP%3E%0A%3C%2FTD%3E%0A%3C%2FTR%3E%0A%3CTR%3E%0A%3CTD%20width%3D%22337.812px%22%3E%3CP%3EDoNotUpload%3C%2FP%3E%0A%3C%2FTD%3E%0A%3CTD%20width%3D%2278.7031px%22%3E%3CP%3E%3CSPAN%3ENo%3C%2FSPAN%3E%3C%2FP%3E%0A%3C%2FTD%3E%0A%3CTD%20width%3D%22340.75px%22%3E%3CP%3E%3CSTRONG%3EDescription%3A%3C%2FSTRONG%3E%3C%2FP%3E%0A%3CP%3ESwitch%20parameter%20to%20not%20directly%20upload%20the%20reports%20to%20SRRS.%20That%20might%20be%20helpful%20if%20you%20do%20not%20have%20the%20rights%20to%20upload%20and%20need%20to%20give%20the%20files%20to%20another%20person%20for%20example.%20In%20that%20case%2C%20just%20use%20the%20report%20files%20in%20the%20work%20folder%20and%20upload%20them%20manually.%20(Was%20called%20%22Upload%22%20in%20the%20first%20script%20version)%3C%2FP%3E%0A%3C%2FTD%3E%0A%3C%2FTR%3E%0A%3CTR%3E%0A%3CTD%20width%3D%22337.812px%22%3E%3CP%3E%3CSPAN%3EReportSourcePath%3C%2FSPAN%3E%3C%2FP%3E%0A%3C%2FTD%3E%0A%3CTD%20width%3D%2278.7031px%22%3E%3CP%3E%3CSPAN%3ENo%3C%2FSPAN%3E%3C%2FP%3E%0A%3C%2FTD%3E%0A%3CTD%20width%3D%22340.75px%22%3E%3CP%3E%3CSTRONG%3EValue%3A%3C%2FSTRONG%3E%3CBR%20%2F%3E%22C%3A%5CTemp%5CReports%22%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSTRONG%3EDescription%3A%3C%2FSTRONG%3E%3CBR%20%2F%3EThe%20script%20will%20use%20the%20script%20root%20path%20to%20look%20for%20a%20folder%20called%20%22Sourcefiles%22%20and%20will%20copy%20all%20the%20report%20files%20from%20there.%20But%20you%20could%20also%20provide%20a%20different%20path%20where%20the%20script%20should%20look%20for%20a%20%22Sourcefiles%22%20folder%3C%2FP%3E%0A%3C%2FTD%3E%0A%3C%2FTR%3E%0A%3CTR%3E%0A%3CTD%20width%3D%22337.812px%22%3E%3CP%3EForceLegacyFormat%3C%2FP%3E%0A%3C%2FTD%3E%0A%3CTD%20width%3D%2278.7031px%22%3E%3CP%3E%3CSPAN%3ENo%3C%2FSPAN%3E%3C%2FP%3E%0A%3C%2FTD%3E%0A%3CTD%20width%3D%22340.75px%22%3E%3CP%3E%3CSTRONG%3EDescription%3A%3C%2FSTRONG%3E%3C%2FP%3E%0A%3CP%3ESwitch%26nbsp%3Bparameter%26nbsp%3Bto%26nbsp%3Bchange%26nbsp%3Bthe%26nbsp%3Bxml%26nbsp%3Bdefinition%26nbsp%3B%3CBR%20%2F%3Eof%26nbsp%3Beach%26nbsp%3Breport%26nbsp%3Bto%26nbsp%3Bthe%26nbsp%3Bolder%26nbsp%3Bpre%26nbsp%3BSSRS%26nbsp%3B%3C%2FP%3E%0A%3CP%3E2016%26nbsp%3Bformat.%26nbsp%3BThat%26nbsp%3Bway%26nbsp%3Bthe%26nbsp%3Breports%26nbsp%3Balso%26nbsp%3B%3C%2FP%3E%0A%3CP%3Ework%26nbsp%3Bwith%26nbsp%3BSSRS%26nbsp%3B2014%20for%20example.%3C%2FP%3E%0A%3C%2FTD%3E%0A%3C%2FTR%3E%0A%3CTR%3E%0A%3CTD%20width%3D%22337.812px%22%3E%3CP%3EForceLegacyCardinalitySQL2016SP1AndHigher%3C%2FP%3E%0A%3C%2FTD%3E%0A%3CTD%20width%3D%2278.7031px%22%3E%3CP%3E%3CSPAN%3ENo%3C%2FSPAN%3E%3C%2FP%3E%0A%3C%2FTD%3E%0A%3CTD%20width%3D%22340.75px%22%3E%3CP%3E%3CSTRONG%3EDescription%3A%3C%2FSTRONG%3E%3CBR%20%2F%3ESwitch%20parameter%20to%20change%20some%20SQL%20queries%20to%20use%20legacy%20cardinality%3CBR%20%2F%3E(More%20information%20can%20be%20found%20in%20the%20sources%20list%20below)%3C%2FP%3E%0A%3CP%3E%3CSTRONG%3EIMPORTANT%3A%3C%2FSTRONG%3E%20Can%20only%20be%20used%20if%20the%20SQL%20Server%20hosting%20the%20MECM%20database%20is%20at%20least%20running%20%3CSTRONG%3ESQL%20Server%202016%20SP1%3C%2FSTRONG%3E.%3C%2FP%3E%0A%3C%2FTD%3E%0A%3C%2FTR%3E%0A%3CTR%3E%0A%3CTD%20width%3D%22337.812px%22%3E%3CP%3EForceLegacyCardinalityOlderThanSQL2016SP1%3C%2FP%3E%0A%3C%2FTD%3E%0A%3CTD%20width%3D%2278.7031px%22%3E%3CP%3E%3CSPAN%3ENO%3C%2FSPAN%3E%3C%2FP%3E%0A%3C%2FTD%3E%0A%3CTD%20width%3D%22340.75px%22%3E%3CP%3E%3CSTRONG%3EDescription%3A%3C%2FSTRONG%3E%3CBR%20%2F%3ESwitch%20parameter%20to%20change%20some%20SQL%20queries%20to%20use%20legacy%20cardinality.%3CBR%20%2F%3EMore%20information%20can%20be%20found%20here.%3C%2FP%3E%0A%3CP%3E%3CSTRONG%3EIMPORTANT%3A%3C%2FSTRONG%3E%20Can%20only%20be%20used%20if%20the%20SQL%20Server%20hosting%20the%20MECM%20database%20is%20%3CSTRONG%3EOLDER%20than%202016%20SP1.%3C%2FSTRONG%3E%3C%2FP%3E%0A%3CP%3E%3CSTRONG%3E%26nbsp%3B%3C%2FSTRONG%3E%3C%2FP%3E%0A%3C%2FTD%3E%0A%3C%2FTR%3E%0A%3C%2FTBODY%3E%0A%3C%2FTABLE%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CH3%20id%3D%22ScriptExamples%22%20id%3D%22toc-hId--868666910%22%20id%3D%22toc-hId--868666887%22%20id%3D%22toc-hId--868666887%22%20id%3D%22toc-hId--868666887%22%20id%3D%22toc-hId--868666887%22%20id%3D%22toc-hId--868666887%22%20id%3D%22toc-hId--868666887%22%20id%3D%22toc-hId--868666887%22%20id%3D%22toc-hId--868666887%22%20id%3D%22toc-hId--868666887%22%20id%3D%22toc-hId--868666887%22%20id%3D%22toc-hId--868666887%22%20id%3D%22toc-hId--868666887%22%20id%3D%22toc-hId--868666887%22%20id%3D%22toc-hId--868666887%22%20id%3D%22toc-hId--868666887%22%3E%3CSTRONG%3EScript%20examples%3A%3C%2FSTRONG%3E%3C%2FH3%3E%0A%3CP%3EGet%20the%20full%20list%20of%20parameters%20by%20running%3A%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CPRE%20class%3D%22lia-code-sample%20language-powershell%22%3E%3CCODE%3EGet-Help%20.%5CImport-SSRSReports.ps1%20-Full%3C%2FCODE%3E%3C%2FPRE%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSTRONG%3EUpload%20all%20reports%20with%20the%20minimum%20required%20parameters%3C%2FSTRONG%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CPRE%20class%3D%22lia-code-sample%20language-powershell%22%3E%3CCODE%3E.%5CImport-SSRSReports.ps1%20-ReportServerURI%20%22http%3A%2F%2Freportserver.domain.local%2Freportserver%22%20-TargetFolderPath%20%22ConfigMgr_P11%2FCustom_UpdateReporting%22%20-TargetDataSourcePath%20%22ConfigMgr_P11%2F%7B5C6358F2-4BB6-4a1b-A16E-8D96795D8602%7D%22%3C%2FCODE%3E%3C%2FPRE%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSTRONG%3EUpload%20all%20reports%20with%20the%20minimum%20required%20parameters%20and%20force%20legacy%20format%3C%2FSTRONG%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CPRE%20class%3D%22lia-code-sample%20language-powershell%22%3E%3CCODE%3E.%5CImport-SSRSReports.ps1%20-ReportServerURI%20%22http%3A%2F%2Freportserver.domain.local%2Freportserver%22%20-TargetFolderPath%20%22ConfigMgr_P11%2FCustom_UpdateReporting%22%20-TargetDataSourcePath%20%22ConfigMgr_P11%2F%7B5C6358F2-4BB6-4a1b-A16E-8D96795D8602%7D%22%20-ForceLegacyFormat%3C%2FCODE%3E%3C%2FPRE%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSTRONG%3EJust%20change%20the%20report%20files%20and%20do%20not%20upload%20them%3C%2FSTRONG%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CPRE%20class%3D%22lia-code-sample%20language-powershell%22%3E%3CCODE%3E.%5CImport-SSRSReports.ps1%20-ReportServerURI%20%22http%3A%2F%2Freportserver.domain.local%2Freportserver%22%20-TargetFolderPath%20%22ConfigMgr_P11%2FCustom_UpdateReporting%22%20-TargetDataSourcePath%20%22ConfigMgr_P11%2F%7B5C6358F2-4BB6-4a1b-A16E-8D96795D8602%7D%22%20-DoNotUpload%3C%2FCODE%3E%3C%2FPRE%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSTRONG%3EUpload%20all%20reports%20and%20change%20the%20default%20C%3CSPAN%3EollectionID%3C%2FSPAN%3E%20and%20Collection-Filter%3C%2FSTRONG%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CPRE%20class%3D%22lia-code-sample%20language-powershell%22%3E%3CCODE%3E.%5CImport-SSRSReports.ps1%20-ReportServerURI%20%22http%3A%2F%2Freportserver.domain.local%2Freportserver%22%20-TargetFolderPath%20%22ConfigMgr_P11%2FCustom_UpdateReporting%22%20-TargetDataSourcePath%20%20%20%22ConfigMgr_P11%2F%7B5C6358F2-4BB6-4a1b-A16E-8D96795D8602%7D%22%20-DefaultCollectionID%20%22P1100012%22%20-DefaultCollectionFilter%20%22All%20Servers%20of%20Contoso%25%22%3C%2FCODE%3E%3C%2FPRE%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CH3%20id%3D%22DataCaching%22%20id%3D%22toc-hId-1618845923%22%20id%3D%22toc-hId-1618845946%22%20id%3D%22toc-hId-1618845946%22%20id%3D%22toc-hId-1618845946%22%20id%3D%22toc-hId-1618845946%22%20id%3D%22toc-hId-1618845946%22%20id%3D%22toc-hId-1618845946%22%20id%3D%22toc-hId-1618845946%22%20id%3D%22toc-hId-1618845946%22%20id%3D%22toc-hId-1618845946%22%20id%3D%22toc-hId-1618845946%22%20id%3D%22toc-hId-1618845946%22%20id%3D%22toc-hId-1618845946%22%20id%3D%22toc-hId-1618845946%22%20id%3D%22toc-hId-1618845946%22%20id%3D%22toc-hId-1618845946%22%3E%3CSTRONG%3EActivate%20report%20data%20caching%3A%3C%2FSTRONG%3E%3C%2FH3%3E%0A%3CP%3EActivate%20report%20data%20caching%20to%20increase%20report%20render%20speed.%20As%20mentioned%20before%20almost%20every%20report%20retrieves%20data%20from%20the%20same%20dataset.%20By%26nbsp%3Bactivating%20report%20data%20caching%20you%20can%20increase%20report%20render%20speed%20especially%20for%20the%20compliance%20sub-reports%20(like%20the%20first%20sub-report).%26nbsp%3B%3C%2FP%3E%0A%3CP%3EFirst%20you%20need%20to%20show%20all%20hidden%20items%20of%20your%20report%20folder%20by%20clicking%20on%20%22%3CSTRONG%3ETiles%3C%2FSTRONG%3E%22%20and%20%22%3CSTRONG%3EShow%20hidden%20items%3C%2FSTRONG%3E%22.%3C%2FP%3E%0A%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%22ShowHidden-B.png%22%20style%3D%22width%3A%20400px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F306304i040209B006B195AB%2Fimage-size%2Fmedium%3Fv%3Dv2%26amp%3Bpx%3D400%22%20role%3D%22button%22%20title%3D%22ShowHidden-B.png%22%20alt%3D%22Figure%208%3A%20Show%20hidden%20items%22%20%2F%3E%3CSPAN%20class%3D%22lia-inline-image-caption%22%20onclick%3D%22event.preventDefault()%3B%22%3EFigure%208%3A%20Show%20hidden%20items%3C%2FSPAN%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EChoose%20the%20%22%3CSTRONG%3EUpdatesSummary%3C%2FSTRONG%3E%22%20dataset%20and%20click%20on%20the%20three%20dots%20%22%3CSTRONG%3E...%3C%2FSTRONG%3E%22%20and%20choose%20%22%3CSTRONG%3EManage%3C%2FSTRONG%3E%22.%3C%2FP%3E%0A%3CP%3EClick%20on%20%22%3CSTRONG%3ECaching%3C%2FSTRONG%3E%22%20and%20%22%3CSTRONG%3ECache%20copies%20of%20this%20dataset%20and%20use%20them%20when%20available%3C%2FSTRONG%3E%22%20and%20%22%3CSTRONG%3EApply%3C%2FSTRONG%3E%22.%3C%2FP%3E%0A%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%22Caching-B.png%22%20style%3D%22width%3A%20655px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F306305iE5AFE001F49157B7%2Fimage-dimensions%2F655x503%3Fv%3Dv2%22%20width%3D%22655%22%20height%3D%22503%22%20role%3D%22button%22%20title%3D%22Caching-B.png%22%20alt%3D%22Figure%209%3A%20Activate%20data%20source%20caching%22%20%2F%3E%3CSPAN%20class%3D%22lia-inline-image-caption%22%20onclick%3D%22event.preventDefault()%3B%22%3EFigure%209%3A%20Activate%20data%20source%20caching%3C%2FSPAN%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CH3%20id%3D%22toc-hId--188608540%22%20id%3D%22toc-hId--188608517%22%20id%3D%22toc-hId--188608517%22%20id%3D%22toc-hId--188608517%22%20id%3D%22toc-hId--188608517%22%20id%3D%22toc-hId--188608517%22%20id%3D%22toc-hId--188608517%22%20id%3D%22toc-hId--188608517%22%20id%3D%22toc-hId--188608517%22%20id%3D%22toc-hId--188608517%22%20id%3D%22toc-hId--188608517%22%20id%3D%22toc-hId--188608517%22%20id%3D%22toc-hId--188608517%22%20id%3D%22toc-hId--188608517%22%20id%3D%22toc-hId--188608517%22%20id%3D%22toc-hId--188608517%22%3E%26nbsp%3B%3C%2FH3%3E%0A%3CH3%20id%3D%22AdditionalReport%22%20id%3D%22toc-hId--1996063003%22%20id%3D%22toc-hId--1996062980%22%20id%3D%22toc-hId--1996062980%22%20id%3D%22toc-hId--1996062980%22%20id%3D%22toc-hId--1996062980%22%20id%3D%22toc-hId--1996062980%22%20id%3D%22toc-hId--1996062980%22%20id%3D%22toc-hId--1996062980%22%20id%3D%22toc-hId--1996062980%22%20id%3D%22toc-hId--1996062980%22%20id%3D%22toc-hId--1996062980%22%20id%3D%22toc-hId--1996062980%22%20id%3D%22toc-hId--1996062980%22%20id%3D%22toc-hId--1996062980%22%20id%3D%22toc-hId--1996062980%22%20id%3D%22toc-hId--1996062980%22%3E%3CSTRONG%3EAdditional%20report%3A%3C%2FSTRONG%3E%3C%2FH3%3E%0A%3CP%3EAlso%2C%20a%20while%20ago%20I%20created%20a%20report%20to%20compare%20the%20patch%20status%20of%20a%20maximum%20of%20six%20systems%20which%20will%20also%20be%20upload%20to%20your%20SSRS%20if%20you%20run%20the%20install%20script.%20It%20should%20just%20help%20to%20have%20a%20fast%20and%20simple%20way%20to%20spot%20differences.%3CBR%20%2F%3EThe%20report%20has%20a%20filter%20to%20limit%20the%20amount%20of%20systems%20returned%20by%20name%20and%20you%20can%20choose%20a%20maximum%20of%20six%20systems%20to%20compare%20them.%20You%20could%20also%20choose%20to%20only%20view%20required%20updates%20to%20limit%20the%20view%20and%20complexity%20of%20the%20report.%3C%2FP%3E%0A%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%22CompareUpdates-B.png%22%20style%3D%22width%3A%20999px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F306302i86EFF3BA40D9ECC5%2Fimage-size%2Flarge%3Fv%3Dv2%26amp%3Bpx%3D999%22%20role%3D%22button%22%20title%3D%22CompareUpdates-B.png%22%20alt%3D%22Figure%2010%3A%20Compare%20update%20compliance%20report%22%20%2F%3E%3CSPAN%20class%3D%22lia-inline-image-caption%22%20onclick%3D%22event.preventDefault()%3B%22%3EFigure%2010%3A%20Compare%20update%20compliance%20report%3C%2FSPAN%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EI%20hope%20you%20like%20the%20report%20solution%20and%20I%20hope%20it%20is%20a%20good%20extension%20of%20what%20you%20are%20using%20right%20now.%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EStay%20safe%20and%20healthy!%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EBest%20regards%3C%2FP%3E%0A%3CP%3EJonas%20Ohmsen%3C%2FP%3E%0A%3CP%3ESenior%20Customer%20Engineer%20-%20Microsoft%20Germany%3C%2FP%3E%0A%3CP%3E%3CSTRONG%3E%26nbsp%3B%3C%2FSTRONG%3E%3C%2FP%3E%0A%3CP%3E%3CSTRONG%3EDisclaimer%3A%3C%2FSTRONG%3E%3C%2FP%3E%0A%3CP%3EThis%20posting%20is%20provided%20%22AS%20IS%22%20with%20no%20warranties%2C%20and%20confers%20no%20rights%3C%2FP%3E%0A%3CP%3E%3CSTRONG%3E%26nbsp%3B%3C%2FSTRONG%3E%3C%2FP%3E%0A%3CH3%20id%3D%22Resources%22%20id%3D%22toc-hId-491449830%22%20id%3D%22toc-hId-491449853%22%20id%3D%22toc-hId-491449853%22%20id%3D%22toc-hId-491449853%22%20id%3D%22toc-hId-491449853%22%20id%3D%22toc-hId-491449853%22%20id%3D%22toc-hId-491449853%22%20id%3D%22toc-hId-491449853%22%20id%3D%22toc-hId-491449853%22%20id%3D%22toc-hId-491449853%22%20id%3D%22toc-hId-491449853%22%20id%3D%22toc-hId-491449853%22%20id%3D%22toc-hId-491449853%22%20id%3D%22toc-hId-491449853%22%20id%3D%22toc-hId-491449853%22%20id%3D%22toc-hId-491449853%22%3E%3CSTRONG%3EResources%3A%3C%2FSTRONG%3E%3C%2FH3%3E%0A%3CP%3EDownload%20the%20whole%20solution%20or%20clone%20the%20repository%20here%3A%3CBR%20%2F%3E%3CA%20href%3D%22https%3A%2F%2Fgithub.com%2Fjonasatgit%2Fupdatereporting%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttps%3A%2F%2Fgithub.com%2Fjonasatgit%2Fupdatereporting%3C%2FA%3E%3C%2FP%3E%0A%3CP%3EOther%20blogs%3A%3C%2FP%3E%0A%3CP%3E%3CA%20href%3D%22https%3A%2F%2Faka.ms%2FJonasOhmsenBlogs%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttps%3A%2F%2Faka.ms%2FJonasOhmsenBlogs%3C%2FA%3E%3C%2FP%3E%0A%3CP%3E%3CA%20href%3D%22https%3A%2F%2Faka.ms%2FStefanRoellBlogs%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttps%3A%2F%2Faka.ms%2FStefanRoellBlogs%3C%2FA%3E%3C%2FP%3E%0A%3CP%3ESlow%20ConfigMgr%20console%3A%3C%2FP%3E%0A%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fsupport.microsoft.com%2Fen-us%2Fhelp%2F3196320%2Fsql-query-times-out-or-console-slow-on-certain-configuration-manager-d%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttps%3A%2F%2Fsupport.microsoft.com%2Fen-us%2Fhelp%2F3196320%2Fsql-query-times-out-or-console-slow-on-certain-configuration-manager-d%3C%2FA%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CH3%20id%3D%22Changes%22%20id%3D%22toc-hId--617842692%22%20id%3D%22toc-hId--617842669%22%20id%3D%22toc-hId--617842669%22%20id%3D%22toc-hId--617842669%22%20id%3D%22toc-hId--617842669%22%20id%3D%22toc-hId--617842669%22%20id%3D%22toc-hId--617842669%22%20id%3D%22toc-hId--617842669%22%20id%3D%22toc-hId--617842669%22%20id%3D%22toc-hId--617842669%22%20id%3D%22toc-hId--617842669%22%20id%3D%22toc-hId--617842669%22%20id%3D%22toc-hId--617842669%22%20id%3D%22toc-hId--617842669%22%20id%3D%22toc-hId--617842669%22%20id%3D%22toc-hId--617842669%22%3E%3CSTRONG%3EChanges%3A%3C%2FSTRONG%3E%3C%2FH3%3E%0A%3CP%3E(The%20version%20number%20can%20be%20found%20in%20the%20lower%20left%20corner%20of%20the%20dashboard.%20No%20version%20number%20means%20v1.0)%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSTRONG%3E2021-07-02%20v3.5%3A%3C%2FSTRONG%3E%3C%2FP%3E%0A%3CUL%3E%0A%3CLI%3EChanged%20the%20overall%20compliance%20state%20from%20%22all%20approved%20and%20missing%20updates%22%20%2B%20%22a%20security%20update%20installation%20happend%20within%20one%20month%22%20to%20%3CU%3E%22All%20deployments%20are%20compliant%22%20%2B%20%22either%20the%20last%20or%20the%20current%20cumulative%20update%20is%20installed%22%20%2B%20%22a%20security%20update%20installation%20happend%20within%20one%20month%22%3C%2FU%3E%20(based%20on%20Win32_QuickFixEngineering)%3C%2FLI%3E%0A%3CLI%3EAdded%20help%20text%20to%20all%20report%20column%20headers%3C%2FLI%3E%0A%3CLI%3EAdded%20Update%20install%20errors%20bar%20graph%20to%20dashboard%20(below%20WSUS%20scan%20errors)%3C%2FLI%3E%0A%3CLI%3EChanged%20filter%20for%20top%2010%20systems%20on%20dashboard%20to%20be%20more%20accurate%3C%2FLI%3E%0A%3CLI%3EAdded%20top%2010%20update%20install%20errors%20to%20dashboard%3C%2FLI%3E%0A%3CLI%3EAdded%20new%20report%20with%20details%20about%20install%20errors%20and%20WSUS%20scan%20errors%0A%3CUL%3E%0A%3CLI%3EContains%20around%20400%20common%20windows%20update%20related%20errors%20with%20possible%20actions%20on%20how%20to%20fix%20them%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3C%2FLI%3E%0A%3CLI%3EAdded%20new%20parameter%20to%20exclude%20deployments%20containing%20Microsoft%20Defender%20and%20System%20Center%20Endpoint%20Protection%20updates%0A%3CUL%3E%0A%3CLI%3EWas%20previously%20part%20of%20the%20SQL%20query%20and%20not%20easily%20changeable%20nor%20visible%20to%20the%20report%20user%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3C%2FLI%3E%0A%3CLI%3ERemoved%20Server%202008%20specific%20parts%3C%2FLI%3E%0A%3CLI%3EAdded%20new%20filter%20to%20%22per%20device%22%20report%20called%3A%20%22Missing%20updates%20with%20errors%22%20and%20%E2%80%9CAll%20missing%20updates%20deployed%20or%20not%E2%80%9D%3C%2FLI%3E%0A%3CLI%3EAdded%20more%20details%20about%20errors%20to%20%22per%20device%22%20report%3C%2FLI%3E%0A%3CLI%3EAdded%20update%20collection%20and%20maintenance%20window%20list%20to%20%E2%80%9Cper%20device%E2%80%9D%20report%3C%2FLI%3E%0A%3CLI%3EAdded%20column%3A%20%E2%80%9CEarliest%20Deadline%E2%80%9D%20to%20%E2%80%9Cper%20device%E2%80%9D%20report%3C%2FLI%3E%0A%3CLI%3EChanged%20first%20sub-report%20name%20from%20%E2%80%9Call%20uncompliant%E2%80%9D%20to%20%E2%80%9Ccompliance%20list%E2%80%9D%3C%2FLI%3E%0A%3CLI%3EChanged%20default%20sort%20order%20from%20%22count%20of%20missing%20updates%22%20to%20%22month%20since%20last%20update%20install%22%3C%2FLI%3E%0A%3CLI%3EChanged%20%22WSUS%20version%22%20to%20%22OS%20build%20version%22.%20Easier%20to%20determine%20actual%20OS%20version%20and%20patch%20level%3C%2FLI%3E%0A%3CLI%3EChanged%20%22Defender%20Pattern%20Version%22%20to%20%22Defender%20Pattern%20Age%22%20to%20be%20able%20to%20spot%20systems%20with%20older%20pattern%20more%20easily%3C%2FLI%3E%0A%3CLI%3EAdded%20column%20%22WSUS%20scan%20error%22%20to%20system%20list%3C%2FLI%3E%0A%3CLI%3EAdded%20column%20count%20of%20%22Updates%20with%20install%20error%22%20to%20system%20list%3C%2FLI%3E%0A%3CLI%3EAdded%20column%20number%20of%20%22Deployments%20non%20compliant%22%20to%20system%20list%0A%3CUL%3E%0A%3CLI%3EHelps%20to%20determine%20any%20problems%20with%20deployments%20when%20all%20updates%20are%20installed%2C%20but%20deployments%20are%20still%20marked%20as%20uncompliant%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3C%2FLI%3E%0A%3CLI%3EAdded%20new%20report%20to%20list%20all%20update%20deployments%20and%20their%20states%20per%20device%3C%2FLI%3E%0A%3CLI%3EMade%20%22Per%20device%22%20and%20%E2%80%9Ccompliance%20list%22%20report%20visible%20to%20be%20able%20to%20schedule%20subscriptions%20without%20the%20dashboard%3C%2FLI%3E%0A%3CLI%3EFixed%20several%20minor%20issues%20with%20each%20report%3C%2FLI%3E%0A%3CLI%3EChanged%20SQL%20query%20for%20deployed%20updates%20to%20work%20better%20in%20larger%20environments%3C%2FLI%3E%0A%3CLI%3EChanged%20import%20script%20to%20also%20handle%20SSRS%20folder%20path%20with%20spaces%20in%20it%3C%2FLI%3E%0A%3CLI%3EChanged%20import%20script%20to%20delete%20existing%20contents%20of%20%22work%22%20folder%20from%20a%20previous%20run%3C%2FLI%3E%0A%3CLI%3EChanged%20import%20script%20parameter%20name%20%22Upload%22%20to%20%22DoNotUpload%22.%20Function%20is%20the%20same.%3C%2FLI%3E%0A%3CLI%3ERemoved%20import%20script%20parameter%20%22UseViewForDataset%22.%20(To%20much%20work%20to%20keep%20the%20view%20consistent%20with%20regular%20query)%3C%2FLI%3E%0A%3CLI%3EAdded%20new%20import%20script%20parameters%3A%20%22ForceLegacyCardinalitySQL2016SP1AndHigher%22%20and%20%22ForceLegacyCardinalityOlderThanSQL2016SP1%22%20Read%20more%20about%20it%20%3CA%20href%3D%22https%3A%2F%2Fsupport.microsoft.com%2Fen-us%2Fhelp%2F3196320%2Fsql-query-times-out-or-console-slow-on-certain-configuration-manager-d%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehere%3C%2FA%3E%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3CP%3E%3CSTRONG%3E2020-12-09%20v2.1%3A%3C%2FSTRONG%3E%3C%2FP%3E%0A%3CUL%3E%0A%3CLI%3EFixed%20language%20and%20QFE%20problem%3C%2FLI%3E%0A%3CLI%3EAdded%20new%20parameter%20-ForceLegacyFormat%2C%3C%2FLI%3E%0A%3CLI%3EFixed%20minor%20issues%20and%20linked%20all%20reports%20to%20the%20per%20device%20sub-report%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3CP%3E%3CSTRONG%3E2020-11-03%20v1.0%3A%3C%2FSTRONG%3E%3C%2FP%3E%0A%3CUL%3E%0A%3CLI%3EFixed%20wrong%20parameter%20name%2C%20updated%20repository%20with%20several%20fixes%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-TEASER%20id%3D%22lingo-teaser-1415088%22%20slang%3D%22en-US%22%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%22Teaser.png%22%20style%3D%22width%3A%20999px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F194171iA7E860F096B5C411%2Fimage-size%2Flarge%3Fv%3Dv2%26amp%3Bpx%3D999%22%20role%3D%22button%22%20title%3D%22Teaser.png%22%20alt%3D%22Teaser.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3EPatch%20compliance%20reporting%20solution%20for%20MECM%20environments.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-TEASER%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1415088%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EJonasOhmsen%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2753885%22%20slang%3D%22en-US%22%3ERe%3A%20Mastering%20Configuration%20Manager%20Patch%20Compliance%20Reporting%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2753885%22%20slang%3D%22en-US%22%3E%3CP%3E%3CBR%20%2F%3EHi%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F1156391%22%20target%3D%22_blank%22%3E%40famelton%3C%2FA%3E%26nbsp%3Byou%20should%20see%20a%20description%20for%20each%20bar%20or%20column%20header%20if%20you%20hover%20over%20it%20with%20your%20mouse.%3CBR%20%2F%3EI%20described%20the%20compliance%20state%20in%20the%3A%20%22Some%20key%20facts%20and%20prerequisites%3A%22%20section.%20But%20to%20be%20honst%20it%20was%20easy%20to%20miss.%20So%2C%20I%20highlighted%20each%20fact%20and%20put%20that%20specific%20one%20on%20the%20third%20position.%20%3CBR%20%2F%3EBut%20my%20guess%20would%20be%20column%3A%20%22Month%20Since%20Last%20Update%20Install%22%20(see%20first%20sub-report)%20because%20that%20is%20based%20on%20WMI%20class%20Win32_QuickFixEngineering%20which%20is%20not%20enabled%20in%20Hardware%20Inventory%20by%20default.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2754596%22%20slang%3D%22en-US%22%3ERe%3A%20Mastering%20Configuration%20Manager%20Patch%20Compliance%20Reporting%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2754596%22%20slang%3D%22en-US%22%3E%3CP%3EThank%20you%20Jonasoh%20for%20the%20update%2C%20looking%20forward%20to%20seeing%20the%20new%20version%20of%20report%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks%2C%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2755409%22%20slang%3D%22en-US%22%3ERe%3A%20Mastering%20Configuration%20Manager%20Patch%20Compliance%20Reporting%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2755409%22%20slang%3D%22en-US%22%3E%3CP%3EThanks%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F268468%22%20target%3D%22_blank%22%3E%40jonasoh%3C%2FA%3E%26nbsp%3Bthat%20was%20exactly%20what%20it%20was.%20As%20soon%20as%26nbsp%3B%3CSPAN%3EWin32_QuickFixEngineering%20was%20enabled%20and%20the%20hardware%20inventory%20task%20run%2C%20the%20compliance%20started%20increasing.%20Thanks%20for%20your%20swift%20assistance.%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2760383%22%20slang%3D%22en-US%22%3ERe%3A%20Mastering%20Configuration%20Manager%20Patch%20Compliance%20Reporting%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2760383%22%20slang%3D%22en-US%22%3E%3CP%3EHi%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F1060338%22%20target%3D%22_blank%22%3E%40webcat123%3C%2FA%3E%26nbsp%3BI%20hope%20you%20saw%20the%20new%20version%20(v3.5)%20already.%20I%20listed%20all%20the%20changes%20here%3A%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fcore-infrastructure-and-security%2Fmastering-configuration-manager-patch-compliance-reporting%2Fba-p%2F1415088%23Changes%22%20target%3D%22_blank%22%3Ehttps%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fcore-infrastructure-and-security%2Fmastering-configuration-manager-patch-compliance-reporting%2Fba-p%2F1415088%23Changes%3C%2FA%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2770461%22%20slang%3D%22en-US%22%3ERe%3A%20Mastering%20Configuration%20Manager%20Patch%20Compliance%20Reporting%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2770461%22%20slang%3D%22en-US%22%3E%3CP%3EHey%20Jonas%2C%3C%2FP%3E%3CP%3EGreat%20work!%3C%2FP%3E%3CP%3EWhenever%20I%20run%20the%20script%2C%20I%20get%20the%20following%20error%3A%3CBR%20%2F%3EAt%20C%3A%5CScripts%5CSSRS_Reports%5CImport-SSRSReports.ps1%3A211%20char%3A21%3CBR%20%2F%3E%2B%20Sign%26amp%3Bnbsp%3Bup%3CBR%20%2F%3E%2B%20~%3CBR%20%2F%3EThe%20ampersand%20(%26amp%3B)%20character%20is%20not%20allowed.%20The%20%26amp%3B%20operator%20is%20reserved%20for%20future%20use%3B%20wrap%20an%20ampersand%20in%20double%20quotation%20marks%20(%22%26amp%3B%22)%20to%20pass%20it%20as%20part%20of%20a%20string.%3CBR%20%2F%3EAt%20C%3A%5CScripts%5CSSRS_Reports%5CImport-SSRSReports.ps1%3A223%20char%3A18%3CBR%20%2F%3E%2B%20%20%3CBR%20%2F%3E%2B%20~%3CBR%20%2F%3EThe%20'%26lt%3B'%20operator%20is%20reserved%20for%20future%20use.%3CBR%20%2F%3EAt%20C%3A%5CScripts%5CSSRS_Reports%5CImport-SSRSReports.ps1%3A237%20char%3A16%3CBR%20%2F%3E%2B%20%20%3CBR%20%2F%3E%2B%20~%3CBR%20%2F%3EThe%20'%26lt%3B'%20operator%20is%20reserved%20for%20future%20use.%3CBR%20%2F%3EAt%20C%3A%5CScripts%5CSSRS_Reports%5CImport-SSRSReports.ps1%3A250%20char%3A189%3CBR%20%2F%3E%2B%20...%20ata-ga-click%3D%22(Logged%20out)%20Header%2C%20go%20to%20Features%22%26gt%3BFeatures%20%3CSPAN%20cla%3D%22%22%20...%3D%22%22%3E%3CBR%20%2F%3E%2B%20~%3CBR%20%2F%3EThe%20'%26lt%3B'%20operator%20is%20reserved%20for%20future%20use.%3CBR%20%2F%3EAt%20C%3A%5CScripts%5CSSRS_Reports%5CImport-SSRSReports.ps1%3A250%20char%3A269%3CBR%20%2F%3E%2B%20...%20nk-symbol%20float-right%20text-normal%20color-text-tertiary%20pr-3%22%26gt%3B%26amp%3Brarr%3B%2B%20~%3CBR%20%2F%3EThe%20ampersand%20(%26amp%3B)%20character%20is%20not%20allowed.%20The%20%26amp%3B%20operator%20is%20reserved%20for%20future%20use%3B%20wrap%20an%20ampersand%20in%20double%20quotation%20marks%20(%22%26amp%3B%22)%20to%20pass%20it%20as%20part%20of%20a%20string.%3CBR%20%2F%3EAt%20C%3A%5CScripts%5CSSRS_Reports%5CImport-SSRSReports.ps1%3A254%20char%3A167%3CBR%20%2F%3E%2B%20...%20ck%20Link--secondary%20no-underline%20f5%20Bump-link--hover%22%26gt%3BMobile%20%3CSPAN%20cla%3D%22%22%20...%3D%22%22%3E%3CBR%20%2F%3E%2B%20~%3CBR%20%2F%3EThe%20'%26lt%3B'%20operator%20is%20reserved%20for%20future%20use.%3CBR%20%2F%3EAt%20C%3A%5CScripts%5CSSRS_Reports%5CImport-SSRSReports.ps1%3A254%20char%3A247%3CBR%20%2F%3E%2B%20...%20nk-symbol%20float-right%20text-normal%20color-text-tertiary%20pr-3%22%26gt%3B%26amp%3Brarr%3B%2B%20~%3CBR%20%2F%3EThe%20ampersand%20(%26amp%3B)%20character%20is%20not%20allowed.%20The%20%26amp%3B%20operator%20is%20reserved%20for%20future%20use%3B%20wrap%20an%20ampersand%20in%20double%20quotation%20marks%20(%22%26amp%3B%22)%20to%20pass%20it%20as%20part%20of%20a%20string.%3CBR%20%2F%3EAt%20C%3A%5CScripts%5CSSRS_Reports%5CImport-SSRSReports.ps1%3A255%20char%3A178%3CBR%20%2F%3E%2B%20...%20k%20Link--secondary%20no-underline%20f5%20Bump-link--hover%22%26gt%3BActions%20%3CSPAN%20cla%3D%22%22%20...%3D%22%22%3E%3CBR%20%2F%3E%2B%20~%3CBR%20%2F%3EThe%20'%26lt%3B'%20operator%20is%20reserved%20for%20future%20use.%3CBR%20%2F%3EAt%20C%3A%5CScripts%5CSSRS_Reports%5CImport-SSRSReports.ps1%3A255%20char%3A258%3CBR%20%2F%3E%2B%20...%20nk-symbol%20float-right%20text-normal%20color-text-tertiary%20pr-3%22%26gt%3B%26amp%3Brarr%3B%2B%20~%3CBR%20%2F%3EThe%20ampersand%20(%26amp%3B)%20character%20is%20not%20allowed.%20The%20%26amp%3B%20operator%20is%20reserved%20for%20future%20use%3B%20wrap%20an%20ampersand%20in%20double%20quotation%20marks%20(%22%26amp%3B%22)%20to%20pass%20it%20as%20part%20of%20a%20string.%3CBR%20%2F%3EAt%20C%3A%5CScripts%5CSSRS_Reports%5CImport-SSRSReports.ps1%3A256%20char%3A184%3CBR%20%2F%3E%2B%20...%20ink--secondary%20no-underline%20f5%20Bump-link--hover%22%26gt%3BCodespaces%20%3CSPAN%20cla%3D%22%22%20...%3D%22%22%3E%3CBR%20%2F%3E%2B%20~%3CBR%20%2F%3EThe%20'%26lt%3B'%20operator%20is%20reserved%20for%20future%20use.%3CBR%20%2F%3ENot%20all%20parse%20errors%20were%20reported.%20Correct%20the%20reported%20errors%20and%20try%20again.%3CBR%20%2F%3E%2B%20CategoryInfo%20%3A%20ParserError%3A%20(%3A)%20%5B%5D%2C%20ParseException%3CBR%20%2F%3E%2B%20FullyQualifiedErrorId%20%3A%20AmpersandNotAllowed%3C%2FSPAN%3E%3C%2FSPAN%3E%3C%2FSPAN%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAny%20idea%20what%20I'm%20doing%20wrong%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2770619%22%20slang%3D%22en-US%22%3ERe%3A%20Mastering%20Configuration%20Manager%20Patch%20Compliance%20Reporting%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2770619%22%20slang%3D%22en-US%22%3E%3CP%3EHi%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F1162267%22%20target%3D%22_blank%22%3E%40Zirigo%3C%2FA%3E%26nbsp%3Bmy%20guess%20would%20be%20that%20you%20copied%20too%20much%20from%20the%20GitHub%20page%20here%3A%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fgithub.com%2Fjonasatgit%2Fupdatereporting%2Fblob%2Fmaster%2FImport-SSRSReports.ps1%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttps%3A%2F%2Fgithub.com%2Fjonasatgit%2Fupdatereporting%2Fblob%2Fmaster%2FImport-SSRSReports.ps1%3C%2FA%3E%3CBR%20%2F%3EThe%20easiest%20way%20to%20download%20the%20whole%20solution%20is%20to%20use%20the%20%22Code%22%20and%20%22Download%20ZIP%22%20button%20on%20the%20following%20GitHub%20page%3A%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fgithub.com%2Fjonasatgit%2Fupdatereporting%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttps%3A%2F%2Fgithub.com%2Fjonasatgit%2Fupdatereporting%3C%2FA%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2771204%22%20slang%3D%22en-US%22%3ERe%3A%20Mastering%20Configuration%20Manager%20Patch%20Compliance%20Reporting%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2771204%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20Jonasoh%2C%3C%2FP%3E%3CP%3EThank%20you%20so%20much%20for%20promptly%20answering%20my%20inquiry.%3C%2FP%3E%3CP%3EYes%2C%20you%20were%20right%2C%20I%20copied%20too%20much%26nbsp%3B%3CSPAN%3Efrom%20the%20GitHub%20page.%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3EUsing%20the%20link%20you%20provided%2C%20I%20was%20able%20to%20get%20the%20right%20code%20and%20run%20successfully%20the%20PowerShell%26nbsp%3Bscript.%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EThank%20you%20a%20million!%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2771271%22%20slang%3D%22en-US%22%3ERe%3A%20Mastering%20Configuration%20Manager%20Patch%20Compliance%20Reporting%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2771271%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20Jonasoh%2C%3C%2FP%3E%3CP%3ESorry%20to%20send%20you%20this%20second%20request.%3C%2FP%3E%3CP%3EWhat%20would%20be%20the%20best%20way%20to%20send%20this%20report%20to%20an%20IT%20VP%20that%20cannot%20access%20the%20SSRS%20report%20but%20could%20read%20it%20in%20any%20other%20format%3F%3C%2FP%3E%3CP%3EThank%20you.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2771400%22%20slang%3D%22en-US%22%3ERe%3A%20Mastering%20Configuration%20Manager%20Patch%20Compliance%20Reporting%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2771400%22%20slang%3D%22en-US%22%3E%3CP%3EHi%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F1162267%22%20target%3D%22_blank%22%3E%40Zirigo%3C%2FA%3E%26nbsp%3BI%20normally%20create%20a%20report%20subscription%20to%20send%20the%20report%20via%20email%20and%20use%20the%20report%20format%20appropriate%20for%20the%20audience.%26nbsp%3B%3C%2FP%3E%0A%3CP%3ERead%20more%20about%20it%20here%3A%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fsql%2Freporting-services%2Fsubscriptions%2Fsubscriptions-and-delivery-reporting-services%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fsql%2Freporting-services%2Fsubscriptions%2Fsubscriptions-and-delivery-reporting-services%3C%2FA%3E%3C%2FP%3E%0A%3CP%3EOr%20here%3A%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fconfiguration-manager-archive%2Fconfiguring-email-notification-for-configuration-manager-reports%2Fba-p%2F274241%22%20target%3D%22_blank%22%3Ehttps%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fconfiguration-manager-archive%2Fconfiguring-email-notification-for-configuration-manager-reports%2Fba-p%2F274241%3C%2FA%3E%3C%2FP%3E%0A%3CP%3EI%20tend%20to%20create%20the%20subscription%20via%20the%20SQL%20Server%20Reporting%20Services%20website%20instead%20of%20the%20ConfigMgr%20console%2C%20but%20both%20ways%20are%20appropriate.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2771880%22%20slang%3D%22en-US%22%3ERe%3A%20Mastering%20Configuration%20Manager%20Patch%20Compliance%20Reporting%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2771880%22%20slang%3D%22en-US%22%3E%3CP%3EThank%20you%20so%20much%20Jonasoh%2C%20this%20is%20great.%3CBR%20%2F%3EI%20will%20read%20the%20document%20and%20implement%20it%20into%20my%20environment.%3C%2FP%3E%3CP%3EAgain%2C%20thank%20you!%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E
Co-Authors
Version history
Last update:
‎Sep 15 2021 10:51 AM
Updated by: