> Automated Deployment
> All collection types, except Existing Desktops collection type, support automated deployment of virtual machines. The conditions under which new DVMs are automatically deployed are based on user demand and the values that you specify when the collection is created or updated.
> Because deploying a new DVM from a template can take several minutes or more, depending on the size of the template being copied and the performance of the storage sub-system, the Pano VDS can automatically deploy extra DVMs but not assign them to users right away. When a new user signs into the collection, the Pano VDS automatically assigns that user to one of the extra DVMs, then deploys a new DVM to replenish the extra DVMs so future users do not need to wait for a new DVM to be deployed.
> You can specify a certain number of extra DVMs that are pre-provisioned. Within this set of extra DVMs, some can be kept powered on for instant access, while others can be powered off to reduce resource utilization, but still provide fast access.
> The Extra Powered On and Extra Powered Off values in the collection properties dialog determines how many extra DVMs you want the Pano Manager to maintain for the collection, and whether they should be powered on or off:

> • | If you specify a total of two extra DVMs

> The Pano Manager starts deploying a new DVM whenever there are less than two DVMs not assigned to users. If three new users sign in at the same time, one of the users must wait for the Pano VDS to deploy a new DVM.

> • | If you specify zero extra DVMs

> The Pano Manager automatically deploys the new DVMs, but only when a new user logs in. In this case, the user logs in to the Pano client login screen and the Pano Manager asks the user to wait while the Pano VDS deploys a new DVM specifically for that user. Once the DVM is ready, the user can complete the login process.
> To turn off automated deployment for a collection, uncheck the Deploy Enabled option.

Did you find what you're looking for?
v2.5.1