anyweb

the msi is something called Surface Platform Support and it shows up in Programs and Features after being installed, but apart from that I'm not sure what it does and yes you can install it using a standard package method, it's just a msiexec /i bla.msi /q

The next chapter of Windows 10 will be streamed live on January 21st and I'm sure we are all looking forward to seeing what is coming next and what has changed. Microsoft has already tweeted this screenshot to get us alerted to how you can separate work and play with Windows 10 and this one to show how you can keep tabs on your apps don't forget the date, January 21st. Be there, or be square ! http://news.microsoft.com/windows10story/

Introduction Microsoft released new updated drivers for the Surface Pro 3 yesterday and you can read about what those driver updates contained here. Here's a breakdown of what those driver versions are: Surface Pro UEFI update (v3.11.450.0) adds support for updated HD Graphics Family driver. HD Graphics Family driver update (v10.18.14.4029) enhances display stability and performance, improves user experience when using Miracast adapters. Improves compatibility with DisplayPort monitors and daisy chaining. Wireless Network Controller and Bluetooth driver update (v15.68.3073.151) addresses connectivity issues while Hyper-V is enabled. Adds an advanced feature to control the 2.4Ghz and 5Ghz band preference. Surface Home Button driver update (v2.0.1179.0) ensures compatibility with the Surface Hub app. Microsoft Docking Station Audio Device driver update (v1.31.35.7) improves the user experience while using the Surface Pro 3 Docking Station so that sound is available when a speaker is not connected to the docking station. Last year I blogged about automating the deployment of the Microsoft Surface Pro 3 using MDT 2013 and PowerShell, the original blogpost is here and I updated it in November with a newer version of the script here. Now that there are new drivers available, I've modified the PowerShell script to download and install them including the new MSI file. It creates the deployment share with a new name (MDTDeploy) instead of the default, you can always configure it as you wish. For those of you that don't know, this script is totally automated and builds a complete MDT 2013 deployment solution for deploying the Surface Pro 3 with all drivers included from Microsoft right up to January 2015, all you have to provide is Windows 8.1 x64 Update source files and optionally Office 365. Here's the new updated script. Setup MDT 2013 for Microsoft Surface Pro 3 - January 2015.zip This is what it looks like when running Once complete, it should look like this, scroll up to see if there are any errors in red, if so, fix them, The script will have downloaded several new drivers to your source path And those drivers are automatically imported into the Deployment Workbench. Below you can see the updated Intel HD Graphics driver is shown. and below is what you'll see when you UEFI network boot your Surface Pro 3 computers Prompted to change the name Prompted whether you want the optional Applications or not and off it goes with the automated deployment Please test this out and let me know how it went ! cheers niall

i'd suggest a call to Microsoft CSS assuming you are already on R2 CU3

look at the smsts.log on the client computer that failed, you cannot restart a failed task sequence, you have to fix the issue then start again

Here’s a quick post to let you know that I’ll be speaking at a System Center Configuration Manager event in Zurich, February 9th, for the Switzerland User Group, the details are here. There are other cool speakers like Kenny Buntinx and Tim De Keukelaere amongst others. The sessions I’ll host are shown below:- 10.15-11.15 Migrating bitlockered uefi devices Security related Settings Migrating BitLockered UEFI computers using network boot and System Center 2012 R2 Configuration Manager – See more at: http://configmgr.ch/cmce-r2/#sthash.kpvMGRkD.dpuf 14.45-15.45 Deploying Windows 8.1 x64 to the Microsoft Surface Pro 3 with Configuration Manager 2012 R2 and MDT 2013 Deploying Windows 8.1 x64 to the Microsoft Surface Pro 3 with Configuration Manager 2012 R2 and MDT 2013 – See more at: http://configmgr.ch/cmce-r2/#sthash.kpvMGRkD.dpuf 16.00-17.00 Interview about Windows Noob and the Website Behind. Interview with Niall abut his awesome Windows-noob.com website the Forum and the Guides – See more at: http://configmgr.ch/cmce-r2/#sthash.kpvMGRkD.dpuf If you are interested in the content above, and are in the area on the 9th of February then do please sign up now ! cheers niall

not mine, did you see how I added the drivers in this video ? http://channel9.msdn.com/Series/Surface-Pro-3-Deployment

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

look for the ccmsetup.log, it probably logs the error, attach it here

also, take a look at the CM12 BitLocker Frontend HTA, it has way many more things than you need in the task sequence and associated scripts, however it also deals with auto computer naming and it might be worth your while taking a look at it CM12 in a Lab - The CM12 BitLocker FrontEnd HTA

have a read of this old post, it should help you with your task in Configuration Manager at least, if you are using MDT its as easy as editing your customsettings.ini as described here.

sure thing http://www.windows-noob.com/forums/index.php?/topic/8846-how-can-i-pause-a-task-sequence-in-system-center-2012-configuration-manager/ from the index here http://www.windows-noob.com/forums/index.php?/topic/4045-system-center-2012-configuration-manager-step-by-step-guides/

are you using configuration manager or not ?

yes you can deploy as many operating systems as the version of MDT you are using will support, speaking of which, XP is no longer supported by Microsoft.

hi there, i've made the change

glad you got it sorted

simply monitor the smsts.log and review the success or failure of the step setting the variable, also check the dumpvars step, it allows you to view variables that are set in winpe. to do all this, use the pause functionality built into the task sequence

