JDMils_Interact Tracker

Re: Ignore Try..Catch on terminating errors

JDMils_Interact — Thu, 09 Nov 2023 22:05:45 GMT

I was using Get-Item -Location "C:\Temp" because I wanted to create a terminating error, then using the -ErrorAction Ignore, I was hoping the code would ignore the error and continue running.

This is just my way of testing.

Re: Ignore Try..Catch on terminating errors

JDMils_Interact — Wed, 08 Nov 2023 23:01:11 GMT

That's what I thought. When I run the code, it actually ALWAYS enters the Catch block as shown here:

PS C:\Users\jmilano\Documents\PowerShell_Scripts\Datastores> C:\Users\jmilano\Documents\PowerShell_Scripts\TestTryCatch.ps1 Try this.... Try-Catch activated Finally activated

I have the Try..Catch to capture all major terminating errors, however I have one command which i do NOT want to terminate on, I just want the code to continue running. The problem is that the code ALWAYS enters the Catch block and I cannot figger out why I.

Note: Get-Item does not have a location parameter so this should trigger an error which I want to ignore. This is for testing purposes atm.

Even testing from the command line, ErrorAction doesn't work:

PS C:\Users\jmilano\Documents\PowerShell_Scripts> get-item -location "c:\temp" -ErrorAction Continue Get-Item : A parameter cannot be found that matches parameter name 'location'. At line:1 char:10 + get-item -location "c:\temp" -ErrorAction Continue + ~~~~~~~~~ + CategoryInfo : InvalidArgument: (:) [Get-Item], ParameterBindingException + FullyQualifiedErrorId : NamedParameterNotFound,Microsoft.PowerShell.Commands.GetItemCommand PS C:\Users\jmilano\Documents\PowerShell_Scripts> get-item -location "c:\temp" -ErrorAction Ignore Get-Item : A parameter cannot be found that matches parameter name 'location'. At line:1 char:10 + get-item -location "c:\temp" -ErrorAction Ignore + ~~~~~~~~~ + CategoryInfo : InvalidArgument: (:) [Get-Item], ParameterBindingException + FullyQualifiedErrorId : NamedParameterNotFound,Microsoft.PowerShell.Commands.GetItemCommand PS C:\Users\jmilano\Documents\PowerShell_Scripts> get-item -location "c:\temp" -ErrorAction Inquire Get-Item : A parameter cannot be found that matches parameter name 'location'. At line:1 char:10 + get-item -location "c:\temp" -ErrorAction Inquire + ~~~~~~~~~ + CategoryInfo : InvalidArgument: (:) [Get-Item], ParameterBindingException + FullyQualifiedErrorId : NamedParameterNotFound,Microsoft.PowerShell.Commands.GetItemCommand PS C:\Users\jmilano\Documents\PowerShell_Scripts> get-item -location "c:\temp" -ErrorAction SilentlyContinue Get-Item : A parameter cannot be found that matches parameter name 'location'. At line:1 char:10 + get-item -location "c:\temp" -ErrorAction SilentlyContinue + ~~~~~~~~~ + CategoryInfo : InvalidArgument: (:) [Get-Item], ParameterBindingException + FullyQualifiedErrorId : NamedParameterNotFound,Microsoft.PowerShell.Commands.GetItemCommand

Ignore Try..Catch on terminating errors

JDMils_Interact — Wed, 08 Nov 2023 01:34:03 GMT

I'm very sorry for this basic question and I MUST be missing something obvious. I cannot get a terminating error located within a Try..Catch to be ignored and for processing to continue.

$ErrorActionPreference = "Ignore" Try { Write-Host "Try this...." Get-Item -Location "C:\Temp" -ErrorAction Ignore Write-Host "Error ignored" } Catch { Write-Host "Try-Catch activated" } Finally { Write-Host "Finally activated" }

Basically I want the terminating error "Get-Item -Location "C:\Temp" -ErrorAction Ignore" to be ignored and processing to continue. In my testing, the Catch block is always processed.

