Surface Pro wont ipv4 PXE boot

[buttonpresser]

Hey,

 

New to the forum I've got that frustrated I had to signup and post a question. Sorry in advance if this question is in the wrong forum.

 

I deploy windows 8 through SCCM 2012 using pxe.

 

I pxe booted a sureface pro 3 with a genuine Microsoft USB network adaptor and it worked great. It pxed, connected to SCCM and installed the OS. However I moved on to my next pro3 with the same adaptop, it goes to ipv4 and instead of saying press enter to network boot it goes straight to ipv6 then fails.

 

Pxe still works as Ive tried other laptops which pxe boots fine except for the pro 3. I've searched everywhere for an answer but no joy. is it maybe when I first pxed with the first one the Mac address from the adaptor got register some how and wont work anymore.

 

Running out of ideas now and any help would mean alot.

 

Thank you.

[Norphy]

Hey,

 

 

 

 

 

is it maybe when I first pxed with the first one the Mac address from the adaptor got register some how and wont work anymore.

 

.

That's exactly it. See here: http://blogs.technet.com/b/askpfeplat/archive/2014/07/28/how-to-use-the-same-external-ethernet-adapter-for-multiple-sccm-osd.aspx

 

There's a PowerShell script on that page which disassociates the mac address of the USB nic from the account in sccm and associates the mac address of its wireless card instead. Run that and you'll be golden

[buttonpresser]

You sir are a legend if this works. I only have one adaptor so do I run this script on the pro3 that I reimaged first or on the SCCM server. I then will add it in the task sequence.

 

Thanks

[buttonpresser]

Actually I should be ok if I delete the first pro3 out of SCCM then configure the script in the TS then re-deploy. Deleting it out of SCCM will delete the adaptor Mac address. Will try this tomorrow and let you know how I get on.

[Norphy]

There's no need to delete the surface from config mgr, just run the script on the surface. As you say, add the script to your tall sequence then you won't have to do it by hand again

[buttonpresser]

Hi,

 

I think I've sorted a good work around and saves me using that VB script to delete the mac address.

 

Here's what i did:

 

All my task sequences was deployed to all unknown machines which means if i already used a usb network adapter to deploy my first pro3 the mac address will register in SCCM and if you use the same adapter and try to pxe, SCCM will reconise it isn't a "unknown machine" and fail.

 

I created a device collection called "Surface Pro 3" and imported the first pro tablet into that collection.

 

I then created a new task sequence and instead of deploying it to unknown machines i deployed it to the device collection i created called "surface pro 3" this will then mean if i use the same adapter it will pxe fine because that adapter is part of the surface pro 3 device collection.

 

Hope the above makes sense.

[Norphy]

That's not going to work. ConfigMgr will think that you're rebuilding the same tablet each time and if the first one was called (for example) Bob, each consequent one is also going to be called Bob. They're going to have the same GUID inside ConfigMgr. You won't be able to manage them.

 

One way or the other, you are going to have to disassociate the USB NIC from your Surfaces.

[buttonpresser]

Didn't think about that to be honest. The script is now part of the TS but fails due to disconnecting the USB adapter, i resolved this by running the script manually after the image (take it out of the TS) which works great. Thank you so much for your help Norphy wouldn't of done it without you.

[Norphy]

Glad I could help.