Examkin

Soru

Zorluk: Çok zorOS Installation and Upgrade Methods

A systems technician is configuring an automated network deployment of Windows 11 Pro across multiple remote subnets using System Center Configuration Manager (SCCM) and a custom answer file (`unattend.xml`). The reference master image was captured from a system formatted with MBR partitioning under Legacy BIOS mode. During staging tests on new NVMe-based client hardware that enforces native UEFI mode, client machines successfully boot via PXE but fail during the Windows Setup disk configuration pass with an error stating that specified disk partitions could not be created. Which of the following actions must the technician take to resolve this deployment failure?

  1. Re-build the master reference image on a UEFI-configured system using GPT partitioning, execute `sysprep /generalize /oobe /unattend:unattend.xml`, and update the disk configuration pass in the answer file for GPT structures.Cevap
  2. B
    Add the `/audit /reboot` switches to the Sysprep command line on the existing MBR image to force automatic MBR-to-GPT disk conversion during the `specialize` configuration pass.
  3. C
    Perform an in-place OS architecture migration by injecting 32-bit legacy boot binaries into the `windowsPE` configuration pass of the existing answer file.
  4. D
    Change the target machines' OS deployment edition from Windows 11 Pro to Windows 11 Enterprise in the answer file to unlock legacy MBR disk emulation under native UEFI.

Cevap

Re-build the master reference image on a UEFI-configured system using GPT partitioning, execute `sysprep /generalize /oobe /unattend:unattend.xml`, and update the disk configuration pass in the answer file for GPT structures.
Native UEFI firmware requires the GUID Partition Table (GPT) disk format and an EFI System Partition (ESP) to boot Windows. When creating a reference image for automated network deployment, the master system must match the target architecture (UEFI/GPT). Preparing the master system with GPT partitioning, generalizing system-specific data via `sysprep /generalize /oobe`, and defining GPT partition layouts in the `unattend.xml` file allows the automated setup pass to partition target NVMe drives correctly.

Adım Adım Çözüm

1
Identify the root cause of the installation setup failure on the target hardware.
Native UEFI hardware strictly requires GUID Partition Table (GPT) partition style and 64-bit UEFI boot files, whereas the reference image was captured from a Legacy BIOS/MBR system.
An image captured from an MBR system carries disk partition layout instructions that fail when applied to target machines operating exclusively under native UEFI mode.
2
Re-configure the reference build environment.
Deploy the source OS on a reference machine initialized with UEFI mode enabled and disk formatted as GPT.
Capturing an image from a native UEFI/GPT environment ensures compatibility with modern client hardware and NVMe storage requirements.
3
Generalize the OS using Sysprep and update the unattended answer file (`unattend.xml`).
Executing `sysprep /generalize /oobe` removes system-specific identifiers (SIDs/hardware configuration), and updating `unattend.xml` ensures setup creates the required EFI system partition, MSR partition, and primary OS partition on target drives.
Proper Sysprep generalization coupled with an updated answer file enables fully automated deployment across diverse hardware on remote subnets.

Anahtar Kavram

Unattended Image Deployment Prerequisites and UEFI vs. MBR Requirements
Tahmini Süre:3m 0s
Bu soruyu puanla

Konular

OS Installation and Upgrade Methods

Bu konudan daha fazla soru