My PS version:

$PSVersionTable Name Value ---- ----- PSVersion 5.1.14393.6343 PSEdition Desktop PSCompatibleVersions {1.0, 2.0, 3.0, 4.0...} BuildVersion 10.0.14393.6343 CLRVersion 4.0.30319.42000 WSManStackVersion 3.0 PSRemotingProtocolVersion 2.3 SerializationVersion 1.1.0.1

Re: Disconnect Serial Port

JDMils_Interact — Fri, 03 Nov 2023 07:43:17 GMT

Hi LucD,

Your script looks gr8, can you modify it so that the serial ports which output to a file on a datastore are modified so that they can be pointed to a new datastore? I need this code in order to migrate VMs off datastores which are to be decomed.

I've noticed that when I manually edit the VM settings, the new com files are created on the new datastores however the old ones are still present on the original datastore?

Thanks.

Re: virtual device ethernet0 will start disconnected

JDMils_Interact — Fri, 27 Oct 2023 00:13:58 GMT

That does not sound right as vCenter associates the VLAN MoRef to the VM not the name so you can change the name to whatever you like whenever you like without any issues.

This issue is happening with me after decoming NSX-V from the hosts and taking the host out of maintenance. All VMs migrated to this host get the error "Virtual device 'Ethernet0' will start disconnected" and only this host from the 10 in total in this cluster.

I will report back with my findings.

How to patch an ESXi server to 7.0u3g which is not connected to the internet?

JDMils_Interact — Thu, 12 Oct 2023 22:59:48 GMT

Thanks for the reply. So you are saying that if I download the 7.0u3g offline patch file, it will patch my hosts with all relevant Critical & Non-Critical patches?

If that's the case then thank you!

How to patch an ESXi server to 7.0u3g which is not connected to the internet?

JDMils_Interact — Thu, 12 Oct 2023 01:56:39 GMT

I have an isolated vCenter 7.0u3h so no connection to the internet. It has 2 hosts running ESXi 7.0u3d.

Normally I would create a patch baseline for 7.0u3g which automatically updates the baseline with all patches upto the date 1st Sep 2022. Then I would use this baseline to patch the hosts. But this works for internet-connected vCenters.

I tried downloading the ESXi 7.0u3g patch from the VMware download site, however I found that the host was still missing the required Critical & Non-Critical patches. My question is how do I select and download the Critical & Non-Critical patches from the VMware download site in order to patch the ESXi hosts offline?

Does the 7.0u3g download contain the Critical & Non-Critical updates as well?

https://customerconnect.vmware.com/downloads/details?downloadGroup=ESXI70U3G&productId=974

Get host CPUID information

JDMils_Interact — Thu, 14 Sep 2023 02:18:52 GMT

I'm looking at a vulnerability with Intel CPUs (https://blogs.vmware.com/security/2023/08/cve-2022-40982.html) and am looking at this page describing which CPUs are affected:

https://www.intel.com/content/www/us/en/developer/topic-technology/software-security-guidance/processors-affected-consolidated-product-cpu-model.html

There are a few PowerCLI scripts which claim to give the CPUID for the hosts, but none that I have found will out put the results I need to compare to the Intel page above.

Does anyone have any pointers?

EDIT: I just needed 2 more minutes after posting this to get the answer I needed!

https://github.com/fgrehl/virten-scripts/blob/master/powershell/get-cpuid.ps1

vMotion fails with error "A general system error occurred: Invalid fault"

JDMils_Interact — Sat, 05 Aug 2023 21:05:54 GMT

The guys in the team were upgrading an ESXi 6.7u3q host to 7.0u3g and they found that once upgraded, they could not vMotion powered on VMs to the host. Error they were seeing was:

Task Name: Relocate virtual machine Status: A general system error occurred: Invalid fault

I checked hostd.log and found the following:

2023-08-05T20:10:26.207Z info hostd[2099895] [Originator@6876 sub=AdapterServer opID=lib2tr14-392654-auto-8ez3-h5:70076941-cc-01-48-4f75 user=vpxuser:VSPHERE.LOCAL\Administrator] AdapterServer caught exception; <<5217f91e-b388-dd1a-0bcc-b971cade8b0f, <TCP '127.0.0.1 : 8307'>, <TCP '127.0.0.1 : 56080'>>, ha-vmotionmgr, vim.host.VMotionManager.initiateDestination>, N3Vim5Fault19PlatformConfigFault9ExceptionE(Fault cause: vim.fault.PlatformConfigFault --> ) --> [context]zKq7AVICAgAAAKEvNgENaG9zdGQAACJDF2xpYnZtYWNvcmUuc28AAX/nz2hvc3RkAAF6988B/mHPAXyPXwGoL1+CWQ8ZAWxpYnZpbS10eXBlcy5zbwABipJSAKzHLQA0Ay4A4hA/Azt9AGxpYnB0aHJlYWQuc28uMAAEbdEObGliYy5zby42AA==[/context] 2023-08-05T20:10:26.215Z info hostd[2099895] [Originator@6876 sub=Solo.Vmomi opID=lib2tr14-392654-auto-8ez3-h5:70076941-cc-01-48-4f75 user=vpxuser:VSPHERE.LOCAL\Administrator] Activation finished; <<5217f91e-b388-dd1a-0bcc-b971cade8b0f, <TCP '127.0.0.1 : 8307'>, <TCP '127.0.0.1 : 56080'>>, ha-vmotionmgr, vim.host.VMotionManager.initiateDestination> 2023-08-05T20:10:26.215Z verbose hostd[2099895] [Originator@6876 sub=Solo.Vmomi opID=lib2tr14-392654-auto-8ez3-h5:70076941-cc-01-48-4f75 user=vpxuser:VSPHERE.LOCAL\Administrator] Arg migrationId: --> 1011845975857744995 2023-08-05T20:10:26.215Z verbose hostd[2099895] [Originator@6876 sub=Solo.Vmomi opID=lib2tr14-392654-auto-8ez3-h5:70076941-cc-01-48-4f75 user=vpxuser:VSPHERE.LOCAL\Administrator] Arg dstConfigPath: --> "/vmfs/volumes/41f8fd2d-4a203baa/MyServer-Test-74yN/MyServer-Test-74yN.vmx" 2023-08-05T20:10:26.215Z info hostd[2099895] [Originator@6876 sub=Solo.Vmomi opID=lib2tr14-392654-auto-8ez3-h5:70076941-cc-01-48-4f75 user=vpxuser:VSPHERE.LOCAL\Administrator] Throw vim.fault.PlatformConfigFault 2023-08-05T20:10:26.215Z info hostd[2099895] [Originator@6876 sub=Solo.Vmomi opID=lib2tr14-392654-auto-8ez3-h5:70076941-cc-01-48-4f75 user=vpxuser:VSPHERE.LOCAL\Administrator] Result: --> (vim.fault.PlatformConfigFault) { --> text = "Failed to attach all ports", --> msg = "", --> }

Turns out the guys forgot to install the new V7.0 host license!

I thought I'd put this out there as I initially spent about 20 minutes on wild goose chases until I found the problem!

How can I find duplicate UUIDs in vCD?

JDMils_Interact — Thu, 20 Jul 2023 01:20:05 GMT

I use Zerto to replicate customer VMs from one site to another, however Zerto "freaks out" when it finds different VMs with the same UUID in vCloud Director.

Zerto support found 2 VMs with the same UUID such as this one:

ID = 'urn:vcloud:vm:2ec418fe-23d0-4ff4-62ba-b5f72c347ceb'

I thus want to know if it is possible to find duplicate vCloud Director UUIDs for virtual servers? Can this be done in PowerShell?

How do I migrate VMs from one host to another when vCD is present?

