We are happy to let you know that update 1710 for the Technical Preview Branch of System Center Configuration Manager has been released. Technical Preview Branch releases give you an opportunity to try out new Configuration Manager features in a test environment before they are made generally available. For information about this month’s new preview features, please see the following two posts.

• Update 1710 for Configuration Manager Technical Preview Branch – Available Now!
• Introducing support for Cryptography: Next Generation (CNG) certificates in Configuration Manager

Here is a step by step upgrade path from System Center Configuration Manager 2012 SP2 hosted on Windows Server 2012 R2 to System Center Configuration Manager 1702 or later hosted on Windows Server 2016.

These steps can be used if you want to upgrade Configuration Manager 2012 R2, R2 SP1 or SP2 version to Configuration Manager 1702, or upgrade your environment to the latest operating system and SQL server.

I strongly recommend you read Upgrade to System Center Configuration Manager before following the upgrade path.

Important points to remember:

• You can directly upgrade Configuration Manager 2012 R2 ,R2 SP1 or SP2 to 1702, no update installation is required.
• You will need to run TestDBupgrade before upgrading the Configuration Manager 2012 SP1 environment to Configuration Manager 1702. (If we are using standalone media for 1702)
• You will need to download Configuration Manager 1702 setup files from your volume licensing website. When you have version 1702 baseline media, you can upgrade the following to a fully licensed version of System Center Configuration Manager version 1702:
  • An evaluation install of System Center Configuration Manager version 1702
  • System Center 2012 Configuration Manager with Service Pack 1
  • System Center 2012 Configuration Manager with Service Pack 2
  • System Center 2012 R2 Configuration Manager
  • System Center 2012 R2 Configuration Manager with Service Pack 1

Let get to it!

In this example we are running a Primary site (Configuration Manager 2012 SP2) on a Windows Server 2012 R2 OS with SQL Server 2014 hosting the Configuration Manager database on the same box. In below steps we are

• Upgrading Base OS windows Server 2012 R2 to Windows Server 2016
• Upgrading SQL Server 2014 R2 to SQL server 2016
• Upgrading Configuration Manager 2012 SP2 to Configuration Manager 1702

Base OS Upgrade

If you plan to upgrade the base OS of the Configuration Manager primary site server, and upgrade SQL then follow these steps:

Take a backup of your existing primary site database, SMS backup, Source directory, SCCMContentLib (All the folders for SCCMContentlib). See  https://technet.microsoft.com/en-in/library/gg712697.aspx#BKMK_SupplementalBackup

1. Rename your current Configuration Manager primary site server and create a new machine with Windows server 2016 installed.
2. It should have same name, drive letters and drive structure as your earlier site server.
3. Install all the pre-requisites for Configuration Manager. See Site and site system prerequisites for System Center Configuration Manager.

SQL upgrade

Please refer to this article for SQL upgrade:

https://docs.microsoft.com/en-us/sccm/core/plan-design/configs/support-for-sql-server-versions#upgrade-options-for-sql-server

As we are running SQL on primary site server locally, we need to install the upgraded version of SQL on this newly created server.

1. In our previous server we were running SQL server 2014 (Microsoft SQL server 2014 (SP2-CU2)- 12.0.5522.0 (X64))

2. On new Primary site server, we installed Microsoft SQL server 2016 Ent version (Microsoft SQL Server 2016 SP1 -13.0.4001.0 (X64))

3. Copied the smsbackup locally on the new server.

4. Copy CM_<Sitecode>.mdf and CM_<SiteCode>_log.ldf files from smsbackup location to the location on the new server exactly where it was stored in your old Primary (SQL) server. For example, if .mdf and .ldf files on your old server are stored in <G:\MSSQL\11\Data> then it has to be stored in the same location on the new server.

SMSBackup Location:

Copy to below location (As per the previous server database files location):

5. Now attach the database on the New server (SQL) and then run site recovery.

Click on Add and provide the location for .mdf and .ldf files copied from the backup and click ok.

