Charles, My guess is you're not using the Venue 8 Pro (5830). As stated here, it only works with x86
http://www.dell.com/support/troubleshooting/us/en/19/KCS/KcsArticles/ArticleView?c=us&l=en&s=dhs&docid=642954 On Tue, Mar 18, 2014 at 10:41 AM, Charles Moore <[email protected]>wrote: > Not sure why you were able to only boot using x86 boot image. We are > testing these in our environment and I have successfully setup an MDT image > which uses Win 8.1 using an x64 boot image. I also use a USB to Ethernet > dongle to start the image with a USB (UEFI boot image attached) to boot the > machine to and then use the usb to Ethernet dongle to see my deployment > shares. > > > > *From:* [email protected] [mailto: > [email protected]] *On Behalf Of *Keith Garner > *Sent:* Monday, March 17, 2014 3:46 PM > *To:* [email protected] > *Subject:* RE: [MDT-OSD] Dell Venue 8 Pro with MDT > > > > I have a Dell Venue 8 Pro (I love it), and was curious to see what the > procedures would be to reimage. > > > > Some notes: > > > > I had some problems booting to WinPE on the Dell Venue 8 Pro, turns out > that it was only able to boot using a *x86* MDT boot image. > > > > My working configuration included OTC Adapter <http://amzn.com/B00BFYH11Q>, > USB Hub <http://amzn.com/B004J24Y5M>, USB > Ethernet<http://amzn.com/B001NLV4TQ>, > Microsoft Keyboard, and USB Flash Drive. > > > > Use the Keyboard to enter the Device Boot Menu (press F12 after turning on > machine). > > > > As for the 4GB Fat32 Problem... You **can** use USB fixed disks, something > like Windows To Go certified devices, however they are expensive. Instead I > would recommend splitting WIM files. I have created procedures before, this > solution is similar: > http://www.osd-couture.com/2013/11/how-to-allow-mdt-2013-to-use-wim-file.html > > > > The quickest solution however, is to keep the *.wim files on the server > and download over the network. Use a USB Ethernet device with WinPE > support, and **extract** the contents of the MDT boot files > ("C:\DeploymentShare\Boot\LiteTouchPE_x86.iso" ) to a USB device that has > been marked **active** and formatted as Fat32. This is what I did above. > > > > *From:* [email protected] [ > mailto:[email protected] <[email protected]>] *On > Behalf Of *Brian Klish > *Sent:* Thursday, March 13, 2014 7:19 PM > *To:* [email protected] > *Subject:* [MDT-OSD] Dell Venue 8 Pro with MDT > > > > So I'm working through some of the challenges with imaging tablets that > have no network port. I also have no dock with a network port. I decided > to try building some media with MDT that has all the components I need. > Problem is it's uEFI only which means I need a fat32 formatted USB stick. > My image is over 4GB so it won't fit on the boot partition. I saw Michael > Niehaus make a comment at the end of his uEFI blog post saying: > > > > "There are a few solutions to that, some of which you might not > immediately think of, such as partitioning the media into FAT32 for boot > files and NTFS for everything else." > > > > Everything I've read along these lines suggests you need to have a USB > stick that shows up as a fixed disk or this won't work. Back when he wrote > that comment I don't think USB sticks like that even existed. Can anyone > confirm that is a requirement? > > > > Another option seems to be using split WIM files. From what I've read > they are not supported by Windows 8 setup though. MDT doesn't use setup > any more, but I'm guessing it's still a limitation without tweaking the > DISM logic. > > > > Even with the increase in tablets I'm not seeing a lot of information on > the net that addresses these challenges. Tips? > > ------------------------------ > > CONFIDENTIALITY NOTICE: This email message and any attachments hereto are > intended only for use by the addressee(s) named herein and may contain > information which is legally privileged, confidential and/or exempt from > disclosure under applicable law. If you are not the intended recipient, or > an authorized representative of the intended recipient, of this email > message, you are hereby notified that any review, dissemination, > distribution, copying, or use (including any reliance thereon) of this > email message, and/or any attachment hereto, is strictly prohibited. > > Although this transmission and any attachments are believed to be free of > any virus or other defect that might affect any computer system into which > it is received and opened, it is the responsibility of the recipient to > ensure that it is free from virus or other defect and no responsibility is > accepted by the sending company, its subsidiaries and affiliates, as > applicable, for any loss or damage arising in any way from its use. > > If you have received this email message in error, please immediately > notify the sender by return email and permanently delete from your system, > the original and any copies of this email and any attachments hereto and > any printout hereof. Unauthorized interception of this email is a violation > of federal criminal law. >
