Published Desktops - Deployment Scenarios (mspCloud)
Background: Because the mspCloud is a multi-tenant Active Directory Environment, each tenant requires it's own Active Directory Organizational Unit, OrgVdc Network, and vApp Container. This will keep each tenant's Virtual Machine resources logically segregated for billing purposes, and provide network isolation between each tenant for improved security. If you are setting up Published Desktops for a new organization that does not yet have it's own Organizational Unit, OrgVdc Network, and vApp Container in the mspCloud, the Desktop Deployment Wizard has built in functionality to create these prerequisites as part of the Published Desktops deployment workflow. To create the first group of Published Desktops for a new Organization (tenant) in your mspCloud, see Create Published Desktops for a New Organization (mspCloud). If the organization (tenant) already has published desktops in your mspCloud or it already has the prerequisite Organizational Unit, Org Vdc Network, and vApp Container, and you would like to add additional Published Desktops to the existing organization (tenant), see Add Published Desktops to an Existing Organization.
- Create Published Desktops for a New Organization (tenant) in your mspCloud. Use this procedure to deploy Published Desktops in your mspCloud (multi-tenant domain) if you have not yet setup an Active Directory Organizational Unit, OrgVdc Network and vApp Container for the tenant.
- Add Published Desktops to an Existing Organization. Use this procedure to add additional Published Desktop Virtual Machines if your tenant already has Published Desktops or already has an Organizational Unit, OrgVdc Network, and vApp Container. This procedure is also used to create Published Desktops in a Private Domain.