With this we should see the Primary Site Database visible under Databases in SQL Server Management Studio.

Now we can start the site recovery Process

Primary Site Recovery

6. Run the Configuration Manager setup and recover the site using “Manually recovered DB option”.

https://technet.microsoft.com/en-us/library/gg712697.aspx#Recover

-Please follow below link for the Recovery process.

-General:   System Center 2012 Configuration Manager R2 – Disaster Recovery for Entire Hierarchy and Standalone Primary Site recovery scenarios     http://www.microsoft.com/en-us/download/details.aspx?id=44295

-After waiting for couple of hours, we can start the Upgrade process for Configuration Manager 1702.

-Copy the Configuration Manager 1702 Media locally on the Primary site server.

-Also take the current SMSbackup for the primary site.

-The following is a checklist of required and recommended actions to perform prior to upgrading to System Center Configuration Manager:

https://docs.microsoft.com/en-us/sccm/core/servers/deploy/install/upgrade-to-configuration-manager#bkmk_checklist

-Make sure that all the Tasks are verified before we go for the Upgrade.

-Also make sure that TestDbUpgrade is successful before we go for the upgrade.

Note: We need to take the backup of current Database and restore to a separate SQL server (Non- production SQL) and run TestDbUpgrade.

Test upgrade should not be run on production database.

-Now we can run the Configuration Manager 1702 media to start the upgrade process.

https://docs.microsoft.com/en-us/sccm/core/servers/deploy/install/upgrade-to-configuration-manager#bkmk_upgrade

NOTE– We can implement all the above steps in case we have multiple sites, to upgrade multiple sites, we need to perform the above steps from Top to bottom (First we need to Upgrade CAS then Primary sites)

–Rajat Choubey

Support Engineer, Microsoft

Starting with System Center Configuration Manager, version 1702, unknown computers that are started from media or PXE may not find task sequences targeted to them. The SMSTS.log shows:

There are no task sequences available to this computer. Please ensure you have at least one task sequence advertised to this computer"
 Unspecified error (Error: 80004005; Source: Windows)

This issue may occur if the Previous button on the “Select a task sequence to run” page is selected on the unknown computer.

This is a known issue that is now fixed by applying Update rollup for System Center Configuration Manager current branch, version 1702.

We are aware of a new publicly disclosed class of vulnerabilities that are referred to as speculative execution side-channel attacks as detailed in Microsoft Security advisory ADV180002. These vulnerabilities affect many modern processors and operating systems, including chipsets from Intel, AMD, and ARM.

This post is intended to centralize and share current guidance to help Enterprise Mobility + Security customers ensure their environments are protected against these vulnerabilities. We will continue to update as more information becomes available.

The post includes sections for the three main customer scenarios:

• Configuration Manager – just the first section applies
• Configuration Manager with Microsoft Intune (hybrid) – all three sections may apply
• Microsoft Intune – just the third section applies

Configuration Manager

Windows Update

If you have Windows 10 devices receiving Windows Update for Business policy, or are using co-management and the Windows Update workload is switched to Microsoft Intune, these devices will automatically get the January cumulative update on the ring definition you define.

For traditional management of Windows 10 and other affected operating systems, use the software updates management feature of Configuration Manager to deploy the January cumulative update. For example, 2018-01 Cumulative Update for Windows 10 Version 1709 for x64-based Systems (KB4056892). For more information, see Windows client support article KB 4073119. (For more information about additional actions specifically for Windows Server, see “Configuration Manager infrastructure” section below.)

Compatibility issues may exist with a small number of antivirus software products. As a result, Microsoft is only offering the Windows security updates released on January 3, 2018, to devices running antivirus software from partners who have confirmed that their software is compatible with the January 2018 Windows security update. If your devices are not detecting the security update as applicable, you may be running incompatible antivirus software, and you should consult the antivirus software vendor. For more information, see Microsoft Support article KB 4072699.

Firmware update

