[sccm 2012] Failed to load task sequence

[bushby]

Hi All,

 

i havent touched our sccm for 2 weeks and now all of a suden when i need it i can select any images to deploy.

 

i boot via pxe and type in the password then get fail to run task sequence ther are no task sequences availible to this machine.

 

in the past it would show all the images i have then just select to required build followed by bish bash then done.

 

the machine im currently trying is unkown to the system and another is known getting the same responce.

[CyberDrac]

Check the system time is close to the domain time

[bushby]

sadly they are correct on all the machines iv checked

[sllorep]

Have you looked at the build log files to see if there is something in there that can explain or help to Google search an answer:

 

Whilst it is on the failed screen, press F8 and then map a network drive (net use y: \\server\share)

Then copy the smsts.log and smsts-date-time.log files to the share. Use another PC to view the logs to see where the task sequence error occurred.

Quote from Microsoft https://technet.microsoft.com/en-gb/library/bb932135.aspx:

Smsts.log

Log file location:

• If task sequence completes when running in the full operating system with an Configuration Manager 2007 client installed on the computer: \Logs

• If a task sequence is completed when running in the full operating system with no Configuration Manager 2007 client installed on the computer: %temp%\SMSTSLOG

• If a task sequence is completed when running in Windows PE: \SMSTSLOG

 

I use CMTrace<32/64>.exe to view/open the logs as this highlights error or warning lines so is easier to see.

 

Note, you can open the logs on the workstation being built without mapping the network drive with "notepad.exe smsts.log" but I find it easier to view on a machine with a bigger monitor and CMtrace.

 

CMTrace is part of SCCM Toolkit:

Download System Center 2012 R2 Configuration Manager Toolkit from Official Microsoft Download Center

 

Ash.

 

P.S.:

Check the system time is close to the domain time

+1 to Date/Time! We've been caught out with this before. Make sure that it is correct in the BIOS.

Edited February 26, 2015 by sllorep

[gaz350b]

Are they the 2nd time the machines have been deployed? If so 1st time you probably had them advertised to unknown computers.

 

Once they have been deployed to you then need advertise (deploy) to a collection that the machine is in.

[Gatt]

Are they the 2nd time the machines have been deployed? If so 1st time you probably had them advertised to unknown computers.

 

Once they have been deployed to you then need advertise (deploy) to a collection that the machine is in.

 

I was thinking the same, but this issue normally results in an "Abort PXE" error due to no valid Task Sequence for the device. Also the OP states one PC is "Unknown"

 

To the OP, check that the correct NIC and Mass Storage drivers are in your boot image

Also, make sure both the x86 and x64 boot images are correctly distributed.

[gaz350b]

Very true, also has the network access account password changed?

 

Do the task sequences still have a boot file specified?

 

I would personally recheck all the previous steps.

 

Check boot images/ os images are all on the distribution points.

 

Make sure pxeboot files are deployed to a pxe enabled distribution point ( this is in the properties in 2012 and caught me out when I deleted the inbuilt pxe images)

 

Make sure inknown computer support is enabled

 

Make sure your collections are correct

 

Delete all advertisements ( deployment? In 2012? )

 

Then Readvertise/deploy task sequence to the inknown and system collections of your choice.

 

make sure the task sequence is available to media and pxeboot (not hidden)

 

Never tested it but maybe this last option when selected allows you to boot in pxe but won't show the task sequence?

[ITGuyWestMidlands]

Do they have a generic bios guid? We had a batch of machines with the same bios guid which caused a similar issue. Had do use amid I to generate a new I'd for each of them

[Gatt]

Without the logfiles we wont know for sure what is happening here.

 

Can the OP post or PM me their smsts.log and smspxe.log (Found on the Device and the WDS point respectively)?

 

Also, a few things to check here:

 

OSD Task Sequence fails with "There are no task sequences available for this computer" if multiple machines have the same SMBIOS GUID - The Official Configuration Manager Support Team Blog - Site Home - TechNet Blogs

 

One regarding duplicate GUID's and one about ensuring your certificates are correct.

 

It's booting so PXE so that indicates that the boot images have been correctly copied to WDS and that WDS is working.

The error is pointing at a lack of Task Sequences for that device.

 

There must be something there as it boots into PXE without an "Abort PXE" which is normal if no TS is advertised to at least one collection the device is a member of.

 

This leads me to believe a few things could be the problem:

 

1. NIC / Mass Storage Drivers are missing from the Boot Image (can be tested in WinPe by pressing F8 (enable it in your Boot Image) and doing an "IPCONFIG" and also making sure it can see the Hard Drives of the PC.

2. Duplicate SMBIOS GUID - There is a query in SCCM that allows you to find duplicate Machines.

3. The DP doesn't have the correct SSL Certificate allocated to it.

[ITGuyWestMidlands]

Try https://social.technet.microsoft.com/Forums/en-US/7702e267-6c1a-4844-9a2b-2347137b17e3/os-deployment-task-sequence-doesnt-show-up?forum=configmanagerdeployment to fix if it is due to duplicate ids. The way i tell is that just before it picks up an ip address the long number (guid) after tge name of the nic is sequential and doesnt look random. Something like 0001-0002-0004...

[TechMonkey]

+1 to Date/Time! We've been caught out with this before. Make sure that it is correct in the BIOS.

 

I thank you! Had 2 machines returned from servicing and one built perfectly the other was just failing. Had checked everything else, from the logs to duplication to deleting the old record from SCCM. Hadn't thought about the BIOS time and it was horribly out. So I am sorted now

[bushby]

Hi Gatt

 

thanks for the advice i will go and pull the logs from two of the machines in question and get them sent over

[sllorep]

I thank you! Had 2 machines returned from servicing and one built perfectly the other was just failing. Had checked everything else, from the logs to duplication to deleting the old record from SCCM. Hadn't thought about the BIOS time and it was horribly out. So I am sorted now

 

I'm glad that I could help. We've had some older PC where the CMOS battery had run out and all of them were failing task sequences until we changed the batteries and set the BIOS time and date (and the rest of the settings).

Ash

[bushby]

Thanks everyone for the help it ended up there was errors in the sql side of the server.

it took 4 days of our support company looking in to it and me being a pest to them to get updates.

 

but the good thing is its now working XD.

 

SOLUTION: SCCM Clients Unable To Download Policy From Management Point - Lockstep Technology Group Blogs

 

thats what they sent me as what was going on

[Sam_Brown]

I had a similar issue a year back. Maybe this will help...

 

http://www.edugeek.net/forums/o-s-deployment/132557-installing-clients-servers-shows-sccm-console-but-wont-deploy-scep.html