did you edit the hta/javascript backend too ? what happens when you select an ou, did you confirm that it's set before the task sequence starts

below is the updated script which now includes a function to drop the network share drive letter if not needed/used ' windows-noob.com (c) niall@windows-noob.com 2014/4/14. ' This script allows you to selectively run a hidden prestart command based on previous actions. ' In addition, it will list all DeploymentId's found in a file called DeploymentIDs.txt located on a UNC share ' see http://www.windows-noob.com/forums/index.php?/topic/4045-system-center-2012-configuration-manager-guides/ for details ' updated 2015-1-8 to add network share disconnect functionality ' Option Explicit DIM fso, WshNetwork, strUser, strPassword, clDrives, i, objFileToRead, strFileText Set fso = CreateObject("Scripting.FileSystemObject") Set WshNetwork = WScript.CreateObject("WScript.Network") strUser = "HiddenList" strPassword = "Password123" 'Map network drive WshNetwork.MapNetworkDrive "Z:", "\\192.168.1.2\hidden$", , strUser, strPassword 'Check if Devel Mode was selected If (fso.FileExists("x:\hidden.txt")) Then 'WScript.Echo("hidden.txt file exists, devel mode selected!") ' Now check to see if DeploymentIDs.txt file exists, this file is used so that we can display what deployment ID's are available in the prestart prompt If (fso.FileExists("z:\DeploymentIDs.txt")) Then 'Found the DeploymentIDs.txt file, read it's contents into a variable Set objFileToRead = CreateObject("Scripting.FileSystemObject").OpenTextFile("z:\DeploymentIDs.txt",1) strFileText = objFileToRead.ReadAll() 'InputBox ("The following hidden DeploymentID's are available. Please enter the Task Sequence Deployment ID:-" & vbCrLf & vbCrLf & strFileText) objFileToRead.Close Set objFileToRead = Nothing 'WScript.Quit() else 'msgbox "could not find DeploymentIDs.txt, please select manually" End If ' Devel mode was selected so display the Prestart prompt Dim env set env = CreateObject("Microsoft.SMS.TSEnvironment") env("SMSTSPreferredAdvertID") = InputBox ("The following hidden DeploymentID's are available." & vbCrLf & vbCrLf & strFileText & vbCrLf & vbCrLf & "Please enter the Task Sequence Deployment ID eg: P0120038 and click [OK] or click [Cancel] to continue.") 'MsgBox "The following Task Sequence Advertisement ID will be selected: " & env("SMSTSPreferredAdvertID") Disconnect() Else 'WScript.Echo("The hidden.txt File does not exist so will not change SMSTSPreferredAdvertID!") Disconnect() End If Function Disconnect() 'Disconnect ALL mapped drives Set clDrives = WshNetwork.EnumNetworkDrives For i = 0 to clDrives.Count -1 Step 2 WSHNetwork.RemoveNetworkDrive clDrives.Item(i), True, True Next End Function WScript.Quit()

based on your log above it doesnt understand the cmdlets Set-ADComputer when you run scripts in the task sequence they are running as System,. you should test manually running the script using psexec as system as described here basically psexec –s –i. http://blogs.technet.com/b/askds/archive/2008/10/22/getting-a-cmd-prompt-as-system-in-windows-vista-and-windows-server-2008.aspx http://windowsitpro.com/systems-management/psexec lastly, what you are trying to do must happen after the “Setup Windows & ConfigMgr” step, so that the computer is restarted after it is joined to the domain. The account which executes the script must have permissions in the AD to set the AD Description, Jorgen blogged about this using a vbs here

Microsoft's head of Windows Insider program, Gabriel Aul, has confirmed that Windows 10 will require a fresh install on Windows devices older than Windows 7. Revealed in a reply from his Twitter account, Aul wrote that there won't be any full upgrade paths as these will be solely available for Windows 7 and Windows 8.1 users. It makes sense given that some of them might be on older filesystems (e.g. FAT32). That's also assuming that Windows 10 will run on these systems, which although they may have enough resources (RAM/CPU) to power Microsoft's newest OS, may well run into compatibility issues with legacy components/peripherals (rather than software). Upgrade pathThat said, you can upgrade Windows XP to Windows 10 (Technical Preview) and still keep some (if not all) of your applications and settings in place. You will need to adhere to three rules (same bit and language versions) and have access to older Windows ISOs. Microsoft is set to reveal more details about Windows 10 at an event scheduled on January 21 at its campus in Redmond. There's even talk of an updated version of Office for Mobile being announced there. via Techradar > http://www.techradar.com/us/news/software/operating-systems/windows-7-and-8-1-pcs-will-get-direct-upgrade-to-windows-10-1278884?src=windows-noob.com

first tip would be what is logged in your smsts.log for the install software step, can you include that here ?

no it does a special format called a WIPE where it removes everything on the hard drive except the data you want to save (via custom XML rules), that data is then saved in a special folder (statestore) and the task sequence then installs Windows on on the wiped drive, when done it restores the files that were hard linked back to their original place here's an example custom xml file for doing just that http://www.niallbrady.com/2012/08/16/migrate-me-to-windows-8/

didn't you see this ? 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/

have you seen this yet ? 100 guides for Configuration Manager 2012 and plenty for R2 http://www.windows-noob.com/forums/index.php?/topic/4045-system-center-2012-configuration-manager-step-by-step-guides/ here's one for installing R2 itself CM12 in a Lab - How can I install System Center 2012 R2 Configuration Manager ?