Jump to content


anyweb

How can I deploy Windows 8.1 x64 to the Microsoft Surface Pro 3 using System Center 2012 R2 Configuration Manager ?

Recommended Posts

if you are using a mix of devices then what boot images are deployed in your task sequences ? if they are all x64 bit boot images then all is fine, if they are x86 and x64 then the last task sequence deployed to your osd collection will be the one that 'wins' - it follows the LIFO statement (last in first out)

 

what error messages are you seeing exactly ?

Share this post


Link to post
Share on other sites

Hi, Niall,

 

Thanks for your response.

 

Only 64 bit boot image in use.

 

Not really getting any error message just nothing when trying to PXE boot the surface - no indication about trying for IP4 or IP6 address - just straight through to a normal boot.

 

However, I have managed to get it working and it must have been (at least) one of these things:

 

1) removed DHCP option 67

2) configured the PXE options in WDS - it was a new install and I'd overlooked this

3) injected the recent Surface 3 firmware updates into the boot image

 

All good now! Thanks!

Share this post


Link to post
Share on other sites

as it's UEFI you'll need to remove the DCP settings and configure ip helpers instead, OR boot from bootable media (usb media)

 

can you try that ? also i've not tested with a dock, dont have one. Try connecting the USB dongle directly and see what happens

Hi buddy, first of all great blogging!

 

Secondly we are having a nightmare pxe booting the sp3.

 

We have ip helpers in place. Running server 2008 r2 sp2, sccm 2012 r2. All other tablet, UEFI, PXE perfectly.

 

We see the pxe screen but it just drops through and we end up having to build via usb boot.

The sccm pxe log just says 'not serviced' next the sp3 Mac and guid, we have tried docking stations, usb nics, all MS approved for surface pro 3.

 

Any ideas? I have already built 34 but we need to hand the builds to the help desk as we have created a zero touch build in place for them where Mac and asset is all that is required and I'm afraid explaining usb boot to some of these lads will be a nightmare! (I'm not kidding!)

Share this post


Link to post
Share on other sites

Hi buddy, first of all great blogging!

 

 

thanks !

 

econdly we are having a nightmare pxe booting the sp3.

 

We have ip helpers in place. Running server 2008 r2 sp2, sccm 2012 r2. All other tablet, UEFI, PXE perfectly.

 

We see the pxe screen but it just drops through and we end up having to build via usb boot.

 

 

have you tried updating the firmware (offline or online) on the troublesome Surface Pro 3's ?

Share this post


Link to post
Share on other sites

what i mean is to update the firmware BEFORE the build, as there were issues with some docking stations having issues with PXE boot and those issues are resolved with the updated firmware.

 

Here's the process of updating the firmware offline, I'd suggest you try it.

 

http://blogs.technet.com/b/askpfeplat/archive/2014/10/20/how-to-update-the-surface-pro-3-firmware-offline-using-a-usb-drive.aspx

  • Like 1

Share this post


Link to post
Share on other sites

what i mean is to update the firmware BEFORE the build, as there were issues with some docking stations having issues with PXE boot and those issues are resolved with the updated firmware.

 

Here's the process of updating the firmware offline, I'd suggest you try it.

 

http://blogs.technet.com/b/askpfeplat/archive/2014/10/20/how-to-update-the-surface-pro-3-firmware-offline-using-a-usb-drive.aspx

Haha great minds must think a like as I am already in the process of this. I will let you know what happens.

Share this post


Link to post
Share on other sites

have you followed my guide exactly ? are you sure it's pulling down a 64bit boot wim ? what happens when you UEFI network boot, what do you see before it fails...

Share this post


Link to post
Share on other sites

Yes we are following your guide exactly to the letter. it is how we are and have been doing so for many different tablets. i.e hp elitepad 900 g1 (x86) hp elitpad 1000 g2 (x64) and dell venue 8 pro and many more.

 

It is not even pulling down the boot wim. It checks ip v4 pxe then skips straight to v6 then through to usb.

 

The pxe log on the sccm server just says 'not serviced'.

 

It has the correct mac in the windows 8.1 TS deployment collection also.

we are stumped...

Share this post


Link to post
Share on other sites

