The PowerON Power BI Configuration Manager Dashboard 1612 is now out!

With the 1611 version We've had some great feedback from the community and made some minor changes to the queries as well as adding some additional support information from Microsoft.

  Version 1611 Release Notes
•Included Branch Support information from into the admin settings.
 •Addressed duplicate entry issue on Client Information where devices with multiple chassistype were causing relationship error.
 •Updated EndPoint Protection table queries to address duplicate entry error.
 •Added parameter to Support Lifecycle URL note: The URL seems to be intermittently causing a 400 error. To to and fix this, flip the URL to send one and flip it back again.

You can download the Dashboard from the TechNet gallery:


So I came across a random issue when working on enabling PS remoting on a Windows 2012 R2 server with a customer then other day.


When trying to run Enable-PSRemoting, It would return an error saying: Unable to check the status of the firewall issue.


The customer had removed the Windows Remote Management inbound rules in Windows Firewall, there are two ways to sort this.

Using Windows Firewall with Advanced Security GUI

1. Select Inbound Rules
2. Select New Rule from the action pane
3. In the New Rule Wizard, Select Predefined
4. Drop the Predefined list and select Windows Remote Management
5. Click Next
6. In Predefined Rules, select the two rules and click Next
7. Click Finish

Using PowerShell to Create Copy of Predefined Rule

If((Get-NetFirewallRule -Group "@FirewallAPI.dll,-30267" -ErrorAction SilentlyContinue | Measure).Count -gt 0)


Write-Output "Firewall Rule Already Exists"




Write-Output "Firewall Rule Not Found"

New-NetFirewallRule -Group "@FirewallAPI.dll,-30267" -Name "WINRM-HTTP-In-TCP" -DisplayName "Windows Remote Management (HTTP-In)" -Direction Inbound -Description 'Inbound rule for Windows Remote Management via WS-Management. [TCP 5985]' -Profile Domain,Private -Enabled True -Action Allow -Protocol TCP -LocalPort 5985 -Program System -EdgeTraversalPolicy Block -LooseSourceMapping $False -LocalOnlyMapping $false

New-NetFirewallRule -Group "@FirewallAPI.dll,-30267" -Name "WINRM-HTTP-In-TCP-PUBLIC" -DisplayName "Windows Remote Management (HTTP-In)" -Direction Inbound -Description 'Inbound rule for Windows Remote Management via WS-Management. [TCP 5985]' -Profile Public -Enabled True -Action Allow -Protocol TCP -LocalPort 5985 -Program System -RemoteAddress LocalSubnet -EdgeTraversalPolicy Block -LooseSourceMapping $False -LocalOnlyMapping $false

Enable-PSRemoting -Force
Traditionally getting the most out of reporting in Service Manager (SCSM) can be challenging. Gaining the visibility and information out of the reports, can be time consuming and difficult, using SQL reports or excel pivot tables to get the information required.

At PowerON we've been working hard to make reporting more accessible and take the pain out of System Center reporting. With the success of our community Power BI Configuration Manager Dashboard, I felt it was a good time to give back to the community and release PowerON BI Service Manager Community Dashboard!

With feedback from our customers and using our expert knowledge of SCSM, we've adapted our PowerON BI Service Manager Pro Dashboard to give the community a snippet of what is capable with Power BI and SCSM.

PowerON BI Service Manager Community Dashboard

This Power BI report enables you to view Incident and Service Request information from System Center Service Manager 2012 R2 and above.

It queries the SCSM DWDataMart SQL database to retrieve SCSM information and presents it in Power BI Desktop. This then allows you to dynamically filter your data in a more visual way.


- 1711 Release Version
- Incident Overview
- Service Requests Overview
- Edit Language in settings
- Edit Company in settings
- Filter number of days returns from DW data.

Incidents (IR)

This provides an overview for incident management around:

- IR by Classifications
- IR by Support Group
- Total IR by Status
- IR by Affected Users
- IR by Assigned to Users
- IR by Urgency
- IR by Impact
- IR by Month and Year
- IR by Time Blocks *Allows you to see IR's by raised time giving you visibility of how busy you Service Desk is by time.
- Table overview

Service Requests (SR)

This provides overview information for service requests around:

- SR By Classifications
- SR By Support Group
- Total SR by Status
- SR by Affected Users
- SR by Assigned to Users
- SR by Urgency
- SR by Priority
- SR by Month and Year
- SR by Time Blocks *Allows you to see SR's by raised time giving you visibility of how busy you Service Desk is by time.
- Table overview


Ensure you have at least read access to the SCSM SQL Database and you can access the Internet from the machine running Power BI Desktop.

Download the file and the latest Power BI desktop (you can find the lastest BI desktop here).

Once installed Open Power BI.

1. Go to File > Options and Settings > Options.

2. Under Privacy enable Fast Combine to file privacy.

3. Under Security untick "Require user approval for native SQL database queries".

4.  Select Edit Queries to load the Query Editor.

5. Supply parameter information in the Setup section.

- SCSM DW SQL Server
Specify the SCSM Data Warehouse SQL Server name or instance.
- SCSM DW SQL Database
Specify the SCSM Database name (you shouldn't need to change this unless you've changed the name from default).
- Language
Specify language if not using default. (Note: this is as is and not fully supported as not had chance to test)
- Organisation Name
Specify your Organisation name. 
- Filter Days 
By default "0" will return all the records from the SCSM DWDatamart, if you want to limit the data returned, you can specify the number of days to returned with this field (for example, 365 days would bring back the last 365 days worth of records.

6. Select the "Incident" or "Service Request" query under the Service Manager folder and supply any credentials required to access the database.

7. If prompted, Click OK on the encryption support message.

8. Close the Query Editor and load the data  

Next PostNewer Posts Previous PostOlder Posts Home