I get a blinking cursor for about 30 seconds before it times out and returns to the command prompt - which is the same response from the other four vCenters.

Hello LucD,

Running the command as you suggested results in the same error, but just  Get-VM $getCIVMinfo*  by itself works fine. I've pasted the results of some attempts below. And here's the version info:

Get-Module -Name VMware.PowerCLI | Select-Object -Property Name,Version

Name            Version

----            -------

VMware.PowerCLI 10.2.0.9372002

PS C:\ps> $getCIVMinfo = Get-OrgVdc NameRedacted | Get-CIVApp -Name Collector-02 | Get-CIVM -Name Collector02

PS C:\ps> $vsphereVMView = Get-VM -RelatedObject $getCIVMinfo

Get-VM : 08-Oct-18 09:58:11     Get-VM          vCenter server  'https://fqdnredacted:443' could not be

found. Please make sure you are connected.

At line:1 char:18

+ $vsphereVMView = Get-VM -RelatedObject $getCIVMinfo

+                  ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

    + CategoryInfo          : NotSpecified: (:) [Get-VM], CIException

    + FullyQualifiedErrorId : CloudImpl_VIObjectInteropServiceImpl_GetDatastore_Error,VMware.VimAutomation.ViCore.Cmdl

   ets.Commands.GetVM

PS C:\ps> get-vm Collector02*

Name                 PowerState Num CPUs MemoryGB

----                 ---------- -------- --------

COLLECTOR02 (... PoweredOn  2        4.000

PS C:\ps> Get-VM -RelatedObject $getCIVMinfo

Get-VM : 08-Oct-18 09:59:34     Get-VM          vCenter server  'https://fqdnredacted:443' could not be

found. Please make sure you are connected.

At line:1 char:1

+ Get-VM -RelatedObject $getCIVMinfo

+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

    + CategoryInfo          : NotSpecified: (:) [Get-VM], CIException

    + FullyQualifiedErrorId : CloudImpl_VIObjectInteropServiceImpl_GetDatastore_Error,VMware.VimAutomation.ViCore.Cmdl

   ets.Commands.GetVM

PS C:\ps> $getCIVMinfo

Name                           Status                      GuestOSFullName                          CpuCount MemoryGB

----                           ------                      ---------------                          -------- --------

COLLECTOR02                PoweredOn                   Microsoft Windows Server 2012 (64-bit)   2        4.000

PS C:\ps> Get-VM $getCIVMinfo*

Name                 PowerState Num CPUs MemoryGB

----                 ---------- -------- --------

COLLECTOR02 (... PoweredOn  2        4.000

Sorry, I don't know how to paste with the PowerShell colors in-tact. Thanks in advance.

I just RDPed into the Windows box to check, and we have the windows firewall completely disabled. Good thought though.

"network trace with the cmdlet" do you mean tracert to the vCenter? Thanks.

Ah, got it.

I think I'm going to head down the SR route and see where that goes. I did some manual testing on different machines, including logging in with a local account to a Windows VM on the same subnet as the vCenter I'm having issues with. PowerCLI had never been installed on this box. I installed power CLI, connected to vCenter using the IP, and I'm still receiving the same error. Interestingly enough, the error includes the FQDN even though I connected by IP. I'll update this thread with anything I get from support in case someone else out there runs into this issue. Thanks!