New features included in SCCM 1802

• Reassign distribution point
• Configure Windows Delivery Optimization to use Configuration Manager boundary groups
• Support for Windows 10 ARM64 devices
• Improved support for CNG certificates
• Boundary group fallback for management points
• Cloud distribution point site affinity
• Management insights
• Cloud management gateway support for Azure Resource Manager
• Surface device dashboard
• Microsoft Edge browser policies
• Allow user interaction when installing an application
• Do not automatically upgrade superseded applications
• Improvements to Windows 10 in-place upgrade task sequence
• Install multiple applications in Software Center
• Phased deployments for task sequences
• Hide installed applications in Software Center

Checklist for SCCM 1802:

• Ensure that all sites run a version of System Center Configuration Manager that supports update to 1802
• Review the status of your Software Assurance or equivalent subscription rights
• Review installed Microsoft .NET versions on site system servers
• Review the version of the Windows Assessment and Deployment Kit (ADK) for Windows 10 : The Windows 10 ADK should be version 1703 or later. (For more information on supported Windows ADK versions, see Windows 10 ADK.) If you must update the Windows ADK, do so before you begin the update of Configuration Manager. This ensures the default boot images are automatically updated to the latest version of Windows PE. (Custom boot images must be updated manually.)
• Review the site and hierarchy status and verify that there are no unresolved issues
• Review file and data replication between sites
• Install all applicable critical updates for operating systems on computers that host the site, the site database server, and remote site system roles
• Disable database replicas for management points at primary sites
• Set SQL Server AlwaysOn availability groups to manual failover
• Reconfigure software update points that use NLBs
• Disable all site maintenance tasks at each site for the duration of the update installation on that site
• Temporarily stop any antivirus software on the System Center Configuration Manager servers
• Create a backup of the site database at the central administration site and primary sites

Ensure that all sites run a version of System Center Configuration Manager that supports update to 1802:
Each site server in the hierarchy must run the same version of System Center Configuration Manager before you can start the installation of update 1802. To update to 1802, you must use version 1702, 1706, or 1710.

Review installed Microsoft .NET versions on site system servers: When a site installs this update, Configuration Manager automatically installs .NET Framework 4.5.2 on each computer that hosts one of the following site system roles when .NET Framework 4.5 or later is not already installed:

  • Enrollment proxy point
  • Enrollment point
  • Management point
  • Service connection point

This installation can put the site system server into a reboot pending state and report errors to the Configuration Manager component status viewer. Additionally, .NET applications on the server might experience random failures until the server is restarted.

Review the version of the Windows Assessment and Deployment Kit (ADK) for Windows 10 The Windows 10 ADK should be version 1703 or later. (For more information on supported Windows ADK versions, see Windows 10 ADK.) If you must update the Windows ADK, do so before you begin the update of Configuration Manager. This ensures the default boot images are automatically updated to the latest version of Windows PE. (Custom boot images must be updated manually.)

Review the site and hierarchy status and verify that there are no unresolved issues: Before you update a site, resolve all operational issues for the site server, the site database server, and site system roles that are installed on remote computers. A site update can fail due to existing operational problems.

Install all applicable critical updates for operating systems on computers that host the site, the site database server, and remote site system roles:Before you install an update for Configuration Manager, install any critical updates for each applicable site system. If an update that you install requires a restart, restart the applicable computers before you start the upgrade.

Disable database replicas for management points at primary sites:
Configuration Manager cannot successfully update a primary site that has a database replica for management points enabled. Disable database replication before you install an update for Configuration Manager.

For more information, see Database replicas for management points for System Center Configuration Manager.

Disable all site maintenance tasks at each site for the duration of the update installation on that site:
Before you install the update, disable any site maintenance task that might run during the time the update process is active. This includes but is not limited to the following:

  • Backup Site Server
  • Delete Aged Client Operations
  • Delete Aged Discovery Data

