PrepAway - Latest Free Exam Questions & Answers

You need to resolve the problem that causes the warning…

You have a Hyper-V host named Server1 that runs Windows Server 2016. Server1 has a virtual machine that
uses a virtual hard disK (VHD) named disk1.vhdx.
You receive the following warning message from Event Viewer: “One or more virtual hard disks have a physical
sector size that is smaller than the physical sector size of the storage on which the virtual hard disk file is
located.”
You need to resolve the problem that causes the warning message.
What should you run?

PrepAway - Latest Free Exam Questions & Answers

A.
the Mount-VHD cmdlet

B.
the Diskpart command

C.
the Set-VHD cmdlet

D.
the Set-VM cmdlet

E.
the Set-VMHost cmdlet

F.
the Set-VMProcessor cmdlet

G.
the Install-WindowsFeature cmdlet

H.
the Optimize-VHD cmdlet

Explanation:

Issue
One or more virtual hard disks have a physical sector size that is smaller than the physical sector size of the storage on which the virtual hard disk file is located.
ResolutionDo one of the following:
* Perform a storage migration to move the virtual hard disk to a new physical system
* Use a registry setting to enable a VHD-format virtual hard disk to report a physical sector size of 4k
* Use Windows PowerShell or WMI to enable a VHDX-format virtual hard disk to report a specific sector size
The Set-VHD cmdlet sets the ParentPath or PhysicalSectorSizeBytes properties of a virtual hard disk. The two properties must be set in separate operations.
The Set-VHD -PhysicalSectorSizeBytes parameter specifies the physical sector size, in bytes. Valid values are
512 and 4096. This parameter is supported only on a VHDX-format disk that is not attached when the operation is initiated.
References:
https://technet.microsoft.com/en-us/windows-server-docs/compute/hyper-v/best-practices-analyzer/avoid-usingvirtual-hard-disks-with-sector-size-less-than-size-of-physical https://technet.microsoft.com/en-us/library/hh848561.aspx

One Comment on “You need to resolve the problem that causes the warning…


Leave a Reply