Extend Raw Device Mapping Disk – virtual compatibility mode on VMware

You can follow the below procedure to extend an RDM disk with virtual compatibility mode on VMware. As described in the article attached on the bottom, you can accomplish that either by migrating the RDM or by shutting down the VM and performing the procedure below. The article implements the shut down way.

The first step is to extend the RDM disk from storage. Find the UUID descriptor and provide some additional space.

Then you need to locate the VMware disk that you want to extend and record the SCSI controller and SCSI ID because it is needed on a later stage.

on my case SCSI target is 8

Then you should delete the disk from virtual machine. You can also select (delete files from datastore) as only the RDM pointer will be deleted and not the actual disk data.

After that you should rescan storage devices and volumes on the ESXi host and locate if the device has identified the new capacity.

in my case the new storage capacity is 150G

Then edit virtual machine settings and select add new device that will be of type RDM Disk

The next dialog shows the new disk with the extended capacity.

Click OK and be careful in order to add the same SCSI ID and controller as previously.

Perform a rescan inside the Operating system and the capacity will be available for use

https://kb.vmware.com/s/article/1007021

Remove Windows recovery partition to extend drive

There is a common issue on Windows to have a disk blocked from Windows recovery partition. In that way, if you extend the physical disk (virtual environments) you cannot extend from Operating system side.

Windows Recovery partition blocking C:\ to be extended

A recovery partition is a partition on the disk that helps to restore the factory settings of the OS (operating system) if there is some kind of system failure. This partition has no drive letter, and you can use only Help in Disk Management. In my case I did not need this partition and I was able to delete it with the below steps:

select disk 0 select volume 3 (3 was the id of my recovery partition)
select recovery partition in order to delete from diskpart
delete volume ovveride

After those steps you will be able to extend your disk.

Disk Conversion Hyper-V vhd to vhdx – Cannot attach new disk on Virtual machine

Hyper-V includes a tool that can convert vhd disks to vhdx which is the newer version and should be used on production environments.

Sometimes the below error can occur which prevents one from attaching the new disk (vhdx) to the virtual machine needed. It seems as the new disk after the conversion to be locked and only by rebooting host the disk can be attached.

The process cannot access the file because it is being used by another process

This issue happens because the original disk is attached on the virtual machine during the conversion. The disk device should be attached as stated from Microsoft (link below). After the conversion the new disk can be attached and will not be locked from the host.

https://docs.microsoft.com/en-us/powershell/module/hyper-v/convert-vhd?view=win10-ps

Map Network drive location on Windows Server

The easiest way to perform massive identical installations on web servers that are located on the same network (VLAN) is through a network map of the remote location. With only two steps you can perform remote installations.

Firstly select map a network drive and assign a drive letter to the remote location.

Select map network drive

Select your preferred drive letter.

Map your network location server to a Drive letter
Open a terminal and just go to the specified location. In my case it was Z:

change directory to your remote location through a cmd or GUI and perform your installations.