Comments on: PowerCLI 4.1: A fork in the road http://poshoholic.com/2010/07/14/powercli-4-1-a-fork-in-the-road/ Totally addicted to PowerShell Thu, 09 Feb 2012 00:54:13 +0000 hourly 1 http://wordpress.com/ By: Kirk Munro http://poshoholic.com/2010/07/14/powercli-4-1-a-fork-in-the-road/#comment-2185 Mon, 10 Jan 2011 21:14:52 +0000 https://kirkmunro.wordpress.com/2010/07/14/powercli-4-1-a-fork-in-the-road/#comment-2185 FYI, I just published a beta version with PowerCLI 4.1 U1 (and 4.1) support). See the message at the top of the blog post for more details.

Kirk out.

]]> By: Maybe VMware Needs a Quality Oversight Department… | Daily Hypervisor http://poshoholic.com/2010/07/14/powercli-4-1-a-fork-in-the-road/#comment-2162 Tue, 04 Jan 2011 02:03:39 +0000 https://kirkmunro.wordpress.com/2010/07/14/powercli-4-1-a-fork-in-the-road/#comment-2162 [...] across an apology by one of the PowerGUI guys. Essentially, he was apologizing for something that VMware changed in the functionality of PowerCLI that affects how the PowerGUI Virtualization Powerpack interacts [...]

]]> By: PowerCLI 4.1 U1: Current state of affairs « Poshoholic http://poshoholic.com/2010/07/14/powercli-4-1-a-fork-in-the-road/#comment-2134 Fri, 17 Dec 2010 19:43:58 +0000 https://kirkmunro.wordpress.com/2010/07/14/powercli-4-1-a-fork-in-the-road/#comment-2134 [...] in July 2010 I shared my concerns about upgrading to version 4.1 of the PowerCLI due to a number of breaking changes introduced in that release.  These changes [...]

]]> By: Kirk Munro http://poshoholic.com/2010/07/14/powercli-4-1-a-fork-in-the-road/#comment-2133 Fri, 17 Dec 2010 18:35:16 +0000 https://kirkmunro.wordpress.com/2010/07/14/powercli-4-1-a-fork-in-the-road/#comment-2133 FYI, I have dug into this some more and unfortunately it is not as simple as it seems because 4.1.1 still doesn’t have the type names from 4.0 U1 properly included in the object model in all cases, and now there will be many warnings that appear when you get data from VMware using the PowerCLI cmdlets about properties that will be deprecated in the future. These warnings are a concern, and myself and other MVPs and vExperts are voicing those concerns with VMware to make sure they are aware of the problems.

Also, if you want to understand some more of the challenges with upgrading to PowerCLI 4.1.1, read this blog post: http://poshoholic.com/2010/12/17/a-letter-of-apology-to-the-vmware-powerpack-community/

Thanks,

Kirk out.

]]> By: A letter of apology to the VMware PowerPack community « Poshoholic http://poshoholic.com/2010/07/14/powercli-4-1-a-fork-in-the-road/#comment-2129 Fri, 17 Dec 2010 17:15:18 +0000 https://kirkmunro.wordpress.com/2010/07/14/powercli-4-1-a-fork-in-the-road/#comment-2129 [...] changed the object model that they were using in earlier releases.  This change came with many undesirable and unwelcome side effects, effectively breaking backwards compatibility with many scripts that are built on top of the [...]

]]> By: Paul Paradiso http://poshoholic.com/2010/07/14/powercli-4-1-a-fork-in-the-road/#comment-2110 Mon, 13 Dec 2010 17:20:39 +0000 https://kirkmunro.wordpress.com/2010/07/14/powercli-4-1-a-fork-in-the-road/#comment-2110 Thanks for the info, Posh! :)

]]> By: Kirk Munro http://poshoholic.com/2010/07/14/powercli-4-1-a-fork-in-the-road/#comment-2105 Fri, 10 Dec 2010 22:09:00 +0000 https://kirkmunro.wordpress.com/2010/07/14/powercli-4-1-a-fork-in-the-road/#comment-2105 Hi Derek,

Last night PowerGUI 2.3 went GA, and that release has a hard requirement for PowerCLI 4.0 U1 built in to the installer. We added this requirement due to the incompatibility described here. It seems that earlier this month, between our RTM and our GA dates, VMware released PowerCLI 4.1 U1 with backward compatibility support, so that version *should* work with our VMware PowerPack. We have not tested this yet however, but it should work. Unfortunately to use them together you have to first install PowerGUI with PowerCLI 4.0 U1 and the VMware PowerPack, then uninstall PowerCLI 4.0 U1 and then install PowerCLI 4.1 U1. That should allow you to use it with the latest version of the PowerCLI. Note again that I have not had time to test this scenario myself, but I will make time to try it soon.

We also have an update planned for the VMware PowerPack to move to the new object model so that we can support PowerCLI 4.1 and later releases, but that work has not happened yet. It isn’t far off though.

I hope this helps and let me know if you have any other questions. If you don’t want to wait for us to test with PowerCLI 4.1 U1 and you want to try it with that release yourself, I’d love to hear about your experiences with it.

Thanks!

Kirk out.

]]> By: Derek http://poshoholic.com/2010/07/14/powercli-4-1-a-fork-in-the-road/#comment-2045 Mon, 06 Dec 2010 03:47:24 +0000 https://kirkmunro.wordpress.com/2010/07/14/powercli-4-1-a-fork-in-the-road/#comment-2045 So what’s the state of PowerCLI 4.1.x support?

]]> By: Episode 119 – Adam Driscoll on PowerGUI Visual Studio Extensions « PowerScripting Podcast http://poshoholic.com/2010/07/14/powercli-4-1-a-fork-in-the-road/#comment-1745 Tue, 27 Jul 2010 02:44:00 +0000 https://kirkmunro.wordpress.com/2010/07/14/powercli-4-1-a-fork-in-the-road/#comment-1745 [...] as we elaborate on the impact of this change to your scripts. You can also read more about this on Poshoholic and the VI PowerShell blog. Possibly related posts: (automatically generated)New RadioTFS episode [...]

]]> By: VMware Infrastructure Management PowerPack – now with Visio 2010 support! « Poshoholic http://poshoholic.com/2010/07/14/powercli-4-1-a-fork-in-the-road/#comment-1729 Fri, 16 Jul 2010 02:57:37 +0000 https://kirkmunro.wordpress.com/2010/07/14/powercli-4-1-a-fork-in-the-road/#comment-1729 [...] that the VMware PowerCLI 4.1 is not supported with this release at this time, due to a number of issues.  For now the only supported version of the VMware PowerCLI is version 4.0 [...]

]]> By: Kirk Munro http://poshoholic.com/2010/07/14/powercli-4-1-a-fork-in-the-road/#comment-1728 Thu, 15 Jul 2010 13:01:07 +0000 https://kirkmunro.wordpress.com/2010/07/14/powercli-4-1-a-fork-in-the-road/#comment-1728 I’m surprised as well. Fortunately there are discussions going on with the VMware PowerCLI developer team about this issue right now to help them figure out what to do about it, but it may take some time to work out the details.

]]> By: Maish http://poshoholic.com/2010/07/14/powercli-4-1-a-fork-in-the-road/#comment-1727 Thu, 15 Jul 2010 12:52:38 +0000 https://kirkmunro.wordpress.com/2010/07/14/powercli-4-1-a-fork-in-the-road/#comment-1727 I am surprised that this has not made a bigger noise..

This is not a good thing – to put it mildly…

]]>