Thanks for your response.
As such there is no reason for using older version of powercli.
I even tried with following version(latest version):
PowerCLI Version
----------------
VMware PowerCLI 11.2.0 build 12483598
---------------
Component Versions
---------------
VMware Cis Core PowerCLI Component PowerCLI Component 11.2 build 12483642
VMware VimAutomation VICore Commands PowerCLI Component PowerCLI Component 11.2 build 12483638
But still getting same results:
PS C:\Users\admin> Get-CIVM -Name $VM_Name | Open-VMConsoleWindow
WARNING: PowerCLI scripts should not use the 'Uid' property. The property will be removed in a future release.
Open-VMConsoleWindow : 3/8/2019 1:43:20 PM Open-VMConsoleWindow Current version of VMRC only supports vS
phere VMs
At line:1 char:28
+ Get-CIVM -Name $VM_Name | Open-VMConsoleWindow
+ ~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : InvalidArgument: (:) [Open-VMConsoleWindow], InvalidArgument
+ FullyQualifiedErrorId : Core_OpenVMConsoleWindow_OnlyvSphereVMsSupported,VMware.VimAutomation.ViCore.Cmdlets.Com
mands.OpenVMConsoleWindow
Open-VMConsoleWindow : 3/8/2019 1:43:20 PM Open-VMConsoleWindow Current version of VMRC only supports vS
phere VMs
At line:1 char:28
+ Get-CIVM -Name $VM_Name | Open-VMConsoleWindow
+ ~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : InvalidArgument: (:) [Open-VMConsoleWindow], InvalidArgument
+ FullyQualifiedErrorId : Core_OpenVMConsoleWindow_OnlyvSphereVMsSupported,VMware.VimAutomation.ViCore.Cmdlets.Com
mands.OpenVMConsoleWindow
Open-VMConsoleWindow : 3/8/2019 1:43:20 PM Open-VMConsoleWindow Current version of VMRC only supports vS
phere VMs
At line:1 char:28
+ Get-CIVM -Name $VM_Name | Open-VMConsoleWindow
+ ~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : InvalidArgument: (:) [Open-VMConsoleWindow], InvalidArgument
+ FullyQualifiedErrorId : Core_OpenVMConsoleWindow_OnlyvSphereVMsSupported,VMware.VimAutomation.ViCore.Cmdlets.Com
mands.OpenVMConsoleWindow