Step by Step SCCM 1702 Upgrade

This post describe about SCCM 1702 upgrade. First step to take backup and do the TESTDBUPGRADE , may follow my Prior Post how to do it.

Go to Administration

 

 

Straight forward Click on Configuration Manage 1702 and run the Prerequisite Check , Once its successful then Click on Install Update Pack on same.

Choose the Pre-Release Features as needed

Validate the Client Package, In my Lab , going without validation bit Careless 🙂

 

 

 

 

 

This is One of Feature from 1702 Version, to send the Feedback to the developers.

Another change in 1702 Version, Updates and Servicing node move out from Cloud Service folder.

 

Successfully completed SCCM 1702 Upgrade from 1610 version.

Finally, Follow the post upgrade check list without fail – This is my prior post about the same..! 🙂

 

SCCM 1702 – Applicatoin Deployment Type – Install Behavior TAB not visiable

One of the Feature in SCCM 1702 that is “To check for running executable files before installing an application”

By default , this feature disabled (pre-release) – So we need enable as per below snapshot.

Administration–> Overview–>Updates and Servicing–>Features

In order there are many follow this Microsoft

SCCM 1702 Top Features

 

Microsoft Configuration Manager 1702 have new features and capabilities, In that listed few top features below. For complete list click here: 1702 Full features *****

1. Configuration Manager Current Branch 1702 version stop supporting below products.

  • Windows Server 2008
  • Windows Server 2008 R2
  • SQL Server 2008
  • Windows XP Embedded

Note: This above product versions remains supported when you use Configuration Manager prior 1702 versions.

2. Send Feedback to Configuration Manager Development team.

From SCCM Console, you can send feedback or new Ideas to product development team.

3. Updates and Servicing node location

The Updates and Servicing node moved out from Cloud Services node. It will appear under Administration node.

4. New Update States

When new updates releases henceforth there are two new states.

Ready for download: The update visible in console and ready for download.

Available for Install: The update downloaded and ready for install.

5. Improved cleanup of older updates

At Site Server EasySetuppayload folder automatic cleanup function from 1702 version to delete unused updates

6. Peer Cache improvements

From 1702 Versions, A peer cache source computer rejects content when computer meet any one of below condition.

  • Is in low battery mode.
  • CPU load exceeds 80% at the time the content is requested.
  • Disk I/O has an AvgDiskQueueLength that exceeds 10.
  • There are no more available connections to the computer.

7. Software update points are added to boundary groups

From 1702 version, Client can choose the SUP Server (Software Update Point) based on Boundary groups. And Find new SUP If their current SUP Server unavailable for any reason.

8. Check for running executable files before installing an application

Before going to deploy and install any new application, we can specify now one or more executable files to stop, then to process the installation.

If Application Deployed as Available, then when end user tried to install, will prompt to close the executable files which you specified in Deployment Type.

If Application deployed as Required, then end user get automatically prompt to close running executable files which you specified in Deployment Type.

For example: Adobe flash player want to deploy and install , The Office exe file should not run then only the Flash play start installing.

9. New Hardware Inventory Class.

Now we have new Hardware Inventory class called as SMS_Firmware. With property (UEFI) are available to help you determine whether a computer starts in UEFI mode. When a computer is started in UEFI mode, the UEFI property is set to TRUE. This is enabled in hardware inventory by default. For more information about hardware inventory, see How to configure hardware inventory.

10. Software Center Notifications for TASK SEQUENCES.

There is a new TAB in TASK SEQUENCES to create custom notifications to end users. Default and custom messages.

 

SCCM 1702 Not Visable in Console

SCCM Current Branch 1702 Update not appearing in Console

After Couple of times click on “Check for Updates”  from \Administration\Overview\Cloud Services\Updates and Servicing , The 1702 update not appearing .

So quick fix, The Microsoft posted powershell code to quick turn to visible in console and started downloading.

Follow the link and run the powershell script , it will  appear immediately  in your console with in seconds of time . For me its just 15 seconds to display in console…!

Get-Code

 

Thanks to Microsoft The Configuration Manager Team

 

SCCM 1702 Upgrade Microsoft Checklist

Folks,

I would just love to share that SCCM 1702 upgrade pre & post Check list , recommending by Microsoft…!

Pre Check List

  • Ensure that all sites run a version of System Center Configuration Manager that supports update to 1702
  • 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 Windows10
  • 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
  • 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
  • Create a backup of the site database at the central administration site and primary sites
  • Test the database upgrade on a copy of the most recent site database backup
  • Plan for client piloting
  • Plan to use service windows to control when site servers install updates
  • Run the setup prerequisite checker
  • Update sites

Pre Check List

  • 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.
  • Make sure each site server and site system role has updated to version 1702. 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.
  • Reconfigure database replicas for management points at primary sites that you disabled before starting the update.
  • Reconfigure database maintenance tasks that you disabled before starting the update.
  • If you configured client piloting before installing the update, upgrade clients per the plan you created

For more details on each check list, recommended to walk through the link Microsoft


 

 

 

 

 

When you install an update at the central administration site, be aware of the following limitations and delays that exist until all child primary sites also complete the update installation:  

  1. Client upgrades do not start. This includes automatic updates of clients and pre-production clients. Additionally, you cannot promote pre-production clients to production until the last site completes the update installation. After the last site completes the update installation, client upgrades will begin based on your configuration choices.

  2. New features you enable with the update are not available. This is to prevent the replication of data related to that feature from being sent to a site that has not yet installed support for that feature. After all primary sites install the update, the feature will be available for use.

  3. Replication links between the central administration site and child primary sites display as not upgraded. This displays in the update pack installation status as a status of Completed with warning for Monitoring replication initialization. In the Monitoring node of the console, this displays as Link is being configured

  4. 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.