Hi,

Can anybody offer any assistance.

I am testing SCCM 2012R2 - i was on CU5 and i got OSD to work on both a Physical PC and a HyperV Guest Machine.

I upgraded to SP1 for Windows 10 support.

Since then i cannot get anything to OSD.

A machine will PXE boot - will get to "Preparing Network Connections" and then reboot.

The log file says: There are no task sequences available to this computer.

But I have 1 task sequence and it is 110% deployed to the "Test" collection that contains my 2 test machines ( 1x Phy + 1x HV)

The PXE cleint gets an IP address so its got no issues communicting to the DP during PXE boot.

I have tried creating new boot images and distributing them rather than the built in provided ones but still goes no further then "Preparing Network Connections.

Tried new task sequences - nothing changes.

I deployed test images of Windows 7 to both the physical and hyper-v guest machine Friday morning prior to the SP1 upgrade.

Anybody help me troubleshoot this further please?

Many Thanks

You have distributed your newly created "boot images" to your DP right?

Also, in each task sequence are you using the boot image(s) you created?

Also, in the Boot Image properties under the data source tab do you have "Deploy this boot image from the PXE-enabled DP" checked?

Hi Travis

Its a big yes to all 3 questions :)

• Edited by Fulgent 16 hours 1 minutes ago

But I have 1 task sequence and it is 110% deployed to the "Test" collection that contains my 2 test machines ( 1x Phy + 1x HV)

Hi Travis

Its a big yes to all 3 questions :)

• Edited by Fulgent Monday, June 29, 2015 3:45 PM

But I have 1 task sequence and it is 110% deployed to the "Test" collection that contains my 2 test machines ( 1x Phy + 1x HV)

Was the deployment created just recently or is it already some days old?  There is a known issue with new deployment not showing up "asap", so double check the 'available time' and set it back a couple of days (if it was created after the SP inst

Not much to tell. There is a DST related bug in 2012 SP2/2012 R2 SP1 for Task Sequence Deployments that prevents deployments with an available time within the last hour (I think that's it) from working. The easy solution is to set your available time back 12 hours when cr