UPDATE 2018-02-12: The script below has some issues. I found better version here:https://communities.vmware.com/thread/548671
Those who have experience in VMWare know that there is no 1 to 1 match between VM’s disk number and the disk inside guest OS.
You can use this script to export disk mappings to grid or to a csv file:https://github.com/PKGeorgiev/PowerShell-VMWare/blob/master/Get-VmDiskToWindowsDiskMapping.ps1
This script is a slight modification of Conrad’s version with some improvements:
- Allow pipelining
- Use Guest’s hostname in all WMI calls instead of VM’s name (they can differ)
- Formatting and error checking
Suddenly my Chrome started to consume unusual amount of CPU:
Since I’d opened zillions of tab I wasn’t sure which web page was the suspect. In these cases you can take advantage of Chrome’s built-in task manager.
For those who still use NTFRS – as of KB823230 ntrfsutl can be used to force Sysvol replication:
ntfrsutl forcerepl DST_DC_NAME /r "domain system volume (sysvol share)" /p SRC_DC_FQDN
The replication path will be SRC_DC_FQDN > DST_DC_NAME
In fact ntfrsutl connects to DST_DC_NAME and “tells” NTFRS to pull Sysvol changes from its inbound partner SRC_DC_FQDN.