SOLVED

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

Copper Contributor

Good morning, 

I've recently taken over for our previous systems administrator who left the company abruptly and I'm still in the process of learning configmgr while trying to run the show here.

We recently had an update to our HR system. I had deployed the new URL shortcut to all computers which went off without a hitch. However, now we've fully retired the old system and i'm trying to delete the old shortcut off of the desktops which is not working. 

I'm trying to use a 2 step task sequence to delete 2 files from the PC, the lnk file as well as the ICO file. 

- Troubleshooting 

I had tried the following on a few test machines.

cmd /c del "c:\users\public\desktop\myhr (mfa).lnk" /F /Q

cmd /c del "c:\users\public\desktop\myhr*.lnk" /F /Q

cmd /c del "c:\users\public\desktop\myhr*.*" /F /Q

while none of those worked, i setup a test and placed a file called test.txt under c:\temp

ran the following 

cmd /c del c:\temp\test.txt /f /q

cmd /c del /f /q c:\temp\test.txt

after that, I opened up command prompt as admin, was able to delete everything i needed using the above commands... tried it with non admin, deleted everything out just fine. 

I went back to the TS and added creds to the TS to test, still stuck on "installing" 

after that i decided to try powershell (set with bypass as the execution policy)

Remove-Item "C:\Users\Public\Desktop\MyHR (MFA).lnk"

Still stuck on installing. 

Wrote a batch file, stuck it into a package, called to the package with the script within a task sequence and was able to delete the file. So i currently have a work around with a batch file, but i'd like to get the task sequences back if possible so i can quickly write PS and CMD steps for stuff like this. 

- Checked the following

SMSTS.log

- never updates and i have a feeling this is because it doesn't actually start the TS 

other machines

- tried on some VM's as well as other desktops, had the same exact issue

unsure of what else to check as this is new to me. 

 

Thanks in advance!

 

Screenshot 2023-10-24 at 6.50.14 AM.pngScreenshot 2023-10-24 at 6.50.39 AM.pngScreenshot 2023-10-23 at 9.49.40 AM.pngScreenshot 2023-10-23 at 12.44.09 PM.png

 

2 Replies
best response confirmed by NoahScott (Copper Contributor)
Solution

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.


Please click Mark as Best Response & Like if my post helped you to solve your issue.
This will help others to find the correct solution easily. It also closes the item.


If the post was useful in other ways, please consider giving it Like.


Kindest regards,


Leon Pavesic
(LinkedIn)

thanks! after 2 days it ended up just... working... not sure what is happening there, however i greatly appreciate the infromation! i'm going to jot that down in my SCCM info.
1 best response

Accepted Solutions
best response confirmed by NoahScott (Copper Contributor)
Solution

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.


Please click Mark as Best Response & Like if my post helped you to solve your issue.
This will help others to find the correct solution easily. It also closes the item.


If the post was useful in other ways, please consider giving it Like.


Kindest regards,


Leon Pavesic
(LinkedIn)

View solution in original post