Check for available firmware updates from your hardware vendor. For more information about an update for Microsoft Surface, see support article KB 4073065. Download the Windows Installer package for Microsoft Surface, and deploy using a Configuration Manager application. We recommend an application versus a package for the enhanced compliance reporting capabilities.

Customers running Configuration Manager current branch version 1706 or later can manage Microsoft Surface driver updates through the software update channel.

Some customers may experience devices prompting for BitLocker key entry after updating firmware, even if not normally required. If you are using BitLocker, we recommend testing this behavior, and then consider whether to suspend BitLocker during this process. If needed, you can use a custom task sequence to order these events. For example,

• Disable BitLocker step
• Install Application step: reference the application for the firmware update
•  Restart Computer step

When using the Disable BitLocker step in a task sequence, protection resumes after restart.

Updates for other managed devices

For information about Apple macOS devices, see Apple support article HT208394.

Install the latest updates for Linux and UNIX. For more information, check with your specific Linux distro vendor and UNIX operating system vendor.

Verify protection on Windows devices

To verify protection against these vulnerabilities, both the software updates management and application management features have compliance reporting capabilities. Use these capabilities to determine device compliance for the January Windows update and the firmware update application.

Additionally, there is a new Windows PowerShell module, SpeculationControl, which you can use to verify protections are enabled. For more information, see the “Verifying protections are enabled” section of Microsoft Support article KB 4073119. We recommend downloading the version from the TechNet ScriptCenter as it works offline without further prerequisites. (Using the Install-Module process requires Internet access, trusting the PSGallery repository, and installing a NuGet package.)

Customers running Configuration Manager current branch version 1706 or later can use the Run Scripts feature to deploy a script and receive near real-time response from active clients. The following PowerShell code snippet is an example of what you can use to automate running the Get-SpeculationControlSettings cmdlet at scale:

# The SpeculationControl module is signed; default ‘Restricted’ policy won’t work

Set-ExecutionPolicy AllSigned -Scope Process -Force

# Pull the cert from the module

$cert = Get-AuthenticodeSignature .\SpeculationControl.psd1

# Add the CA cert to the Trusted Publishers store

$store = New-Object System.Security.Cryptography.X509Certificates.X509Store “TrustedPublisher”,”LocalMachine”

$store.Open(“ReadWrite”)

$store.Add($cert.SignerCertificate)

$store.Close()

# Import the module and run the cmdlet

Import-Module .\SpeculationControl.psd1

Get-SpeculationControlSettings

The final cmdlet returns a list of settings and their states. While the Run Scripts feature will report this output, a script to wrap and return a single value makes for easier reporting across many devices.

For example, save the Get-SpeculationControlSettings output into a variable, then access each setting as a property:

$SpecSettings = Get-SpeculationControlSettings
If ($SpecSettings.BTIHardwarePresent) { write-host “BTI hardware present”}

We have also published a compliance baseline to help verify protections.  To download visit https://gallery.technet.microsoft.com/Speculation-Execution-Side-1483f621. 

Configuration Manager infrastructure

As well as deploying the Windows and firmware updates to servers, also review Microsoft Support articles KB 4072698 for Windows Server and KB 4073225 for SQL Server.

For Windows Server, there are additional actions necessary to enable protections. (For Windows Clients, the protections are enabled by default. For Windows Servers, the protections need to be enabled.) Based on feedback from Microsoft IT, we recommend the following order of operations to optimize the number restarts:

• Enable protections (see the “Enabling protections on server” section of KB 4072698)
• Install Windows update
• Restart
• Install firmware update
• Restart

(And remember to possibly disable BitLocker if in use on servers. When using the Disable BitLocker step in a task sequence, protection resumes after restart.)

KB 4073225 outlines customer guidance for SQL Server, which is a critical part of any Configuration Manager system. Currently, we recommend following the SQL guidance for Configuration Manager site database servers, except the following suggested steps which may impact Configuration Manager functionality and performance. Do not perform the steps for these two categories at this time:

