In Get-View Part 1: Introduction I introduced the advanced feature Get-View and a little bit about what it does. Before getting into the views and extension data topic I wanted to add a few thoughts as a segway into this post.
As the Pre-Req Automation Script has been such a hit over the past 12 months I continue to update it for the requirements of each release of vCloud Automation Center and now vRealize Automation. I have received scores of emails and tweets telling me how it saved the users hours of hassle. And so here I am, releasing a Pre-Req Automation Script for vRA 6.2 which is now Generally Available on MyVMware.
The new version can be grabbed from Github HERE. For those that are new to Github you CANNOT just right-click on this link and hit ‘save as’. that will not work. You will want to click on the file, choose “Raw” and copy the script to a .ps1 file on your machine. (There were several comments on my previous blogs about the confusion of downloading the script)
How to use the script
There are a few new options in this script that I added last version, but didn’t take the time to really blog about. So let’s get into it. If the script is run “out of the box” you’ll be presented with something like this:
I am happy to announce a new fling ‘PowerActions for vSphere Web Client’ PowerActions integrates the vSphere Web Client and PowerCLI to provide complex automation solutions from within the standard vSphere management client. In short, we can now run PowerShell/PowerCLI scripts from the Web Client!
in Part 1 we discussed how to add a configuration to the OvfConfiguration object (See Post HERE). In this post we will quickly discuss how to leverage the new –OvfConfiguration parameter when deploying vApps.
As many of you have read in the release notes of vSphere PowerCLI 5.8 r1 we have introduced a new cmdlet ‘Get-OvfConfiguration’ along with a new parameter on the ‘Import-vApp’ cmdlet to allow users to specify and set the OVF properties for an OVF deployment.
In Part 1 we will dive in to the Get-OvfConfiguration cmdlet and how to add your Continue reading →
As many of you are now seeing the announcement that vCloud Automation Center 6.1 is GA, you will most likely already be downloading the bits. Let me save you all some time once again with the latest Prerequisite Automation Script.
There have been a lot of downloads of my initial vCAC Prereq Automation script that I released in December 2013. I had written that specifically for Server 2008 and as some of you found out, it didn’t work for Server 2012. Although there was only a slight modification needed, many were unsure of what to change. This led me to creating v2 of the script, which also includes another feature.