for many different tablets. i.e hp elitepad 900 g1 (x86) hp elitpad 1000 g2 (x64) and dell venue 8 pro and many more.

 

 

hmm are some of those UEFI devices x86 ? if so they REQUIRE an x86 boot wim,

the surface is native x64 hardware so requires a x64 bit boot wim,

please attach the smspxe.log file here please and tell me what mac address you are using on the Surface,

 

also remember the last task sequence deployed to a collection will be the boot wim that 'answers' the pxe request (LIFO)

Share this post


Link to post
Share on other sites

We have separate task sequences for seperate architectures, I.e windows 8.1 x86 ts and collection, windows 8.1 x64 ts and collection.

 

I will attach it on Monday as I am on another site tomorrow.

 

I will set up a home lab on Sunday to rule out this true UEFI idea.

 

Thanks for the fast response by the way! Nice to leave a comment and get a reply for a change! :)

Share this post


Link to post
Share on other sites

I have a working ConfigMgr 2012 R2 CU1 environment, with all servers on 2012 R2. After following the guide, I am still having trouble pxe booting. After the 'Downloading NBP file...' message, a 'Succeed to download NBP file.' message very briefly appears, followed by moving onto an ipv6 pxe attempt. I did have one successful pxe boot yesterday, but am unsure of what I changed that now prevents this from working. Any ideas? Thanks!

Share this post


Link to post
Share on other sites

I have a working ConfigMgr 2012 R2 CU1 environment, with all servers on 2012 R2. After following the guide, I am still having trouble pxe booting. After the 'Downloading NBP file...' message, a 'Succeed to download NBP file.' message very briefly appears, followed by moving onto an ipv6 pxe attempt. I did have one successful pxe boot yesterday, but am unsure of what I changed that now prevents this from working. Any ideas? Thanks!

Disregard my previous post. I realized that I didn't have the Surface Ethernet Adapter added as a computer via MAC Address correctly. I am now pxe booting properly.

Share this post


Link to post
Share on other sites

We are using SCCM SP1 and I am running into an error importing the Surface drivers. Example: The import Wizard completed with errors - The selected driver is not applicable to any supported platforms. I know there is a hotfix out there for SCCM 2007 but I haven't been able to locate one for 2012. Is there an easy fix for this? We plan to upgrade to R2 in the upcoming months but we have Surfaces coming in now that I would like to re-image.

Share this post


Link to post
Share on other sites

can you show a screenshot of the error, or include the relevant error from smsprov.log, it could be just a monitor .inf file it's complaining about in which case it's nothing to worry about,

 

also i've created an automated MDT setup for the Surface Pro 3 which could tie you over until you upgrade to Configuration Manager 2012 R2

 

it's available here.

 

http://www.windows-noob.com/forums/index.php?/topic/11479-how-can-i-deploy-windows-81-x64-to-the-microsoft-surface-pro-3-using-mdt-2013/

Share this post


Link to post
Share on other sites

it must be because Configuration Manager 2012 SP1 doesn't support Windows 8.1 and most of those drivers are for Windows 8.1

 

here's the release notes for R2 in relation to OSD:

 

