cwb124 Posted December 5, 2013 Report post Posted December 5, 2013 I didn't have the deployment set to Make Available to Configuration Manager Clients, media, and PXE. I only had Media and PXE. I removed the deployment and re-deployed with that set properly. Half an hour later, my tests are failing with the same exact error that there are no available task sequences. I really thought that was it. Guess not. Quote Share this post Link to post Share on other sites More sharing options...
Edenost Posted December 6, 2013 Report post Posted December 6, 2013 I had this problem during my first time using SCCM. It turned out to be network card drivers missing from WinPE. For OP, it could be that (assuming it worked before from what you say), the driver for that NIC has become corrupt? For cwb124, check the NIC in the PC's you want to image and make sure the drivers for them are added to SCCM and are added to the boot images. Phil Quote Share this post Link to post Share on other sites More sharing options...
cwb124 Posted December 6, 2013 Report post Posted December 6, 2013 The drivers are added to WinPE for sure. This server built initially the first time it was manually added to SCCM as a computer object in a collection with a required advertisement. It's the rerunning of the task sequence that I can't get to work on at least this one host, and perhaps a couple others. Quote Share this post Link to post Share on other sites More sharing options...
teamfox201 Posted December 6, 2013 Report post Posted December 6, 2013 This is making me mad lol. So this system imaged successfully the first time? Now it doesn't work. If you pull the record in the console , does it show approved and active? Maybe try a delete anyways ? Can you attach the smsts.log file here ? I had an issue earlier in the week where my task sequence was corrupt and I had to recreate it ( copy the current one). Quote Share this post Link to post Share on other sites More sharing options...
cwb124 Posted December 6, 2013 Report post Posted December 6, 2013 Making you mad??? I've been at this most of the week lol The client in the console is Client Type: NONE. Client: NO. Site Code WC1 (correct site code) You can't really delete from SCCM 2012 anymore. Not the way you could in SCCM 2007, which is one of my gripes. I think it's an issue with just this one object though. I think it's corrupt or somehow effed up. I just don't know how to fix it. Quote Share this post Link to post Share on other sites More sharing options...
Yan Posted December 6, 2013 Report post Posted December 6, 2013 I had the same issues when I had undistributed packages in a task sequence. To troubleshoot I would change my advertisement from Required to Available then the error is displayed on the screen instead of just rebooting. Quote Share this post Link to post Share on other sites More sharing options...
cwb124 Posted December 6, 2013 Report post Posted December 6, 2013 But this is only happening on hosts that have gotten the task sequence but the task sequence failed for whatever reason. I am still working out my task sequences since we just migrated to 2012. Quote Share this post Link to post Share on other sites More sharing options...
kishore.au Posted December 23, 2013 Report post Posted December 23, 2013 May be you can go to all systems collection and locate the computer name where the deployment is failed . Delete that machine and try deploying again ? Quote Share this post Link to post Share on other sites More sharing options...
commissar117 Posted December 18, 2014 Report post Posted December 18, 2014 Try this right click on the machine in the collection and click approve. Than give it a try. 1 Quote Share this post Link to post Share on other sites More sharing options...
Adam Bise Posted August 27, 2015 Report post Posted August 27, 2015 I had this issue when I deployed a TS referencing variables to a collection that was missing the variable. Quote Share this post Link to post Share on other sites More sharing options...
