Highlighted
Hot Shot
Hot Shot

PowerGUI and PowerCLI issue

Jump to solution



I can't seem to find this answer from searching online, so I'll ask here.  I'm using PowerGUI 3.8, and I downloaded PowerCLI 5.5 R2 a few days ago.  PowerGUI is not updating PowerCLI, I have performed the usual uninstall/reinstall, I removed the snap-in and added it back, and I find this rather odd.


If I use the built-in Microsoft ISE, the new PowerCLI cmdlets appear, I see New-Tag, Connect-SRMServer, I see all of the new cmdlets that should be there in PowerCLI 5.5 R2 if I use the built-in ISE.  


I ran DefaultVIServer and it shows 5.0, which I guess shows that even if it's 5.5, since the MIcrosoft ISE definitely has the new cmdlets.  I've checked the PowerGUI discussions, but they aren't as active as the VMware PowerCLI forums, so I thought it would be better to ask this here.  Any ideas?


Last thing, I did connect to vCenter directly with PowerCLI, it shows "VMware vSphere PowerCLI 5.5 Release 2" at the top, but the same $global:DefaultVIServershows 5.0, but all of the new cmdlets are there, so this seems to only be affecting PowerGUI.  

0 Kudos
1 Solution

Accepted Solutions
Highlighted
VMware Employee
VMware Employee

I have had this a few times, you need to delete the PowerGUI Intellisense cache, quit powergui and the script editor and then backup/delete C:\Users\...\AppData\Local\Quest Software\PowerGUI\ then it should come back up and recreate your PowerGUI settings and cache.

Blog: http://virtu-al.net Twitter: http://twitter.com/alanrenouf Co-author of the PowerCLI Book: http://powerclibook.com

View solution in original post

0 Kudos
9 Replies
Highlighted
User Moderator
User Moderator

Did you try the Get-PowerCLIVersion cmdlet ?

Which version of PowerCLI does that show on all the platforms ?

The $global:DefaultVIServer variable shows the vSphere connection that is open.

It normally shows the version of the vSphere server, not the PowerCLI version.


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

0 Kudos
Highlighted
Hot Shot
Hot Shot



Thanks for the response


Yeah, I made an idiot move on the defaultVIServer, and Get-PowerCLIVersion shows 5.5 release 2, but non of the new cmdlets show up in PowerGUI.  On the Microsoft ISE, I see new-tag, I see the parameter on Move-VM -vMotionPriority, I see all of the new cmdlets that come with PowerCLI 5.5 Release 2, but non of them show up on PowerGUI.  I know this forum isn't the place for this type of question, I was hoping that someone had the same issue.  I'm going to setup a new VM and install everything new, just to see what happens.  Thanks for the help.

0 Kudos
Highlighted
Hot Shot
Hot Shot



It seems to be some type of issue with PowerGUI, I installed PowerGUI and PowerCLI on a brand new machine, and I can see the new cmdlets.  On the machine that I've had problems with, I was updating PowerGUI and PowerCLI over the last year or so, so I guess PowerGUI is holding old data somewhere.  

0 Kudos
Highlighted
User Moderator
User Moderator

You are checking this in the PowerGUI Script Editor - PowerShell Console I assume ?

What does the Get-PowerCLIVersion cmdlet return there ?


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

0 Kudos
Highlighted
Hot Shot
Hot Shot



Yes, I checked inside the PowerGUI script editor where it actually shows PowerShell Console, I'm not running it as a script.  I also went to Tools "Powershell Command Prompt" in PowerGUI, I added the snapin vm* and I see the new cmdlets there.  All of the versions show 5.5 Release 2, but PowerGUI does not show any of the new cmdlets or parameters.  


There has to be some old data lingering, I can't even count how many times I've uninstalled and reinstalled the software, but something is staying, at least it seems that way. 

0 Kudos
Highlighted
User Moderator
User Moderator

What does it show under File - PowerShell Libraries in the Script Editor ?


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

0 Kudos
Highlighted
VMware Employee
VMware Employee

I have had this a few times, you need to delete the PowerGUI Intellisense cache, quit powergui and the script editor and then backup/delete C:\Users\...\AppData\Local\Quest Software\PowerGUI\ then it should come back up and recreate your PowerGUI settings and cache.

Blog: http://virtu-al.net Twitter: http://twitter.com/alanrenouf Co-author of the PowerCLI Book: http://powerclibook.com

View solution in original post

0 Kudos
Highlighted
Hot Shot
Hot Shot



Thank you, thank you, the cache in PowerGUI was it.  This was a case of not knowing the exact name to search.  I was thinking it was PowerCLI, but yes, it was the intellisense in PowerGUI, I removed the folder, started PowerGUI and after a few minutes, everything loaded back in, and I can see the cmdlets.


Wow, I've been at this for quite some time today.  Thanks for the help.  

0 Kudos
Highlighted
VMware Employee
VMware Employee

Glad to help, I know how frustrating it can be, especially the amount of times I unload and reload PowerCLI Smiley Wink

Blog: http://virtu-al.net Twitter: http://twitter.com/alanrenouf Co-author of the PowerCLI Book: http://powerclibook.com
0 Kudos