To simplify the creation of a new Cloud Desktop deployment, itopia offers several predefined deployment types and helps you calculate the VM resources you'll need for your environment. This guide will help you understand what is created as part of each deployment type and how resources are calculated depending on the estimated number of users you specify for your deployment. This guide can also be helpful when creating an Advanced Deployment that requires you to set each component's size and configuration manually.

In both cases, it is important to note that the sizing provided by itopia is based on common usage scenarios. The sizing performed by CAS (and documented in this guide) should provide a good, cost-effective experience for most deployments; however, itopia recommends that you analyze and monitor your environment and adjust the sizing as necessary, particularly if your Cloud Desktops are running custom applications or workloads that are very sensitive to performance.

There are several aspects of a Cloud Desktop deployment that can be configured with different resources to accommodate the needs of your environment.

Infrastructure sizing refers to the underlying components of Microsoft Remote Desktop Services (RDS) and Microsoft Active Directory (AD). These components are responsible for supporting the Cloud Desktop environment, such as performing authentication, accepting end-user connections, and routing users to their respective resources. Generally speaking, these servers are sized only based on the number of concurrent users in the environment; what the users do in their Cloud Desktop environment does not affect the sizing requirements for these components. Sizing is relatively linear; as more users are added, the amount of required CPU and RAM resources increases in direct proportion.

Collection Pool sizing refers to the resources that actually host the Cloud Desktops for end users. These are the servers that run the desktops and applications that are delivered to end users. Sizing a Collection Pool depends on both the number of concurrent users and the types of workloads being performed by the users. Sizing is more complex and not necessarily linear; for example, while a single user may require ~1 vCPU for a workload, a host server with 4 vCPUs may be able to handle 6-8 users (or more) without a negative impact on performance.

Cloud Desktop Basic Deployments are designed to provide the most cost-effective solution for your environment. A Basic Deployment includes the least number of servers to support the Remote Desktop Services (RDS) environment by consolidating certain roles on the same server.

Due to their nature, Basic Deployments have certain limitations; namely, the first Collection Pool that is created as part of the initial deployment cannot be a Dedicated Collection Pool (in which each user is assigned a distinct host server). With a Basic Deployment, the first Collection Pool must be a Shared Collection Pool (in which users can connect to any host server in the pool); however, subsequent Collection Pools that are created can be configured as Dedicated Collection Pools.

Also, because the RD Broker role resides on a host server in the first Collection Pool, the first Collection Pool cannot be deleted.

Basic Deployments do not leverage the Proxy Execution Service (PES). As such, all VMs are assigned public IPs, and CAS manages the VMs using an encrypted connection across the public internet.

Choose this for: very small environments, proofs-of-concept (POC), or secondary workloads that are not business-critical.

Be aware that: Because server roles are consolidated, Basic Deployments do not offer as much scalability as other deployment types. Basic Deployments also do not offer high availability of the infrastructure roles; if certain servers (such as the RD Gateway server or the combined Broker/Session Host server) suffer a failure, access to the entire environment will be affected until the server is recovered from backup.

The following resources are deployed to support the core Remote Desktop Services (RDS) infrastructure in a Basic Deployment.

Cloud Desktop Standard Deployments are designed to provide a scalable, performant solution for your environment. A Standard Deployment provides greater role separation by assigning the RD Broker (and RD Licensing) roles to their own server. This offers additional flexibility as compared to a Basic Deployment: compute resources for the server roles can be scaled more granularly, there are no limitations on the first Collection Pool (see Basic Deployment above for more information), and there no risk that the failure of a host server will affect the entire deployment (as the critical RD Broker server is not running on a host server).

Standard Deployments include the Proxy Execution Service (PES). With the exception of the RD Gateway server, VMs are not assigned public IPs*; CAS manages the VMs using a private network route established via VPC peering.

* The RD Gateway server is assigned a public IP to allow encrypted end-user connectivity from the Internet.

Choose this for: Environments that need greater flexibility in configuration. Standard Deployments can be scaled easily and do not have limitations on configuration

