Updates Servicing and Telemetry in Configuration Manager current branch Aaron Czechowski Senior Program Manager Microsoft Four years on product team nine years at Microsoft and 18 years working with Configuration Manager ID: 734525
Download Presentation The PPT/PDF document "Aaron Czechowski & Kerim Hanif" is the property of its rightful owner. Permission is granted to download and print the materials on this web site for personal, non-commercial use only, and to display it on your personal computer provided you do not modify the materials and that you retain all copyright notices contained in the materials. By downloading content from our website, you accept the terms of this agreement.
Slide1
Aaron Czechowski & Kerim Hanif
Updates, Servicing and Telemetry
in Configuration Manager current branchSlide2
Aaron Czechowski
Senior Program Manager, Microsoft
Four years on product team, nine years at Microsoft, and 18 years working with Configuration Manager
Program manager for Configuration Manager diagnostics and usage data (telemetry)
Active with Boy Scouts of America and an avid hiker
@
AaronCzechowskiSlide3
Kerim Hanif
Senior Program Manager, Microsoft
Four years on product team, 13 years at Microsoft, 16 years working with Configuration Manager.
Program manager for Configuration Manager updates and servicing
A culinary and scuba enthusiast
@
KerimHanifSlide4
Agenda
1
2
3
Updates and ServicingTroubleshooting
Diagnostics and Usage DataSlide5
Servicing Strategy
Simplify the upgrade experience
In-place upgrade from Configuration Manager 2012 to latest version
Support faster pace of updates for Windows 10 and Microsoft Intune
New Updates and Servicing node delivers periodic updates for new features, bug fixes, and extensions for hybrid deployments using Microsoft Intune
Listen to and more quickly respond to customer feedback
Foundational improvements in current branch allow us to respond to customer feedback more quicklySlide6
Configuration Manager Current Branch
Product
v
ersion
Release vehicle
Availability
Windows 10 features supported
Support
Windows Servicing Model supported
Configuration
Manager
Current Branch
Generally available December 2015 with updates released periodically throughout the year
New
features, security updates, and bug fixes
Can defer updates for up to 12 months before you must deploy updates to maintain support
Windows 10 Current Branch, Current Branch for Business,
and Long Term Servicing Branch
Current branch (version 1511)
Current branch (version 1602)
Current branch (version yymm)
Configuration Manager
Technical Preview (version yymm)
WINTER
SPRING
SUMMERSlide7
Kerim Hanif
Updates and ServicingSlide8
Module 1 Agenda
1
2
3
Types of updates and releasesService Connection Point
Order of operations
4
Known issues
5
Future improvementsSlide9
Types of updates and releasesSlide10
Consolidating all ConfigMgr updates
Updates and Servicing node in the console
No more searching for the updates
Get updates automatically from the cloud
No more Cumulative UpdatesService PacksMicrosoft Intune Extensions HotfixesReduce the update checklist as much as possiblehttps://technet.microsoft.com/en-us/library/mt691556.aspx GOAL:Slide11
Types of ReleasesBaseline E.g. Configuration Manager 1511 Full setup (CD)
Will be upgradeable from 2012 R2 SP1/SP2
Supported for 1 year
In-Console Update E.g. Configuration Manager 1602Not a full setup, cumulative
Requires a baseline release Supported for 1 yearOut-of-Band (OOB) UpdateWill be released if neededMostly will contain only featuresHotfixesWill be released if neededGDR (General Distribution Release)LDR (Limited Distribution Release)TraditionalSlide12
History of Releases
Production Release
(every 3-4 months)
Technical Preview Release
(every month)DateBaseline (CD) TPMay 2015Baseline (CD) TP2 (8271)July 2015
Baseline (CD)
TP3 (8287)
August 2015
In-console Update (1st)
1509 (8299)
September 2015
In-console Update
1510 (8321)
October 2015
Baseline (CD)
1511 (8325)
TP4 (8325)
December 2015
In-console Update
1512 (8336)
December 2016
In-console Update
1601 (8347)January 2016In-console Update 1602 (8355) February 2016In-console Update 1602 (8360)March 2016In-console Update 1603 (8372)March 2016Baseline (CD)TP5 (8385)April 2016In-console Update 1604 (8385)April 2016In-console Update 1605 (8396)May 2016https://technet.microsoft.com/en-us/library/mt607046.aspxSlide13
History of Releases
Production Release
(every 3-4 months)
Technical Preview Release (every month)Updates (OOB)None yet(will be released if needed)None (most cases we will not be releasing an update for preview builds)Hotfix1511 Traditional: KB3125905, KB3118485, KB3124274, KB3128090, KB3127032, KB3101706, KB3122677, KB3139572, KB3140781, KB3142341, KB31454011511 GDR: KB3122637 (Exchange Connector)
1602:
None yet
None
(most
cases we will not be releasing an hotfix for preview builds)Slide14
Recommended Customer Infrastructure
Production
Technical
PreviewConfigMgrPreview BuildStandalone Primary
No hierarchy support
10 Clients
Update monthly
Test new features
Pre-Production
ConfigMgr
Production Build
Replica of production site (on the server side)
Appropriate number of clients for testing purposes
Install updates here first
ConfigMgr
Production Build
Live environmentSlide15
Service Connection PointSlide16
Service Connection Point
Can be
Online
or Offline or Skipped (not recommended)
During Setup
After SetupSlide17
Requirements Service Connection Point (SCP) role needs to be installedEither in Online
or
Offline
modeSCP role == Intune Connector role (doesn’t exist anymore)ConfigMgr 2012 R2SP1/SP2 Hybrid (
Intune+ConfiMgr) customers upgrading to 1511 will not need to install SCP since it is already thereSlide18
If SCP Installation is Skipped
Nags will show
Nag will only show at the top level site, during console start, to the admins with “
SMS_Site
modify” rightSlide19
Offline ServicingCreated for customers that can’t connect to a cloud serviceSTILL needs to install Service Connection Point (SCP) role to a server (doesn’t have to be connected to the internet)
Set the SCP to
Offline
modeUse “Service Connection Tool” on computer connected to the internet download the content from the cloud service
TIP: ServiceConnectionTool.exe needs to be copied together with all the other files in the directory when needs to be copied and run in another locationRecommended to have 2GB on media (if USB)Slide20
Service Connection Tool
Server with Service Connection Point
(no internet connection)
Any machine with
internet connectionMicrosoft CloudServiceConnectionTool.exe-Prepare -usagedatadest D:\USB\usagedata.cab
1
2
Cab
ServiceConnectionTool.exe
-
Connect
-
usagedatasrc
D:\USB\usagedata.cab –
updatepackdest
D:\USB\UpdatePacks
1602
1602
ServiceConnectionTool.exe
-
import –updatepacksrc D:\USB\UpdatePacks 3Slide21
Order of operationsSlide22
Updating Site SystemsCAS/Standalone PrimaryDownload automatic in Online
mode
Download and import manually in
Offline mode (using the Service Connection Tool) For both modes, initiate install manually using the console Primary Sites
Download and install automatic but can be controlled specifying “Service Windows” Secondary SitesDownload and install is manualDistribution Points and all other site system rolesDownload and install is automaticSlide23
Configuration Manager ConsolesDetects during initialization, auto upgrades if server version is greaterCan be ignored, but not recommended
If ignored, it continues nagging when using the consoleSlide24
ClientsAllow admins to select a pre-production collection to test new clientAfter testing, admins can choose to promote the new client bits to productionSlide25
Known issuesSlide26
Known Issues as of 1602Full administrator with default scope can NOT see 1602 update. Admins needs to have permission for “All instances of the object” under “Security Scopes”
Redistributables can fail to download for various reasons, please check dmpdownloader.log and configmgrsetup.log for which exact files it fails to download
If the update is being downloaded, CM admin console [Monitoring]->[Overview]->[Site Servicing Status] does not show status for each site
If the update content is being replicated, CM Admin console [Monitoring]->[Overview]->[Site Servicing Status] does not show status for each siteSlide27
Known Issues as of 16021602 update shown in Admin console as Not Applicable, this is because the environment has a LONG CM installation path that 1602 cannot handle correctly.
<CM
InstallDir
>\Inboxes\clifiles.src\Configuration.mof will be overwritten. Please find the backup from <CM
InstallDir>\data\hinvarchive\ and add your custom extension back.Using 1602 CD.Latest to add a new peer primary site to a CAS, you will get a prereq failure (setup file build number does not match parent site build number), after verifying this is the only prereq rule failure, use /noprereq optionSlide28
Future improvementsSlide29
Future ImprovementsMonitoring interface renamed to “Updates and Servicing Status”More granular status monitoringClearly see each phase in a new monitoring user interface (Download, Replication, Prerequisite install and Install) progress
References to applicable log files in user interface
SQL upgrade performance improvements
Pre-release Consent for pre-release featuresFeature node improvementsPrevious updates moved to new History node
Limiting SQL access during database upgrade (1602+)Stop all current SQL connections to CM DBDeny remote MP “execute” permissions to CM DB1602+ MPs will return "no new policy" to clients when update is in progressSlide30
DemonstrationUpdates and Servicing in Configuration ManagerSlide31
Module 1 Summary
1
2
3
Types of updates and releasesService Connection Point
Order of operations
4
Future Improvements
5
Best practicesSlide32