MDT 2013 + create 5 recommended UEFI/GPT drive partitions

Hi
My end goal is to deploy a custom x86 image to a UEFI device (tablet) using a USB stick. It is likely that my .wim file will be >4GB, but for now, I'm just trying to get the process working with a standard OEM <4GB .wim file.
As per this post, I have performed steps under sections 5.1, 5.2 and 5.3 MANUALLY, by booting the tablet using a WINPE 5.0 USB and running
1) diskpart /s E:\CreatePartitions.txt 
and
2) E:\ApplyImage E:\Images\ThinImage.wim
Q: Above worked perfectly and it's exactly what I'm looking for.  How do I incorporate 1) + 2) into MDT, or do I simply attempt to replicate the code from 1) + 2) under "Format and Partition Disk" under PreInstall\New
Computer only step?
Any advice or pointers would be really appreciated.
Many thanks in advance.

Recovery images, that's a different story.
First option is to increase the size of the System partition to the desired size:
BdeDriveSize=5000
Otherwise, the best solution I've seen is to build the standard MDT partition configuration using the default MDT "Format and Partition" step. and *THEN* shrink the partition to the desired size. Yes Shrink.
The other option is to increase the size of partition 1 from
See Mike's post on WimBoot for the example script LTIApplyWim.wsf script that shows how shrinking works.
http://blogs.technet.com/b/mniehaus/archive/2014/04/13/experimenting-with-wimboot-using-mdt-2013.aspx
Keith Garner - Principal Consultant [owner] -
http://DeploymentLive.com

