PowerCLI 11.0 is Out – Easy Update and Features Galore!

PowerCLI fans unite and celebrate as the launch of the latest edition is now public.  If you’re a reader of my blog then there is a good chance you probably found me from PowerShell or PowerCLI  content which also is a hint of much more to come in the next while.

The first thing you will want to do as the new release is out is to make sure you get your install up to date.  If you haven’t already deployed PowerCLI using the modular approach and get past a couple of common gotchas with these blogs.

This is the list of added goodness as shared from the official PowerCLI blog on the update

  • Added a new Security module
  • Added new cmdlets for Host Profiles
  • Added a new cmdlet to interact with NSX-T in VMware Cloud on AWS
  • Support for vSphere 6.7 Update 1
  • Support for NSX-T 2.3
  • Support for Horizon View 7.6
  • Support for vCloud Director 9.5
  • Multiplatform support for the Cloud module
  • Updated the Get-ErrorReport cmdlet
  • Removed the PCloud module
  • Removed the HA module

These are handy as you get rolling with the most recent versions of vSphere and if you are a vCloud Director fan.  The security updates are probably the most prominent with the update to adding more with both native vSphere 6.7 Update 1 and the vSphere Platinum edition.

Running the Update using Update-Module in PowerShell

This example here shows how to easily update using PowerShell Module management which I’m showing from a Mac OSX installation.

You want to check to see which version you have first which is done using the Get-Module -Name VMware.PowerCLI first:

That confirms our current version.  This happens to be running 10.1.1 before the update.  All you have to do to get the latest update is run the Update-Module -Name VMware.PowerCLI and walk through the prompts. You will be asked about whether to trust the repository or not (spoiler alert:  you have to say Yes)

NOTE: If you’re reading this after future updates beyond 11.0 then you will get the latest edition available at that time from the PSGallery.

Here’s a quick 2 minute video to show you the install in action!

Happy Scripting!




vSphere Announcement:  Goodbye C#, Hello HTML5 Client

No more C# client. It’s a new world where HTML 5 is the way to go. This is a very exciting announcement as we look towards the new iteration of VMware vSphere as it begins to trickle into the roadmap in the coming months. The web client has been something that has been a big push as a target for the day-to-day management of your VMware infrastructure.

The challenge is that a few people have one thing to say about this based on some experience in using the current iteration of the Flash based web UI…

But, I like the C# Client…

The real question is “why do we like it?”

– Performance – Let’s face it, we have seen some massive increase in speed when using the web client, but it is still not as quick as the native client. This is a reality that we will face, but I believe there will be additional improvements.
– Reliability – The Flash UI of the current web client has been know to be slow, and to fail altogether when used regularly.
– OVF imports work – the vSphere Client Plugin needed for the current web client will be retired as we move into the next HTML5 interface, so this will be addressed as a long-standing issue with the web client and common functionality.
– User Experience – we have grown used to the workflows and task flow as we do a lot of traditional administrative functions. This is less about it being “right” today, and more about what folks are just used to.

The reason that the new HTML5 client will be an advantage is that all of the features within the current Flash client will be available, as well as some of the legacy features that were left behind in the full, or what is often called the C# (C-sharp) client.

Remember that UI and UX are Two Different Things

This is the sticking point that people forget sometimes. UI is a view, whereas UX is literally user experience. That is the difference from what you see on the screen, to how you perform tasks within that screen. It is also notable that there are more than just VMware engineers who build features for the vCenter client. External partners have been asked repeatedly about making it easier to consume their platforms within the same UI as the day-to-day vCenter tasks.

There will be some challenges for external partners to make sure that they are all fully ready for the new HTML5 only interface. We have seen a lot of partner technologies ignore client integration altogether in order to avoid compatibility issues. That breaks from the elusive (aka unreachable) goal of the Single Pane of Glass.

What will it look like?

