Jump to content


We use cookies to let you log in, for ads and for analytics. OK

Photo

[SCCM 2012] TS failed:There no task sequences available to this computer

SCCM 2012 no task sequence




  • Please log in to reply
14 replies to this topic

#1 alim_long

alim_long

    Advanced Member

  • Established Members
  • PipPipPip
  • 38 posts

Posted 25 February 2013 - 08:01 AM

I am using SCCM 2012 SP1 beta build 7782 for OSD, Recetly I come across a strange promble. I import computer to a collection and deploy a TS to the collection, when do a PXE boot, it can boot to winPE successful, but after winPE initialized system reboot, by checking smsts.log it report a no task sequence available error. actually I have deployed some TS to the collection inclueded the system. If I delete the record and reimport the system to sccm. everything is ok and OSD succeed, but if I make a PXE boot again the error occures. I need to delete and reimport the record again. I have googled for serval days. I check DP certificate is ok and no duplicate SMBIOS GUID records.

 

It has puzzled me for a long time.

 

 Anyone can help me?

Attached Files





#2 Oneone

Oneone

    Advanced Member

  • Established Members
  • PipPipPip
  • 196 posts
  • Gender:Male
  • Location:Stockholm Sweden

Posted 25 February 2013 - 10:19 AM

How does your advertisment look like?

 

if you want to be able to re-install that computer you have to check the box "always rerun" when doing the advertisment. OR just remove the computer from the collection and wait like 15 mins, then add it back in again, tryed that?



#3 alim_long

alim_long

    Advanced Member

  • Established Members
  • PipPipPip
  • 38 posts

Posted 26 February 2013 - 01:16 AM

Hi Oneone, thanks for your reply!

 

I select pupose as available on deployment settings and deploy mutilp TS to a collection. On this mode rerun behavior selection is gray out.

 

I also remove computer from the collection and then add it back, promble is not resolved.

 

Computer record is not obsolete.

 

Re-installing the computer is work previously. The collection and TS deployment are not changed, I don't know Why it fail now.

 

All the records in sccm are shown active under "client Activity" enven when the computer is shutdown, is it normal?



#4 alim_long

alim_long

    Advanced Member

  • Established Members
  • PipPipPip
  • 38 posts

Posted 28 February 2013 - 01:50 AM

Is there anyone meet the similar problem?



#5 Jonney

Jonney

    Newbie

  • Established Members
  • Pip
  • 3 posts

Posted 28 February 2013 - 06:07 PM

Is this affecting just one workstation or all of your workstations?

 

I had a problem like this that affected all of my workstations. Turns out that I had a corrupted policy in the database which caused the management point to freak out and not give out any policy to the clients.



#6 alim_long

alim_long

    Advanced Member

  • Established Members
  • PipPipPip
  • 38 posts

Posted 01 March 2013 - 12:27 AM

It seems all of my wrokstations are affected.

Jonney, How did you solve this problem?



#7 Oneone

Oneone

    Advanced Member

  • Established Members
  • PipPipPip
  • 196 posts
  • Gender:Male
  • Location:Stockholm Sweden

Posted 01 March 2013 - 06:33 AM

Alim_long

 

have you checked the health on your site? is everything OK?

 

AND

 

Did you create a new TS > Deploy > New Collection > Add computer > Test

 

? =)



#8 alim_long

alim_long

    Advanced Member

  • Established Members
  • PipPipPip
  • 38 posts

Posted 05 March 2013 - 03:45 AM

I tried to create a new Collection, but it is not help.

 

 

Now I re-install my SCCM server and upgrade to SP1 final version.



#9 Jonney

Jonney

    Newbie

  • Established Members
  • Pip
  • 3 posts

Posted 08 March 2013 - 07:38 PM

Microsoft provided me with two SQL queries to run against the database.

 

This one will check for bad policies in the database. if no results are returned from this query then you don't have the same issue.

 

SELECT * FROM ResPolicyMap WHERE machineid = 0 and PADBID IN (SELECT PADBID FROM PolicyAssignment WHERE BodyHash IS NULL)

 

 

This one will remove any bad policies if there are any.

 

Delete FROM ResPolicyMap WHERE machineid = 0 and PADBID IN (SELECT PADBID FROM PolicyAssignment WHERE BodyHash IS NULL)

 

 

After that restart the management point and everything should be working normally.

 

 


  • BogdanR, jcortez103 and srjac68 like this

#10 alim_long

alim_long

    Advanced Member

  • Established Members
  • PipPipPip
  • 38 posts

Posted 14 March 2013 - 08:06 AM

Thanks Jonney.

 

The problem was resoved. but you reply is also useful.

 

This occurs on my new installed SCCM 2012SP1 server.

I researched for a long time and find the reason this afternoon.

 

Due to I join my clients to workgroup instead of domain, so client will not be approved in SCCM server.

 

