Explore Our MECM / SCCM Training →
Resolving SCCM OSD Task Sequence Application Install Failures
Why applications randomly fail post-MECM client install
During the deployment of Windows via OSD task sequences, applications can sometimes fail to install correctly. This is often due to timing issues and conflicts between the MECM client installation and the application installation.
Recommended delay and restart practices
To address these issues, it’s recommended to add a Restart Computer step immediately after Setup Windows and Configuration Manager step, followed by a Wait step (minimum 120 seconds) before Install Application steps. Grouping applications into smaller batches with intermediate restart steps can also improve stability.
Using SMSTS.log for failure analysis
When encountering application installation failures, review the SMSTS.log located at X:\Windows\Temp\SMSTSLog\SMSTS.log (press F8 if command prompt is enabled). This log file contains valuable information about the task sequence execution and can help identify issues.
Application detection method best practices
Instead of using MSI product code for application detection, it’s recommended to use file-based or registry-based detection methods for better reliability. This approach reduces the likelihood of false positives and negatives during the task sequence execution.
Dependencies and supersedence in OSD context
When deploying a large number of applications (30+), consider deploying critical apps via task sequence and remaining apps post-OSD via standard required deployments. This strategy can help ensure that essential applications are installed first and reduce the potential for conflicts.
Explore Our MECM / SCCM Training →
Written by Mohammed Akhter
Founder of ITP Training. 50,000+ students trained across 30+ countries in Microsoft endpoint and cloud security. Learn more →