anyweb

ok you must have made some error in the script, please re-download it, and retest it after changing only the ip addresses

that line must run otherwise the network will never initialize and neither will winpe. I've tested this over and over and it works great, so something is up on your end, if have access to virtual machines to test this and have teamviewer i can take a look.

I haev not tested it with SCCM 2007, please do and report back how it goes

well you can simply change the boot image referenced in the task sequence to quickly switch between boot wims, i'd definetly be interested in seeing your smsts.logs

you really should be creating reference images on virtual hardware and use apply driver package steps to customize a deploy task sequence to custom hardware, can you attach your bdd.log and smts.log ?

hi this guide is not supposed to assist you with lack of network drivers AFTER you start a task sequence, but before you start one, and your issue sounds like the latter, do please attach your smsts.log files here so we can figure out why

from your error message "Failed to load class properties and qualifiers for class BDD_UsePackage in task sequence.": that's complaining about the lack of MDT Integration. This integration gives a lot more abilities that you think and it all collectively helps the task sequence mentioned above into a reality, (via the scripts etc), try it and see.

x86 boot wim can deploy both x86 images and x64 operating system images except when it's UEFI and in that case the boot image must match the architecture of the device, surface pro 2/3 devices are UEFI and must have a 64bit UEFI boot image, so you can either move all your task sequences to a 64 bit boot wim and keep the x86 boot wim task sequences as exceptions with their own collection, or target only unknown x86 devices with that deployment, or use boot media for those devices.

can you press f8 and grab the bdd.log or smsts.log ?

sorry, if still in the litetouch wizard look in x:\minint\smsosd\osdlogs does bdd.log reveal anything ? if after that look in x:\windows\temp\smstslog\smsts.log

well it should work just fine (it does here and we are using it in production) where exactly are you see the 5 minute delay, can you video it so i can see ?

by the way the VEN_11AB&DEV_2B38 refers to the marvell wireless, so not an issue here

go back and look at the powershell, are there ANY errors when it created the boot wim or installed/configured WDS, if so, you'll have to fix those problems, for example, verify if the correct litetouch boot wim is in place in wds and that it has the drivers in it.... i'm happy to do a teamviewer session and take a look if you want

well you should be changing the serverstoping ip addresses, did you ? can you show me that edit ?

well rem out the 'hide the cmd prompt' so that you can see what is going on, did you make any changes at all in the script ?

did you modify the wscript.sleep statement at all, it should only wait a maximum of 15 seconds.

Microsoft have released a new build for Windows 10 TP, this one has Spartan enabled. Here are some issues we fixed in this build We’ve fixed the issue from Build 10041 for when the Photos app on your PC crashes when you tap on the circular icon (your camera roll – thanks Rafael) at the top left to view the photo you just took. We’ve also fixed the issue from Build 10041 where you might end up in a state where windows open on your desktop are accidentally visible behind the Start Screen, Task View, Snap Assist, and when rearranging windows in Tablet Mode. You will no longer get stuck when you manually lock your PC (Windows Key + L) during the initial out-of-box experience. Here are some known issues for this build After logging in, you may see a blue screen instead of your desktop. To work around this issue, lock your PC (with the hardware button or by pressing the Windows Key + L) and try logging in again. You can also try Ctrl + Shift + Esc to open Task Manager. Indexing of new email in Outlook is not working, so search results will be limited to when the last index was built. If you have Virtual Machines hosted in Hyper-V on your PC running Windows 10, you will want to move to the Slow ring and wait for the next build as this build breaks the ability to run VMs. There are 2 issues using Visual Studio 2015 preview on this build: The emulators will not boot and you won’t be able to deploy a Windows Universal app to the Mobile emulator. The XAML designer in VS and Blend will crash when opened. If you are a developer using these tools today to develop Windows Universal apps and need this functionality to work – we recommend switching to the Slow ring until we release a patch to fix these issues. This build is pretty much all about Project Spartan, so we hope you enjoy getting your hands on it for the first time. As with all other new features we’ve introduced, we have a ton of work left to do with Spartan so expect to see some bugs and rough edges in this first preview. As always, we look forward to hearing your feedback via the Windows Feedback App. via > http://blogs.windows.com/bloggingwindows/2015/03/30/windows-10-technical-preview-build-10049-now-available/

verify if you have a connection to the deployment share in winpe, if not something went wrong with the driver injection into the boot wim, check the powershell logs in ISE, scroll back and look for any red errors thanks !

press F8 and open a cmd prompt, look for the smsts.log file what does it reveal, most likely you have no correctly defined the deployment share connection credentials and it's rebooting as a result, or you have no network...

do you have mdt 2013 integrated ?

did either of you try restarting the windows deployment service ? do any other computers successfully UEFI network boot ? what does the smspxe.log file reveal ?

I just checked my lab and that's the way it appears

Microsoft have released the ISOs for build 10041. You can also download the ISO files for a clean installation of the operating system or if you want to do an upgrade, you can download them directly using the links below: Download ISO file for Windows 10 build 10041 64-bit (English) Download ISO file for Windows 10 build 10041 32-bit (English) Download all ISO files in all the languages and platforms available here cheers niall

i guess it depends on how you set your nic up, have you allowed it to be shared with the operating system ?

the task sequence below backs up data just fine to mapped shares CM12 in a Lab - The CM12 UEFI BitLocker FrontEnd HTA - Part 2. Installation CM12 in a Lab - The CM12 UEFI BitLocker Frontend HTA - Part 1. The features.