Category Archives: 1610

How can I use Express Updates when patching Windows 10 with Quality Updates in System Center Configuration Manager (Current Branch) ?

Introduction Windows 10 Enterprise first shipped in July 2015 with Windows 10 version 1507, and since then there have been 2 versions, Windows 10 version 1511 and Windows 10 version 1607. In spring of this year (2017) we will see … Continue reading

Posted in 1607, 1610, express updates, Windows 10 | 2 Comments

Why Telemetry is great, and why the uptake of Configuration Manager Current Branch is unprecedented

Introduction Brad Anderson (corporate vice president for Enterprise Mobility at Microsoft) wrote a blog post today about “What ConfigMgr Customers were Doing During the 2016 Holiday Break” and it revealed how a question posed by their own staff internally was … Continue reading

Posted in 1607, 1610, System Center Configuration Manager (Current Branch), System Center Configuration Manager Technical Preview, Telemetry, Windows 10 | Leave a comment

How can I install System Center Configuration Manager version 1606 (Current Branch) on Windows Server 2016 with SQL 2016

Introduction In a previous guide I showed you how to install System Center Configuration Manager version 1511 (Current Branch) on Windows Server 2012R2. Times are changing fast in this cloud-first  mobile-first world, and as a result the System Center Configuration … Continue reading

Posted in 1606, 1610, PowerShell, SQL Server 2016, System Center Configuration Manager (Current Branch), Windows Server 2016 | Leave a comment

Update 1610 for System Center Configuration Manager (Current Branch) is now available

Introduction Microsoft has released yet another update for System Center Configuration Manager (Current Branch), this time it’s version 1610, that means that since System Center Configuration Manager’s (Current Branch) first release there have been the following releases: 1511 (Initial release, … Continue reading

Posted in 1610, System Center Configuration Manager (Current Branch) | Leave a comment