Most of the clients want the flawless, error-free Windows 10 Version Upgrade Process, with minimal reboots with lesser downtime to user machine but with all the Windows 10 client-specific customization which is a challenge.
As the SCCM Engineer, we have a choice to decide on which feature use to upgrade the Windows 10 i.e we have to decide on using Task Sequence or Windows 10 Servicing
To understand the Difference between Task Sequence and Windows 10 Servicing please refer to the table below.
| Title | Task Sequence | Servicing Feature Update |
|---|---|---|
| Engine Used | Task Sequence uses the Task Sequence engine. The Task Sequence method allows running additional tasks after an upgrade or installation of new applications. |
servicing features is using the ADR/Software Update engine |
| Drivers | Outdated device drivers can be handled within the task sequence. | Outdated device drivers cannot be handled in Servicing Feature update. |
| Packages | This feature can be added in the Task Sequence. | This feature cannot be added to the Servicing Feature Update. |
| Command Lines | Can be Run during an upgrade. | Cannot be Run during an upgrade. |
| Power Shell scripts | Can be Run during an upgrade. | Cannot be Run during an upgrade. |
| Domain Membership | This feature cannot be changed in the Task Sequence. | This feature cannot be changed in the Servicing Feature Update as well. |
| Disk Partitions | This feature cannot be changed in the Task Sequence. | This feature cannot be changed in the Servicing Feature Update as well. |
| Modifying Base OS Language | This feature cannot be changed in the Task Sequence. | This feature cannot be changed in the Servicing Feature Update as well. |
| Bandwidth | Task Sequence has better control over bandwidth. | In Servicing Feature Update there are not many options available to control the bandwidth. |
| Customization | Customization can be reconfigured in the Task Sequence. For example- Startmenu or Task Bar | Cannot reconfigure customizations in the Servicing Feature Update. |
| Universal Windows Platform Applications (Default applications) | Can be removed in the task sequence. | Cannot be handled during a feature update. |
| Flexibility | Flexibility modifies the task sequence at any point in time during deployment. | No Flexibility in Servicing Feature Update. |
| User visibility | User cannot work when there is an upgrade, since core application needs to be closed, i.e it is more controlled. | Users can work, but the core updates may fail if any core application like the office. Those applications need to be closed i.e we cannot control here. |
| Reporting | Good Reporting capability. | Reporting capability is lacking when compared to Task Sequences. |
| Documentation Limitation | Vast documentation is available | There a just a few pages in the docs for Windows 10 that cover options for managing Feature Updates via servicing.,The examples are very high level and Complicated. |
| Reboot | Reboots can be controlled in the Task Sequence. | Multiple reboots might require in the Feature update. |
| Application Compatibility | Non-compatible applications can be upgraded. | cannot upgrade non-compatible applications. |
| Bitlocker | Bitlocker Can be Managed or disabled before upgrade | Bitlocker cannot be managed. |
