MiSCUG – Using Power BI to Report OS Deployment Stats

On 11 January 2019 I had the privilege to speak at the Michigan System Center Users Group meeting on the topic of using Power BI to report your OSD build stats.  This is a companion post to that presentation.

This is an update to my original post ( here ) on how to gather and present statistics on your build sequences.  I’ve taken what I’ve learned since that original post and have expanded the process to handle not only an OSD “build” but also a WaaS CompatScan or In-Place Upgrade, or any other Task Sequence.

Advertisement

Automating Windows 10 Servicing

[6-Jul-2018: Updated Script to v 1.2 – New .NET 3.5.1 install command (per Mike Horton @mikeh36)]

After attending MMS one of the items that I put on my “Post-MMS To Do” list was to patch my OS Upgrade package source the proper way.  I don’t want to do it manually, nobody does, so I set out to learn exactly how to do it right and script it.

That where Mike Terrill and Johan Arwidmark come in.

So your boss is going to want stats for your OSD sequence? [Part 2 – Reporting with Excel]

How to provide hard statistics on your build sequences.

---

In Part 1 I went into how I collected the data that would be used to report on the 2 goals my boss set out for our OS deployment; 1) a 90% success rate and 2) 60 minute build times.

ConfigMgr Current Branch–Windows PE Peer Caching

What is Windows PE Peer Caching?

Windows PE Peer Caching was a feature added in Configuration Manager Technical Preview 2.  During an OS deployment, it allows a machine being built to pull content from other systems on the local subnet (its peers) as opposed to going across a potentially slow WAN connection.  It is quite simply a peer-to-peer network of content providers.  This is similar functionality to 1E’s NomadBranch and 2Pint’s BranchCache for OSD Toolkit.