This article applies to MCIT AVD modern (v3), and does not apply to MCIT classic (v2).
MyCloudIT (MCIT) AVD deployments can “scale up” and “scale out”. Scale up means that you can increase the size of the VMs to support additional users, scale out means that you can add additional VMs as your user load increases.
MCIT automates the Installation, management and monitoring of your AVD deployments within Azure. You take 10 minutes to describe how you want it built and our automation takes the next 1 (approximate) hour to build your AVD solution in Azure. Once it’s built, you have a fully functional AVD deployment.
We will show "what we build" for an example small business called "AVD Desktops". Below are the deployment options the customer selected.
(click for full image)
Note: The "avdd" resource-name-prefix was selected in deployment.
Default network configurations:
VDSH-n
The Session Host Server(s) provide the end user delivery portion of AVD. Having multiple Session Host Servers is the ideal way to scale your deployment based on user demand. The Session Host Servers are the VMs that deliver resources to the end users. You can customize each Session Host Server after your deployment is created, but it is critical that all Session Host Servers within the same collection be configured identically. This concept is so important, that MCIT allows you to create an initial image of the Session Host Server as a template to be used by all Session Host Servers in a deployment. This is referred to as clone and Golden Image. This Golden Image should be configured for the end user experience you want to deliver to your end users. All the end user applications should be installed on the Golden Image. You can also update this Golden Image as additional applications and patches need to be deployed to your end users.
MSDC-001 (A.K.A Management Server)
The File Server role manages the shares created on the Management Server. Every Management Server has an additional volume attached to it, usually it is the “F:” drive and contains the Active Directory database and the User Profile shares (via FSLogix). FSLogix is used to ensure that whichever Session Host a user is connected to, their personal settings and documents are available (Windows user profile). The Management Server has additional storage capacity to serve as a File Server for user applications and company shares as well.
Each AVD deployment requires access to a Windows Server Active Directory Domain. The AD DS and DNS roles are installed on the management server, and the Management Server is promoted to a Domain Controller of the new Active Directory root forest created within the environment. Additionally Azure AD and the management server AD domain require syncing and this is achieved via Azure AD Connect cloud sync running on the management server.
Normal users never log into the Management Server, but users may access File Shares shared from the Management Server.
Services Topology
OAuth 2.0 authentication with Azure AD