Downloading updates fails zero percent complete

Examined a server recently that refused to download deployed security updates. This server was also a Distribution Point in a remote location. Further, this site is running CM Current Branch.

Software Center presented the following:


DataTransfer.log showed something similar to the following:

Successfully sent location services HTTP failure message.

Error sending DAV request. HTTP code 500, status 'Internal Server Error'

GetDirectoryList_HTTP('http://<server>:80/SMS_DP_SMSPKG$/<guid>') failed with code 0x87d0027e.    DataTransferService  4/29/2016 8:51:36 PM  3028 (0x0BD4)

Error retrieving manifest (0x87d0027e).  

After review, content boundaries were correct, DP was installed correctly. Enabling HTTP anonymous authentication did not help.

Found a similar problem on the web, with a tip to enable ASP.NET 4.5:

Adding the ASP.NET 4.5 Role (and proposed Features) under Roles and Features > "Web Server (IIS)" > "Web Server" > "Application Development" solved our issue.

For more details see

Took these steps, rebooted the server and all is well.

New Power BI dashboard for CM and Intune Hybrid

This is one of the nicest offerings that I have seen for a while… using PowerBI and access to the CM database.

Highly recommend!

Some sample screen shots:


Details on the offering, including the download link:

Exploring your System Center Configuration Manager and Microsoft Intune (Hybrid) data on Power BI Dashboard

The SQL Server 2014 Upgrade Advisor


1.1 SQL Server Upgrade Readiness

One of the best ways to proceed with SQL Server upgrades is by running the Upgrade Advisor. The SQL Server 2014 Upgrade Advisor analyzes the configuration of installed SQL Server components, and then generates a report of issues that you must address to assure a successful upgrade.

1.1.1 To install the Upgrade Advisor

Either use the Upgrade Advisor installation file (sqlua.msi) in the redist folder of the installation media or download the *msi as part of the Microsoft SQL Server 2014 Feature Pack.

The best to way to get the items you need, use this download link:

Microsoft SQL Server 2014 Feature Pack

Select SQLDom.msi and SQLUA.msi (x64)


SQL Server 2014 Feature Pack Download

Install the downloaded files in the following order:

1. Install SQLDom.msi

2. Install SqlUA.msi

1.1.2 To Run the Upgrade Advisor

From the Start menu, lauch the SQL Server 2014 Upgrade Advisor.


SQL Server 2014 Upgrade Advisor – Home page

Start the Launch Upgrade Advisor Analysis Wizard. Click Next.


SQL Server 2014 Upgrade Advisor Analysis Wizard

Enter the SQL Server name, select components that you need to evaluate and click Next.


SQL 2014 Upgrade Advisor – Select Components

Select the Instance name, and appropriate Authentication method, click Next.


SQL 2014 Upgrade Advisor – Connection parameters

Select the appropriate databases to analyze, optionally select Analyze trace files and/or SQL batch files, click Next.


SQL 2014 Upgrade Advisor – Select Databases

Review Confirmation settings, then click Run.


SQL 2014 Upgrade Advisor – Confirm Selections

Upgrade wizard result dialog. The Launch Report button will display more detailed results.


SQL 2014 Upgrade Advisor –Results

1.1.3 View Upgrade Advisor Report

The Upgrade Advisor report can be run from the SQL Server 2014 Upgrade Advisor, shown at the begging of the last section, or from the completion dialog. Review and resolve any issues prior to the upgrade.

An example of a successful upgrade analysis report is shown next.


SQL 2014 Upgrade Advisor – Reporting

Use PowerShell to Install Server 2012 roles and features for CM

Using PowerShell to install the Server 2012 roles and features for Configuration Manager is really super easy. Discovered an issue installing several features as the script needed access to the server 2012 source.

Open PowerShell as an administrator, modify the –Source parameter (below) to point to the proper location for sources\sxs (note: UNC will work as well).


Get-Module servermanager
Install-WindowsFeature Web-Windows-Auth
Install-WindowsFeature Web-ISAPI-Ext
Install-WindowsFeature Web-Metabase
Install-WindowsFeature Web-WMI
Install-WindowsFeature BITS
Install-WindowsFeature RDC -Source K:\sources\sxs
Install-WindowsFeature NET-Framework-Features -Source K:\sources\sxs
Install-WindowsFeature Web-Asp-Net -Source K:\sources\sxs
Install-WindowsFeature Web-Asp-Net45 -Source K:\sources\sxs
Install-WindowsFeature NET-HTTP-Activation -Source K:\sources\sxs
Install-WindowsFeature NET-Non-HTTP-Activ -Source K:\sources\sxs

