Hi Mike, Just curious - Has anything changed with the deployment? Are you deploying to unknown machines or All Systems (to only PXE and Media)? Is this behavior happening for unknown machines as well as known machines? Maintenance Windows? Mike-
From: [email protected] To: [email protected] Subject: [mssms] CM12 - No Task Sequences Available?? Date: Wed, 14 Jan 2015 14:53:14 +0000 For the third week in a row something has knocked out OS deployment offline. We can PXE boot a machine but during the boot it will suddenly reboot out of WinPE and back into the full OS. We can pop a command window to prevent the reboot and the SMSTS log has this right before it bailed out and attempted to reboot: “There are no task sequences available to this computer.. Please ensure that you have at least one task sequence advertised to this computer. Unspecified error (Error: 80004005; source: Windows)” If there were no sequences advertised then SCCM wouldn’t allow it to PXE boot in the first place. I boot a machine using SCCM boot media and when I hit Next on the welcome screen I get the message that there are not sequences available. SMSTS log : “No assigned task sequences” There are no other errors in the SMSTS logs on the clients. The site status within SCCM shows all green as well. Now this has happened three weeks straight now. It first happened New Year’s Eve, then Thursday of last week and now again this morning. It starts around 9:00 am and magically corrects itself within 2-3 hours. We’ve checked out networking, DNS, WINS, the SCCM guys say that there are no external process running (like backups, virus scans, etc.) on the infrastructure at this time. It’s maddening since it magically starts and magically corrects itself and we cannot figure out what is causing it. Within WinPE we can ping the Management Points, in fact we can ping all of the SCCM servers. Machines that are already in the process of building continue to do so and do not fail. Also, any non-OSD deployment will still work during this time. We can pull deployments, even non-OSD task sequences will run. So whatever is causing the problem is only affecting machines attempting to start an OS deployment. Anyone else ever see anything like this? Mike Marable Application Programmer/Analyst Lead Enterprise Device Engineering and Management MCTS, MCITP, MCSA, MS [Profile] [Blog] -------------------------------------------- "The difficult we do at once. The impossible takes a little longer." -US Army Corps of Engineers "It is better to have less thunder in the mouth and more lightning in the hand." -Apache Proverb I will rise when I have fallen. "Unless you try to do something beyond what you have already mastered, you will never grow." -Ralph Waldo Emerson ********************************************************** Electronic Mail is not secure, may not be read every day, and should not be used for urgent or sensitive issues
