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

[cosmic]

the hint is in the error message

 

 

it can't find pnputil

 

if you are using a 64 bit os (and the SP3 is 64bit) then use

 

C:\Windows\Sysnative\pnputil.exe as the path

 

cheers

niall

Hi,

thanks for the hint, does it mean that the ps should look like the one below:?

 

$ScriptPath = Split-Path -parent $MyInvocation.MyCommand.Definition

$files = get-childitem -path $Scriptpath -recurse -filter *.inf

foreach ($file in $files)

{

Write-host "Injecting driver $file"

C:\Windows\System32\pnputil.exe -i -a $file.FullName

}

Write-Host "Press Enter to continue"

read-host

[anyweb]

I think you should use SysNative instead like so

 

http://www.samlogic.net/articles/sysnative-folder-64-bit-windows.htm

 

If you for example specify this folder path in your application's source code:

C:\Windows\Sysnative

the following folder path is actually used:

C:\Windows\System32

[cosmic]

 

I think you should use SysNative instead like so

 

http://www.samlogic.net/articles/sysnative-folder-64-bit-windows.htm

 

If you for example specify this folder path in your application's source code:

 

C:\Windows\Sysnative

 

the following folder path is actually used:

 

C:\Windows\System32

 

Great, works like a charm! thanks a lot!

[anyweb]

ok so post your working solution here so others can benefit :-)

[carsontl]

Hey Niall,

 

Thanks for your help so far. Running into an issue where after my task sequence completes i cannot alter lock screen preview, input a picture password, or do windows update. They just hang when you try to do any of them.

 

The task sequence is pretty basic:

 

I've tried adding an unattend.xml but with or without it the TS completes fine and the lock screen / picture password / windows updates still do not work.

 

My boss removed all the basic apps from the surface and sysprepped the machine and all of a sudden all the options were working again.

 

Any ideas? This is super frustrating.

 

Thanks,

 

Tom

[anyweb]

are you using Windows 8.1 x64 with Update (the with update part is important...)

[carsontl]

are you using Windows 8.1 x64 with Update (the with update part is important...)

 

Yessir!

[anyweb]

ok well have you confirmed that the task sequence is laid down correctly, you can attach the smsts*.log files here so we can verify

[cosmic]

ok so post your working solution here so others can benefit :-)

 

Hope it will help ...

What was done:

Extracted the driver pack and put the PS script on top:

see borrowed picture (thanks for that) http://goo.gl/1JiZ41

 

then ...

 

Made a package ...

• Package properties:

  Data Source tab: This package contains source files \\sccm\sources\...

​Created program with following settings:

• General tab:

  - Command line: Powershell.exe -executionpolicy Bypass -file .\InstallDrivers.ps1

  - Run: Normal

  - After Running: No action

• Environment tab:

  - Program can run: Only when a user is logged on;

  - Run Mode: Run with administrative rights;

  - Ticked: Allow users to interact with this program;

  - Drive mode: Runs with UNC name;

• Advanced tab:

  - Run once for the computer;

  - Ticked: Suppress program notifications;

Distributed Content into DPs;

 

Deployed to existing test collection;

 

Deployment settings:

- Action:Install;

- Purpose: Available;

 

PowerShell:

$ScriptPath = Split-Path -parent $MyInvocation.MyCommand.Definition

$files = get-childitem -path $Scriptpath -recurse -filter *.inf

foreach ($file in $files)

{

Write-host "Injecting driver $file"

C:\Windows\Sysnative\pnputil.exe -i -a $file.FullName

}

Write-Host "Press Enter to continue"

read-host

Also, under Administration -> Client Settings -> Computer Agent: set PowerShell execution Policy to: Bypass

[cosmic]

just want to add that deploying the .msi from Firmware upgrade as an application also works fine