JDMils_Interact — Tue, 18 Jul 2023 00:33:12 GMT

I'm planning to perform maintenance on my hosts and need to put them into maintenance to do this. My question is: If the hosts contain a number of VMs which are present in vCD inside vApps, can the host-2-host migration still be done in vCenter without affecting vCD?

I know that vCD can get upset when certain changes are made to a VM from vCenter instead of vCD so I wanted to check if host-migrations are OK when performed from vCenter.

Re: Strange issue- Move-VM moves the VM, however it also errors out!

JDMils_Interact — Wed, 26 Apr 2023 07:05:36 GMT

Another code change I had to make was in the calling line:

# Move-VMThin (Get-VM $oTemplateAsVM) (Get-Datastore $TargetDS) Move-VMThin -VM $($oTemplateAsVM.Name) -Datastore $DatastoreName

Had to change the -VM & Datastore to strings.

One other thing I need your help with is that, surprisingly to me, you can have more than one template in a vCenter with the SAME name!?

So this line returns multiple objects:

$vmView = Get-View -ViewType VirtualMachine -Filter @{"Name" = "$VM"}

If there's no way to fix this then all I can do is check for $vmView.Count and anything gt 1 will get a message to the user to say something like "Sorry, too many objects returned- do this one manually".

Re: Strange issue- Move-VM moves the VM, however it also errors out!

JDMils_Interact — Wed, 26 Apr 2023 06:46:14 GMT

Hmmm, with the new code it now no longer storage migrates the Template/VM and errors with:

$Error[0] Exception calling "RelocateVM" with "2" argument(s): "Invalid configuration for device '13'." At C:\Users\jmilano\Documents\PowerShell_Scripts\Datastores\2023-03-04 NetApp Datastore Migration\Storage-MigrateTemplates.ps1:150 char:9 + $vmView.RelocateVM($spec, $null) + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + CategoryInfo : NotSpecified: (:) [], MethodInvocationException + FullyQualifiedErrorId : VimException

I think this code exposes the "real" issue- that the connected portgroup to the template is not valid. I fixed the above issue by disconnecting the network from the VM and converting it back to a template and the script storage migrated it OK.

I'll keep testing to see what happens with the rest of the templates.

Re: Strange issue- Move-VM moves the VM, however it also errors out!

JDMils_Interact — Wed, 26 Apr 2023 00:04:57 GMT

The code I'm using actually came with another module to migrate the templates after they were converted to VMs, and I re-instated the module and it actually migrates the VMs with no issues. Here it is:

Call the new module using this line:

# $MoveVMToDS = Move-VM -VM (Get-VM -Name $oTemplateAsVM) -Datastore ($TargetDS) -Confirm:$false -ErrorAction Stop Move-VMThin (Get-VM $oTemplateAsVM) (Get-Datastore $TargetDS)