When a site database maintenance task runs during the update installation, the update installation can fail. Before you disable a task, record the schedule of the task so you can restore its configuration after the update has been installed.

For more information, see Maintenance tasks for System Center Configuration Manager and Reference for maintenance tasks for System Center Configuration Manager.

Temporarily stop any antivirus software on the System Center Configuration Manager servers: Before you update a site, ensure that you have stopped antivirus software on the Configuration Manager servers.

Create a backup of the site database at the central administration site and primary sites: Before you update a site, back up the site database to ensure that you have a successful backup to use for disaster recovery.

For more information, see Backup and recovery for System Center Configuration Manager.

Run the setup prerequisite checker:
When the update is listed in the console as Available, you can independently run the prerequisite checker before installing the update. (When you install the update on the site, prerequisite checker runs again.)

To run a prerequisite check from the console, go to the Administration workspace, and select Updates and Servicing. Select the Configuration Manager 1802 update package, and click Run prerequisite check in the ribbon.

For more information about starting and then monitoring the prerequisite check, see Step 3: Run the prerequisite checker before installing an update in the topic Install in-console updates for System Center Configuration Manager.

Important

When the prerequisite checker runs independently or as part of an update installation, the process updates some product source files that are used for site maintenance tasks. Therefore, after running the prerequisite checker but before installing the update, if you need to perform a site maintenance task, run Setupwpf.exe (Configuration Manager Setup) from the CD.Latest folder on the site server.

Update sites:
You are now ready to start the update installation for your hierarchy. For more information about installing the update, see Install in-console updates.

We recommend that you plan to install the update outside of normal business hours for each site when the process of installing the update and its actions to reinstall site components and site system roles will have the least effect on your business operations.

For more information, see Updates for System Center Configuration Manager.

Post update Checklist

Review the following actions to take after the update installation is finished.

  1. Make sure that site-to-site replication is active. In the console, view Monitoring > Site Hierarchy, and Monitoring > Database Replication for indications of problems or confirmation that replication links are active.
  2. Make sure each site server and site system role has updated to version 1802. In the console, you can add the optional column Version to the display of some nodes including Sites and Distribution Points.

When necessary, a site system role will reinstall automatically to update to the new version. Consider restarting remote site systems that do not update successfully.

  1. Reconfigure database replicas for management points at primary sites that you disabled before starting the update.
  2. Reconfigure database maintenance tasks that you disabled before starting the update.
  3. If you configured client piloting before installing the update, upgrade clients per the plan you created.
  4. If you use any extensions to Configuration Manager, update them to the latest version to support this Configuration Manager update.

https://www.systemcenterdudes.com/step-by-step-sccm-1802-upgrade-guide

Installation Process
Open SCCM Console, click on Administration Tab, go to Overview > Updates and Servicing. On right Pane you will see “Configuration Manager 1802”

Right click it and download the update. Update will be download as cab file under following location (F:\Program Files\Microsoft Configuration Manager\EasySetupPayload)



This can be verified using log file dmpdownloader.log

Once downloaded it will extract the content with same name folder as cab file.

Run Prerequisite Check

Once update is downloaded, right click “configuration Manager 1802” on console and select “Run Prerequisite Check”. Verify CMUpdate.log for process initiation and verify c:\ConfigMgrPrereq.log for success or failure.

Next Step
Right click “Configuration manager 1802” and click on install.

Select next, select the options you want to select or leave it as default. You can enable this at latest stage as well.

Next screen shows Client Update options, its always better to use option “Validate in pre-production collection” so that you can test new client agent on few systems before rolling out in production.

Select next and specify your Software Assurance expiration date.

Click next to complete.

You can monitor the installation through CMUpdate.log. And can see the results showing as success.

Verify the same in SCCM console as well:

Once installation is done, and you try to open the SCCM console, this will ask you to update your console.

Once completed you can verify the site version and control version (by clicking on top left of the SCCM ribbon and selection option “About Configuration Manager”.

Advertisements