These settings define the behavior of Adobe Flash within the virtual desktop machine sessions. The settings options are shown in the following screenshot:

The configuration options for Adobe Flash Settings for Sessions are detailed here:

1. On the option for Adobe Flash Quality, click the drop-down menu (29) for the available options:
   • Do not control: This allows the web page to determine the best setting
   • Low (default): Low quality means less bandwidth consumption
   • Medium: Medium quality means average bandwidth consumption
   • High: High quality means more bandwidth consumption
2. The other configurable setting is for Adobe Flash throttling. Adobe Flash updates the screen by default, using a timer service to determine the update interval. By changing this time interval setting, you can control the frame rate of the screen updates and therefore reduce the bandwidth requirements. Click the drop-down menu (30) for the available options:
   • Disabled: Throttling is turned off
   • Conservative: The update interval is set to 100 ms
   • Moderate: The update interval is set to 500 ms
   • Aggressive: The update interval is set to 2,500 ms

The final section in this configuration screen is to configure the Mirage Settings. These settings define how VMware Mirage interacts with the virtual desktop machine images. The settings options are shown in the following screenshot:

The Mirage Settings are described here:

1. The only option here is to Override global Mirage settings (31). To enable the override, check the box.
2. Then, in the Mirage Server configuration box (32), enter the address of the Mirage server you want to use. To find out more about the VMware Mirage solution, you can read the book titled Learning VMware Mirage, by Packt Publishing.

Once you have completed the configuration settings on this screen, then click on Next > button to continue to the next configuration screen. This next screen is where you configure Provisioning Settings, as shown in the following screenshot:

As done previously, we are going to break this screen down into its different configuration sections, starting with the Basic section, as shown in the following screenshot:

The Provisioning Settings are described here:

1. The first setting in the Basic section is to Enable provisioning. Tick the Enable provisioning box (33) to basically switch provisioning on. This setting means that virtual desktop machines can be provisioned as per the configuration settings.
2. The next setting is for Stop provisioning on error (34). By checking this box, it means that provisioning will stop if there is an error during the provisioning process. This is quite important, as rather than going ahead to continue provisioning hundreds of virtual desktop machines that have errors, you would want to stop provisioning so that you can go back in and fix the issues first.

The next section to configure is for the Virtual Machine Naming, as shown in the following screenshot:

In this section, there are two options for configuring how newly built virtual desktop machines are named, either manually, or automatically. The name we are referring to here is the machine name that will also appear as the computer account in Active Directory. With this in mind, it's worthwhile picking a suitable naming convention.

In the first example, we are going to take a look at the manual option, before configuring the naming pattern method, as this method is the recommended way to name your virtual desktop machines unless there is some reason your desktops need unique non-contiguous names. To do this, perform the following steps:

1. Click the radio button for Specify names manually (35).
2. You will now see the Enter Machine Names box. In the empty box (36), type in a name for the first virtual desktop machine. In this example, we have called this machine Windows-7-001. You could also add a username to this machine if it is going to be a dedicated assignment. So in the example lab, we could enter this machine name as Windows-7-001,pvolab.competer.
3. Continue entering machines as required and then click Next > (37) when you have entered all the machine names you want to add.
4. Now you will see a list of the entered names (38). You can now either go back and enter more names or, if you have completed entering names, click the Finish button (39).
5. Finally, you will return to the Virtual Machine Naming screen where you will see that it now says 1 names entered (40) to show how many machine names have been manually entered.
6. You also have a couple of other options under the manual section. You can Start machines in maintenance mode, which allows virtual desktop machines to be customized manually before users can log in. This mode must be exited manually. You also have the option to configure # Unassigned machine kept powered on. This allows you to keep virtual desktop machines powered on ready, even if they have not been assigned to an end user yet. This option would allow you to quickly assign a machine that had already been built and customized, thereby speeding up the process.

Now we have looked at how to enter a machine name manually, we are going to look at the option to use a naming pattern, as shown in the following screenshot:

Configure the Virtual Machine Naming using the following settings:

1. Click the radio button for Use a naming pattern (41).
2. In the Naming Pattern box (42), type in a name for the virtual desktop machines. In the example lab, and for this pool, we are going to enter Win7-VM-{n}. This will result in the virtual desktop machines being named Win7-VM-1, Win7-VM-2, and so on, up to the number of machines you specify that you want to build. By using {n} somewhere in the machine name, Horizon View will add a single digit to the name in the required location. By adding {n:fixed=2}, you can allow for for two digits, and {n:fixed=3} for three, and so on. This will ensure the desktops appear in numerical order.

The next section is the Desktop Pool Sizing section.