mem-zone / mem.zone-dashboards Goto Github PK

If you run the install without any parameters, no destination is required for example

SW - SQL Server Products

This report does not cover when only SQL Reporting services or Analysis services are installed on separate servers. As per the documentation, if the database is running in one server, Analysis Services on a second, and Reporting Services on a third, then three licenses are required.the report does not show Reporting and Analysis servers due to missing Reg Keys for SCCM Inventory. Any future plan to add them?

Adding functions to the CMDB is not really supported.
They need to be placed in a separate DB.

The dashboard installer #4 will support this option.

Received error on site server trying to connect to remote DB. Using windows auth. Used install with extension option. Was able to go to remote db and install extension. When loading reports in console, getting an error when view a report on a collection/device.

SU DAS Overall Compliance graphs displaying 0 (ZERO) when the number of devices is 0.
Need to hide if the value is 0

Since the get next maintenance window function is optional, the permission block for the other tables and functions needs to have it’s own file

A dashboard installer needs to be created, in order to make installation easier and fix issue #5

Add a uninstall option for the installer

Unknown scan state actionable chart item throws an error, an incorrect reference most likely.

With the upcoming PowerBI integration coming with MEMCM 2001 this Dashboard needs a PowerBI version

Header rows are not displayed on subsequent pages

• AL Alerts
• SU Compliance by Collection
• SU Scan Status by Collection
• SU SUP Sync Status

Dashboard and SU Compliance reports not working when CMDB and SSRS DB are not hosted on the same SQL server.

-Ioan

When I try to run the report I get this error:

It works in our dev enviroment but not in our production, the only difference beetween them is that the reporting databas is not on the same server as the cm-database. I have run the prereq sql-script.

I get this error for all the reports exept the AL Alerts and SU SUP Sync Status reports.

Under 'Next Service Window' it says 'Missing helper function'.

The report is currently only displaying the hostname of the device.
In environments with multiple domains, there can be servers with same hostname in different domains, that makes it hard distinguishing them in the reports.
The view v_RA_System_ResourceNames contains the FQDN of the device.

It would be nice if it per default shows the FQDN or giving the option to display it.

Call this function first to clean up results

Use N'Some nvarchar'

When the helper function is not installed, systems show up as unhealthy

First, these look awesome! I've installed 5.0.2 but am unfortunately running in to an issue with a few reports. Specifically, attempting to execute the Operating System - Version Compliance by Collection and Operating System - Windows 11 Readiness by Collection reports generate the following error:

An error has occurred during report processing. (rsProcessingAborted)
Query execution failed for dataset 'ComplianceInfo'. (rsErrorExecutingCommand)
Invalid column name 'co'. Invalid column name 'l'.

I installed the reports via the automatic PowerShell script. Is this a bug or could there be something else wrong? I'm running SQL Server and SSRS 2017 and my ConfigMgr database is at the 140 compatibility level.

Filter scan statuses to maximum 4, they get squashed together and you can't see much.
Add an 'other' status nobody cares if the scan is running or is being retried

When a collection utilizes a maintenance window such as "Occurs 4 day(s) after the Fourth Tuesday of every month," the next maintenance window is not calculated in the report and is marked as not having a service window defined.

Steps to reproduce the behavior:

1. Create a maintenance window using the "offset days" function
2. Run report.
3. Observe a lack of dates in the "Next Maintenance Window" column

I would expect to see the next maintenance window calculated in this column.

The maintenance window:

The SRS report:

SystemCenterDudes report detailing maintenance windows;

Desktop (please complete the following information):

• OS: Windows Server 2016
• Browser: Edge
• Version 116.0.1938.62

After changing the maintenance window to not utilize the offset days, the Next Maintenance Window column is properly calculated and displayed.

when i use scan status by collection report failed

the error is:
An error occurred while processing the report（rsProcessingAborted）
unable to read the data set DevicesScanStateInfo of next data row（rsErrorReadingNextDataRow）

Limit the number of updates showing up in Devices Missing a Specific Update chart.
If the number is over 30 de chart becomes unreadable

Rewrite Dashboard compliance query it eats up 80% of the processing time.
This should speed up the dashboard at leas 2x.

SU Scan Status by Collection is not showing devices without client as Unknown