• Running SQL Server with CLR enabled (sp_configure ‘clr enabled’, 1)
• Using Linked Servers (sp_addlinkedserver)

For customers that run their Configuration Manager environment in Microsoft Azure, or are using connected Azure services like the Cloud Management Gateway, see this blog post for information. 

Configuration Manager with Microsoft Intune (hybrid)

For more information about Apple iOS and macOS devices, see Apple support article HT208394.

For more information about Android devices, see Google’s blog post and support FAQ. 

Microsoft Intune

Windows 10 devices will automatically get the January cumulative update on the ring definitions you define. For example, 2018-01 Cumulative Update for Windows 10 Version 1709 for x64-based Systems (KB4056892). For more information, see Windows client support article KB 4073119.

For information on classic Intune PC management, see the software update documentation.

Compatibility issues may exist with a small number of antivirus software products. As a result, Microsoft is only offering the Windows security updates released on January 3, 2018, to devices running antivirus software from partners who have confirmed that their software is compatible with the January 2018 Windows security update. If your devices are not detecting the security update as applicable, you may be running incompatible antivirus software, and you should consult the antivirus software vendor.  For more information, see Microsoft Support article KB 4072699.

For more information about Apple iOS and macOS devices, see Apple support article HT208394.

For more information about Android devices, see Google’s blog post and support FAQ.

We will continue to update this post as more information becomes available.

If you have any feedback, please use the Windows 10 Feedback Hub.

The System Center Configuration Manager Team

I’m pleased to announce that over the next few days, Steven Rachui, a Principal Premier Field Engineer focused on manageability technologies will be sharing a video tutorial series here about software updates.  His topics will be:

• ConfigMgr Current Branch – Software Update Delivery
• ConfigMgr Current Branch – Windows Update for Business
• ConfigMgr Current Branch – Express Updates

We invite you to tune in and enjoy.  Leave us your comments if you would like to see more of these in the future.

The release of Windows 10 brought with it a change in the way updates are released – updates are now cumulative.  Since the release of Windows 10 this same cumulative update approach has been adopted for the remainder of supported operating systems.  While this approach has significant advantages there still remains some confusion about what it all means. 

The video linked below was prepared by Steven Rachui, a Principal Premier Field Engineer focused on manageability technologies.  In this session, Steven talks through the changes, why the decision was made to move to a cumulative approach to updating, how this new model affects software updating, how the cumulative approach is applied similarly and differently between versions of supported operating systems and more.

Next in the series, Steven will discuss Windows Update for Business and its integration with Configuration Manager.

Posts in this Series

• Software Updates Video Tutorial Series Introduction
• ConfigMgr Current Branch – Software Update Delivery (this post)
• ConfigMgr Current Branch – Windows Update for Business 
• ConfigMgr Current Branch – Express Updates

An update rollup for System Center Configuration Manager current branch, version 1710, is now available. This update is available for installation in the Updates and Servicing node of the Configuration Manager console. Please note that if the Service Connection Point is in offline mode, you must re-import the update so that it is listed in the Configuration Manager console. Refer to the Install in-console Updates for System Center Configuration Manager topic for details.

For complete details regarding the update rollup for ConfigMgr current branch v1710, including the list of issues that are fixed, please see the following:

