VMware Cloud Community
rzeygerman
Enthusiast
Enthusiast
Jump to solution

PowerCLI - upgrade VM hardware from v10 to v13 failing

Hi, I am receiving an error when I try to execute the following commands.

set-vm -name $Server -version v13

or

set-vm -VM (get-vm -Name $server) -version v13

The error message I keep receiving is:

Set-VM        The operation for the entity <ServerName> failed with the following message: "The operation is not supported on the object." 

Environment:

Windows 7 64bit &  Windows Server 2012 R2

Powershell v4.0

PowerCLI Version
----------------
   VMware PowerCLI 6.5 Release 1 build 4624819
---------------
Component Versions
---------------
   VMware Cis Core PowerCLI Component 6.5 build 4624453
   VMware VimAutomation Core PowerCLI Component 6.5 build 4624450

Please advise

0 Kudos
1 Solution

Accepted Solutions
rzeygerman
Enthusiast
Enthusiast
Jump to solution

LucD,

It is exactly the same issue and I looked I saw this a week ago. That's when I upgraded to my current version:PowerCLI Version.

I looked deeper into this, was having warning that parts were still loaded while performing update-module command.

Solved everything this way:

1. Uninstalled PowerCLI from ADD/Remove programs

2. executed Install-Module VMware.PowerCLI

3. Imported: VMware.PowerCLI instead of VMware.*.Core

     import-moduel PowerCLI

Current PowerCLI version:


PowerCLI Version
----------------
   VMware PowerCLI 6.5.1 build 5377412
---------------
Component Versions
---------------
   VMware Cis Core PowerCLI Component 6.5 build 6983166
   VMware VimAutomation Core PowerCLI Component 6.5 build 6234650
   VMware SRM PowerCLI Component 6.5 build 5374694
   VMware Licensing PowerCLI Component 6.5 build 5375648
   VMware Vds PowerCLI Component 6.5 build 5374428
   VMware vROps PowerCLI Component 6.5 build 5375723
   VMware Nsxt PowerCLI Component 2.0 build 6870461
   VMware Vmc PowerCLI Component 6.5 build 7086404
   VMware HA PowerCLI Component 6.0 build 7147627
   VMware HorizonView PowerCLI Component 7.1.0 build 5307191
   VMware Cloud PowerCLI Component 6.5 build 5375799
   VMware PCloud PowerCLI Component 6.5 build 5376282
   VMWare ImageBuilder PowerCLI Component 6.6 build 6997673
   VMWare AutoDeploy PowerCLI Component 6.6 build 6997673
   VMware Storage PowerCLI Component 6.5 build 7154886
   VMware vSphere Update Manager PowerCLI 6.6 build 5301639

I am now able to upgrade the VM Hardware from v10 to v13

Thank you very much for your help!

View solution in original post

0 Kudos
10 Replies
LucD
Leadership
Leadership
Jump to solution

Is that VM running on an ESXi node that supports v13?


Blog: lucd.info  Twitter: @LucD22  Co-author PowerCLI Reference

0 Kudos
rzeygerman
Enthusiast
Enthusiast
Jump to solution

Yes and I am able to upgrade via Web Client.

The node is running Hypervisor: VMware ESXi, 6.5.0, 6765664

0 Kudos
RAJ_RAJ
Expert
Expert
Jump to solution

Can u try to Upgrade from v10  to v11   as testing and update here .

getting same error or not ?

RAJESH RADHAKRISHNAN VCA -DCV/WM/Cloud,VCP 5 - DCV/DT/CLOUD, ,VCP6-DCV, EMCISA,EMCSA,MCTS,MCPS,BCFA https://ae.linkedin.com/in/rajesh-radhakrishnan-76269335 Mark my post as "helpful" or "correct" if I've helped resolve or answered your query!
0 Kudos
rzeygerman
Enthusiast
Enthusiast
Jump to solution

