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 SCCM Task Sequence not showing Up

ASharpe

New Member
Messages
3
Reaction score
0
Points
1
I am having a strange issue. For some reason, it seems like the Task Sequences are not syncing to the WinPE environment. I currently have two TS. When I try to deploy an additional Task Sequence, it does not show up. When I try to delete one of the deployments that is currently there, it does not get removed. I have waited over 24 hours and nothing has changed. I have tried this on VMs and workstations and nothing changed. I have looked at the distmgr. Is there some other log I need to look at to troubleshoot this or do you have any clue why this would occur? I am running the latest SCCM 1702 with hotfix.
 
"When I try to delete one of the deployments that is currently there, it does not get removed. " - Do you see any errors here ?. Deleting the TS from deployment is very simple. What user account are you using and what permissions does it have ?.
 
Thanks for the response. When I say "When I try to delete one of the deployments that is currently there, it does not get removed.", I mean from the WinPE environment, not from within SCCM itself. I am able to delete those deployments (e.g Unknown Computers). But for some reason, that portion of it works now (strange). Now my issue is just that I cannot get any new Task Sequence to show in WinPE. I have tried EVERYTHING to get new task sequences to show up. The only ones that show up are the two I did a while back.
 
Okay so ended up removing all the deployments and now I am having some different issues. I am now getting in the SMSTS.log a messaging stating
RegOpenKeyExW failed for Software\Microsoft\SMS\Task Sequence GetTsRegValue() failed. 0x80070002 and as a result the computers reboots immediately after Preparing Network Connections. It cant be a network driver if it was working before. It seems like there is not a fix for this as I have been searching forums. Any ideas?
 
Back
Top