non OSD task sequence will not run - stuck on "installing" (v.2211)

Hi NoahScott,

possible solution to your issue / problem of a task sequence getting stuck on "installing" is to follow these steps:

1. Check the SMSTS.log file. The SMSTS.log file contains detailed information about the execution of the task sequence. Review the log file for any error messages or warnings that may indicate the root cause of the issue.
2. Verify that all of the content required for the task sequence is available on the distribution points. You can use the Content Status node in the Configuration Manager console to check the status of the task sequence content.
3. Check the boundary assignments for the client machines. Make sure that the client machines are assigned to the appropriate boundary groups so that they can access the necessary content.
4. Review the task sequence for any application or package dependencies. Make sure that all of the required applications and packages are available and configured correctly.
5. Check the distribution points for any errors or warnings. You can use the Distribution Point Status node in the Configuration Manager console to check the status of the distribution points.
6. Verify that the task sequence is running with the necessary permissions. You can use the Security tab of the task sequence to check the permissions.
7. Test the custom scripts and content that are being used in the task sequence. Make sure that the scripts and content are functioning as expected.
8. Remove or disable individual steps from the task sequence and test it in phases. This can help you to identify the specific step that is causing the issue.
9. Enable more detailed logging in the task sequence. This can provide additional information about the issue.
10. Check the health of the Configuration Manager clients on the target machines. You can use the built-in Configuration Manager Client Health script to check and repair client issues.
11. Update Configuration Manager to the latest version. This may include bug fixes and improvements that can resolve task sequence issues.
12. Check for any network issues on the affected machines. Network problems can cause content download problems, which can lead to task sequence failures.