Similar Messages

  • Is it possible to bitlocker-encypt a UEFI/GPT drive from which I boot with Windows 7 64-bit ultimate (TPM-motherboard)?

    Is it possible to bitlocker-encypt a UEFI/GPT drive from which I boot with Windows 7 64-bit ultimate (TPM-motherboard)?

    Sure. BL does support GPT.

  • MDT 2013 - Create New User

    Hello,
    I've recently setup MDT 2013 to deploy some customized images that we deploy to student laptops, that were sysprep-ed and captured with ImageX.  I've uploaded the custom image WIM files to MDT, and setup a task sequence.  Almost everything works,
    thanks to Microsoft documentation and searches of this forum for various questions I've had, however I'm stuck on two items:
    1.) MDT forces an administrator account to be created during the process.  That's not such a huge issue, but I'd like to disable the administrator account at the end of the task sequence.  I'm not sure where/what to add to do this.
    2.) We would like the machine, after imaging, to deploy the generic Windows Welcome, as if it had just been purchased from the OEM.  This way when the student receives the imaged laptop, they can create their own personal account.  These laptops are
    not bound to AD.  Right now, when the task sequence finishes the systems are logged in as an administrator.  Again, I'm not sure what code to add to the task sequence (and where) to accomplish this.
    Any information or links on what I'm looking for would be greatly appreciated.  I'm sure that both these items are possible, but I'm not using the proper terminology on my searches to find the information I'm looking for.  Thanks!

    I question the usage of MDT in this scenario. I also question your premise that your users should go into OOBE Setup.
    MDT is designed to assist IT departments in getting windows up on machines in a End to End scenario.
    MDT prompts which Task Sequence, Language/Locale/TImezone, Applications, drivers, and User Data Migration Status. Once the TAsk Sequence has started, MDT should be as automated as possible. No prompts, no user interaction.
    What you are asking for is the opposite, you want user interaction during deployment, and rather than customizing each deployment, the image is pre-configured. (Unless you have different *types* of machines that require driver loading via MDT).
    IN your case I would recommend just slapping an install.Wim up on a WDS server, and custom crafting an unattend.xml file to prompt each user for user accounts. (as long as you don't have to worry about drivers).
    The other solution is to prompt the user for their new user account from the MDT wizard, and slam that into the machine during the task sequence (and removal of the Administrator account with net user administrator /active:no )
    I actually created a powershell script to accomplish this:
    http://keithga.wordpress.com/2013/09/24/microsoft-account-automation-in-windows-8/
    This alternative solution is MDT 400 level work. Scripting required. :^(
    Keith Garner - Principal Consultant [owner] -
    http://DeploymentLive.com

  • How do I create a bootable hard drive partition?

    Hello,
    Would someone out there be kind enough to give me step by step instructions for creating a partition on my external hard drive that I could use to boot my computer in the event of an emergency? I understand how to use Backup for my files, but I want to know how to make the hard drive bootable, as well.
    Thanks!
    Eli Garfinkel

    When you say step by step I'm guessing you're saying you are a little inexpierenced so I'm going to give it to you very thoroughly.
    First: If you are not using this external HD for anything else then there is no need to partition and you should skip to "Making Bootable Clone"
    "Making the Partition":
    1) Plug in the external HD.
    2) Launch Disk Utility
    3) Click on the ext. HD in the left hand column
    4) Click on the Partitions tab.
    5) Create the number of partitions by clicking the dropped down menu under "Volume Scheme"
    5a) The partition that will be the bootable one should be as big as the internal HD.
    6) Format it as Mac OS X Extended (Journaled)
    7) Check the Mac OS 9 Drivers...just in case.
    8) Click the Partition button in the bottom right and let DU do its work.
    "Making Bootable Clone"
    -I highly recommend you buy the $27.95 copy a SuperDuper! (shirtpocket.com)
    -It will allow for easy incremental backups, which can be done each day, that will keep you up-to-date.
    1) Once you've downloaded SuperDuper! & have the disk partitioned open SuperDuper!
    2) In the "Copy" box select your internal HD.
    3) In the "to" box select the partition.
    4) Make sure "using" says "backup-all files"
    5) Select "Options" button and under the "During Copy" make chose the first option. This erases the partition and then copies the internal onto the external.
    -After this is completed you can continue to do this, daily. The only difference is you'll have to change the "During Copy" in the "Options" button to the second option. This is the "Smart Update".
    -A Smart Update will delete or create files on the ext. HD so it mirrors the internal. The results is the ext. HD is exactly like the internal and it only takes 10-15min. You ext. HD will always be up to date then. You can run this every night.
    -This will result in an exact clone and you can boot form this partition if you ever need to.

  • SOLVED!!! - MDT 2013/Windows 8.1 Sysprep & Capture Fails

    I'm running a basic Client Task Sequence that installs the OS, installs a few applications/drivers and then should Sysprep and Capture the image.  Everything works fine until after the Sysprep.  The machine reboots but does not reboot into the
    PE environment.  Instead it reboots to the local disc and the machine runs the initial OOBE setup.
    My BDD.log file can be found @ 
    https://dl.dropboxusercontent.com/u/14521312/BDD.log
    I see what look like some BCDEdit errors being returned but I'm not sure what they mean.
    If anyone can help I would greatly appreciate it.  I have to get 30 machines out yesterday.
    EDIT:  REPLACED BDD.LOG

    Lets try a disk format first.. I still use the old Win98 fdisk utility :)
    Wipe all drives clean and then re-run it...
    I will do that but is that not already happening at this stage of the Task Sequence?
    Free Drive Letter(s): D: E: F: G: H: I: J: K: L: N: O: P: Q: R: T: U: V: W:
    ZTIDiskpart 8/7/2014 8:13:16 AM
    0 (0x0000)
    New ZTIDisk : \\MININT-DPLVH5K\root\cimv2:Win32_DiskDrive.DeviceID="\\\\.\\PHYSICALDRIVE0"
    ZTIDiskpart 8/7/2014 8:13:16 AM
    0 (0x0000)
    Found Disk Index: 0   size: 128034708480
    ZTIDiskpart 8/7/2014 8:13:16 AM
    0 (0x0000)
    Disk Index: 0   size: 128 GB ZTIDiskpart
    8/7/2014 8:13:16 AM 0 (0x0000)
    This is an EFI machine, therefore we will need a Boot Partition.
    ZTIDiskpart 8/7/2014 8:13:16 AM
    0 (0x0000)
    bCreateBootPartition = True ZTIDiskpart
    8/7/2014 8:13:16 AM 0 (0x0000)
    Configuring Disk Alignment ZTIDiskpart
    8/7/2014 8:13:16 AM 0 (0x0000)
    No Disk Alignment variables specified, alignment not updated.
    ZTIDiskpart 8/7/2014 8:13:16 AM
    0 (0x0000)
    About to run command: Diskpart.exe ZTIDiskpart
    8/7/2014 8:13:16 AM 0 (0x0000)
    Command has been started (process ID 1480) ZTIDiskpart
    8/7/2014 8:13:16 AM 0 (0x0000)
      Console + RESCAN ZTIDiskpart
    8/7/2014 8:13:16 AM 0 (0x0000)
      Console + LIST DISK ZTIDiskpart
    8/7/2014 8:13:16 AM 0 (0x0000)
      Console + LIST VOLUME ZTIDiskpart
    8/7/2014 8:13:16 AM 0 (0x0000)
      Console + REM Move Drive C: to a diffrent drive letter.
    ZTIDiskpart 8/7/2014 8:13:16 AM
    0 (0x0000)
      Console + Select volume C: ZTIDiskpart
    8/7/2014 8:13:16 AM 0 (0x0000)
      Console + Assign Letter=W: ZTIDiskpart
    8/7/2014 8:13:16 AM 0 (0x0000)
      Console + SELECT DISK 0 ZTIDiskpart
    8/7/2014 8:13:16 AM 0 (0x0000)
      Console + CLEAN ZTIDiskpart
    8/7/2014 8:13:16 AM 0 (0x0000)
      Console + CONVERT GPT NOERR ZTIDiskpart
    8/7/2014 8:13:16 AM 0 (0x0000)
    Create an uEFI/GPT Boot Partition set. V: ZTIDiskpart
    8/7/2014 8:13:16 AM 0 (0x0000)
      Console + CREATE PARTITION PRIMARY Size=300
    ZTIDiskpart 8/7/2014 8:13:16 AM
    0 (0x0000)
      Console + FORMAT QUICK FS=NTFS LABEL="Windows RE tools"
    ZTIDiskpart 8/7/2014 8:13:16 AM
    0 (0x0000)
      Console + ASSIGN LETTER=U ZTIDiskpart
    8/7/2014 8:13:16 AM 0 (0x0000)
      Console + set id="de94bba4-06d1-4d40-a16a-bfd50179d6ac"
    ZTIDiskpart 8/7/2014 8:13:16 AM
    0 (0x0000)
      Console + gpt attributes=0x8000000000000001
    ZTIDiskpart 8/7/2014 8:13:16 AM
    0 (0x0000)
      Console + DETAIL PARTITION ZTIDiskpart
    8/7/2014 8:13:16 AM 0 (0x0000)
      Console + DETAIL VOLUME ZTIDiskpart
    8/7/2014 8:13:16 AM 0 (0x0000)
      Console + CREATE PARTITION EFI Size=499
    ZTIDiskpart 8/7/2014 8:13:16 AM
    0 (0x0000)
      Console + FORMAT QUICK FS=Fat32 LABEL="System"
    ZTIDiskpart 8/7/2014 8:13:16 AM
    0 (0x0000)
      Console + ASSIGN LETTER=V ZTIDiskpart
    8/7/2014 8:13:16 AM 0 (0x0000)
      Console + DETAIL PARTITION ZTIDiskpart
    8/7/2014 8:13:16 AM 0 (0x0000)
      Console + DETAIL VOLUME ZTIDiskpart
    8/7/2014 8:13:16 AM 0 (0x0000)
      Console + CREATE PARTITION MSR SIZE=128
    ZTIDiskpart 8/7/2014 8:13:16 AM
    0 (0x0000)
      Console + DETAIL PARTITION ZTIDiskpart
    8/7/2014 8:13:16 AM 0 (0x0000)
      Console + DETAIL VOLUME ZTIDiskpart
    8/7/2014 8:13:16 AM 0 (0x0000)
      Console + REM -------------- ZTIDiskpart
    8/7/2014 8:13:16 AM 0 (0x0000)
      Console + REM Partition 0 ZTIDiskpart
    8/7/2014 8:13:16 AM 0 (0x0000)
       Partition(0): 100 % ZTIDiskpart
    8/7/2014 8:13:16 AM 0 (0x0000)
    Size is Empty: Expand to remaining space. ZTIDiskpart
    8/7/2014 8:13:16 AM 0 (0x0000)
       Size:  [ isEmpty = True] ZTIDiskpart
    8/7/2014 8:13:16 AM 0 (0x0000)
      Console + Create Partition Primary ZTIDiskpart
    8/7/2014 8:13:16 AM 0 (0x0000)
    Do not mark a 2nd partition active. ZTIDiskpart
    8/7/2014 8:13:16 AM 0 (0x0000)
      Console + Assign letter=C: ZTIDiskpart
    8/7/2014 8:13:16 AM 0 (0x0000)
    Property OSDisk is now = C: ZTIDiskpart
    8/7/2014 8:13:16 AM 0 (0x0000)
      Console + FORMAT QUICK FS=NTFS LABEL="OSDisk"
    ZTIDiskpart 8/7/2014 8:13:16 AM
    0 (0x0000)
      Console + DETAIL VOLUME ZTIDiskpart
    8/7/2014 8:13:16 AM 0 (0x0000)
      Console + DETAIL PARTITION ZTIDiskpart
    8/7/2014 8:13:16 AM 0 (0x0000)
      Console + LIST PARTITION ZTIDiskpart
    8/7/2014 8:13:16 AM 0 (0x0000)
      Console + LIST VOLUME ZTIDiskpart
    8/7/2014 8:13:16 AM 0 (0x0000)
      Console + EXIT ZTIDiskpart
    8/7/2014 8:13:16 AM 0 (0x0000)

  • Keep extra partition on deployment with MDT 2013

    hello all,
    I am using MDT 2013 to make the
    deployment of some workstations in the company,
    however they all have an extra
    partition (D: \),
    doing some testing I noticed that the
    MDT does clean the entire
    disk, not just on the C:\ drive.
    Is it possible to get the MDT format
    just drive the system keeping
    the extra drive (D:\)?
    Thank you.
    Eduardo Sena | Microsoft Certified Professional | Embaixador Windows 8 | MVP Windows-Expert IT Pro | [email protected] Blog - www.eduardosena.com.br

    if you are just replacing the OS, then I recommend the "Refresh" scenario. Refresh will take an existing Machine and refresh it to a new OS version, persisting the existing partition configuration.
    Keith Garner - Principal Consultant [owner] -
    http://DeploymentLive.com

  • Eufi partition on MDT 2013

    I am using LT for deploying Windows desktop with MDT 2013. What I would like to do is to be able to customize the partition layout for any eufi capable system. I know how to create a diskpart script to do the job. If I am going to create a custom Task sequence
    for the eufi layout, how does MDT handle the situation if the system is not uefi capable\enabled?
    Thanks

    Hi,
    You can create an answer file to customize disk configuration.
    DiskConfiguration
    http://technet.microsoft.com/en-us/library/ff715671.aspx
    The unattended file is applied to both BIOS-Based and UEFI-based computers. If you don’t want the configuration applied, you have to remove the file.
    In addition, answer file should be placed to the right place.
    Methods for Running Windows Setup
    http://technet.microsoft.com/en-us/library/cc749415(v=ws.10).aspx
    Please notice “Implicit Answer File Search Order”.
    Hope this helps.

  • Surface Pro Driver injection no longer working under MDT 2013

    Since upgrading to MDT 2013 we are experiencing an issue with deploying Windows 8.1 to our Surface Pros. The deployment seems to be ignoring driver group settings in CS.ini and it basically injects no drivers. We are following the guide Microsoft posed here:
    http://www.microsoft.com/en-us/download/details.aspx?id=38826
    So I'm confused as to where we are going wrong. Here is the section in question from CS.ini:
    [ByModel]
    Subsection=Model-%Model%
    [Model-Surface with Windows 8 Pro]
    OSDComputerName=TAB%SerialNumber%
    DriverGroup001="Windows 8.1 x64\Microsoft\Surface Pro"
    DriverSelectionProfile=Nothing
    XResolution=1920
    YResolution=1080
    Incidentally the computer name is getting set so i know this block is working. Any idea why the drivers would get skipped over?

    I've been deploying to Surface tablets just fine and deployed to a Surface 3 just a couple days ago without any issues, but I do follow Johan's "Total control" way of managing drivers. http://www.deploymentresearch.com/Research/tabid/62/EntryId/112/MDT-2013-Lite-Touch-Driver-Management.aspx
    I'd recommend you go that way as well as you'll most likely have fewer issues. Depending on your situation you may also want to make use of the "ModelAliasExit" script and use Make variables or you can just follow the method above exactly as is.
    If this post is helpful please vote it as Helpful or click Mark for answer.

  • MDT 2013 Fails to Format or Partition disk on Surface Pro 3

    I have been trying to image a Surface Pro 3 using MDT 2013 and have been unable to get past the Format and Partition portion of the deployment.  At first I would get an error that it was unable to format or partition the drive and then after that it
    just reboots after trying for so long.  I am able to image any other device with the same task sequence and have no issue just having an issue with the Surface Pro 3.  Any help would be great.
    Thanks in advance.
    I am getting the error FAILURE (5210)
    ZTI Error - Unhandled error returned by ZTIDISKPART: Object required (424)

    I think our problem is also hardware failure although without re-imaging a working surface pro 3 I can't be sure.
    I tried what imfusio suggested in this thread.
    https://social.technet.microsoft.com/Forums/en-US/d31384bc-4e96-4a5b-a400-637bd6006d81/failure-5456-unable-to-determine-destination-disk-partition-and-or-drive-surface-pro-3?forum=mdt
    Unfortunately the deployment failed with the same ZTI Error - Unhandled error returned by ZTIDISKPART:
    Object required (424)
    I then rebooted into WinPE and ran diskpart, I could see the two volumes (EFI and OSDisk). I then tried to format the OS disk volume using diskpart. I got a paramater is incorrect error and the disk was no longer visible with a 'list disk' command. So it's
    like the format is putting the disk offline. I'm going to try restore one of these surfaces, apply all firmware updates then re-image. If that doesn't work I'm out of ideas.

  • HP EliteBook 820 G2 - Network Driver - MDT 2013

    Hi We have one of the new HP EliteBook 820 G2. When trying to boot from WDS/MDT 2013 into WIN PE it is saying that it cannot connect to the deployment share. because PCI\VEN_8086&DEV_15A2&SUBSYS_225A103C&REV_03 - did not have a driver installed. I downloaded the driver pack from http://ftp.hp.com/pub/capssoftpaq/cmit/HP_Driverpack_Matrix_x64.html I imported the network drives into WDS and imported all Drivers from driverpack into MDT. However I am still getting this error. Googling the device returns no results. Can anyone advise?
    Thanks 

    I think its the middle one. In my environment i have used a drivergroup selection type of installation that will inject the drivers using the computer csproduct name. If your environment doesn't have this then i don't know how you would make it work. In theory it should still pick up the drivers if you are using the "chaos" type of driver selection ie every model fetch the drivers from the same driver folder. Also make sure you do regenerate the WinPE image and then move it over from your deploymentshare to your WDS service. This is crucial because in most environments the location where the new PE image is created is not the same where WDS images are stored. Also remember to put the Windows Deployment Services-service down from services.msc and bring it back up before trying. Use a different file name (or a different background on the deployment as i did) to make sure that the PXE download is in fact updated. I can confirm that this driver package also works on EliteBook 840 G2 although the deployment summary gives me errors connecting to the deploymentshare due to the installation of this driver taking considerably long. I attached a screenshot of my network drivers in WinPE that do work. Importing these to the individual computer model folders below is also required in my environment. This may be different in yours.

  • Install Arch on USB flash drive (partitioning and UEFI)?

    I am trying to install Arch on a USB flash drive. However I have few questions... in particular about pratitioning and UEFI.
    What partition table should I use? dos or gpt? and from this... what partitioning tool should I use? (cfdisk, parted, gdisk... etc)?
    Also... I am going to be using this USB flash drive with a new computer that has a UEFI BIOS. Should I do anything different because of this? (Have a different boot flag?)

    I think you need to read up on UEFI.  Depending on what partitioner you use the boot flag can mean something entirely different. 
    MBR(dos) or GPT is a personal preference, so asking that is like asking someone else what your favorite soap should be.  There is one exception though.  I have heard of some systems that have firmware bugs that won't allow GPT/bios and some that won't allow MBR/UEFI.  There are also some machines that won't do a damn thing if they aren't MBR partitioned, but those all tend to not be UEFI.
    As far as the tool to use, if you want to use GPT then use gdisk and friends, of you want to use MBR(dos) use fdisk and friends.  Or you can learn how to use parted, which can apparently handle both.  But, for example gdisk offers a number of different tools that can all achieve the same thing.  Again, it is like asking someone else if you should prefer boxers or briefs...

  • How to create drive partition in window 8.1

    i have number of doubt on partition of disk management. i have new dell laptop, little difficult to using the same and i want to partition of the c disk and want to create d disk, but i unable to perform the same.
    when i click to the shrink volume and want to shrink the same, but a error flash out (there is no space on the disk to comple this operation).
    i had understand the same and when i'm going to delete the extra partition called health, EFI system, health recovery partition. the option of the delete volume is not available. 
    please give me some idea for doing partition to save the data, video and picture. if there an alternative option to save the same, please share it to me.

    Shrinking or using any other third party tools to create partition from C is not suggested. It usually results in complete installation of Windows, with files being lost forever.
    As a workaround, you can either create and mount a VHD/VHDx or map a folder inside the C drive (in C:\) as a separate drive. This will look like a separate drive and the steps are quite easy compared to creating a new physical partition. The following links
    will be helpful:
    http://www.howtogeek.com/howto/windows-vista/map-a-drive-letter-to-a-folder-the-easy-way-in-windows/
    http://www.wikihow.com/Create-a-Virtual-Hard-Drive-in-Windows-8
    Balaji Kundalam

  • Is it not recommended to use a partitioned external hard drive for time machine?

    1. i hv a 1 tb seagate  back up plus hard disc ..,,i want to make partitions for  using it for time machine, mac, and window repectively . is it not recommended to use a partitioned drive for time machine? some where i have red that time machine wont be able to restore data from external partioned hard drive  in case internal hard drive crashes.
    2. if i use the seagate back up plus 1tb for mac only and use time machine to take backup (roughly 250 GB) , then the rest space i cant use to transfer movies, pictures from a PC
    3. how should i best use the seagate back up plus hard drive (not seagate back up plus for mac) in a way that i use it for back up , and to work with both mac and PC?

    I use a partitioned external drive for Time Machine as well as other things.
    How you partition it is a function of yoru needs.
    Barry

  • Creating Windows 8.1 master image with MDT 2013,cannot capture .WIM

    I am having an issue with creating a master image with Windows 8.1 and MDT 2013.  
    I have followed extensive tutorials on how to create a master image using Microsoft Deployment Toolkit. my goal is to have a fully configured windows 8.1 image which I can deploy through Windows Deployment Services. I have been relatively successful thus far,
    except for one issue I have run into, which is successfully capturing this image as a .WIM.
    I have successfully created a task sequence and the task sequence is able to run all the way through until the final step. Essentially the task sequence is supposed to install Windows and Office, then suspend the task sequence to allow me to make customisations
    to the start screen and desktop background, and I simply click resume task sequence, and the task sequence should sysprep reboot and capture the machine image as a .WIM file.
    the task sequence is able to sysprep the machine, but upon rebooting it boots into out of box experience, and does not create a wim file. I receive an error saying: "cannot find script file C:\ltibootstrap.Vbs" after the machine completes OOBE 
    I am using Windows Server 2012 r2, creating my Master machine image using hyper-v, and my master image is running Windows 8.1.
    Any help would be greatly appreciated.

    I'm not sure about the sequence of steps here. Try taking your captured.wim file and deploying it using MDT again, or at least to another machine. MDT sometimes leaves extra files around on the captured machine, so simply rebooting it may not get a accurate
    test results.
    IF you are getting the ltibootstrap.vbs it is most likely because there is a stray unattend.xml file somewhere in your image that is looking for this file. Crack open your Wim file and search for any unattend.xml files.
    Keith Garner - Principal Consultant [owner] -
    http://DeploymentLive.com

  • HP Client WinPE Driver Packs and MDT 2013

    Just today I noticed that HP had a couple of WinPE driver Packs for download on their site for WinPE 3.0 and 4.0. I'm using MDT 2013 to deploy Win 7 x64 for now, perhaps Win 8.1 out in the future. What version of WinPE does MDT make for Boot Images? Which
    driver pack would be best for MDT 2013 and Win 7 deployment? WinPE 3.0?
    Orange County District Attorney

    Just found my answer in a great post at
    http://www.deploymentresearch.com/Research/tabid/62/EntryId/112/MDT-2013-Lite-Touch-Driver-Management.aspx
    Just in time!
    Orange County District Attorney

Maybe you are looking for