diff --git a/intune/configmgr/sum/deploy-use/create-orchestration-groups.md b/intune/configmgr/sum/deploy-use/create-orchestration-groups.md
index 2fcf9ae632..24928fa135 100644
--- a/intune/configmgr/sum/deploy-use/create-orchestration-groups.md
+++ b/intune/configmgr/sum/deploy-use/create-orchestration-groups.md
@@ -142,9 +142,8 @@ To delete the orchestration group, select it then select **Delete** in the ribbo
 
 > [!WARNING]
 > - Starting in version 2111, pre and post-scripts [require approval](#approvals-for-orchestration-group-scripts) to take effect. Editing a script after it's approved will reset the approval state to **Waiting for approval**. Scripts that don't have approval will not run on clients.
-> - In version 2103 and later, scripts that have parameters aren't supported<!--9893550--> and the maximum script length is 50,000 bytes which is 25,000 characters (as we use Unicode encoding) <!-- MEMDocs#1575 -->.
-> - For Configuration Manager 2010 and earlier, add scripts to your orchestration groups on the **Pre-Script** and **Post-Script** tabs. 
->   - Ensure pre-scripts and post-scripts are tested before using them for orchestration groups. The pre-scripts and post-scripts don't timeout and will run until the orchestration group member timeout has been reached. Scripts that have parameters aren't supported<!--9893550--> and the maximum script length is 5,000 characters<!-- MEMDocs#1575 -->.
+> - In version 2103 and later, scripts that have parameters aren't supported<!--9893550--> and the maximum script length is 16,383 characters<!-- MEMDocs#1575 -->.
+>   - Ensure pre-scripts and post-scripts are tested before using them for orchestration groups. The pre-scripts and post-scripts don't timeout and will run until the orchestration group member timeout has been reached.
 
 ## Display orchestration groups and members