MMS2016 Upgrading to System Center Configuration
Download
Report
Transcript MMS2016 Upgrading to System Center Configuration
Upgrading to System Center Configuration
Manager
So much easier than the last major update!
Wally Mead
Cireson
Brian Mason
Wells Fargo
Wally Mead
@Wally_Mead
Microsoft MVP Enterprise Mobility
SMS before it had a version
Red Robin!
Brian Mason
@abetterpc
Microsoft MVP Enterprise Mobility
SMS 2.0 SP2
Wine!
The Scope of an Upgrade
In just 60 seconds
Upgrade Scope
You’re already on CM07 SP2 or CM12 SP1/2
This is usually in-place, but can be a migration
No new hardware needed like CM07 to CM12
Tech Preview – Tech Preview is self updating and not
part of this discussion
Freakshows on SMS 2003 will require an after-hours
consultation at the bar!
Validate that you are ready to move fast in the future!!!
CM Versions
CM07
• At least SP2 (R2/R3 or not)
• Migration only
• You can leave now
• You already know migration
• OK, really stay, you’ll still
learn good info for the
future
CM12
• All versions but RTM
• Upgrade or Migration
• Upgrade is in-place
• Migrate if you have new
hardware or want fresh OS
• TestDBUpgrade!
• New ADK (get used to it)
The Upgrade Process
Prep, verify, upgrade, verify
General Upgrade Process
Verify software versions are supported
Verify current environment is functioning properly
• Site systems are healthy
• Component status is OK
• No inbox backlogs
• Clients are communicating properly
• Deployments are functioning correctly
Backup current site/hierarchy!
Upgrade Prep
Remove MP replicas
Uninstall AMT OOB and System Health Validator roles
Remove SUP NLBs
Disable maintenance tasks
Run Prereqchk.exe
• This may indicate that you need to upgrade some operating system components
Run TestDBUpgrade!
• Upgrades a copy of the site database to the new version
Close all running consoles
CAS 1st (or hey, migration can get you off using a CAS)
Demo
Prepare for upgrade
Verification Process
Verify ConfigMgrSetup.log
Verify site system health
Verify component status
Verify reports run
Upgrade remote consoles
Upgrade child sites
Recommended to upgrade child sites as soon as possible
Upgrade clients
• No confirmed doc on CM12 support length
Demo
Verify after upgrade
Current Branch
After verification, don’t stay on 1511 - it’s buggy
Upgrades will start to show in the Updates and Servicing node of the
console
• Update to the 1602 update as a minimum
You can skip 1602 and go straight to 1606 or 1610, etc.
Communicate out that these updates are going to keep coming; you’re
now on a moving train with just one year of support per update build
You can skip the 1511 client and go straight to 1602 or the latest (1511
has a bug – KB 3140781)
Upgrading Current Branch
The Updates and Servicing feature will automatically detect and
download applicable upgrades every 3-4 months
• ServiceConnectionTool.exe supports disconnected environments
• Independent release cycle than WIn10 branches
You have control over which build you want to install and when
Supports pre-production client testing before release to full production
In-console monitoring of update status
CM upgrades primary sites after it updates the CAS - you just sit back
and watch the show
Server and SQL Versions
• Only Windows Server 2008, Windows Server 2008 R2, Windows
Server 2012 and Windows Server 2012 R2 are supported as site
systems
• Windows Server 2008 and R2 support will end at end of 2016
• Only SQL Server 2008 R2 SP3, SQL Server 2012 SP2 and SQL Server
2014 SP1 are supported for site database
• SQL Server 2008 R2 support will end at end of 2016
• Secondary sites support Express editions of SQL Server 2012 SP2 and
SQL Server 2014 SP1
https://technet.microsoft.com/en-US/library/mt628077.aspx
Impossible?
Out of Band Updates
https://technet.microsoft.com/en-us/library/mt691544.aspx
Logs to Monitor
DMPDownloader.log
• On Service connection point – shows discovery and download of new builds
Hman.log
• On CAS or primary – shows processing of Easy Setup download
DistMgr.log
• On CAS or primary – shows creation of Easy Setup package
CMUpdate.log
• On CAS or primary – shows update installation process
ConfigMgrPrereq.log
• On CAS or primary – shows prerequisite check phase
ConfigMgrSetup.log
• On CAS or primary – shows prerequisite message processing
Resources
Microsoft Blog
https://blogs.technet.microsoft.com/configurationmgr/2016/05/04/walk
ing-through-an-upgrade-from-microsoft-configmgr-1511-toconfigmgr-1602/
MMS Sessions:
• ConfigMgr Servicing and Telemetry
• SCCM – Disaster Recovery
Demo
Update 1511 to 1602
House of Tails
Safety, food, water, health,
blankets, shade, love, fun
70 dogs!!!
$15 = 1 month food
Donation box near registration area and
participate in the raffle for huge rewards!
www.houseoftails.org/support-us
www.facebook.com/sthouseoftails
[email protected]
Dutch bank IBAN: NL87INGB0006669920
And Then …