Jump to content


abouelse

There are no task sequences available to this computer

Recommended Posts

We have and SCCM 2012 SP1 server. We've been deploying task sequences okay for a few months now. However, just this week when I attempt to deploy task sequences to do OS deployments I am having a problem.

 

The PC will PXE boot, finish configuring network and restart. When I look in the SMSTS.log file I see the error: There are no task sequences available to this computer. I've tried a number of different task sequences on a number of different computers. I've checked the cert, deleted and re-added the computers, deleted and recreated collections, I've rebooted my SCCM server, none of this resolved the issue.

 

I'm not sure what the problem is. I've attached my SMSTS log. I'd appriciate any help.

smsts.log

Share this post


Link to post
Share on other sites

It is in a collection, I believe the task sequence is advertised to it, but to be 100% honest, I do not know how to check if a task sequence is advertised, or how to advertise one.

Share this post


Link to post
Share on other sites

You should be able to right click on the collection and check the Deployments tab. You can also just delete that computer name from System Center to make it unknown again.

Share this post


Link to post
Share on other sites

The task sequence is listed in the deployments tab of the Device Collection as "required". So, I believe it is advertised. Also, I have delete and recreated both the computer and the device collection. This is happening on all of my computers currently.

Share this post


Link to post
Share on other sites

I also just did a system query to look for dupliacte GUIDs. as that was suggested someplace, but that did not pan out. The PC in question here (imc124-pc-17) does not have a GUID that conflicts with any other devices.

Share this post


Link to post
Share on other sites

Did you ever resolve this problem? I am running into the same issue. We have 6 build collections, each with a different task sequence deployed to them. They are set to required and Always Rerun Program. The problem I am having is a new bare metal box will build once. If it fails at some point beyond laying down the OS and it boots to the OS and checks into SCCM, I can never get it to run that task sequence again. If I clear PXE advertisement it says there are none to clear. I verify that the task sequence is deployed to that collection and that the computer object is still in that collection. In the properties of the computer object, on the deployments tab, it shows that the task sequence is available to it.

 

However when I PXE boot it goes into WinPE and establishes network connectivity and then reboots immediately. If I hit F8 and check out the smsts.log, I see the following: There are no task sequences available to this computer.

 

In SCCM 2007, I could delete the object from SCCM and then re-create it. No problem. However in SCCM 2012, it handles "deletion" completely differently. Here's an article: http://myitforum.com/myitforumwp/2012/08/08/sccm-2012-when-you-delete-a-system-from-the-console-its-removed-from-v_r_system-but-still-exists-in-table-system_disc/

 

So I can't figure out how to redeploy a task sequence to an existing SCCM object or one that failed at some point but still checked into SCCM.

Share this post


Link to post
Share on other sites

Do you have "Disable this task sequence on computers where it is deployed" checked?

 

Does the Task Sequence deployment have "Make available to the following: Configuration Manager clients, media and PXE" selected?

Share this post


Link to post
Share on other sites

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.

Share this post


Link to post
Share on other sites

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

Share this post


Link to post
Share on other sites

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.

Share this post


Link to post
Share on other sites

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).

Share this post


Link to post
Share on other sites

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.

Share this post


Link to post
Share on other sites

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.

Share this post


Link to post
Share on other sites

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.

Share this post


Link to post
Share on other sites

I had the same thing yesterday. I looked at the smsts.log and saw the same error. It turned out that while I was using the MDT SCCM nitrated task sequence I forgot to distribute the Microsoft Corporation User State Migration Tool for Windows 8 package to the distribution point. So make sure all of your packages related to that OSD are on the DP.

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...

×
×
  • Create New...