Dedicated VM setup ensures that a user is not connecting to a shared server but has a dedicated machine assigned that no other user can connect to.
Dedicated VM is a great option for users that consume a lot of resources so they don't impact the rest of the users on the server.
You can enable dedicated VMs for users by creating them their own Collection Pool. The new VM instance will count as a separate server in your itopia subscription.

Create Collection Pool

In CAS browse to Cloud Desktops > Collection Pools

Click the Green + on the right hand side to create a new collection. 

The top half is where you'll enter the Name, Description. The name is what would be used for the RDP file, so we suggest keeping it short and simple, separating words with dashes, not periods to avoid issues in the resulting collection that the broker points to.
If you have more than one region enabled for the deployment, you can select here what regions will be available for the collection

For the Image option under Boot Disk Configuration, you can either use a blank Windows server image, or use one of the custom images you have created. 

Then choose the Disk type and Size.

The bottom part is where the Autoscale settings come in. Here you would choose 1 user per server.  

On the bottom half determine the Server specs for the instance. Since this is meant for 1 user, delete the 3 default rules at the bottom by hitting the trash bin icon. 

Now you'll create a new server spec rule

Enter 0 - 1 for the user range

Choose the Machine Type or enter custom specs

Click the ADD button on the right to add the rule to the Autoscale configuration. Once done, it will look like the below screenshot:

When you enable Custom Collection Sizing, you can specify custom sizing limits in the Collection Pool, and CAS will automatically create the appropriate number of RD Session Hosts based on the sizing you specify.
When disabled, CAS will automatically create the appropriate number of RD Session Hosts based on the total number of users assigned to the collection.

You can also enable StackDriver agents installation on the servers that are assigned to the collection.

Client connection settings section allows you define basic GPOs for client connection:

Once all is ready, click Create on the bottom right. 

This process takes about 30 min to complete. You'll have to wait until the collection status goes from Pending (orange) to Ready (green).

Add user to collection

The user must be logged off for this process. When this change happens, it disables the user, moves profile disk to the new server, edits the collection settings, then enables the user again. 

Once green, head over to Cloud Desktops > Users

Find and select the user needing the dedicated VM on the list and click Edit

Now change the Collection Pool setting to be the one you just created and hit Save

This will trigger the Autoscale settings to deploy a new server. 

Allow the system to finish the new server configuration. The server will be automatically configured with an image that was selected in the Autoscaling settings. Your new server will be configured with the apps and settings that were set up for the image but you will also get the application installation tasks in the Tasks module so you can confirm they are all configured correctly.

If you don't have any image selected in your autoscaling settings, you will need to install all the applications manually in the server. The system will create tasks to install all the applications that user is assigned to in order to make it easier for you to keep track of them.

Once applications are installed and the tasks are marked as complete, you can have the user download again from and delete the old one since there will be a small change in the RDP file configuration.

💡 NOTE: In case you are using the above setup for several users inside one collection, the system will connect the user to one of the dedicated servers randomly. In case you have a custom server configuration in place that requires every user to be connected to the same server every time, you'd need to create a separate collection per every dedicated VM user.

Related articles: 

Configuring Collection Pools

Did this answer your question?