The following items are new or have changed for operation system deployment in System Center 2012 R2 Configuration Manager:

  • Support for Windows Server 2012 R2 and Windows 8.1. For more information about supported operating system versions, see Prerequisites For Deploying Operating Systems in Configuration Manager.
  • Support for boot images created by using the Windows Automated Installation Kit (Windows AIK) for Windows 7 SP1 and based on Windows PE 3.1. For more information about customizing and adding boot images to Configuration Manager, see How to Customize Windows PE Boot Images to Use in Configuration Manager.
  • Added support for PXE boot of IA32 UEFI computers. For more information about operating system requirement for a PXE-enabled distribution point, see the Operating System Requirements for Typical Site System Roles section of the Supported Configurations for Configuration Manager topic.
  • Ability to create prestaged content files for task sequence content. The Create Prestaged Content action creates a compressed, prestaged content file that contains the files and associated metadata for the content in the task sequence. By default, Configuration Manager detects and adds the dependencies associated with the task sequence to the prestaged content file. You can then manually import the content at a site server, secondary site, or distribution point. For more information about prestaged content, see the Determine Whether To Prestage Content section in the Planning for Content Management in Configuration Manager topic.
  • Added virtual hard disk management from the Configuration Manager console. You can create and modify virtual hard disks, and upload them to Virtual Machine Manager.
  • New task sequence steps:
    • Run PowerShell Script: This task sequence step runs the specified Windows PowerShell script on the target computer.
    • Check Readiness: This task sequence step verifies that the target computer meets the specified deployment prerequisite conditions.
    • Set Dynamic Variables: This task sequence step gathers information and sets specific task sequence variables with the information. Then, it evaluates defined rules and sets task sequence variables based on the variables and values configured for rules that evaluate to true.
    clear.gifNote For more information about task sequence steps, see Task Sequence Steps in Configuration Manager.
  • New task sequence built-in variables:
    • SMSTSDownloadRetryCount: Use this variable to specify the number of times that Configuration Manager attempts to download content from a distribution point.
    • SMSTSDownloadRetryDelay: Use this variable to specify the number of seconds that Configuration Manager waits before it retries to download content from a distribution point.
    • TSErrorOnWarning: Use this variable to specify whether the task sequence engine treats the requirements not met warning from an application as a fatal error. You can set this variable to True or False. False is the default behavior.
    • SMSTSMPListRequestTimeout: Use this variable to specify how much time a task sequence waits before it retries to install an application after it fails to retrieve the management point list from location services. By default, the task sequence waits one minute before it retries the step. This variable is applicable only to the Install Application task sequence step.
    • _TSAppInstallStatus: The task sequence sets the _TSAppInstallStatus variable with the installation status for the application during the Install Application task sequence step. The task sequence sets the variable with one of the following values:
      • Undefined: Set when the Install Application task sequence step has not been run.
      • Error: Set when at least one application failed because of an error during the Install Application task sequence step.
      • Warning: Set when no errors occur during the Install Application task sequence step, but one or more applications, or a required dependency, did not install because a requirement was not met.
      • Success: Set when there are no errors or warning detected during the Install Application task sequence step.
      clear.gifNote For more information about built-in task sequence variables, see Task Sequence Built-in Variables in Configuration Manager.

For more information, see the Introduction to Operating System Deployment in Configuration Manager topic in the Deploying Software and Operating Systems in System Center 2012 Configuration Manager guide.

Share this post


Link to post
Share on other sites

This is somewhat off topic but wanted to share. We recently deployed over 1000 Surface Pro 2 tablets out to our school district with not much to do. "Thankfully". We just received our first pallat of Surface Pro 3 tablets and discovered that even with the PXE boot challanges of try try again and date and time issues (correct with cmd prompt prior to starting task sequence after PXE boot) but now 80% of these tablets overheat and boot to the UEFI screen.

 

After much research I discovered that the overheating is a known issue that Microsoft will not acknowledge. A Microsoft spokesperson said that they are not aware of the issue but they are writing a firmware upgrade anyway (Surface Pro UEFI 3.11.350) to enhance system stability and help prevent the date and time from changing when the battery goes below 3% (? that spells acknowledgement). This firmware upgrade does not help the problem of overheating. I was told by our Microsoft education sales technical rep that our problem is a side effect of our custom image. I ruled out our image by just using the OOBE and the problem can be reproduced all day long. Custom or OOBE.

 

The lots that we received came from lot 1433 and 1434. If your organization plans on doing a mass deployment please purchase a small lot and watch to see if they are affected by the overheating issue. Keep in mind that the more they overheat the worse they get so a one year warranty doesn't mean much when week 53 comes and you have a $1000 brick.

 

I sent a few of ours to Microsoft for field testing but ultimately they will want to replace. For our organization that is a whole pallet.

 

There are tons of reference to this overheating problem and highly recommend research prior to mass deployment.

Share this post


Link to post
Share on other sites

Just wondering is anybody using a Chip and Pin bitlocker encryption config with these devices.

I cant seem to get them to PXE boot again successfully ( 8 attempts) when the device has a PIN applied as the surface pro logo appears before the PIN request and also after the PIN is entered so not sure if there is another method that has to be used other that holding the volume down button when powering on and releasing when the logo appears?

 

Thanks

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...


×
×
  • Create New...