If you Get <![LOG[Setting wizard error: There are no task sequences available for this computer.] as in your SMSTS/log file then check these points... Ø The computer is not imported in the console if you are using known computers not unknown computers Ø If you are using unknown computers, delete any devices with the name unknown (but whatever you do DO NOT delete the two builtin unknown records) Ø Make sure that the TS is enabled Ø Make sure the device is in a collection with a TS deployed to it Ø Change the schedule of the deployment to yesterday Ø Check if the TS deployment is set to ‘configmgr client, media and PXE’ Ø The computer is imported with a mac address that is already in the database (check the report ‘MAC computers for a specific mac address’ Ø The computer still has a cached pxe advertisement Ø The computer is in the console but is not approved Ø The computer has incorrect date/time settings Ø Check if the DP certificates have not expired Ø The Boot Image associated to the TS has not been distributed yet Ø The ResourceId of the computer that boot’s is already used by another machine in the console (verify the ‘itemkey’ value from SMSPXE.log versus the result from select * from v_R_system where resourceid=’….’ Ø The biosguid of the computer that boot’s is already used by another machine in the console (check the biosguid from SMSPXE.LOG versus the result from select * from v_R_system where smbios_guid0 LIKE ‘%…%’ (try with a part of the biosguid…) Ø Delete the device from the console and import it again Ø Check if there are any bad policy assignments in the sql db: Ø SELECT * FROM ResPolicyMap WHERE machineid = 0 and PADBID IN (SELECT PADBID FROM PolicyAssignment WHERE BodyHash IS NULL) if this returns anything then you have to delete the items with: Delete FROM ResPolicyMap WHERE machineid = 0 and PADBID IN (SELECT PADBID FROM PolicyAssignment WHERE BodyHash IS NULL)

If you Get <![LOG[Setting wizard error: There are no task sequences available for this computer.] as in your SMSTS/log file then check these points...

Ø  The computer is not imported in the console if you are using known computers not unknown computers

Ø  If you are using unknown computers, delete any devices with the name unknown (but whatever you do DO NOT delete the two builtin unknown records)

Ø  Make sure that the TS is enabled

Ø  Make sure the device is in a collection with a TS deployed to it

Ø  Change the schedule of the deployment to yesterday

Ø  Check if the TS deployment is set to ‘configmgr client, media and PXE’

Ø  The computer is imported with a mac address that is already in the database (check the report ‘MAC computers for a specific mac address’

Ø  The computer still has a cached pxe advertisement

Ø  The computer is in the console but is not approved

Ø  The computer has incorrect date/time settings

Ø  Check if the DP certificates have not expired

Ø  The Boot Image associated to the TS has not been distributed yet

Ø  The ResourceId of the computer that boot’s is already used by another machine in the console (verify the ‘itemkey’ value from SMSPXE.log versus the result from select * from v_R_system where resourceid=’….’

Ø  The biosguid of the computer that boot’s is already used by another machine in the console (check the biosguid from SMSPXE.LOG versus the result from select * from v_R_system where smbios_guid0 LIKE ‘%…%’ (try with a part of the biosguid…)

Ø  Delete the device from the console and import it again

Ø  Check if there are any bad policy assignments in the sql db:

Ø  SELECT * FROM ResPolicyMap WHERE machineid = 0 and PADBID IN (SELECT PADBID FROM PolicyAssignment WHERE BodyHash IS NULL) if this returns anything then you have to delete the items with: Delete FROM ResPolicyMap WHERE machineid = 0 and PADBID IN (SELECT PADBID FROM PolicyAssignment WHERE BodyHash IS NULL)