Be aware that: Standard Deployments do not offer high availability (HA) of the infrastructure roles; if certain servers (such as the RD Gateway server or the RD Broker server) suffer a failure, access to the entire environment will be affected until the server is recovered from backup.

The following resources are deployed to support the core Remote Desktop Services (RDS) infrastructure in a Standard Deployment.

Cloud Desktop Enterprise Deployments are designed to provide a scalable, performant solution with full redundancy for load balancing, high availability, and fault tolerance. An Enterprise Deployment eliminates any single points of failure within the RDS infrastructure and has a greatly reduced chance of service disruption due to a server failure.

Enterprise Deployments include the Proxy Execution Service (PES). VMs in the deployment are not assigned public IPs*; CAS manages the VMs using a private network route established via VPC peering.

* The Google Load Balancer is assigned a public IP to allow encrypted end-user connectivity from the Internet.

Choose this for: Environments that run business-critical workloads that cannot sustain server-related outages.

Be aware that: Enterprise Deployments create a minimum of two servers for each role and also include additional supporting infrastructure for full redundancy; as such, the cost of an Enterprise Deployment can be significantly higher than a Standard Deployment.

The following resources are deployed to support the core Remote Desktop Services (RDS) infrastructure in an Enterprise Deployment.

Cloud Desktop Advanced Deployments allow you to define each aspect of the RDS infrastructure manually. This deployment option also exposes additional configurations such as being able to use an existing VPC network or providing a preconfigured GCP service account.

In an Advanced Deployment, CAS will pre-populate certain configurations based on the number of users you specify, but for each component you can specify whether to deploy the role on a shared server, dedicated server, or redundant servers. You can also specify the VM instance size, disk type, and disk size.

Regardless of the deployment type, CAS configures the initial resources for each infrastructure server according to the estimated number of users. In the event that the number of users for the deployment increases or decreases, these resources can be manually adjusted any time after the deployment is created.

Note that non-VM components such as the Managed Microsoft AD instance, the network load balancer, or the do not require scaling based on the number of users; these components natively support any practical number of users (well into the thousands).

In an itopia CAS deployment, a file server is required to store user profiles (using FSLogix profile containers) and shared network drives. Regardless of which Deployment type you select, you can choose what type of file server resource to deploy:

A Windows VM Instance is created to host your file shares for user profile data and shared network drives.

NetApp Cloud Volume Services is a managed service that provides SMB file shares without the cost or management overhead of a traditional Windows File Server. A Cloud Volume instance is created to host your file shares for user profile data and shared network drives.

Regardless of the deployment size or the number of users, the Cloud Volume is created with an initial size of 1 TB using NetApp's Standard performance tier. Both the volume size and the performance tier can be increased after the deployment is created.

Similar to how the RD Broker and RD Licensing roles can be installed on the first Session Host, the file server role can also be installed on that same VM instance. In this scenario, sizing for the VM instance is dependent on the Collection Pool sizing for the first Collection Pool (see below).

A data disk is created with an initial size equal to 2 GB per user for the number of users specified for the deployment.

This file server option is recommended only for small Basic Deployments (fewer than 50 users).

When a deployment is configured with highly-available RD Connection Brokers, CAS provisions a Google Cloud SQL managed instance to host the Connection Broker database. This database is relatively small and does not require significant compute or I/O performance, even when hosting thousands of user connections.

As such, CAS provisions a single sized Cloud SQL instance for all deployments with HA Connection Brokers:

Collection Pool sizing is independent of the Infrastructure sizing defined above. Sizing a Collection Pool consists of two factors:

Determining the correct sizing for a Collection Pool requires an analysis of the workloads that users will perform in their Cloud Desktops. The key metrics for identifying the resources required for a workload are:

The table below provides the preconfigured workload sizes that itopia CAS provides for Collection Pools. Administrators can choose one of the sizes below or set a custom configuration that defines both the host server size and the user density.

In order to maximize resource efficiency, itopia recommends creating different Collection Pools to support different workloads. Each Collection Pool can be configured with its own host server configuration, operating system image, and Cloud Desktop policies (such as allowing file transfers to and from the user's local device).