There has been the HTML5 vSphere Host Client fling available for a while (http://blogs.vmware.com/vsphere/2016/03/vmware-vsphere-html5-web-client-fling.html), so it isn’t difficult to see how the move is going to go. In fact, the fling is now a part of the general availability product now and is included in the core platform for vSphere 6.x from now forward. I’m a fan, but we also know that using multiple interfaces to achieve certain admin functions is a pain in the backside.

html-web-fling

Image source: http://blogs.vmware.com/vsphere/2016/03/vmware-vsphere-html5-web-client-fling.html

Features are separated by client today. VSAN can only be managed by the web client. vSphere replication can only be affected by the web client. vFlash Read Cache can only be handled in the web client. You get where we are going. New features will only be developed towards the web client, and the transition of the last stragglers (SRM and some others) will be completed by the next iteration of vSphere.

Looking forward to the updated client that can be used across all browsers, and all devices. I’m a Mac user most of the time, and the current Flash UI plugin does not work on OSX with Chrome unless you literally open up the rights to give the browser complete root access…which nobody in their right, security-oriented mind would ever do.

Let’s see what the next few weeks brings as we prepare for the inevitable launch, or at least the announcement, of the newest vSphere product line at VMworld in Las Vegas.




Fixing Ubuntu Vivid Vervet apt error for CDROM source: sed one-liner goodness

While I tend towards mainly Ubuntu 14.04 LTS (Trusty Tahr) as my core Linux derivative, it is time to move on to the 15.x stream and embrace the Ubuntu 15.04 (Vivid Vervet) for the next bunch of work I’ll be doing.

A common practice is that I run the installation and then do an apt-get update to make sure I’ve got the latest goodness from the source repository. If you’ve tried this after doing a CD or ISO install of Vivid Vervet, you will discover that it leaves the CD-ROM as an apt source.

This is what the process will look like out of the box:

apt-update-error1

apt-update-error2

This leaves you with that sad, can’t be updated feeling.  Nobody likes that feeling.

Removing the CD-ROM apt source with sed

Because I’m fundamentally lazy, I decided that the process of using nano to edit the /etc/apt/sources.list file is a few too many steps.  Plus, I’m a vim lover, but it isn’t installed and can’t be because of the apt source issue.

Note:  I also recognize that true laziness would mean using Vagrant, but there are times when an ISO install happen, so I wanted to share this 🙂

Sed is a great little tool baked into Linux, so let’s just do the process using sed and the one-liner as follows:

sudo sed -i 's/deb cdrom/#deb cdrom/g' /etc/apt/sources.list

sed-fix-apt-source

That just means that we stream the /etc/apt/sources.list file and replace the instances of deb cdrom with #deb cdrom which turns it into a comment line in the file.

There is a comment line in the sources.list file which will get an extra hash in front of it, but I’m doing this rather quick and dirty.

Once we run that command we can now run the apt-get update again now and it looks much better:

apt-update-success

Now you can update as needed.  Hope this is a simple, but helpful tip!




VMware Workstation 10.0.1 is available!

If you are a user of VMware Workstation you will be pleased to know that there is an incremental update available now with the 10.0.1 release today.

update-available

What’s New with 10.0.1

This is a minimal update to the Workstation 10.x product. Aside from a number of bug fixes, there is a significant addition for those who are working with Windows guests running Windows 8.1 or Windows Server 2012 R2. With the 10.0.1 update, you will get to enjoy the “easy install” wizard that has been available for previous Windows and Linux guests.

easy-install

Full release notes for the 10.0.1 update are available here: http://www.vmware.com/support/ws10/doc/workstation-1001-release-notes.html and of course you can download the full product including this release from the VMware Workstation product site here: http://www.vmware.com/products/workstation/

For existing users of VMware Workstation, you should be prompted for the update when you launch the product, but you may also initiate the update by going to the Help menu and clicking on Software Updates.

update-menu

For brand new users, click the image below to download a free 30 day trial. Editions available for Windows and Linux installations!

VMW-BXSHT-WORK10