and there are multiple lines that show shenanigans/diskpart getting confused. OP's log only shows 2 partitions at the end before diskpart exits. in the OP's last pass through diskpart, both the EFI and MSR partitions are AWOL. Here's the final diskpart scan off a recent EFI build of mine. Yes, it SEEMS to create the partitions, then it blows them away. I don't have the answer, but I do have the evidence. Just an FYI - that UEFI booting problem that it fixed is where MDT wouldn't update the boot order after installing Windows, so the computer would PXE boot a second time. Thanks all for the suggestions, and if anyone has seen this already and found a solution, please let me know. I'll have to order another 7290 and do further testing as time permits. I should have had this one out already, so I don't have nay more time to troubleshoot. ISO and manually add the needed LOB apps. Ugh.Īt this point I have to just install from an. Tried the deployment again, and I'm getting the same error. I generated a new boot image and added it to WDS. 1000 (I was really hopeful with this because the changelog stated that one bug fix was a UEFI booting problem with some hardware on 1607+ and later). I updated the ADK to 1803 (4.1), and updated MDT to. Added the "no drivers" selection profile. Added the "all drivers" selection profile to the TS. Thanks to all who offered troubleshooting assistance, your help was greatly appreciated! SysInfo confirms that BIOS mode is UEFI, and I ran DiskPart and it shows GPT, with 4 partitions: I PXE-booted the 7290, started the deploy task sequence, and FINALLY, it worked! I changed the Success codes to 0 only, and saved and updated the Deployment Share. I also selected the "Make this a boot partition" and set it to be a primary partition. I deleted all of the partitions, except for one, set it to partition 0, set it to use 100% of free space, and selected Standard (MBR) for the partition type. I didn't have any old steps to copy and paste, so I just created a new step and tweaked the parameters, until it worked. Dell says to disable both the BIOS and UEFI steps, and then copy a Format and Partition Disk step from an old task sequence and paste in your existing TS. Supposedly there's a bug in MDT that doesn't respect the disk format and partition steps in the task sequence. I found this "workaround" that Dell posted Opens a new window after my initial post about this issue. Please let me know if you need any more info. Are there any MDT experts that can shed some light as to why it's not seeing a boot drive on restart? I've attached the BDD.log and can add the ZTIDiskPart.log if needed. For more information on the command type: HELP CREATE PARTITION EFI]LOG]!> The arguments specified for this command are not valid.]LOG]!> DiskPart successfully converted the selected disk to GPT format.]LOG]!> DiskPart succeeded in cleaning the disk.]LOG]!> DiskPart successfully assigned the drive letter or mount point.]LOG]!> Volume 1 Recovery NTFS Partition 5508 MB Healthy Hidden ]LOG]!> Volume 0 C Windows NTFS Partition 471 GB Healthy ]LOG]!> Volume # Ltr Label Fs Type Size Status Info]LOG]!> Text DiskPart has finished scanning your configuration.]LOG]!>
0 Comments
Leave a Reply. |