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

don't capture the image directly from the surface pro 3, use virtual machines instead to build your master image, and capture it from there,

as regards customizing the start screen see here > http://www.windows-noob.com/forums/index.php?/topic/8101-using-system-center-2012-configuration-manager-part-13-deploying-windows-8-x64-with-custom-start-screen/

 

to build and capture windows 8.1 it's the same process as Windows 7 or less (with ConfigMgr) as described here > http://www.windows-noob.com/forums/index.php?/topic/6353-using-system-center-2012-configuration-manager-part-7-build-and-capture-windows-7-x64-sp1/

 

or use MDT to build your reference image as most people advise, you can setup a quick MDT infrastructure following my guides here > http://www.windows-noob.com/forums/index.php?/forum/74-mdt/

 

hope that helps !

 

lastly, have you seen this yet ?

 

CM12 in a Lab - 5 video series on deploying the Microsoft Surface Pro 3 - available now !

Share this post


Link to post
Share on other sites


There is much good information here but I have a question to see if I can do what I hope it possible.

 

Ok, so, we buy surface pro 3 in our company. What I'd like to do is set it up to where, I can have the majority of all the software installed on a surface and have the start screen set up the way I like it. Then once all that is done, we hand the surface to a sales rep. I'd like to see if I can take that, and deploy it on to to the surfaces of the same make and model. Is it possible to do something like this? As I understand it, the Windows 8.1 key is stored in the UEFI BIOS.

 

Can this be possible? It would be nice to have a base setup, then add some programs after the fact. It would save a lot of time in terms of not having to download all windows updates when they can already be applied.

 

I wonder how it'll work with windows 10 around the corner.

 

Anyweb, do you have a procedure setup to capture an surface pro 3's image and using that image for deployment to other surfaces? Do you need to change the windows key or is that done automatically.

 

Yes, you can tell I'm a noob lol. We just wanted to see if it was possible to save time setting up the devices in the office when we hire new reps.

 

 

Just a thought, but if you are only customizing the start screen and installing applications, you could do everything you need without any redeployment of the operating system. You could create a Post OS Installation Task Sequence in MDT that is configured for installing the applications you need and run that on each machine you need to configure.

 

Customizing the Start Layout is as easy as exporting the start layout and importing it with your task sequence, or better yet, using Group Policy. Note that if you import the start layout with a user account already active on the Surface Pro 3 the new layout will only take effect for new users, not the existing user. It is also important that the Start Menu shortcut links be present or the tiles from the layout will not appear.

 

Brandon

Windows Outreach Team- IT Pro

Windows for IT Pros on TechNet

Share this post


Link to post
Share on other sites

PS: Made sense to create new thread.. You site and forum is amazing and I wonder why it did not show up on my Google searches regarding issues for Surface Pro 3.

 

I will link to that thread here. I figured the MDT might be easier than SCCM for me.. But maybe you have a simpler way for this simple task.

 

Create/ Image/ Sysprep Win 8.1 & Win 10 VHDs WIMs for Native Boot on Surface Pro 3 for isolated activities without huge server setup?

Share this post


Link to post
Share on other sites

I need some help deploying a Surface Pro 3 in SCCM 2012 SP1 (no CUs installed).

 

I know this is not supported, but I managed to cobble together a solution which so far has worked, I'm just having trouble with one specific unit. Here's the method I used to get to this point:

 

  • Use MDT 2013 to build and capture Windows 8.1 WIM which includes SP3 network drivers
  • Use SCCM 2012 SP1 to create boot image, injecting SP3 network drivers
  • Import WIM from MDT and use SCCM 2012 SP1 to create deploy task sequence
  • Task sequence installs Surface Pro 3 update MSI package since importing drivers to create proper driver package does not work
  • Other usual actions are performed such as enabling BitLocker, joining to domain, installing software packages, etc.

The deployment is done with boot media rather than PXE because I've had trouble getting it to work. In order to create the boot drive I had to combine files from the MDT boot drive and SCCM boot drive. The whole process is a Frankenstein combination of MDT and SCCM that is in no way supported, but surprisingly works. We're only doing this in a very limited pilot and so far all SCCM deployments have been done by me at my site.

 