Yes, RAJ_RAJ, I am able to Upgrade from v10 to v11 without issues.

Yet, from v10 to v13 and v11 to v13 give the same error

0 Kudos
RAJ_RAJ
Expert
Expert
Jump to solution

Ok . if you try from v9 to v10  should be a successful one .

In that case  powercli might be not able to understand v11 , v13  for  that object

RAJESH RADHAKRISHNAN VCA -DCV/WM/Cloud,VCP 5 - DCV/DT/CLOUD, ,VCP6-DCV, EMCISA,EMCSA,MCTS,MCPS,BCFA https://ae.linkedin.com/in/rajesh-radhakrishnan-76269335 Mark my post as "helpful" or "correct" if I've helped resolve or answered your query!
0 Kudos
rzeygerman
Enthusiast
Enthusiast
Jump to solution

Raj_Raj it's not just "that" object. I have tried 3 different objects and all give me the same error going to v13 via set-VM comand

0 Kudos
RAJ_RAJ
Expert
Expert
Jump to solution

Can u try with v9 to v10 as a test

RAJESH RADHAKRISHNAN VCA -DCV/WM/Cloud,VCP 5 - DCV/DT/CLOUD, ,VCP6-DCV, EMCISA,EMCSA,MCTS,MCPS,BCFA https://ae.linkedin.com/in/rajesh-radhakrishnan-76269335 Mark my post as "helpful" or "correct" if I've helped resolve or answered your query!
0 Kudos
LucD
Leadership
Leadership
Jump to solution

Upgrade your PowerCLI version, your issue looks like the one in  Re: Bug with Set-VM -version v13?


Blog: lucd.info  Twitter: @LucD22  Co-author PowerCLI Reference

0 Kudos
rzeygerman
Enthusiast
Enthusiast
Jump to solution

LucD,

It is exactly the same issue and I looked I saw this a week ago. That's when I upgraded to my current version:PowerCLI Version.

I looked deeper into this, was having warning that parts were still loaded while performing update-module command.

Solved everything this way:

1. Uninstalled PowerCLI from ADD/Remove programs

2. executed Install-Module VMware.PowerCLI

3. Imported: VMware.PowerCLI instead of VMware.*.Core

     import-moduel PowerCLI

Current PowerCLI version:


PowerCLI Version
----------------
   VMware PowerCLI 6.5.1 build 5377412
---------------
Component Versions
---------------
   VMware Cis Core PowerCLI Component 6.5 build 6983166
   VMware VimAutomation Core PowerCLI Component 6.5 build 6234650
   VMware SRM PowerCLI Component 6.5 build 5374694
   VMware Licensing PowerCLI Component 6.5 build 5375648
   VMware Vds PowerCLI Component 6.5 build 5374428
   VMware vROps PowerCLI Component 6.5 build 5375723
   VMware Nsxt PowerCLI Component 2.0 build 6870461
   VMware Vmc PowerCLI Component 6.5 build 7086404
   VMware HA PowerCLI Component 6.0 build 7147627
   VMware HorizonView PowerCLI Component 7.1.0 build 5307191
   VMware Cloud PowerCLI Component 6.5 build 5375799
   VMware PCloud PowerCLI Component 6.5 build 5376282
   VMWare ImageBuilder PowerCLI Component 6.6 build 6997673
   VMWare AutoDeploy PowerCLI Component 6.6 build 6997673
   VMware Storage PowerCLI Component 6.5 build 7154886
   VMware vSphere Update Manager PowerCLI 6.6 build 5301639

I am now able to upgrade the VM Hardware from v10 to v13

Thank you very much for your help!

0 Kudos
LucD
Leadership
Leadership
Jump to solution

Yes, you must remove the MSI-based PowerCLI installation completely before going to a PSGallery-based installation.

See also Welcome PowerCLI to the PowerShell Gallery – Install Process Updates


Blog: lucd.info  Twitter: @LucD22  Co-author PowerCLI Reference

0 Kudos