Forums on Intune, SCCM, and Windows 11

Welcome to the forums. Register a free account today to become a member! Once signed in, you'll be able to participate on this site by adding your topics and posts, as well as connect with other members through your own private inbox!

PENDING Task sequence Stuck and restarts after fails to load

  • Thread starter Thread starter UMAR
  • Start date Start date
  • Replies Replies 13
  • Views Views 2K
If you have debugging enabled. Try pressing F8 on your Task Sequence window where you put your TS password (you will get a command prompt windows) and try to see if you are able to ping to your SCCM server using Fully Qualified DN provided that it is the management point. It can be a DNS problem too, if you are able to ping. Do an nslookup in the command prompt for the server FQDN and see if it brings any results.
 
If you have debugging enabled. Try pressing F8 on your Task Sequence window where you put your TS password (you will get a command prompt windows) and try to see if you are able to ping to your SCCM server using Fully Qualified DN provided that it is the management point. It can be a DNS problem too, if you are able to ping. Do an nslookup in the command prompt for the server FQDN and see if it brings any results.
Thanks for reply. i tried pinging IP of SCCM (MP) it works but not the FQDN, also no result at nslookup.
 
Thanks i find out that was the DNS issue i rebuild the DHCP and was made some mistake in DNS there, Thanks for your help joe_e
 
Just check you C: by using the command prompt and see if you have enough space for the Image to be applied to the drive. If the image size to be applied is 4 GB, then there should be enough space to accommodate that plus some free space. Is it applying the Image to the recovery partition? Is your drive physical or virtual?
 
Just check you C: by using the command prompt and see if you have enough space for the Image to be applied to the drive. If the image size to be applied is 4 GB, then there should be enough space to accommodate that plus some free space. Is it applying the Image to the recovery partition? Is your drive physical or virtual?
The last one is just for information (physical or virtual).
 
The last one is just for information (physical or virtual).
Its virtual machine, its fresh machine i am testing. The hard disk i did diskpart as well. The issue is when it deployed Tasksequence hard to get C: drive. It creates D: and then move back to C: in early stage.
 
You might need to check the account used for network access, to access the image or the distribution point. Do you have any account specified under Software Distribution Component Properties?
 
You should also be able to see the errors in the log where it would show those errors in red while scrolling through the SMSTS.log
 
Back
Top