function Move-VMThin { PARAM( [Parameter(Mandatory=$true,ValueFromPipeline=$true,HelpMessage="Virtual Machine Objects to Migrate")] [ValidateNotNullOrEmpty()] [System.String]$VM, [Parameter(Mandatory=$true,HelpMessage="Destination Datastore")] [ValidateNotNullOrEmpty()] [System.String]$Datastore ) Begin { #Nothing Necessary to process } #Begin Process { #Prepare Migration info, uses .NET API to specify a transformation to thin disk $vmView = Get-View -ViewType VirtualMachine -Filter @{"Name" = "$VM"} $dsView = Get-View -ViewType Datastore -Filter @{"Name" = "$Datastore"} #Abort Migration if free space on destination datastore is less than 50GB if (($dsView.info.freespace / 1GB) -lt 50) {throw "Move-ThinVM ERROR: Destination Datastore $Datastore has less than 50GB of free space. This script requires at least 50GB of free space for safety. Please free up space or use the VMWare Client to perform this Migration"} #Prepare VM Relocation Specificatoin $spec = New-Object VMware.Vim.VirtualMachineRelocateSpec $spec.datastore = $dsView.MoRef $spec.transform = "sparse" #Perform Migration $vmView.RelocateVM($spec, $null) $MoveResult = Move-VM -VM $VM -Datastore $Datastore } #Process }

Actually, this was a code module posted by you in this thread a while back:

https://communities.vmware.com/t5/VMware-PowerCLI-Discussions/SVmotion-source-thick-disk-gt-svmotion-gt-should-become-thin/td-p/2120625

So I really would love to know why the original Move-VM would migrate the template-convertedTo-VM and ALSO produce an error (Operation is not valid due to the current state of the object.).

Re: Strange issue- Move-VM moves the VM, however it also errors out!

JDMils_Interact — Tue, 25 Apr 2023 23:41:03 GMT

Thanks LucD, same issue. It's so strange that I don't think there will be a fix for this. It just does not make sense!

Strange issue- Move-VM moves the VM, however it also errors out!

JDMils_Interact — Sat, 22 Apr 2023 08:17:27 GMT

The script below is used to storage vmotion Templates by first converting them into VMs, migrate them, then convert them back again to a template. Strangely, the Move-VM command starts a storage migration, as viewed in the vCenter GUI, however it also errors out!?? I cannot figure out why it is doing this! And it seems to be doing it with all my templates.

I tested this from a PowerShell command line and the PowerShell IDE- same result.

Function:

function Move-VMTemplate { # This function will migrate a template VM to the target datastore. # The template is first converted to a VM, # then migrated, then converted back to a template. param( [string] $TemplateName, [string] $DatastoreName ) # Try # { if($TemplateName -eq ""){Write-Host "Enter a Template name"} if($DatastoreName -ne ""){$svmotion = $true} # Firstly, verify we have a target datastore presented to the vCenter: $TargetDS = Get-Datastore $DatastoreName -ErrorAction Stop Write-Host "$LineItem2 Converting to VM." -ForegroundColor DarkCyan # Convert the template to a VM. $oTemplateAsVM = Set-Template -Template (Get-Template $TemplateName) -ToVM -ErrorAction Stop Write-Host "$LineItem2 Migrate template to target datastore." -ForegroundColor DarkCyan # Move the VM to the target datastore. $MoveVMToDS = Move-VM -VM (Get-VM $oTemplateAsVM) -Datastore ($TargetDS) -Confirm:$false -ErrorAction Stop # Move-VMThin (Get-VM $oTemplateAsVM) (Get-Datastore $fDatastore) Write-Host "$LineItem2 Converting VM to template." -ForegroundColor DarkCyan # Convert the VM back to a template. (Get-VM $oTemplateAsVM | Get-View).MarkAsTemplate() | Out-Null Write-Host "$LineItem2 Conversion done." -ForegroundColor Green # } <# Catch { Write-Host "$LineItem2 Error: $($PSItem.ToString())." -ForegroundColor Red Write-Host "$LineItem2 Skipping template [$TemplateName]." -ForegroundColor Red } #> }

I took out the Try/Catch just to see if I could get more info.

The function is called with this line:

$MoveVMTemplate = Move-VMTemplate -template $TemplateName -datastore $NewDatastoreName

Here are the values of the variables:

$TemplateName nashadow_RHEL6.5-x64_SOE_v1.1_mgt_t1_syd_vmdata_0001 $NewDatastoreName mgt_t1_syd_vmdata_0003 $TargetDS Name FreeSpaceGB CapacityGB ---- ----------- ---------- mgt_t1_syd_vmdata_0003 4,659.154 4,680.000 (Get-VM $oTemplateAsVM) Name PowerState Num CPUs MemoryGB ---- ---------- -------- -------- nashadow_RHEL6.5-... PoweredOff 1 2.000

Template is currently sitting on datastore "mgt_t1_syd_vmdata_0001 ".

When the Move-VM line executes, a new task appears in the vCenter GUI showing the VM being migrated, and it completes without issues, however the script produces the following error:

$PSItem Move-VM : 22/04/2023 6:01:33 PM Move-VM Operation is not valid due to the current state of the object. At C:\Users\jmilano\Documents\PowerShell_Scripts\Datastores\2023-03-04 NetApp Datastore Migration\Storage-MigrateTemplates.ps1:102 char:23 + ... oveVMToDS = Move-VM -VM (Get-VM $oTemplateAsVM) -Datastore ($TargetDS ... + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + CategoryInfo : NotSpecified: (:) [Move-VM], VimException + FullyQualifiedErrorId : Core_BaseCmdlet_UnknownError,VMware.VimAutomation.ViCore.Cmdlets.Commands.MoveVM

The "CS/DVD Drive 1" is set to "Client Device" and not connected. The Template has one 60GB hard disk.

I can manually migrate the template once converted to a VM, using the vCenter GUI without issues. I can then migrate it back to its original datastore.

$PSVersionTable.PSVersion Major Minor Build Revision ----- ----- ----- -------- 5 1 14393 5582 $PSVersionTable Name Value ---- ----- PSVersion 5.1.14393.5582 PSEdition Desktop PSCompatibleVersions {1.0, 2.0, 3.0, 4.0...} BuildVersion 10.0.14393.5582 CLRVersion 4.0.30319.42000 WSManStackVersion 3.0 PSRemotingProtocolVersion 2.3 SerializationVersion 1.1.0.1

Re: Disable DRS rule then enable it

JDMils_Interact — Tue, 18 Apr 2023 05:48:56 GMT

Sorry, for some reason this was not working earlier but is working OK now:

$DRSRuleDisabled = $DRSRule | Set-DRSVMHostRule -Enabled $False $DRSRuleDisabled = $DRSRule | Set-DRSVMHostRule -Enabled $True

Done!

Disable DRS rule then enable it

JDMils_Interact — Tue, 18 Apr 2023 05:35:29 GMT

I'm writing a VM migration script to storage migrate VMs form old to new datastores. In the situation where a VM has its swap file on a datastore which is designated as a host swap file (Configure | Swap File Location | Default swap file location),and you change the host's swap file location to a new datastore, the only way to migrate the VMs off the old swap datastore to the new is to host-migrate the VMs.

My script will host-migrate the VM from host1 to host2 back to host1 which effectively moves the VM's swap file to the newly setup host swap file. One issue is that if there are DRS Host Rules pinning the VM to a specific host, my code fails. I thus need to disable any rules which that VM is a part of, host-migrate the VM then re-enable those rules.

So far I've been able to get this code to work, which gets the DRS host rules which the respective VM is part of:

$VMHostGroup = Get-VM -Name $VMName | Select Name,@{N='DRSGroup';E={$script:group = Get-DrsClusterGroup -VM $_; $script:group.Name}},@{N='GroupType';E={$script:group.GroupType}} $DRSRule = Get-DrsVMHostRule -Cluster $MyCluster -VMGroup $VMHostGroup.drsgroup

How do I disable the rules, do my thing with the VM, then enable the rules afterwards?

Major Minor Build Revision
----- ----- ----- --------
5 1 14393 5582

How to properly export ESXi host boot devices to CSV

JDMils_Interact — Tue, 18 Apr 2023 00:26:43 GMT

I am using the script written by William Lam called "Get-ESXiBootDevice" (https://www.powershellgallery.com/packages/AsBuiltReport.VMware.vSphere/1.2.1/Content/Src%5CPrivate%5CGet-ESXiBootDevice.ps1) and it exports the data correctly to the console:

Get-ESXiBootDevice * Host Device BootType Vendor Model SizeMB IsSAS IsSSD IsUSB ---- ------ -------- ------ ----- ------ ----- ----- ----- MyHost01.MyDomain naa.600a098038303455575d484d46442f59 remote NETAPP LUN C-Mode 10240 false false false MyHost02.MyDomain naa.600a098038303455575d484d46442f2f remote NETAPP LUN C-Mode 10240 false false false MyHost03.MyDomain naa.600a098038303455575d484d46442f5a remote NETAPP LUN C-Mode 10240 false false false

However, now when I try to export the results to a CSV, I get this in the CSV file:

et-ESXiBootDevice * | export-csv -Path MyvCenter_Host_BootDevices.csv -NoTypeInformation -UseCulture "ClassId2e4f51ef21dd47e99d3c952918aff9cd","pageHeaderEntry","pageFooterEntry","autosizeInfo","shapeInfo","groupingEntry" "033ecb2bc07a4d43b5ef94ed5a35d280",,,"Microsoft.PowerShell.Commands.Internal.Format.AutosizeInfo","Microsoft.PowerShell.Commands.Internal.Format.TableHeaderInfo", "9e210fe47d09416682b841769c78b8a3",,,,, "27c87ef9bbda4f709f6b4002fa4af63c",,,,, "27c87ef9bbda4f709f6b4002fa4af63c",,,,, "27c87ef9bbda4f709f6b4002fa4af63c",,,,, "27c87ef9bbda4f709f6b4002fa4af63c",,,,, "27c87ef9bbda4f709f6b4002fa4af63c",,,,,

I even wrote code to loop thru each host individually and return the results with the same outcome:

$oVMHosts = Get-VMHost * $HostBootDevices = @() ForEach ($oVMHost in $oVMHosts) { $VMHostBootDevice = Get-ESXIBootDevice ($oVMHost) $HostBootDevices += $VMHostBootDevice } $HostBootDevices | export-csv -Path MyvCenter_Host_BootDevices.csv -NoTypeInformation -UseCulture

What is the correct way to export the data to CSV?

Re: Test if a datastore is read/write

JDMils_Interact — Tue, 07 Mar 2023 22:22:18 GMT

Sorry for any confusion. Let me explain better.

Further up in my code there is a section which adds the datastore to the host. Sometimes the storage guys forget to make the underlying LUN writable, so it is presented to the host as a read-only datastore. Then when I run my VM storage migration during my change window, I find the new datastores are read-only and I have to scramble to get a storage resource to fix it. We are talking about replacing 50 datastores on many vCenters so it needs to be automated.

The other part of the script will add the new datastores to each respective hosts, and it should test that the datastore is writable, by creating a test folder and then deleting the folder from the datastore.

I found the issue. It's not about removing the PSDrive, it was more about removing the folder from the datastore after it was created, and I found that Remove-Item is what I needed. So here's the resulting, working script, which tests if a datastore is writable:

# # Function to test read/write properties of a datastore by # creating a folder on the new datastore then delete the folder. Function CheckDSReadWriteOK { Param( [STRING]$HostObject = '', [STRING]$DatastoreName = '', [STRING]$RemotePath = '' ) Try { $TestDatastoreFolderName = "DS:\NEW_FOLDER" # Get the new datastore. $oDatastore = Get-Datastore -VMHost $HostObject -Name $DatastoreName # Ensure we get a catch-able error if something goes wrong. $ErrorActionPreference = "Stop" # Create the drive connection. $NewPSDrive = New-PSDrive -Location $oDatastore -Name DS -PSProvider VimDatastore -Root "\" # Create the test folder. If this fails, the datastore is most-likely in read-only mode. $NewPSFolder = New-Item -Path $TestDatastoreFolderName -ItemType Directory # If all went well, remove the test folder from the datastore. $RemovePSFolder = Remove-Item -Path $TestDatastoreFolderName -Confirm:$false # Remove the drive connection $RemovePSDrive = Remove-PSDrive -Name DS -Confirm:$false $ErrorActionPreference = “Continue” } Catch { Write-Host "$StringText_DS $StringText_Host- The datastore is NOT writeable." -ForegroundColor Red } }

Thank you all for your help.