Proper TempDB creation for Configuration Manager

As a consultant, one of the major issues I see with SQL Server configuration for Configuration Manager is allowing default settings for TempDB.

The default TempDB size for all versions of SQL Server (prior to SQL 2016 – more on this later), is set to 8MB, file growth 1 MB.

Recently checked a Configuration Manager site SQL Server database properties, and TempDB had grown to 1.5 GB. This was with the default settings of 8MB size, 1 MB file growth. Can you imagine how many data file fragments occurred to get to 1.5GB?!

When SQL Server (MSSQLServer) service is restarted, TempDB gets reset to? The default size! And, the fun starts all over again.

First steps in correcting this; estimate the size of TempDB. There are some great calculators out there, Kent Agerlund did a nice job taking standard MSFT recommendations and converting it to an Excel “calculator”. This is a great starting point to determine the total size of TempDB, based on estimated client counts. Typically TempDB will be approximately 25-30% of the total, estimated CM DB size.

The only flaw with this calculator, it calculates a single TempDB file. TempDB can greatly benefit from multiple data files.

Let’s work through an example:

Projected # clients


Estimated CM data size

54 GB

Estimated TempDB size

16 GB

Making the assumption that your server has at least 2 processors and 8 cores, you’d want to start TempDB at least four (4) equal sized files, of 4GB each. Now, there may be some benefit in creating TempDB with eight (8) total, equal sized data files. Under no circumstance should you create more than 8 data files.

Now, to create, you can use the SQL Server management studio and add the files… even easier, use PowerShell.

To create using PowerShell follow the following instructions:

Open an elevated PowerShell prompt, create the additional SQL TempDB database files and set their initial size to a total of 16 GB by running the following command (the command is wrapped and should be one line):

Invoke-Sqlcmd –QueryTimeout 0
-InputFile C:\Setup\Scripts\ConfigureTempDB.sql


The SQL TempDB database files.

Note: change paths as appropriate – sample script can be downloaded for free, from book sample files, from my Reporting Services book.

As a side note, SQL Server 2016 now creates the following default TempDB settings. Probably still too small for most production instances. None the less, much better!


The SQL Server 2016 TempDB database files.

Intune – Mobile Application Management policy

What are Mobile Application Management policies?

According to Microsoft:

Mobile application management policies in Microsoft Intune let you modify the functionality of apps that you deploy to help bring them into line with your company compliance and security policies. For example, you can restrict cut, copy and paste operations within a managed app, or configure an app to open all web links inside a managed browser.


For example; when you first attempt to deploy a managed application, such as Skype for Business, you may receive the following informational dialog.

"The software you are trying to deploy must be associated with a mobile app management policy and there are currently none defined. Create a policy from the Policy workspace."


Application Policy Informational

To create an Application policy (sometimes called MAM), choose New Policy, then Mobile Application Management (platform), then choose Create a policy with the recommended settings, click Create Policy.

Note: This policy is not deployed, it will be associated with a subsequent app deployment. Also, note the available Managed Browser policies.


Policy – Create Mobile Application Management

Resultant MAM policy.


Policy – Mobile Application Management

The only modification made to the default MAM policy, was allow the device settings to control the encryption.


Policy – Mobile Application Management Properties

Now we are ready to Deploy Skype for Business. This application was deployed using the standard process. At the Mobile App Management step, associate the app with the App Management Policy, created in the last step. Click Next, through to Finish.


Deployment – with MAM policy


Configure and deploy mobile application management policies in the Microsoft Intune console

Multi-Identity and Mobile App Management with Microsoft Intune

Deploying Windows 10 GPO Administrative Templates

New GPO administrative templates are available with Windows 10.

You can find them here:

Administrative Templates (.admx) for Windows 10

The corresponding GPO settings matching XLS can be found here:

Group Policy Settings Reference for Windows and Windows Server

Note: You’ll want the “Windows 10 ADMX spreadsheet.xlsx” file

To install

If you have not previously enabled the domain GPO central store, see scenario 2 (next link):

Managing Group Policy ADMX Files Step-by-Step Guide