«

»

Dec 17

Scripted Full-Deploy of vRealize Automation 6.2 (vRA)

The title says it all. As I’ve talked with many folks around the globe either through social media, email, or in person. One thing people seem to always want in regards to vRA, is a way to quickly deploy it to play with it, test something, evaluate it, etc. Currently there is no quick solution.

I’ve tried to help alleviate some of the pain by creating the vRA 6.2 Pre-Req Automation Script, which has seen over 20,000 downloads since I posted the vCAC 6.0 version last December. To make things EVEN EASIER, I’ve thrown together a script that will:

  • Deploy the Identity Server
  • Configure the Identity Server
  • Deploy the vRA Appliance
  • Configure the Appliance
  • Verify DNS (Forward and Reverse) entries

 

But that’s not all, If you have a Windows 2008r2 VM (untested on 2012 r2), with an internet connection, the script will also:

  • Perform all vRA Prerequisite tasks
  • Set Batch Logon’s
  • Download and install .Net 4.5.2
  • Download and install Java JRE 1.7 64-bit
  • Set the Java_Home variable
  • Firewall configuration
  • Download and install SQL Server 2008r2 SP1 Express
  • Configure SQL for use with vRA (Includes opening the correct port and enabling the IPv4 connection)
  • Grab and install the needed vRA Appliance certificate
  • Download all vRA Component installers
  • Install and Configure the vRA Components
  • Install and configure a Distributed Execution Manager (DEM) Worker
  • Install and configure a Distributed Execution Orechestrator (DEO)
  • Install and configure the Web API (WAPI)
  • Install and configure  the vSphere Agent

 

Now I know you are reading this and saying “BRIAN! Leave some of the fun for me!!” (ok ok maybe not). This will bring your vRA deployment to the point where you will then login to the portal using the https://FQDNofvRA/shell-ui-app/  where you will then create your identity stores, tenants, and so on and so forth. The rest of the installation can be customized by following the vRA 6.2 Installation Guide. 

Maybe if I get ambitious enough in the future I’ll script part of that as well 🙂

Ok, so now that I have your attention after listing off everything this script will do, let’s take a look at it and see how it works.

PREREQUISITES:

You will need PowerCLI 5.8 r1 to perform this install.

You will need a Windows Server 2008r2 virtual machine with an internet connection (yes it can be done without but there’s a bit of tweaking to do that, so just bear with me and give it a connection)

You will also need to populate forward and reverse DNS with the settings for these VM’s prior to running the script.

If you take a look at the script, you’ll notice there are a number of variables to set to make this work correctly. Starting with line 28:

I’ve added in more comments than I regularly do to ensure that users understand what they need to enter for each variable. Failure to give each variable a value unless otherwise stated in the code, will result in a failed vRA deployment.

Screenshot 2014-12-17 15.03.31

In the above screenshot you can see that you will need to add the vCenter credentials. You will also add the VM Name of the Identity Server and vRA Appliance, along with a password for each. If these appliances haven’t been deployed, this information will be used to deploy and configure. If these appliances HAVE been deployed, we still need this information. and of course DO NOT FORGET TO ADD A LICENSE KEY HERE OR THE DEPLOYMENT WILL NOT WORK!

Moving on: We’ll do the same thing for the Windows IAAS machine. Like I stated earlier, I have only tested this with Server 2008r2 (if you don’t have a copy go download the 180-day trial). I did test this using the credentials “Administrator” and password “VMware1!”

Add in whatever details you wish to use for the Certificate generation and then move into the vCAC Component variables.

Screenshot 2014-12-17 15.03.10

As you can see, if you are using this to deploy both OVA’s and you do not specify their location, the script will look in the c:\temp\ folder and find and use them.

RUNNING THE SCRIPT

Upon executing this script in PowerShell, the script will query the DNS server to ensure your DNS entries are correct prior to proceeding. If you do not have 3 valid lines under both forward and reverse here, hit ‘N’ and go fix your DNS issue. This will make things much easier to verify and take care of DNS prior to starting the installation.
Screenshot 2014-12-17 15.04.26

The next prompt will happen after the PowerShell session connects to vCenter. It will present you with 4 options:

  1. Deploy & Configure both Virtual Appliances, Install & Configure IAAS (essentially the full install)
  2. Configure both Virtual Appliances (Already deployed OVAs), Install &  Configure IAAS
  3. Just Install & Configure IAAS (Pre-reqs, SQL, and vRA Software)
  4. Exit

Most people will tend to choose option 1.

Screenshot 2014-12-17 15.04.41

 

Once the script starts to install the vRA components, you can tail the install log by consoling the IAAS VM, opening PowerShell and running: get-content c:\temp\vcac-config.log -wait

At the end of the deploy you should see a something like this at the end of the log: vCloud Automation Center Server Configuration is complete.

Screenshot 2014-12-17 15.46.36

 

If you’ve entered all the values into the variables correctly and followed this post, about 30-40 minutes later, you’ll have a vRA deployment up and running and ready to finish setup.

Please feel free to provide feedback and comments below or on twitter: @vBrianGraf

