Can't Install Windows Server 2022 On HP Proliant DL380p Gen 8

Anonymous
2024-10-21T01:21:51+00:00

Hello, I Have A Physical Server Named HP Proliant DL380p Gen 8. I want to Install Windows Server 2022. I Conver Usb Bootable Media Using NTSM Method Partition Scheme MBR And I Starting Using Rufus It Works Smoothly But When I Tried To Install It, It works until Select The Disk. It Has a Warning "Your Disk Doesn't Match With NTSM Method". So I tried To Create Virtual Disk And Cleared Whole Disk (Using Shift + F10). Convert To MBR, Create Partition Primary Command. But It Doesn't work? Is there Any Cause For This One and How To Solve That?

Windows for business | Windows Server | Devices and deployment | Set up, install, or upgrade

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question. To protect privacy, user profiles for migrated questions are anonymized.

0 comments No comments
{count} votes

2 answers

Sort by: Most helpful
  1. Anonymous
    2024-10-21T12:23:07+00:00

    The error you're seeing indicates a mismatch between the boot mode and the partitioning scheme. Let’s go through the possible causes and steps to resolve the issue.

    Possible Causes

    1. UEFI vs. Legacy Boot Mode: The main reason for this issue is often related to the system's boot mode. HP Proliant servers can use either UEFI or Legacy BIOS boot modes. When using the MBR partition scheme, the system needs to boot in Legacy mode. If it's in UEFI mode, it expects a GPT partition scheme.
    2. Partition Scheme: MBR (Master Boot Record) is only compatible with Legacy BIOS boot mode, while GPT (GUID Partition Table) is required for UEFI mode.
    3. Media Creation Issues: If the USB bootable media was not created correctly with the appropriate partition scheme for the boot mode, it can lead to this type of issue.

    Step 1: Verify Boot Mode in BIOS/UEFI

    1. Restart your server and enter the BIOS/UEFI settings by pressing the required key (usually F9, F10, or Delete).
    2. Look for the option related to boot mode. You should find something like:
      • Legacy BIOS or CSM (Compatibility Support Module)
      • UEFI Boot Mode
    3. If you are using MBR, make sure the server is set to Legacy BIOS/CSM mode.
    4. If you prefer to use UEFI Boot Mode, you'll need to convert the disk to GPT instead of MBR.

    Step 2: Recreate the Bootable USB in the Correct Mode Since you're using Rufus to create the bootable USB, follow these steps to ensure the correct settings:

    1. Open Rufus.
    2. Select your Windows Server 2022 ISO file.
    3. Under Partition Scheme, set it to MBR if you're using Legacy BIOS mode or GPT if you're using UEFI mode.
    4. For Target System, choose BIOS (or UEFI-CSM) if using MBR or UEFI (non-CSM) for GPT.
    5. Click Start to create the USB bootable drive.

    Step 3: Disk Conversion and Preparation (If Needed) If your server's disk is currently in the wrong format (MBR when using UEFI or GPT when using Legacy BIOS), you will need to convert it:

    1. Boot from the USB installer.
    2. Press Shift + F10 to open the command prompt.
    3. Type the following commands to clean and convert the disk (this will erase all data on the disk):
       cmdCopy codediskpart
       list disk
       select disk 0 (replace '0' with the correct disk number)
       clean
       convert mbr (or 'convert gpt' if you're using UEFI mode)
       create partition primary
       exit
      
    4. Close the command prompt and continue with the installation process.

    Step 4: Install Windows Server 2022

    1. Proceed with the Windows Server 2022 installation.
    2. When you reach the disk selection screen, choose the partition you created.
    0 comments No comments
  2. Anonymous
    2024-10-22T02:51:49+00:00

    But When I tried With GPT It seems error like this picture. i need to reinstall whole thing into mbr to make it work and then until disk selection it kinda error related to ntsmImage

    0 comments No comments