So after you go and make your Virtual Machine you realize you forgot to mount the .ISO for Windows Server 2012 and you left the Floppy Drive in the config which is not really hurting anyone but it makes things more aesthetically pleasing to not see it there. So what do you do….
Here are the detailed steps to change the hardware configuration of a virtual machine from the VMware vSphere Client.
With the virtual machine selected in the navigation pane you should see the “Getting Started” tab in the center panel. On that tab towards the bottom you will see the “Basic Tasks” section as seen in the screenshot below.
Click on “Edit Virtual Machine Settings” and the Virtual Machine Properties Window will open up for you.
From here you can see all of the virtual hardware that is assigned to the virtual machine in question. You can also make changes to the virtual hardware as you see fit.
Please note: you will not be able to modify all of the settings if the VM is powered on. Some things like Memory and CPU will require the VM to be off before VMware will let you modify it.
To remove the Floppy drive select the device by clicking on it and click the remove button.
You will now see that the device has a line though it, meaning that this is a pending change for removal and will not take effect until you click okay at the bottom.
To add the boot ISO you will need to click on the CD/DVD Drive to highlight it.
To add an ISO stored on a Datastore like a LUN or the Local Datastore on the virtual host click Datastore ISO file radio button.
Once you click on the radio button the browse button then becomes available to you. Click on the Browse button to open the Browse Data store window.
Navigate to where you ISO is stored and click Open.
The file path for the ISO is now populated for you. I suggest that you click connect at power on up at the top of the window. This will make sure that the CD drive presents the ISO to the VM at boot up and allows you to boot into the VM.
Click okay to close the window and to commit the changes. Once the tasks have been committed you will then be able to power the VM back on.