# Also a shoutout to William Lam (www.virtuallyghetto.com) for originally creating a version for vCAC 6.0. That version was fantastic but also required a few more steps than this. Also vCAC has had a number of changes in 6.1 and 6.2 that required changes to his code, however it’s what got the idea rolling and jumpstarted for 6.1 (although I didn’t release it)  and 6.2 (which you can find below).

DOWNLOAD NOW

 

 

17 comments

Skip to comment form

  1. Cesare G. Rossi

    Brian,

    many compliments, great work!

    Only one doubt: where I must put the OVA files for importing to vCenter?

    1. Brian Graf

      you can place them in c:temp

  2. Cesare G. Rossi

    Brian,

    a couple of questions:

    – the IaaS part of vRA will be installed on the same Windows 2008 R2 machine that execute the script?
    – your script also install SQL Server on the IaaS machine?

    Thank You

    1. Brian Graf

      Cesare,
      the Iaas part will be installed on the windows VM specified in the script. That could mean that it is the same machine you are executing the script from but I’ve always had a different VM where it will install.

      As the post says, this will do a full deploy of vRA 6.2. This will install .Net, Java, SQL Express, and all of the vRA components.

  3. Pankaj Chhabra

    Brian,

    I am using external DNS server in my lab.

    One question – Do we need to set up Active Directory on the Windows Server 2008 R2?.

    Thanks,
    Pankaj

    1. Brian Graf

      You will need either active directory or an LDAP connection to setup the users and tenants of vRA once it is installed.

  4. karlo

    hi Can I used Windows 2008 R2 with Service Pack 1?

    thanks

    1. Brian Graf

      it should

  5. Faisal Fayyaz

    A few questions:
    – You mentioned about scenario if IaaS Windows Server did not have an internet connection. What modifications would you need to make to the script for such a scenario?
    – Will the vRA 6.2 script above work for vRA 6.2.1 ?
    – Will your vRA 6.2 Pre-Req Automation Script work for vRA 6.2.1 ?
    Thanks, Faisal

    1. Brian Graf

      Faisal,
      Take a look at the script itself. You’ll need to download the executables that normally get downloaded automatically, you’ll also need to point (if doing Server 2012) the script to the Installation media to add certain roles during the script’s running.

      These scripts should work fine with vRA 6.2.1

  6. Eric

    Brian,
    Great Work!!
    For some reason, I cannot connect my lab to the internet and I’m new to play with script. After reading your script I didn’t find the part that install .Net Framework and JAVA 1.7.

    Only one question:
    -Is that means I have to install them by myself? Or the script will also be able to install them if I just put the .exe files into C:temp?

    Thanks,
    Eric

    1. Eric

      Brian,
      I think they may be included in $MBED_AUTOMATIONSCRIPT . Just for confirmation.
      Thanks,
      Eric

  7. Zahir

    Hi I got install the vcac version 6.2.1 with the latest auto-script. But in the prerequisite still show Not OK – IIS Server. I install and reinstall the IIS component few times, but the result still the same. Any solution or which of the requirement that I need to check first?

  8. Clement

    Hi Brian,

    Firstly, thanks for the script! I’ve successfully ran this script all the way until the IAAS VM installation and it gets stuck on the “Register Catalog” portion. It is giving me an error with regards to “Could not establish trust relationship for the SSL/TLS secure channel” and goes on to say “The remote certificate is invalid according to the validation procedure”.

    I’m using a Windows 2008R2 Ent SP1 VM and before running this script, I basically joined it to a domain, make sure host name maps to dns and IP, removed windows firewall and disable UAC.

    Is there something that I did not do on my end on the IAAS VM? Appreciate if you could advise on the issue.

  9. Paul

    Thanks for this script! Just wanted to update you that I ran this under Win2k12R2 and PowerShell CLI 6.0, but had to modify the lines containing get-pssnapin as follows:
    “get-pssnapin -name VMware.VimAutomation.Core” to
    “get-module -name VMware.VimAutomation.Core”

    The deployment was successful and much easier thanks to this script!
    Cheers!

  10. Brian Graf

    correct Paul, I wrote this before PowerCLI 6.0 came out. as a result all scripts being run with PowerCLI will need to replace ps-snapin with import-module. similarly I prefer to use the following logic:

    if ( !(Get-Module -Name VMware.VimAutomation.Core -ErrorAction SilentlyContinue) ) {
    . “C:Program Files (x86)VMwareInfrastructurevSphere PowerCLIScriptsInitialize-PowerCLIEnvironment.ps1”
    }
    so that it doesnt matter which version of PowerCLI is being run

  11. Vamsi Mohun

    Hi Brian, For switch(1) towards the end of the script, calls are made to both Configure_vCACAP and to Configure_IAAS. The code looks similar in both. What’s the difference between the two? It seems both of them Install & Configure the SQL Server and the vRA Windows Appliance. I am new to PowerCLI, so it’s possible the question is elementary.

    Thanks

Leave a Reply

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code class="" title="" data-url=""> <del datetime=""> <em> <i> <q cite=""> <s> <strike> <strong> <pre class="" title="" data-url=""> <span class="" title="" data-url="">

12 + nineteen =