This page applies to the use case of using an Amazon WorkSpaces Core bundle for the automated full-clone desktop pool. When you create an automated desktop pool of full clones, you can configure certain options. Use this worksheet to prepare your configuration options before you create the pool.
Worksheet: Configuration Options for Creating an Automated Pool That Contains Full Virtual Machines Based on Amazon WorkSpaces Core
| Category | Option | Description | Enter Your Value Here |
|---|---|---|---|
| Type | Select Automated Desktop Pool. | ||
| Capacity Provider | Select Full Virtual Machines and select the capacity provider in which you want the pool's instances to reside. | The system populates the list with the capacity providers configured in Servers > Capacity Providers that are supported for use in an automated desktop pool. | |
| User Assignment | The following settings determine how end users are assigned to the desktops in this pool. | ||
| Select Floating or Dedicated. | Choose the type of user assignment:
| ||
| Enable Automatic Assignment | In a dedicated-assignment pool, a machine is assigned to a user when the user first logs in to the pool. You can also explicitly assign machines to users. If you do not enable automatic assignment, you must explicitly assign a machine to each user. You can assign machines manually even when automatic assignment is enabled. See Assign a Machine to a User in a Dedicated-Assignment Pool. | ||
| Enable Multi-User Assignment | In a dedicated-assignment pool, you can assign multiple users to each machine in the pool. Multi-user assignment is not supported for automatic user assignment desktop pools. If an assigned user has a connected or disconnected session on a multi-user assignment machine, other assigned users will be unable to launch a session on that machine. See Assign a Machine to a User in a Dedicated-Assignment Pool. | ||
| Desktop Pool Identification | The following settings allow you to identify and describe the pool you are creating. | ||
| ID |
The unique name that identifies the pool in Horizon Console.
If multiple capacity providers are configured in your Horizon environment, make sure that another capacity provider is not using the same pool ID.
For Amazon WorkSpaces Core, the pool's instances will be auto-tagged with this ID so that you can easily find them in the AWS WorkSpaces UI if you choose to. You cannot edit or change the Desktop Pool ID after you create the desktop pool. | ||
| Display Name | The pool name that users see when they log in from a client device. If you do not specify a display name, the pool ID is displayed to users. | ||
| Directory | Select the domain in which to place the pool's instances. The system retrieves these values from the capacity provider you select to use for this pool. | ||
| Bundle | The Amazon WorkSpaces Core bundle to use as the source for the pool's instances.
Select the bundle which you prepared for this purpose, according to Amazon WorkSpaces Core - Creating and Preparing Sources for Automated Desktop Pools | ||
| Provisioning Settings | The following settings allow you to provide details on how the pool is provisioned. | ||
| Enable Provisioning |
You can enable or deactivate virtual machine provisioning in the desktop pool. When you deactivate provisioning in the desktop pool, Horizon 8 stops provisioning new virtual machines for the desktop pool. After you deactivate provisioning, you can enable provisioning again.
Before you change a desktop pool's configuration, you can deactivate provisioning to ensure that no new machines are created with the old configuration. You can also deactivate provisioning to prevent Horizon 8 from using additional storage when a pool is close to filling up the available space. When you create a desktop pool and deactivate this option, Horizon 8 creates a desktop pool without any virtual machines. If you edit a desktop pool and deactivate provisioning, Horizon 8 does not allow any new virtual machines to be provisioned in this desktop pool. End users can still connect to existing virtual machines. | ||
| Stop Provisioning on Error | You can direct Horizon 8 to stop provisioning or continue to provision virtual machines in a desktop pool after an error occurs during the provisioning of a virtual machine. If you leave this setting selected, you can prevent a provisioning error from recurring on multiple virtual machines. | ||
Virtual Machine Naming:
| Pools based on Amazon WorkSpaces Core instances use a naming pattern.
Provide the pattern. The pattern you specify is used as a prefix in all the machine names, followed by a unique number to identify each machine. Note: Variables are unsupported in naming patterns for these pool machines sourced from a WorkSpaces Core workspace. | ||
Provision Machines:
|
When you select to provision machines on demand, you specify a minimum number of machines in the pool. That minimum number of machines is created when the system initially creates the pool, and then as users connect to the pool for the first time or as you assign machines to users, the system creates additional machines.
When you select to provision machines up-front, the system creates all of the machines when it initially creates the pool, up to the number specified in the Desktop Pool Sizing. | ||
| Desktop Pool Sizing |
| ||
| Desktop Pool Settings | The following settings determine the desktop state, power status, and display protocol when a virtual machine is not in use. | ||
| State |
| ||
| Connection Server Restrictions |
| ||
| Category Folder | Specifies the name of the category folder that contains a Start menu shortcut for the desktop pool entitlement on Windows client devices. For more information, see "Configuring Shortcuts for Entitled Pools" in the Horizon 8 Administration document. | ||
| Client Restrictions | Select whether to restrict access to entitled desktop pools from certain client computers. You must add the names of the computers that are allowed to access the desktop pool in an Active Directory security group. You can select this security group when you add users or groups to the desktop pool entitlement. | ||
| Remote Machine Power Policy |
Determines how a virtual machine behaves when the user logs off of the associated desktop. For Amazon WorkSpaces Core, the choices are:
| ||
| Log Off After Disconnect |
Applies only to dedicated user assignments.
| ||
| Show Assigned Machine Name | Applies only to dedicated user assignments.
With this choice, when a user logs in to their client, the client displays the host name of the underlying machine instead of displaying the desktop pool display name. If no machine is assigned to the user, then the client displays Display Name (No Machine Assigned) for the desktop pool. | ||
| Show Machine Alias Name | Applies only to dedicated user assignments.
With this choice, when a user logs in to their client, the client displays the machine alias name set for the assigned users of the machine instead of displaying the desktop pool display name. If no machine alias name is set but the Show Assigned Machine Name is set, then the client displays the machine host name for the desktop pool. Otherwise, the desktop display name appears for the desktop pool in Horizon Client. | ||
| Remote Display Settings | The following settings describe how desktops are displayed to end users. | ||
| Default Display Protocol |
For a pool based on Amazon WorkSpaces Core instances, Omnissa Horizon Blast is the only display protocol supported.
| ||
| Session Collaboration | Select Allowed to allow users of the desktop pool to invite other users to join their remote desktop sessions. Session owners and session collaborators must use the Horizon Blast protocol. |
What to read next
Was this page helpful?