Monthly Archives: September 2016

SCCM Power BI Solution Template preview

A few days ago Microsoft released a public preview of the System Center Configuration Manager Power BI solution template

“Stand up a scalable and extensible System Center Configuration Manager dashboard in a few hours. Information is collected daily so you can see not only how your organization’s computer health looks like today, you can also see how those key metrics change over time. Quickly identify machines not up-to-date with software updates, successful and failed mitigations to malware infections to be able to act quickly.”

More information on this can be found here and you can download the template from here 

Requirements:

  • System Center 2012 Configuration Manager R2 SP1 or later. Read access to System Center Configuration Manager database is required.
  • Destination database: Azure SQL database or SQL Server database (SQL Server 2008 R2 SP3 or later).
  • For the machine where the installation is run, Microsoft .NET Framework 4.5 or later & PowerShell version 3.0 or later.
  • Power BI Desktop (latest version)
  • Power BI Pro (to share the template with your organization)

In this post, I am going to test installing the public preview of SCCM Power BI solution template in my lab which has:

  • ConfigMgr Current Branch 1606 & SQL server 2012 SP3
  • Windows Server 2012 R2  with Microsoft .Net Framework 4.5 installed
  • Azure SQL Database as my target database.

First thing I am going to do is create my target SQL server which will be an Azure SQL database.

Login to https://portal.azure.com

Below, I have clicked on Add, then given my database a name, created a new resource group, chosen a blank database, created a new SQL server, and used “S0 Standard” pricing tier as my ConfigMgr site is a very small lab.

When you create the new SQL Server, take a note of the login and password as you will need this later for the ConfigMgr Power BI Solution template setup.

powerbi2

Once my SQL database deployment has finished, I have gone into the SQL database overview, and copied down my Server Name as it is required for later.

powerbi6

Next up in my lab I have installed Microsoft-SCCMTemplate.exe which I downloaded earlier from here  . Once finished installing, you can configure the solution template. Again the requirements are listed. Click Next.

powerbi4

Enter in your source ConfigMgr database server details and select your ConfigMgr database, then validate and click Next:

powerbi5

Next I will enter my target database which is my Azure SQL database name. I have selected “Using Azure SQL” . Make sure in the Azure portal you enter in your public IP for the SQL Server firewall in your SQL Server settings in https://portal.azure.com otherwise you will get the error below as it cannot connect. Steps to add your IP to the firewall are here.

powerbi7

This is how it should look:

powerbi8

On the Customize page I have left settings as default and clicked Next.

On the Progress page you can download your PBIX file and open it up with Power BI Desktop. You can download PowerBI Desktop from here if you do not have it installed.

powerbi11

Once I have opened my downloaded PBIX file and opened it up in Power BI Desktop, I clicked on Refresh so it can get the latest data. It popped up for me to enter credentials to my Azure SQL database. Make sure you click on Database instead of Windows to enter your credentials, otherwise you will not have permission.

powerbi12

Once it has pulled the latest data, you can view the Overview as shown in the screenshot below, or you can view the other tabs Protection, Malware, Updates Compliance and Software.

powerbi14

Here is an example showing Update Compliance

powerbi15

 

Advertisements

Azure AD public preview in new Azure portal is available

Finally – The public preview for Azure AD is now available in the new Azure portal (Azure Resource Manager) portal.azure.com

Azure AD has always only been available in the Azure classic portal (manage.windowsazure.com)

You can read up more on it here https://blogs.technet.microsoft.com/enterprisemobility/2016/09/12/the-azuread-admin-experience-in-the-new-azure-portal-is-now-in-public-preview/

You can pin the Azure AD in the portal.azure.com like this

azuread2

You can then view the public preview of Azure AD

azuread1

WUAHandler.log – Scan failed with error = 0x80244019

In an SCCM Current Branch 1602 environment with a Server 2008 R2 Software Update Point (have not upgraded to Server 2012 R2 yet), in a different site I had about 120 clients at a specific site that were not successfully scanning for updates.

I usually run the built in report “Last scan states by collection” to make sure the clients are scanning for software updates without issues.

When checking WUAHandler.log on the client I saw the errors

OnSearchComplete – Failed to end search job. Error = 0x80244019.
Scan failed with error = 0x80244019.

0x80244019

If you look up the error 0x80244019 it means “Same as HTTP status 404 – the server cannot find the requested URI (Uniform Resource Identifier).”

One thing to check is that you can actually get to the WSUS server in an Internet browser by going to http://wsusserver.domain.com:8530/SimpleAuthWebService/SimpleAuth.asmx and making sure it is reachable. If it is reachable it should take you to a page saying:

0x802440192

In my issue it was the proxy between the SUP and my client. My client was trying to go through a proxy instead of bypassing it, then it was getting the 404 error from the WSUS.  There is also a good post on the Technet forums where people have had a bypass list which was lowercase, but in SCCM their SUP was in uppercase which caused the exact error. The post can be found here

In my site we are using a WinINET proxy script which sets the proxy for the Internet , and we also set the WinHTTP proxy. Our WinINET proxy had a bypass list for the WSUS server but our WinHTTP proxy did not for this specific site.

From Microsoft: https://support.microsoft.com/en-au/kb/900935

The Automatic Updates service does not have access to the user-specific proxy server settings that may be configured in Internet Explorer. WinHTTP has been employed, instead of WinInet in Internet Explorer, as the Automatic Updates service affects system wide level configuration and should require administrator level control

To view the current WinHTTP proxy and bypass list, load up cmd prompt and run:

netsh winhttp show proxy

To add the bypass list to your WinHTTP proxy, you can either set it manually through command prompt, or through group policy.

netsh winhttp set proxy proxy-server=”proxyserver.com:port” bypass-list=”*.domain.com;<local>”

The example above added a bypass list for a server <servername>.domain.com

Note: After setting the proxy through cmd using netsh winhttp or group policy, you must restart your computer before you do the next Software Update scan

After restarting the computer for the proxy settings to take affect and doing another Software Update evaluation scan on the client, the WUAHandler “Successfully completed scan.” on the clients.

 

 

 

Scan failed with error = 0x8007000e

Recently when working on a Windows 7 machine I realized it was not installing Windows Updates deployed from the SUP in SCCM 2012 R2.

When checking WUAHandler.log or UpdatesDeployment.log I kept seeing the error 0x8007000e

0x8007000e

The error 0x8007000e translates to Not enough storage is available to complete this operation.

The fix was to update the Windows Update Agent from https://support.microsoft.com/en-us/kb/3112343

Windows Update Client for Windows 7 and Windows Server 2008 R2: December 2015

Issues that are fixed in this update

  • Assume that you use Software Update agent to apply software updates or determine the software update compliance in System Center Configuration Manager 2007 R2. Windows Update agent scans client computers periodically. In this situation, the scan fails and generates a “Not Required” state for all updates. Additionally, you receive an “8007000E” error message.

After installing this and restating the Windows 7 client machine, I initiated a Software Update Scan cycle from the ConfigMgr agent:

softwareupdatescan

The WUAHandler.log on showed that the agent successfully completed the scan and I was able to install all deployed Windows Updates.