SCCM Task Sequence Failure with Provisionts Argument and CMG http 500 in Datatransfer Log after 2403 Upgrade
Discuss the SCCM Task Sequence Failure with Provisionts Argument and CMG after 2403 Upgrade. After upgrading to SCCM version 2403, users encounter a significant issue where task sequences fail during the Install Application step.
This failure occurs when the PROVISIONTS command line argument is used with the Cloud Management Gateway (CMG). The failure results in an HTTP 500 error recorded in the DataTransfer log.
This problem has been reported since the upgrade, affecting the deployment process for many organizations. In this post, you will find all the details regarding the SCCM Task Sequence Failure related to the PROVISIONTS command line argument and its interaction with the Cloud Management Gateway (CMG) following the upgrade to version 2403.
This issue has significantly affected users, leading to failures during the Install Application step of task sequences. We will also explore the potential causes and available workarounds to help solve the impact of this problem on your deployments.
Table of Contents
What Issue is Occurring with SCCM Task Sequences after Upgrading to Version 2403?
After upgrading to SCCM version 2403, users are experiencing failures in the Install Application step of task sequences when using the PROVISIONTS command line argument.
SCCM Task Sequence Failure with Provisionts Argument and CMG After 2403 Upgrade
The task sequence failure with the PROVISIONTS argument in SCCM 2403 has caused significant challenges for users. The issues related to SCCM Task Sequence Failure with Provisionts Argument and CMG After 2403 Upgrade are explained below.
- FIX KB5020276 Domain Join Hardening Changes using SCCM Task Sequence | 0xaac (2732) Error
- Best Guide to Deploy Windows 11 22H2 using SCCM Task Sequence | ConfigMgr
Current Status of SCCM Task Sequence Failure Issue
A support ticket is open with Microsoft, and the team at MSIntune has confirmed that they can reproduce the issue in their labs. They have acknowledged that the bug causing the failure is present in version 2403.
Temporary Solutions for the Issue
While a fix is being developed, some users have had to change their applications to legacy packages as a temporary workaround. This method allows them to keep their systems running until a permanent solution is available.
- SCCM Versions Build Numbers Client Console Site
- List of Issues Fixed with SCCM 2403 KB26186448
- End of Support Dates for SCCM CB Current Branch | ConfigMgr | SCCM End of Life
Resolution Timeline
The Microsoft team has recognized the issue and confirmed that a fix will be included in the upcoming Current Branch (CB) 2409 release. Users should watch for updates and prepare for the patch, which will restore regular operation to their task sequences.
| Issue Details | Description |
|---|---|
| Issue Acknowledgment | Microsoft has confirmed the bug in version 2403 |
| Issue Fix Confirmation | A fix will be included in the upcoming CB 2409 |
| User Guidance | Users are advised to monitor updates closely |
Join the LinkedIn Page and Telegram group to get the latest step-by-step guides and news updates. Join our Meetup Page to participate in User group meetings. Also, Join the WhatsApp Community to get the latest news on Microsoft Technologies. We are there on Reddit as well.
Author
Anoop C Nair has been Microsoft MVP from 2015 onwards for 10 consecutive years! He is a Workplace Solution Architect with more than 22+ years of experience in Workplace technologies. He is also a Blogger, Speaker, and Local User Group Community leader. His primary focus is on Device Management technologies like SCCM and Intune. He writes about technologies like Intune, SCCM, Windows, Cloud PC, Windows, Entra, Microsoft Security, Career, etc.
Discussion