My current problem is as follows. I had a new Surface shipped directly to a tech at another site. I distributed all the content needed to the local DP there and tried to walk him through the deployment. He created the boot drive, booted to it, diskparted the Surface, and selected the task sequence. After the WinPE environment is copied down from the network he's prompted to remove the drive and reboot. At this point it should reboot back into WinPE and continue with the deployment, that's how it works for me. But for him, it reboots directly to the BIOS if the USB drive is not inserted. I verified the hard drive has been partitioned and formatted properly and that the WinPE files have been downloaded. However it won't boot to the hard drive the way it's done on all the other Surfaces I've deployed with this method. The firmware is definitely outdated because it doesn't give the same number of boot order options, but I can't determine what version it is. The system date was also set to 2012, which I had to manually update in order for the task sequence to run at all. I'm stuck here, and I can't think of what to do next other than manually install Windows just to update the firmware and see if that helps.

 

Any help would be greatly appreciated, since I'd hate to have to boot up manually update firmware for every new Surface we deploy. Every other Surface that was deployed in SCCM was configured and updated manually first before we established this process, so this is the first true deployment from bare metal. I know the best answer will be to upgrade my SCCM environment to a supported version, but that's out of my hands and will not be happening overnight. In the mean time, I'm trying to do whatever I can to make this work. Thanks!

Share this post


Link to post
Share on other sites
that's how it works for me. But for him, it reboots directly to the BIOS if the USB drive is not inserted. I verified the hard drive has been partitioned and formatted properly and that the WinPE files have been downloaded. However it won't boot to the hard drive the way it's done on all the other Surfaces I've deployed with this method.

 

 

it won't boot to a USB drive because of a few factors such as

 

is the USB drive formatted with NTFS, if so, it won't work, UEFI boot must be FAT32

is the USB drive using an x86 boot image ? if so it won't work, UEFI deployments to the Surface Pro 3 must use an x64 boot image

thirdly, to boot to USB, shutdown the surface pro 3 correctly (start, shutdown) then power it on by pressing and holding VOLUME down, then briefly press the power button, it should then boot from the USB device

Share this post


Link to post
Share on other sites

 

it won't boot to a USB drive because of a few factors such as

 

is the USB drive formatted with NTFS, if so, it won't work, UEFI boot must be FAT32

is the USB drive using an x86 boot image ? if so it won't work, UEFI deployments to the Surface Pro 3 must use an x64 boot image

thirdly, to boot to USB, shutdown the surface pro 3 correctly (start, shutdown) then power it on by pressing and holding VOLUME down, then briefly press the power button, it should then boot from the USB device

 

  • The USB drive is FAT32
  • The boot image is x64
  • The hard drive had already been cleaned with diskpart so the only way to shut the device down was with the power button

The USB drive and boot image are configured the same as the ones I use on my deployments. It initially boots to the drive, but once the task sequence calls for a reboot, I won't boot back to the USB drive. I resolved the issue this morning, just not how I would have liked to. I had the tech manually install OEM Windows 8.1 from a USB drive and run the SP3 update MSI. From there he was able to use the same process as before, including cleaning the hard drive with diskpart and the build started with no issue. Unless I'm missing something, the only change is the updated firmware that would survive diskpart, so the older firmware was to blame.

Share this post


Link to post
Share on other sites
The hard drive had already been cleaned with diskpart so the only way to shut the device down was with the power button

 

 

that's a problem !

you must have a CLEAN shutdown otherwise it will always 'resume from standby' and cannot PXE boot or USB boot in that mode,

 

chicken/egg...

 

so... Power it on and hold the powerbutton down to force it off for 13 seconds, count them, slowly.

 

then try again, you'll get it right after about 4 attempts...

Share this post


Link to post
Share on other sites

 

that's a problem !

you must have a CLEAN shutdown otherwise it will always 'resume from standby' and cannot PXE boot or USB boot in that mode,

 

chicken/egg...

 

so... Power it on and hold the powerbutton down to force it off for 13 seconds, count them, slowly.

 

