Home > Business Critical Applications, VMware > vSphere 5 Auto Deploy Now Supported with vShield App and Endpoint

vSphere 5 Auto Deploy Now Supported with vShield App and Endpoint

I previously wrote an article title vSphere 5 and vShield 5 Critical Considerations regarding some important considerations when using vSphere 5 and vShield 5. At the time I originally wrote it one of those considerations was that vShield App and Endpoint would not work with Auto Deploy and were not supported. This is due to the required VIB’s not been available as a stand alone package to include in your custom image. I have some good news.

With the release of vShield 5.0.1 today you can now use vShield App and Endpoint with stateless hosts that are deployed using Auto Deploy. The necessary VIB’s are available for vShield to be included in your vSphere Image Builder Profile and custom image. This is great news for environments that want to use Auto Deploy and also vShield for security, such as in public cloud environments or security conscious environments. It would pay to read my previous article with regard to the Host Profiles considerations as they still apply. Also note that Auto Deploy is supported to be protected with vCenter Heartbeat when it is running on the same host as vCenter. This new edition will enable a larger proportion of customers to leverage Auto Deploy, while also enhancing the security capability of their environments.

This post first appeared on the Long White Virtual Clouds blog at longwhiteclouds.com, by Michael Webster +. Copyright © 2012 – IT Solutions 2000 Ltd and Michael Webster +. All rights reserved. Not to be reproduced for commercial purposes without written permission.

Advertisements
  1. Matt D
    April 13, 2012 at 7:08 am

    I have been able to find the vib for the vShield App (https://vsm-ip/bin/offline-bundles/VMware-vShield-fastpathesx5x-5.0.1-556798.zip) but this does not appear to have the Endpoint vib. Do you know where that can be found?

  2. August 19, 2012 at 6:28 am

    For what it’s worth, mounted the vShield 5.0.2 manager VMDK and the URLs have not changed. Bundle version and build number is still the same. (Now if only the documentation could be updated to do more than hint at the functionality!)

  1. No trackbacks yet.

Leave a Comment

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: