Client Management Suite

Hello world!

Recently, my team and I have been trying to image a Surface Pro 4 using PXE, with no luck....We have tried injecting every Surface Pro 4 driver (including dock drivers)...

Anyone had success with this?

Hi dyeLucky,

have you checked this thread about Surgace Pro imaging?

• https://www-secure.symantec.com/connect/forums/surface-pro-4-storage-driver

Regards,

IP.

Hey Igor,

We just checked this out.  We have already imported a like Storage drive.  We found another storage driver, locally extracted, and it was a little larger.  We are going to reimport this and try again later.  If we succeed, I'll let you know.

What version of PE are you trying? We were able to get ours to PXE and image running PE 5 and the storage driver provided by MS for that version of PE/Win10.

@jpellet2 we are using WinPE 4.0.  I have heard that people have had great success in using WinPE 5 to image the Surface Pro 4, but we want to try and make this happen without the upgrade.

jpellet

We are using 7.5 SP1 HF(whatever is the newest), how much is involved implementing PE5 / PE5.1 over PE4?

Installing appropriate ADK and replacing a few WIM's?

Maybe have to modify a few BDC files?

I m actually on Josh's team and its my Surface Pro 4 we have been playing with.

We can PXE boot and copy boot.wim, it is when it attempts to load WinPE itself.  We are using x64 boot image

After about 2-6 seconds of little icon going around, we get a BSOD and immedaite reboot.  The error I captured on video in the BSOD is  = ACPI BIOS ERROR

We have installed multiple NVMe drivers and all of the Surface Pro 4 drivers we can download from MS..

All nada at leased with our current WinPE environement.

Thanks,

Clay

You guys are having better luck than we did with our two Surface Pro 3's. When we imaged those they were permanently bricked! They wouldn't even go to the BIOS/EFI and had to be swapped out.

I'm glad to see this problem doesn't seem to affect the SP4's, should we ever buy some of them, and will keep an eye on this thread.

This is interesting. We developed a Surface 4 image based on the LTSB version of Windows 10 and it worked fiune during development. We are on 7.6 HF6 and WinPE 4.0.

We stopped working on the Surface 4 for a few weeks and then revisited it and now have run into the exact same issue with NO changes to our Altiris environment or the Surface 4 we had been working on. It is really odd...

That's terrible!  I hate to hear that.

Fortunately, our experience with the Surface Pro 3 was the opposite; everything worked without a lot of issues, that I remember.  :)

tloenhorst,

That is funny you bring that up that it worked without issues and now you see the error we are seeing.

The one thing I failed to mention before was that we were testing image deployment via UEFI USB when we first unboxed it.

One thing I do remember it doing when our latest Surface Pro 4 driver pack (March 2016) was injected during the USB imaging process , that on first boot it knew there were firmware updates and proceeded to do them.  Specifically the UEFI firmeware among others

I bet one of the firmwares that we applied from the get go changed something, seeing hows your initially worked and now possibly your devices could have had their firmwares updated at some point since then and now you get the error as well.

Just throwing things out there and it sounds logical, but no way to downgrade firmware as far as I know to test.

Thanks for the info,

Clay

Just to add more info. Rebuilt our Surface Pro 4 with the latest factory image (SurfacePro4_BMR_15_4.53.0) and still got the above error message with our current boot environment: WinPE4.

Decided to go to WinPE 5 and rebuilt our boot image....now it works like a charm. We are able to PXE boot and image. So, we'll see how it fares when the image is done downloading.

Give it a try!

I used these to upgrade to WInPE 5:

https://support.symantec.com/en_US/article.howto124074.html

https://support.symantec.com/en_US/article.howto124073.html

Thanks @tloenhorst.

I believe these instructions are for a 7.6 environment; we are still at 7.5 SP1 HF5.  I tried this, on our SMS environment, and had no luck...

Anyone else have any ideas on how to do this on a 7.5 SP1 HF5 environment?

Ah, sorry, I didn't know you were still on 7.5x...we never had a need for WinPE5 while on 7.5 so I never looked into getting it going. Heck, we didn't need it in 7.6 HF6 until we got these Surface 4 machines.

Also, we had a fairly smooth transition to 7.6 HF6 a few months back so, another consideration. Also, we built our Surface 4 with the LTSB version of Win10 as it offers better control over updates to the OS. There's another thread heating up over the ability to do feature/servicing upgrades via patch mgmt.

Ah ok.  If we keep this solution, we may end up going to 7.6, but it is hard to say as this time.  At this current time, it would be nice to upgrade to 5.0 (and/or 5.1), so that we can get away from having our help desk use an external drive method...