then try again, you'll get it right after about 4 attempts...

 

That's the thing though, the problem isn't booting to USB. The Surface will boot to USB, I'll diskpart the hard drive, and run the task sequence. I come to a step where I remove the USB drive and select reboot, and it should boot to the WinPE environment that's been copied to the hard drive. That is where the process fails, because it only boots to the BIOS. It I re-insert the USB drive it'll boot to that just fine. Besides, after updating the firmware it started behaving exactly as the others had.

Share this post


Link to post
Share on other sites

Am i right in thinking this wont work on R2 SP1 due to the cmdlet changing?

Share this post


Link to post
Share on other sites

which cmdlet are you referring to ?

Share this post


Link to post
Share on other sites

the script below works fine in CM12 R2 CU3 but does not work correctly without modification in CU4 due to the cmdlet changing

Share this post


Link to post
Share on other sites

here's the amended version of the script, works with both cu's, just comment out as necessary..

# This script creates a driver package and then distributes it
# Niall Brady 2015/3/29, derived from a script from http://tinyurl.com/qzwwffc
#
# set variables for the driver import 
#
clear
CD C: # get-childitem will fail otherwise if you re-run
#
# set the distribution point name
$DistributionPointName = "CM01.VIAMONSTRA.COM"
#
#== Example: "Dell Optiplex 7010" or "Dell Latitude E6540"
$Make = "Microsoft"
$Model = "Surface Pro 3"

#== Example: "Win7" or "Win8"
$DriverOS = "Windows 8.1"

#== Options are "x86" or "x64"
$DriverArchitecture = "x64"

#== Driver root source dir
$DriverRootSource = "\\cm01\Sources\OSD\Drivers"
$DriverPkgRootSource = "\\cm01\Sources\OSD\DriverPackages"

#==============================================================
# Begin
#==============================================================

#Put together variables based on os, make, model and architecture
$DriverPackageName = $DriverOS + " " + $DriverArchitecture + " - " + $Make + " " + $Model
Write-Host "DriverPackageName = " $DriverPackageName
$DriverSource = $DriverRootSource + "\" + $DriverOS + " "+ $DriverArchitecture + "\" + $Make + "\" + $Model
Write-Host "DriverSource = " $DriverSource
$DriverPkgSource = $DriverPkgRootSource + "\" + $DriverOS + " " + $DriverArchitecture + "\" + $Make + "\" + $Model
Write-Host "DriverPkgSource = " $DriverPkgSource

$choice = ""
while ($choice -notmatch "[y|n]"){
    $choice = read-host "Do you want to continue? (Y/N)"
    }

if ($choice -eq "y"){
#unblock the files
gci $DriverSource -recurse | unblock-file

# Verify Driver Source exists.
If (Get-Item "$DriverSource" -ErrorAction SilentlyContinue)
{
# Get driver files
#Write-host "Importing the following drivers.." $Drivers

$Drivers = Get-childitem -path $DriverSource -Recurse -Filter "*.inf"
}
else
{
Write-Warning "Driver Source not found. Cannot continue"
Break
}

# Create Driver package source if not exists
If (Get-Item $DriverPkgSource -ErrorAction SilentlyContinue)
{
Write-Host "$DriverPkgSource already exists… "
}
else
{
Write-Host "Creating Driver package source directory $DriverPkgSource"
New-Item -ItemType directory $DriverPkgSource
}

# Connect to ConfigMgr
#
$CMDrive="E:"
$SiteCode="PS1:\"
Import-Module $CMDrive'\Program Files\Microsoft Configuration Manager\AdminConsole\bin\ConfigurationManager.psd1'
#Set-Location $SiteCode
cd $SiteCode

#

If (Get-CMDriverPackage -Name $DriverPackageName -ErrorAction SilentlyContinue)
{
Write-Warning "$DriverPackageName Already exists. Exiting"
Break
}
else
{
Write-Host "Creating new Driver Package: " $DriverPackageName
# works up to CU3 
# New-CMDriverPackage -Name "$DriverPackageName" -Path "$DriverPkgSource" -PackageSourceType StorageDirect
# use below for CU4 onwards
#
New-CMDriverPackage -Name "$DriverPackageName" -Path "$DriverPkgSource"
$DriverPackage = Get-CMDriverPackage -Name $DriverPackageName
New-CMCategory -CategoryType DriverCategories -Name $DriverPackageName -ErrorAction SilentlyContinue
$DriverCategory = Get-CMCategory -Name $DriverPackageName

foreach($item in $Drivers)
{
$DriverPackage = Get-CMDriverPackage -Name $DriverPackageName
Write-Host "Importing the following driver: " $item.FullName
Import-CMDriver -UncFileLocation $item.FullName -ImportDuplicateDriverOption AppendCategory -EnableAndAllowInstall $True -DriverPackage $DriverPackage -AdministrativeCategory $DriverCategory -UpdateDistributionPointsforDriverPackage $False -verbose

}

}

# distribute it !

Start-CMContentDistribution –DriverPackageName $DriverPackageName –DistributionPointName $DistributionPointName
Start-Sleep -s 60
Update-CMDistributionPoint -DriverPackageName $DriverPackageName
Write-Host "Operations are complete !, exiting."

CD C:
    }
   
