When you configure an automated pool with floating assignments, you can specify that a particular number of machines must be available at a given time. The spare, available machines are always powered on, no matter how the pool policy is set.
Power Policy Example 1
The following table describes the floating-assignment automated pool in this example. The pool uses a machine-naming pattern to provision and name the machines.
| Desktop Pool Setting | Value |
|---|---|
| Number of machines (minimum) | 10 |
| Number of machines (maximum) | 20 |
| Number of spare, powered-on machines | 2 |
| Remote machine power policy | Power off |
When this desktop pool is provisioned, 10 machines are created, two machines are powered on and immediately available, and eight machines are powered off.
For each new user that connects to the pool, a machine is powered on to maintain the number of spare, available machines. When the number of connected users exceeds eight, additional machines, up to the maximum of 20, are created to maintain the number of spare machines. After the maximum number is reached, the machines of the first two users who disconnect remain powered on to maintain the number of spare machines. The machine of each subsequent user is powered off according to the power policy.
Power Policy Example 2
The following table describes the floating-assignment automated pool in this example. The pool uses a machine-naming pattern to provision and name the machines.
| Desktop Pool Setting | Value |
|---|---|
| Number of machines (minimum) | 5 |
| Number of machines (maximum) | 5 |
| Number of spare, powered-on machines | 2 |
| Remote machine power policy | Power off |
When this desktop pool is provisioned, five machines are created, two machines are powered on and immediately available, and three machines are powered off.
If a fourth machine in this pool is powered off, one of the existing machines is powered on. An additional machine is not powered on because the maximum of number of machines has already been reached.