Client can't receive mostly policy from MP(this different than ConfigMgr 2007 where a client that is not approved would still receive most policy).

 

Only two options under action tab in configuration manager

 

After Approve the client through the administrator console manually, The failure disappears.

 

refer to Technet



#11 Sam_Brown

Sam_Brown

    Newbie

  • Established Members
  • Pip
  • 1 posts

Posted 03 March 2014 - 07:56 PM

Microsoft provided me with two SQL queries to run against the database.

 

This one will check for bad policies in the database. if no results are returned from this query then you don't have the same issue.

 

SELECT * FROM ResPolicyMap WHERE machineid = 0 and PADBID IN (SELECT PADBID FROM PolicyAssignment WHERE BodyHash IS NULL)

 

 

This one will remove any bad policies if there are any.

 

Delete FROM ResPolicyMap WHERE machineid = 0 and PADBID IN (SELECT PADBID FROM PolicyAssignment WHERE BodyHash IS NULL)

 

 

After that restart the management point and everything should be working normally.

 

 

 

I thought I'd register and post a thank you for this post because it managed to fix an issue I'd been having for a few days. Also for anyone else that cares this also fixed a few issues we had with deploying clients and the clients not communicating with the SCCM Server and installing SCEP.



#12 srjac68

srjac68

    Newbie

  • Established Members
  • Pip
  • 3 posts

Posted 16 September 2014 - 04:38 PM

Microsoft provided me with two SQL queries to run against the database.

 

This one will check for bad policies in the database. if no results are returned from this query then you don't have the same issue.

 

SELECT * FROM ResPolicyMap WHERE machineid = 0 and PADBID IN (SELECT PADBID FROM PolicyAssignment WHERE BodyHash IS NULL)

 

 

This one will remove any bad policies if there are any.

 

Delete FROM ResPolicyMap WHERE machineid = 0 and PADBID IN (SELECT PADBID FROM PolicyAssignment WHERE BodyHash IS NULL)

 

 

After that restart the management point and everything should be working normally.

 

 

 

This query resolved my issue of my staging collections of OSD deployments were not seeing their assigned OSD task sequences. Thanks for the post it helped me out greatly!



#13 SDR-Team

SDR-Team

    Newbie

  • Established Members
  • Pip
  • 1 posts

Posted 16 October 2014 - 09:10 AM

Microsoft provided me with two SQL queries to run against the database.

 

This one will check for bad policies in the database. if no results are returned from this query then you don't have the same issue.

 

SELECT * FROM ResPolicyMap WHERE machineid = 0 and PADBID IN (SELECT PADBID FROM PolicyAssignment WHERE BodyHash IS NULL)

 

 

This one will remove any bad policies if there are any.

 

Delete FROM ResPolicyMap WHERE machineid = 0 and PADBID IN (SELECT PADBID FROM PolicyAssignment WHERE BodyHash IS NULL)

 

 

After that restart the management point and everything should be working normally.

 

 

 

This solved our Problem, after we stuck for 2 Weeks trying to resolve it

 

we had the Error: no task sequences available for this computer error code 80004005

 

 

 

Thank you very much!



#14 jcortez103

jcortez103

    Member

  • Established Members
  • PipPip
  • 14 posts

Posted 15 January 2015 - 06:56 PM

Microsoft provided me with two SQL queries to run against the database.

 

This one will check for bad policies in the database. if no results are returned from this query then you don't have the same issue.

 

SELECT * FROM ResPolicyMap WHERE machineid = 0 and PADBID IN (SELECT PADBID FROM PolicyAssignment WHERE BodyHash IS NULL)

 

 

This one will remove any bad policies if there are any.

 

Delete FROM ResPolicyMap WHERE machineid = 0 and PADBID IN (SELECT PADBID FROM PolicyAssignment WHERE BodyHash IS NULL)

 

 

After that restart the management point and everything should be working normally.

 

 

 

Just checking in to thank you. This solved my problem as well!



#15 BogdanR

BogdanR

    Member

  • Established Members
  • PipPip
  • 13 posts

Posted 04 March 2015 - 04:52 PM

Microsoft provided me with two SQL queries to run against the database.

 

This one will check for bad policies in the database. if no results are returned from this query then you don't have the same issue.

 

SELECT * FROM ResPolicyMap WHERE machineid = 0 and PADBID IN (SELECT PADBID FROM PolicyAssignment WHERE BodyHash IS NULL)

 

 

This one will remove any bad policies if there are any.

 

Delete FROM ResPolicyMap WHERE machineid = 0 and PADBID IN (SELECT PADBID FROM PolicyAssignment WHERE BodyHash IS NULL)

 

 

After that restart the management point and everything should be working normally.

 

 

 

Works like a charm ! In my case it wasn't necessary to restart the management point service. Thank you for your solution.







0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users