You can set up your system to provision hosts with Auto Deploy, and configure the hosts to use stateless caching. If the Auto Deploy server is not available when a host reboots, the host uses the cached image.

About this task

A host that is set up for stateless caching uses the cached image only if the Auto Deploy server is not available when the host reboots. In all other situations, the host is provisioned with Auto Deploy. If you change the rule that applies an image profile to the host, and you perform a test and repair compliance operation, Auto Deploy provisions the host with the new image and the new image is cached.

Set up a highly available Auto Deploy infrastructure to guarantee that virtual machines are migrated to the host if the host reboots. Because vCenter Server assigns virtual machines to the host, vCenter Server must be available. See Set Up Highly Available Auto Deploy Infrastructure.

You can set up your environment for stateless caching by applying host profiles directly or by using PowerCLI rules.

Table 1. Setting up hosts for stateless caching or stateful installs

Workflow

Stateless caching

Stateful install

Apply host profile directly

Apply the host profile either to individual hosts or to all hosts in a folder or cluster. See Configure a Host Profile to Use Stateless Caching.

Apply the host profile either to individual hosts or to all hosts in a folder or cluster. See Configure a Host Profile to Enable Stateful Installs.

Write and apply PowerCLI rules

Set up a reference host with a host profile that has the caching setup you want. Write an Auto Deploy PowerCLI rule that provisions the host and that applies a host profile that is set up for stateless caching. See Write a Rule and Assign a Host Profile to Hosts.

Set up a reference host with a host profile that has the caching setup you want. Write an Auto Deploy PowerCLI rule that provisions the host and that applies a host profile that is set up for stateful installs. See Write a Rule and Assign a Host Profile to Hosts.