4057517 – Update rollup for System Center Configuration Manager current branch, version 1710 (https://support.microsoft.com/help/4057517)

We are happy to let you know that update 1801 for the Technical Preview Branch of System Center Configuration Manager has been released. Technical Preview Branch releases give you an opportunity to try out new Configuration Manager features in a test environment before they are made generally available. For information about this month’s new preview features, please read:

Update 1801 for Configuration Manager Technical Preview Branch – Available Now!

Ensuring software updates are applied across an organization is a key focus area for system administrators. Configuration Manager has been used by thousands of organizations for years to aid in this pursuit.  Other organizations have opted to use standalone WSUS for their software updates needs while still others may rely solely on the built-in engine to pull updates from Microsoft Updates.

Windows Update for Business, which was introduced around the time of the Windows 10 release, offers an additional option to aid administrators in the critical pursuit of ensuring systems are kept up to date. Understanding what Windows Update for Business is and how it can be implemented either standalone or through integration with Configuration Manager is critical, so you make the best choice for your business.  Steven Rachui, a Principal Premier Field Engineer focused on manageability technologies, talks through the various options and how they can be used in the video linked below

Next in the series, Steven will discuss how Express Updates work and how they are supported in a Configuration Manager environment.

Posts in this Series

• Software Updates Video Tutorial Series Introduction
• ConfigMgr Current Branch – Software Update Delivery
• ConfigMgr Current Branch – Windows Update for Business (this post)
• ConfigMgr Current Branch – Express Updates

Previous posts in this series have referenced the update approach to delivering Windows updates that was introduced first with Windows 10. One side effect of the cumulative update approach is that the single update released is larger than the individual updates of days past. Further, at each release of an update, size increases as additional updates are added over time. This can have a noticeable effect in an organization each month as these new and larger updates are distributed across the network

Express is a capability of WSUS and the Windows Update Agent that was added to help reduced the overall network impact of these larger updates. Express will identify just the portion of the update that is needed by the client and download only that piece. The effect is much smaller overall downloads on the client. Configuration Manager current branch 1702 (though 1710 and higher is recommended for best performance) added full support for Express. Understanding how Express works is important so that administrators know what to expect and can plan accordingly. In the video linked below, Steven Rachui, a Principal Premier Field Engineer focused on manageability technologies, details how Express works and how supporting Express is supported in a Configuration Manager environment.

 This is the final post in this series. Please, leave us a comment and let us know your suggestions for topics for future series.

Posts in this Series

• Software Updates Video Tutorial Series Introduction
• ConfigMgr Current Branch – Software Update Delivery
• ConfigMgr Current Branch – Windows Update for Business
• ConfigMgr Current Branch – Express Updates (this post)

Beginning with December 2017, Microsoft is releasing antimalware platform updates for Windows Defender each month. The platform updates will be published as follows: category: Definition Updates, product: Windows Defender. If you use a Configuration Manager automatic deployment rule (ADR) to approve and deploy definition updates for Windows Defender, that same ADR will now pick up these monthly platform updates. The platform updates are applicable to Windows Defender running on Windows 10 (version 1607 and later) and Windows Server 2016.

The title of the platform updates will be in the form: Update for Windows Defender antimalware platform – KB 4052623 (Version X.X.X.X). For example, Update for Windows Defender antimalware platform – KB4052623 (4.12.17007.17123). Initially, for a given month, the platform update is released gradually. For this reason, you may see low or no required and installed counts in your Configuration Manager console. And there may be more than one version of a platform update released in each month as part of the gradual deployment process. Once the platform update is released broadly, more clients will find the final version of the update as applicable and install.

Frequently Asked Questions

What makes up the platform for Windows Defender and why does it need to be updated monthly?

The platform is often referred to as the “antimalware client”. It is composed of the services, drivers, user interface, and management providers needed to provide protection functionality. In the ever-changing landscape of antimalware and spyware, it is necessary to regularly update components that make up the platform for the highest level of protection.

I keep up-to-date with engine and definition updates. Isn’t that enough to protect my endpoints?

While keeping up-to-date with signatures and engines is a best practice, a machine that is up-to-date with both definition/engine and platform updates can have a higher protection level than a machine that is just update-to-date with definition/engine updates.

Are these platform updates also included in the monthly quality updates for Windows 10?

No. The platform updates are released out of band of the monthly quality updates for Windows 10. New feature updates for Windows 10 will include the latest platform version for Windows Defender at that time but then must be updated monthly via the platform updates.

A second update rollup for System Center Configuration Manager current branch, version 1710, is now available. This update is available for installation in the Updates and Servicing node of the Configuration Manager console. Please note that if the Service Connection Point is in offline mode, you must re-import the update so that it is listed in the Configuration Manager console. Refer to the Install in-console Updates for System Center Configuration Manager topic for details.

For complete information about this update rollup for Configuration Manager current branch v1710, including the list of issues that are fixed, please see the following:

4086143 – Update rollup 2 for System Center Configuration Manager current branch, version 1710 (https://support.microsoft.com/help/4086143)

This update replaces the following previously released updates. If KB4086143 is installed, the previously released updates will no longer appear as applicable in the Updates and Servicing node of the Configuration Manager console:

• 4057517 Update rollup for System Center Configuration Manager current branch, version 1710
• 4088970 Automatic enrollment for co-managed device fails in System Center Configuration Manager current branch, version 1710

Microsoft System Center Configuration Manager 2007 has a support and servicing lifecycle during which we provide new features, software updates, security fixes, etc. This lifecycle lasts for a minimum of 10 years from the date of the product’s initial release. The end of the lifecycle is known as the product’s end of support. Configuration Manager 2007 reaches the end of its support lifecycle on July 9, 2019. We strongly recommend that you migrate your Configuration Manager 2007 infrastructure as soon as possible to the latest version of Configuration Manager (current branch).

Frequently asked questions

Q1: What does end of support mean for me?

A1: Although Configuration Manager 2007 will continue to function after July 2019 the following conditions will apply to the software:

• No Microsoft support will be available.
• No security updates or fixes will be available.

Q2: When does extended support end for Forefront Endpoint Protection 2010?

A2: July 9, 2019. For more information, go to the Support Lifecycle page.

Q3: Will I continue to get definition updates for FEP 2010?

A3: Microsoft plans to discontinue definition, engine, and platform updates for FEP 2010 once the end of support is reached. This discontinuation may occur without any notice.

Q4: What should I do to prepare?

A4: To prepare for end of support, we recommend that you do the following:

• Review the migration guidance and plan your migration to Configuration Manager (current branch).
• If you are also running FEP 2010, migrate to System Center Endpoint Protection (current branch)
• If you have a Premier Support agreement, contact your account team to develop a migration plan. If you don’t have a Premier Support agreement or an agreement with an existing solution provider, you can find a provider at Enterprise Mobility + Security Solution Providers.

Q5: What else should I consider?

A5: Windows 7 and Office 2010 both reach the end of their support lifecycle in 2020. Please review the upgrade options for both products.

• Office 2010 End of Support
• Windows lifecycle fact sheet

For more information please read KB 4096323 Support for System Center Configuration Manager 2007 and Forefront Endpoint Protection 2010 ends July 9, 2019.

Administrators who opted-in to the first (early) wave deployment for System Center Configuration Manager current branch, version 1802, have an update available in the Updates and Servicing node of the Configuration Manager console. This update, made available on May 4, 2018, addresses important late-breaking issues that were discovered during the final release process for version 1802. 

For more information, including the issues fixed and the applicability of the update, please read:

4132447 : Update 2 for System Center Configuration Manager version 1802, first wave – https://support.microsoft.com/help/4132447

In January we presented a Software Update Video Tutorial series. This series hosted by Steven Rachui, was focused on the changes to software updates in Configuration Manager current branch. By popular demand we are adding another video tutorial for Office 365 updates. In this latest video Steven Rachui, a Principal Premier Field Engineer demonstrates configuring a deployment of O365 in Configuration Manager and then discusses the options available for delivering updates for that O365 installation using Configuration Manager 2012 and Configuration Manager current branch.

For people who are new to software updates or who want a refresher, Steven has made his Software Updates Foundations series available. The tutorials in the series are:

• ConfigMgr 2012 – Software Updates - Part I – Introduction and Overview - This video begins a series detailing the Software Update component in ConfigMgr 2012.  Discussion includes comparing differences between ConfigMgr 2007 and ConfigMgr 2012.  Demonstrations also include a general walkthrough of Software Updates components in the console with brief explanation about each.
•  ConfigMgr 2012 - Software Updates - Part II - Server Configuration - This video focuses on detailing the server-side components, including detailed discussion of the Software Update Point - including data flow and configuration options. Discussion then turns to configuring software updates for deploying, discussing strategies for using software update groups, creating deployment packages and automated deployment rules. The session concludes by reviewing the various client-side configurations that are implemented through site server settings.
•  ConfigMgr 2012 - Software Updates - Part III - Server - Deep Dive - This video is a deep dive on the server side that investigates the back-end processing that happens when various administrative actions are taken in the console.  Topics covered include the replication of software update metadata and content data.  The session also discusses how information in the console is expressed in the database.
•  ConfigMgr 2012 - Software Updates - Part IV – Client - This video focuses on the client experience when deploying software updates in several scenarios.  Discussion centers around the client-oriented software update components and gives examples of basic and more advanced deployments to show the user experience.
•  ConfigMgr 2012 - Software Updates - Part V - Client – Internals - This video is a deep dive into the process of software update scanning and installation.  Demonstrations include a detailed look at the scanning process, a review of log files key to software update deployment and a look at a few key WMI namespaces involved in software update installation.
•  ConfigMgr 2012 – Software Updates – Part VI – Monitoring Software Updates - This video focuses on monitoring software update deployment and compliance.  Discussion includes the various nodes of the ConfigMgr console, the data available in each and briefly touches the various report options.
•  ConfigMgr 2012 – Software Updates – Part VII – Automating Software Updates - This video focuses on opportunities to automate routine tasks in software updates.  Specific demos and scripts show automation of software update group maintenance, deployments, maintenance of deployment packages and more.

We would love to hear your suggestions for topics for future series.

An update rollup for System Center Configuration Manager current branch, version 1802 is now available. This update is available for installation in the Updates and Servicing node of the Configuration Manager console. Please note that if the Service Connection Point is in offline mode, you must re-import the update so that it is listed in the Configuration Manager console. Refer to the Install in-console Updates for System Center Configuration Manager topic for details.

For complete details regarding the update rollup for ConfigMgr current branch v1802, including the list of issues that are fixed, please see the following:

4163547 - Update rollup for System Center Configuration Manager current branch, version 1802 (https://support.microsoft.com/help/4163547)

Windows Analytics Upgrade Readiness customers, including Configuration Manager users, may have noticed data from some devices not being updated. The Upgrade Readiness team have now re-enabled a limited subset of the diagnostic data for Windows 7 devices, enough to use Upgrade Readiness.  You will find more information including instructions for how to resume diagnostic data collection here:

https://blogs.technet.microsoft.com/upgradeanalytics/2018/07/02/upgrade-readiness-re-enabled/

Over the next few weeks we will be publishing another video tutorial series on our YouTube channel focused on Operating System Deployment (OSD) with Configuration Manager. These videos have been prepared by Steven Rachui, a Principal Premier Field Engineer focused on manageability technologies.

This series will be divided into 4 main sections, each consisting of multiple tutorials.

•  OSD - Introductory Sessions for those who are new to OSD. Using Config Manager 2012 to demonstrate, Steve covers all the foundational topics including image capture, task sequencing, driver management and PXE.
• OSD - A Deeper Dive will get into task sequence variables, USMT and MDT integration, Pre-staged media and nested task sequences in Configuration Manager current branch.
•  OSD - Advanced Concepts includes optimizing task sequences, UEFI, custom boot images, DaRT, troubleshooting and automation.
• OSD and Windows 10 discusses servicing options and the imaging options available for Windows 10 in Configuration Manager.

Posts in the OSD Introductory Sessions 

• Part I - Introduction and Basics
• Part II - Obtain and Import the Image
• Part III - Task Sequencing
• Part IV - Image Deployment
• Part V - The Logical Task Sequence
• Part VII - Driver Management
• Part VIII - Understanding PXE
• Part IX - Standalone USMT

Go straight to the playlist

We hope you enjoy.