Also, what happens if you advertise a new TS? Mike D- From: [email protected] To: [email protected] Subject: [mssms] RE: CM12 - No Task Sequences Available?? Date: Wed, 14 Jan 2015 15:29:53 +0000
Just to check, you don’t have any scripts running in a Prehook that depends on some external service do you? From: [email protected] [mailto:[email protected]] On Behalf Of Marable, Mike Sent: Wednesday, January 14, 2015 10:23 AM To: '[email protected]' Subject: [mssms] RE: CM12 - No Task Sequences Available?? We are getting this on a number of physical hardware types (desktops, laptops, Dells and HPs….) as well as VMs. The PXE booted machines (how the build is normally initiated) will spontaneously reboot on their own before ever reaching the “Welcome” screen. The boot media machines will at least get to the “Welcome” screen, but regardless of how long it sits there the result is the same. No TS available. From: [email protected] [mailto:[email protected]] On Behalf Of Krueger, Jeff Sent: Wednesday, January 14, 2015 10:16 AM To: [email protected] Subject: [mssms] RE: CM12 - No Task Sequences Available?? “Just because you can PXE boot does not mean there are Task Sequences advertised. It just means you have your boot images setup.” - Acutally, when pxe booting it will check to see if there is a TS deployment available to that machine, if there is no deployment it will abort the pxe process and not go on to download the WinPe image. Mike, I assume you’ve checked to see if this happens on different hardware types? We have seen in the past after booting to WinPe on some machines they took just a bit longer to fully initialize the network driver, so if you clicked as soon as the gui was available to get the list of TS’s it would fail. From: [email protected] [mailto:[email protected]] On Behalf Of Mawdsley R. Sent: Wednesday, January 14, 2015 10:02 AM To: [email protected] Subject: [mssms] RE: CM12 - No Task Sequences Available?? Just because you can PXE boot does not mean there are Task Sequences advertised. It just means you have your boot images setup. Open Config Manager, navigate to Software Library>Operating Systems>Task Sequences. In here should be your Task Sequences. Click on one and check its deployments via the Deployments tab at the bottom. This is who it is currently advertised to. If need be, you could deploy it (advertise) to another Device Collection.. when doing this, DO NOT set it as Required unless you want to wipe everything. Rich From: [email protected] [mailto:[email protected]] On Behalf Of Marable, Mike Sent: 14 January 2015 14:53 To: SMS Subject: [mssms] CM12 - No Task Sequences Available?? 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 CONFIDENTIALITY NOTICE: This email contains information from the sender that may be CONFIDENTIAL, LEGALLY PRIVILEGED, PROPRIETARY or otherwise protected from disclosure. This email is intended for use only by the person or entity to whom it is addressed. If you are not the intended recipient, any use, disclosure, copying, distribution, printing, or any action taken in reliance on the contents of this email, is strictly prohibited. If you received this email in error, please contact the sending party by reply email, delete the email from your computer system and shred any paper copies. Note to Patients: There are a number of risks you should consider before using e-mail to communicate with us. See our Privacy & Security page on www.henryford.com for more detailed information as well as information concerning MyChart, our new patient portal. If you do not believe that our policy gives you the privacy and security protection you need, do not send e-mail or Internet communications to us. ********************************************************** Electronic Mail is not secure, may not be read every day, and should not be used for urgent or sensitive issues
