Upgraded to SP1 and now cannot OSD Win10 to a HyperV Guest

[SM17]

Still battling to learn OSD here!

 

I upgraded my site server to R2 SP1 Friday last week for Win10 support.

 

I have re-deployed the SP1 updated boot images to my DP after the upgrade.

 

I'm trying to test a Build and Capture for Windows 10 build 10030.

 

I have my target VM as a machine in a "Test" collection and have everything deployed and distributed.

 

The Hyper V machine will PXE boot fine but reboot after "Preparing Network Connections"

 

So i imagine that its having problems with the Network Card Drivers.

 

Microsoft would not remove the driver for the Hyper-V Legacy Network Adapter from the SP1 boot image surely???

 

 

The smsts.log file tells me:

 

There are no task sequences available to this computer.

 

But i can assure you my Win 10 B+C Ref Task sequence is deployed to "Test" Collection and only that collection.

 

I can confirm that the target vm is getting a valid IP address on the network within the same scope as the SCCM server and within the same boundary group thats assigned.

 

Please help.

 

TIA

[SM17]

Cant even OSD a W7 machine to Hyper-V and i know i did this successfully pre SP1 upgrade.

 

Think ill re-build the boot images and re-deploy them incase they got screwed during the upgrade

[Garrett804]

Yeah I'd try to redo the boot images and go from there.

[SM17]

So i recreated both boot images as per this article

 

http://myitforum.com/myitforumwp/2013/08/01/how-to-create-configmgr-2012-boot-images-from-scratch/

 

Distributed them both successfully

 

Still unable to OSD anything to HyperV - or even a physical machine.

 

Always reboots on "Preparing Network Connections"

 

I dont know enough about this beast to know where to turn next

 

waaaahhhhhhhh

[anyweb]

i'm happy to remote in and take a look, using teamviewer, let me know if you want me to check

[SM17]

i'm happy to remote in and take a look, using teamviewer, let me know if you want me to check

 

This is a very kind gesture.

 

If you are happy to do so then id be most grateful.

 

Thankyou

[Garrett804]

If its restarting at the preparing network connections part then I'd think you have either the network for the VM set wrong somehow or the drivers aren't present.

[SM17]

UPDATE:

 

To me it appears its something to do with Task Sequences and some sort of advertising delay.

 

Basically i have done nothing since yesterday afternoon when i created my umpteenth task sequence - it failed again so i got the hump and give up on it!

 

Went back this afternoon, tried 1 more VM and hey presto it loaded the OS just like it was pre SP1! - I mean WTF seriously.

 

So i created a new task sequence, used exactly the same settings and boot image - created a brand new VM on the same HyperV Host with identical settings (bar the MAC address of course) - Imported it into my test Collection.

 

Bang - reboots on Preparing Network Connections.

 

Deleted the deployment from my "now working today" sequence - re-deployed again to my test collection.

 

Booted the very same VM again after removing it from the console and re-importing it again, and bang - reboots on Preparing Network Connections.

 

So the same VM managed to load the OS and then an hour later using a different Task Sequence but with all the same details as the one that worked an hour earlier fails to load, and the original that worked an hour later also now fails because its been re-deployed to my collection.

 

Only thing that was different to yesterday and the first attempt today was 18 hours of time!

 

I have a sore head - its been banged against my desk so many times this afternoon.

[SM17]

ANOTHER UPDATE

 

Left my newly created task sequence (created approx 3.30pm yesterday) - not OSD'ing and rebooting on preparing Network Connections at 5.30pm last night.

 

Come back to work this morning - re-fired up the same VM i was using yesterday - and guess what - it started to OSD fine!!

 

So I definitely have some sort of time advertisement of any newly created task sequence issue i think.

 

Anybody R2 SP1 manage to replicate this?

 

Think might have to give the guys at MS a call.

[SM17]

PROBLEM SOLVED!

 

 

If anybody else comes across this issue or any Task Sequence Deployment issue after upgrading to SP2/SP1 and lands at this thread looking for sanity the this is the problem.....

 

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 creating it.

 

credit to Jason Sandys and Torsten Meringer from the Technet forums for the above info!

 

Create your task sequence - make the available time 12 hours (i did 24 hours to be sure) earlier and your Task Sequence Deployment will work straight away!