Okay, so I was able to work past that bug from the Set-PowerCLIConfiguration cmdlet - PowerCLI cmdlets have been throwing that bug under various circumstances for a long time. In this case, I had the PowerCLI modules installed in the User scope, and I was setting the module location to the folder containing my personal modules. I removed PowerCLI and reinstalled it in the AllUsers scope, and I was able to use it successfully.
Now my test code looks like this and returns what I expect:
Write-Host "Test"
import-module VMware.PowerCLI
import-module $PSScriptRoot\connect-vcenter
Set-PowerCLIConfiguration -DefaultVIServerMode Multiple -Scope User -InvalidCertificateAction Ignore -ParticipateInCEIP $false -Confirm:$false
connect-viserver <hostname redacted> -credential <credentialredacted>
get-vm shr* | select Name
I’m also going to be using the following forum post to get up and running with PowerCLI inside of PSU:
Work with VMware vCenter connections - Universal Dashboard / Cookbook - Ironman Software Forums
My apologies for my frustrated rant - a lot of what I expected out of your product was based on my experience with vRealize Orchestrator. Now that I understand what all it does, I’m going to keep plugging away and attempt to get this thing going.
Thanks for your help!