What's New with Auto Deploy in vSphere 6.7 U1
If you havent heard vSphere 6.7 U1 is now out and is loaded with all new features! If you have used 6.7 GA you may have noticed the Auto Deploy functionality did not yet make it into the long awaited vSphere Client. With vCenter Server 6.7 U1 we now have feature parity and this means Auto Deploy has been added to the vSphere Client. Lets jump in and see some of the new functionality that has been included.
What is Auto Deploy?
For those who may not be familiar with Auto Deploy I will give a brief overview on it. Auto Deploy allows you to utilize vCenter Server, a TFTP Server and Network Boot to automatically have hosts boot or install ESXi.
There are 3 types of Auto Deploy:
- Stateless - This feature allows you to have a host re-provisioned on each the hosts is rebooted with Auto Deploy.
- Stateless Caching – This feature allows you to cache the host’s image locally on the host or on a usb drive and continue to provision the host with Auto Deploy.
- Stateful Installs – This feature allows you to install hosts over the network without setting up a complete PXE boot infrastructure. After the initial network boot, these hosts boot like other hosts on which ESXi is installed.
More information on installing hosts using Auto Deploy can be found here.
What’s New with Auto Deploy
There have not been any major changes with Auto Deploy in vSphere 6.7 outside of some bug fixes and performance improvements, but 6.7 U1 included an updated workflow to manage Auto Deploy in the vSphere Client so let’s check out the new interface and see how we can configure Auto Deploy using the new interface.
We can now enable Auto Deploy and Image Builder in One-Click. No longer do we need to go into the services and edit the startup policy, and start the services.
When utilizing an Online Depot we can easily check for updates, view the software packages, image profiles and even export them as needed to be used in an offline software depot.
The workflow to create a deploy rule has also been simplified and can easily see patterns to add or use the default setting of all hosts.
We can also see the current deploy rules and choose to activate or deactivate and test them before activation
So far I have loved using the vSphere Client as it has improved on many tasks we do as a VMware Administrator. Bringing all the configuration into a single UI also makes Auto Deploy easier to manage. Hopefully this has helped highlight some of the changes in vSphere 6.7 U1. Please reach out to me with any feedback!
Share this postcomments powered by Disqus
- Why and How To Upgrade to vSphere 6.7 U1
- Upgrading Platform Services Controller and vCenter Server via the CLI Installer
- Patching your vCenter Server Appliance from 6.7 to 6.7a
- Upgrading to VMware vSphere 6.7