您现在访问的是微软AZURE全球版技术文档网站,若需要访问由世纪互联运营的MICROSOFT AZURE中国区技术文档网站,请访问 https://docs.azure.cn.

Windows 虚拟桌面概念证明Windows Virtual Desktop proof of concept

Contoso cloud 采纳团队在部署其最终用户桌面之前,会通过完成并测试概念证明来验证 Azure 登陆区域和最终用户网络容量的配置。Before the Contoso cloud adoption team deploys its end-user desktops, it validates the configuration of the Azure landing zone and end-user network capacity by completing and testing a proof of concept.

下面对迁移过程的方法进行了简化,以概述概念验证实现。The following approach to the migration process is simplified to outline a proof-of-concept implementation.

  1. 评估:团队使用 (VM) 大小的默认虚拟机部署主机池。Assess: the team deploys host pools by using the default virtual machine (VM) sizes. 评估数据有助于团队确定所需的并发用户会话数,以及支持这些并发会话所需的 Vm 数量。Assessment data helps the team identify the expected number of concurrent user sessions and the number of VMs required to support those concurrent sessions.
  2. 部署:团队使用 Azure Marketplace 中的 Windows 10 库映像和评估步骤1中的规模调整,为共用桌面 创建主机池Deploy: the team creates a host pool for pooled desktops by using a Windows 10 gallery image from Azure Marketplace and the sizing from assessment step 1.
  3. 部署:团队为已迁移的工作负荷 创建 RemoteApp 应用程序组Deploy: the team creates RemoteApp application groups for workloads that it has already migrated.
  4. 部署:团队创建用于存储用户配置文件 的 FSLogix 配置文件容器Deploy: the team creates an FSLogix profile container to store user profiles.
  5. 版本:团队测试应用程序组和部署的桌面的性能和延迟,以实现用户的采样。Release: the team tests the performance and latency of application groups and deployed desktops for a sampling of users.
  6. 版本:团队加入其最终用户向他们讲授如何通过 Windows 桌面客户端web 客户端Android 客户端、 macOS 客户端或 iOS 客户端进行连接。Release: the team onboards its end users to teach them how to connect through Windows desktop client, web client, Android client, macOS client, or iOS client.

假设Assumptions

概念证明方法可满足某些生产需求,但它是基于多个假设构建的。The proof of concept approach could meet some production needs, but it's built on a number of assumptions.

对于 Windows 虚拟桌面的任何企业迁移,以下所有假设都不太可能证明满足此条件。It's unlikely that all the following assumptions will prove to be true for any enterprise migration of Windows Virtual Desktop. 采用团队应假设生产部署需要单独部署,这一点更接近于在 Windows 虚拟桌面评估过程中所确定的生产需求。The adoption team should assume that the production deployment will require a separate deployment that more closely aligns to the production requirements that it identifies during the Windows Virtual Desktop assessment. 假设:The assumptions are:

  • 最终用户连接到 Azure 中分配的登录区域。End users have a low-latency connection to the assigned landing zone in Azure.
  • 所有用户都可以使用共享的桌面池。All users can work from a shared pool of desktops.
  • 所有用户都可以使用   Azure Marketplace 中的 Windows 10 企业多会话映像。All users can use the Windows 10 Enterprise multi-session image from Azure Marketplace.
  • 所有用户配置文件都将迁移到 FSLogix 配置文件容器的 Azure 文件、Azure NetApp 文件或基于 VM 的存储服务。All user profiles will be migrated to either Azure Files, Azure NetApp Files, or a VM-based storage service for the FSLogix profile containers.
  • 所有用户均可由具有每个虚拟中心处理 (单元的六个用户的 vCPU) 和 4   千兆字节 (GB) RAM 的公共角色进行描述, 如 VM 大小调整建议All users can be described by a common persona with a density of six users per virtual central processing unit (vCPU) and 4 gigabytes (GB) of RAM, as per the VM sizing recommendations.
  • 所有工作负荷都与 Windows   10 企业多会话兼容。All workloads are compatible with Windows 10 Enterprise multi-session.
  • 虚拟机和应用程序组之间的延迟可供生产使用。Latency between the virtual desktops and application groups is acceptable for production usage.

若要根据概念证明配置参考来计算 Windows 虚拟桌面方案的成本,团队需使用 " 美国东部"、" 西欧" 或 " 东南亚" 这一价格计算器。To calculate the cost of the Windows Virtual Desktop scenario based on the proof-of-concept configuration reference, the team uses the pricing calculator for East US, West Europe, or Southeast Asia.

备注

这些示例都使用 Azure 文件作为用户配置文件的存储服务。These examples all use Azure Files as the storage service for user profiles.

后续步骤Next steps

有关云采用之旅的特定元素的指南,请参阅:For guidance on specific elements of the cloud adoption journey, see: