Answer the question
In order to leave comments, you need to log in
Why are the PhysicalLocation values of drives different on Windows 2019 and 2022?
There are two virtual servers, on VMware. It is necessary to get the correspondence of disks in the system with VMware itself
On Windows Server 2019
returns a normal value, which corresponds to the value from VMware
On Windows Server 2022 for some reason like this
Get-PhysicalDisk | foreach {$_.PhysicalLocation}
SCSI0
PCI Slot 160 : Bus 3 : Device 0 : Function 0 : Adapter 2 : Port 0 : Target 0 : LUN 0
Answer the question
In order to leave comments, you need to log in
I'm afraid not.
https://docs.microsoft.com/en-us/previous-versions... mentions PhysicalLocation as " free-form string indicating where the hardware is located" and read-only access type, and if suddenly (namely, this and it looks like) Microsoft wanted to change its format, then there is little that can be done to counterbalance.
Didn't find what you were looking for?
Ask your questionAsk a Question
731 491 924 answers to any question