else {write-host "No drivers were imported, exiting!"}
  • Like 1

Share this post


Link to post
Share on other sites

 

That's the thing though, the problem isn't booting to USB. The Surface will boot to USB, I'll diskpart the hard drive, and run the task sequence. I come to a step where I remove the USB drive and select reboot, and it should boot to the WinPE environment that's been copied to the hard drive. That is where the process fails, because it only boots to the BIOS. It I re-insert the USB drive it'll boot to that just fine. Besides, after updating the firmware it started behaving exactly as the others had.

Try formatting the surface drive with a partition. Then boot to USB again. We have seen issues exactly as you explain them and this worked for us.

Share this post


Link to post
Share on other sites

Hello,

 

Do you have a guide on how can I deploy Windows 10 ENT x64 to the Microsoft Surface Pro 3 using System Center 2012 R2 Configuration Manager?

 

Or will this 8.1 guide work?

 

Thanks!

Share this post


Link to post
Share on other sites

not yet, it's coming... have you upgraded to CM12 R2 Sp1 yet ?

Share this post


Link to post
Share on other sites

Have you ran into any issues running the task sequence between the different processor models on the surface pro 3?

 

I have a standard task sequence which installs Windows 8.1, Office 2013, adobe reader, 7zip. This works perfectly on the i3 model. However the i5 and i7 model run through the task sequence and successfully install office, but then essentially pause. The screen shows installing office 2013 (application 1 of 3). No error messages, nothing new added to any log files in C:\Windows\CCM\Logs. It doesn't even attempt to download adobe reader. The last entry in the appdiscovery log is that office 2013 has been successfully discovered.

Share this post


Link to post
Share on other sites

how long have you waited after that ? did you verify if it fails over on that step or not

 

we've only been deploying i5 Surface Pro 3's and have not noticed that behaviour

are you installing these apps as dynamic apps (via variables) if so there's a bug in CM12 R2 SP1 that should be resolved (hopefully) in CU2

Share this post


Link to post
Share on other sites

We have let it run for approx. 12 hours with no changes. I don't see anything that actually shows a failure or not in any of the logs.

 

The apps are being installed by a standard app install application method (not dynamic). I have tried updating firmware as well as updated drivers but it still has the same results.

Share this post


Link to post
Share on other sites

Man, these Surface Pro 3's are kicking my butt. I am able to image a Dell 9010 with the windows 8.1 image that I built for the Surface pro 3, that dose not seem right. How are you able to get around using an external network adapter and its own MAC? I can get the surface to talk to the DP via "Bootable Media" it gets an ip, and then starts to load our x86 boot.wim. I have made sure over and over that the TS is set to only use the ADK 8.1 x64 boot.wim. Any ideas?

Share this post


Link to post
Share on other sites

Can the Surface pro 3 use Legacy Boot options? or are we forced to use the UEFI?

 

the Surface Pro line of products are UEFI only

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