Please note that the VM must be powered off for the cmdlet to succeed. The ISO file is still “registered” in the drive’s settings but the VM’s guest operating system doesn’t see any CD/DVD anymore. Get-VM -Name Computer1 | Get-CDDrive| Set-CDDrive -Connected $false Get-VM -Name Computer1 | Get-CDDrive| Set-CDDrive -Connected $true -IsoPath ' SubfolderName\file.iso' -StartConnected $true If you want, you can also configure the ISO file to be connected when the VM is starting. Get-VM -Name Computer1 | Get-CDDrive| Set-CDDrive -Connected $true -IsoPath ' SubfolderName\file.iso' Now you can connect the ISO file with the Set-CDDrive cmdlet.
This is the relative path you will provide to the cmdlet in order to connect an ISO file. Watch out for a property named DatastoreFullPath. Get-ChildItem -Path vmstore:\DataCenterName\DataStoreName\SubfolderName\file.iso | Format-List Once you found the file, display all properties with the Format-List cmdlet. Use the Get-ChildItemcmdlet associated to the vmstore provider. Please note that the path is case sensitive! To connect an ISO to your VMįirst, you have to find the path to your ISO file. On the other hand, you add(=load) and remove(=unload) an ISO file with the Set-CDDrive cmdlet, and we are using this cmdlet in the current post. Here another quick post about a PowerCli cmdlet.įirst, you must be aware that the New-CDDrive and the Remove-CDDrive cmdlet are just to add and remove the “physically virtual” device.
0 kommentar(er)
