Jump to content




trevmac77

New Members
  • Content Count

    2
  • Joined

  • Last visited

Community Reputation

0 Neutral

About trevmac77

  • Rank
    Newbie
  1. Hi all, I have an unusual problem in that my employer is purchasing old Supermicro blade servers. They don't support SAS and as such I'm using large SATA drives and I'm pretty sure these are BIOS only as I didn't see anything in BIOS setup that looked like I could enable a UEFI boot mode (they are over 7 years old and cheap.) Currently, I've run down to 3TB and above and my 2016 installations are failing as SCCM is forcing initialization to GPT to use the 3TB capacity. I need these to be MBR and 2TB for Windows to successfully be deployed. The trouble is, I can't locate where the diskpart.exe and diskpartscript.txt are being run during the installation. I'm guessing it's buried in a VBS script in the OSDDiskpart step but I haven't acquired the skills yet to get down to the granular level of tweaking. So far I've tried enabling: Set Diskpart BIOS compatibility in both locations where it's greyed out. Disabling all three Format and Partition Disk (UEFI) and tried flipping the Disk Type drop-down option in each UEFI format step to MBR from GPT, but for some reason that didn't work. but the disk still gets initialized to GPT. If I knew where the initialization step was taking place I could just add a WMI query that ignores Supermicro X8DTT-H or something similar. Another possible solution would be to insert my own Diskpart script that converts it back to MBR right before it's failing. Here's part of my log: And here are the details of what's happening in Stdout: Diskpart.exe STDOUT: Microsoft DiskPart version 10.0.14393.0 Copyright (C) 1999-2013 Microsoft Corporation. On computer: MININT-7SO7UHO Volume ### Ltr Label Fs Type Size Status Info ---------- --- ----------- ----- ---------- ------- --------- -------- Volume 0 C NTFS Partition 2047 GB Healthy Disk 0 is now the selected disk. DiskPart succeeded in cleaning the disk. Disk is uninitialized, initializing it to GPT. DiskPart succeeded in creating the specified partition. DiskPart successfully assigned the drive letter or mount point. The selected disk is not a fixed MBR disk. The ACTIVE command can only be used on fixed MBR disks. Thanks for any help! I'm just finding that the MDT task schedule is a bit blackboxed and I can't seem to find where this lives.
  2. Hi, I've set up some task sequences which work great, however in our environment we have many servers that are attached to storage with Emulex HBAs, or LSIs. How do I ensure that I can target the volumes on my internal RAID card so that C is actually on the drive I want, ie volume 0 is volume 0 on my H700 RAID, not a 4TB drive on my Super Micro Array. Currently I just unplug external connectors so the volumes won't be seen during installation and then just plug them back in which works but isn't very elegant and there are times I would like to re-image a machine remotely using IPMI. My google searches aren't turning up much other than creating a user driven Task Sequence, but I like to just walk away after it kicks off. Is there a way to force WinPE to organize my volumes the way I want so that the first volume on my RAID card is drive 0? Also this is potentially catastrophic as I sometimes re-image production nodes in an existing cluster and this would result in the loss of important data. Interesting that I have to install the drivers for the emulex HBA before windows can see the volumes after server 2016 is installed, but apparently the WinPE image supplies the drivers which I never added to the MDT Boot image which surprised me. Thanks in advance for any help!
×