September 2016 Meeting Notes
Next month we'll hold elections. If you are interested in helping or running for P or VP email us at
Brian – SQL 2016 Update – prep – tips tricks
• SQL 2016 – support for CM CB (1606)
• System Center will support SQL 2016 once released end of September
• SQL 2016 is faster
• Before you upgrade – Check you licensing with Microsoft
• Can upgrade from SQL 2008
• Install
• Always use install file.
• Allows for Slip-streaming
• Uninstall
• Need the media for the old version
• Use a INI file
• Need to SQL Management Studio (SSMS) separately
• Remember to flip your databases to SQL 2016 Compatibility mode
• You may have seen blogs that say to keep CM Database in 2012 mode. This is no longer the case
• You can set compat mode to SQL 2016 for SCCM, SSRS, and WSUS DB
• Installing SCCM from base – you need to start with SQL 2014 until there are new bits for SCCM installer
• AZSMUG user group - Brian is speaking (and Kent and Niehaus and Daalmans and Ramsey) - "A Taste of MMS"
Wally – Keeping CM Current
• Awesome shout out!! Wally said MNSCUG is the best user group in the country!
• Do you have a lab environment that runs CM Technical Preview?
• CB = Current Branch. As of this writing it is 1606
• SCCM has gone from 1511, 1602, 1606
• When you open the console you will see the upgrades in the Administration node
• Console upgrades appear when you open the console (requires local admin to update)
• Remember your CD.Latest folder. Absolutely back this up. Most of you should be using SQL for backups and thus this would not be included. If you have a CAS, all your primary sites already have remote copies.
• You can upgrade from CM16XX to any version. They are all cumulative
• You have the ability to enable the new features during the upgrade. Perhaps you should just upgrade first and enable the features later.
• You can upgrade a “beta collection” to the new client version during the upgrade. That way the rest of your SCCM clients stay on the old version until you have validated
• You will need your own Pre-Production (pilot) validation collection to target if you use this feature
• Two different ways to upgrade
• ONLINE MODE
• Service Connection Point – checks daily for new updates
• Some updates are Cumulative Updates some are Update Rollups
• Cumulative Updates may not include Update Rollups depending on the timing of the release
• OFFLINE MODE
• Must upload telemetry data
• Import into the site for installation
• Need to use the Service Connection Tool
• Command Line
• Bundle up your telemetry data to create CAB file
• Run the tool to talk to Microsoft in order to figure out what updates are needed
• Move updates to the Offline CM environment
• Upgrades go to the EasysetupPayload directory
• Currently those upgrades go into different directories – thus SPACE issues!
• CM1610 is supposed to take care of that
• Note: You can use CMTrace.exe or Notepad.exe to view log files – depends on the kind of person you are
• Once you upgrade CM, and open the console, you will be prompted to upgrade the console
• You may want to wait. Not all components in CM have been initialized yet. Check services for CCMExec running before you update the console
• The next CM build will be a BASELINE build. Meaning, you can install straight from that build. Coming late Sept 2016
Q/A
• How to change the log size for clients
• Use a CI to change registry
• HKLM\Software\Microsoft\CCM\Logging
• Most of the time the log files are large because of OSD
• There is a free community tool for OSD logging
• Other User groups: https://www.mnscug.org/misc/web-links/other-user-groups
• How to upgrade Windows 10 to 1607: Use Task Sequences instead of the ‘circle node’
- Created on .