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

Windows 虚拟桌面部署或迁移Windows Virtual Desktop deployment or migration

本文中的指南假设你已 为 Windows 虚拟桌面) 建立了一个计划 评估了桌面部署要求已完成了概念证明,现在可以迁移或部署你的 windows 虚拟桌面实例。The guidance in this article assumes that you've established a plan for Windows Virtual Desktop), assessed the desktop deployment requirements, completed a proof of concept, and are now ready to migrate or deploy your Windows Virtual Desktop instances.

初始范围Initial scope

Windows 虚拟桌面实例的部署遵循类似于 概念证明 过程的过程。The deployment of Windows Virtual Desktop instances follows a process that's similar to the proof of concept process. 使用此初始范围作为基准来解释评估输出所需的各种范围更改。Use this initial scope as a baseline to explain the various scope changes that are required by the output of the assessment.

部署和迁移包括角色迁移、应用程序迁移和用户配置文件迁移。Deployment and migration consist of persona migration, application migration, and user profile migration. 根据工作负荷评估的结果,可能会对其中每个迁移任务进行更改。Depending on the results of the workload assessment, there will likely be changes to each of those migration tasks. 本文可帮助确定根据评估反馈,范围将发生变化的方式。This article helps identify ways that the scope would change based on the assessment feedback.

迭代方法Iterative methodology

每个角色都可能需要以前概述的初始范围的迭代,从而生成多个主机池。Each persona will likely require an iteration of the previously outlined initial scope, resulting in multiple host pools. 根据 Windows 虚拟桌面评估,采纳团队应根据角色或每个角色的用户数来定义迭代。Depending on the Windows Virtual Desktop assessment, the adoption team should define iterations that are based on the number of personas or users per persona. 将该过程分解为角色驱动的迭代有助于降低对业务的更改速度影响,并使团队能够专注于对每个角色池进行适当的测试或加入。Breaking the process into persona-driven iterations helps to reduce the change velocity impact on the business and allows the team to focus on proper testing or onboarding of each of the persona pools.

作用域注意事项Scope considerations

要迁移或部署的每个角色组的设计文档中应包括以下每个注意事项集。Each of the following sets of considerations should be included in the design documentation for each persona group to be migrated or deployed. 将范围注意事项分解到前面讨论的 初始范围之后,就可以开始部署或迁移。After the scope considerations are factored in to the previously discussed initial scope, the deployment or migration can begin.

Azure 登陆区域注意事项Azure landing zone considerations

在部署角色组之前,应在 Azure 区域中创建一个登陆区域,该区域需要支持每个要部署的角色。Before you deploy the persona groups, a landing zone should be created in the Azure region that's required to support each persona to be deployed. 应根据 登陆区域审查要求评估每个分配的登录区域。Each assigned landing zone should be evaluated against the landing zone review requirements.

如果分配的 Azure 登陆区域不满足你的要求,则应为对环境进行的任何修改添加作用域。If the assigned Azure landing zone doesn't meet your requirements, scope should be added for any modifications to be made to the environment.

应用程序和桌面注意事项Application and desktop considerations

某些角色可能依赖于旧解决方案,这些解决方案与 Windows   10 企业多会话不兼容。Some personas might have a dependency on legacy solutions, which are not compatible with Windows 10 Enterprise multi-session. 在这些情况下,一些角色可能需要专用桌面。In these cases, some personas might require dedicated desktops. 在部署和测试之前,可能不会发现此依赖关系。This dependency might not be discovered until deployment and testing.

如果在此过程中发现了这些延迟,则将来的迭代应分配到旧应用程序的现代化或迁移。If they're discovered late in the process, future iterations should be allocated to modernization or migration of the legacy application. 这将降低桌面体验的长期成本。This will reduce the long-term cost of the desktop experience. 应根据现代化与专用桌面相关的额外成本的整体定价影响来确定这些未来迭代的优先级和完成时间。Those future iterations should be prioritized and completed based on the overall pricing impact of modernization versus the extra cost associated with dedicated desktops. 为了避免管道中断和业务结果的实现,这种优先顺序不应影响当前迭代。To avoid pipeline disruptions and the realization of business outcomes, this prioritization should not affect current iterations.

某些应用程序可能需要修正、现代化或迁移到 Azure,以支持所需的最终用户体验。Some applications might require remediation, modernization, or migration to Azure to support the desired end-user experience. 这些更改可能会在发布后发布。Those changes are likely to come after release. 或者,当桌面延迟可能会影响业务功能时,应用程序更改可能会为某些角色的迁移创建阻塞依赖关系。Alternately, when desktop latency can affect business functions, the application changes might create blocking dependencies for the migration of some personas.

用户配置文件注意事项User profile considerations

初始作用域假设你使用的是基于 VM 的 FSLogix 用户配置文件容器The initial scope assumes that you're using a VM-based FSLogix user profile container.

可以使用 Azure NetApp 文件来托管用户配置文件You can use Azure NetApp Files to host user profiles. 这样做将需要范围中的几个额外步骤,其中包括:Doing so will require a few extra steps in the scope, including:

  • 每个 NetApp 实例: 配置 NetApp 文件、卷和 Active Directory 连接。Per NetApp instance: Configure NetApp files, volumes, and Active Directory connections.
  • 每个主机/角色: 在会话主机虚拟机上配置 FSLogix。Per host/persona: Configure FSLogix on session host virtual machines.
  • 每个用户: 将用户分配到主机会话。Per user: Assign users to the host session.

你还可以使用 Azure 文件来托管用户配置文件You can also use Azure Files to host user profiles. 这样做将需要范围中的几个额外步骤,其中包括:Doing so will require a few extra steps in the scope, including:

  • 每个 Azure 文件实例: 配置 "存储帐户"、"磁盘类型" 和 "Active Directory 连接" (Active Directory 域服务 ("AD DS",为) 用户组分配 Azure 基于角色的访问控制访问权限,应用新的技术文件系统权限,并获取存储帐户访问密钥。Per Azure Files instance: Configure the storage account, disk type, and Active Directory connection (Active Directory Domain Services (AD DS) is also supported, assign Azure role-based access control access for an Active Directory user group, apply new technology file system permissions, and get the storage account access key.
  • 每个主机/角色: 在会话主机虚拟机上配置 FSLogix。Per host/persona: Configure FSLogix on session host virtual machines.
  • 每个用户: 将用户分配到主机会话。Per user: Assign users to the host session.

某些角色或用户的用户配置文件可能还需要数据迁移工作,这可能会延迟特定角色的迁移,直到可以在本地 Active Directory 或单个用户桌面中修正用户配置文件。The user profiles for some personas or users might also require a data migration effort, which can delay the migration of specific personas until user profiles can be remediated within your local Active Directory or individual user desktops. 此延迟可能会显著影响 Windows 虚拟桌面方案之外的作用域。This delay could significantly affect the scope outside of the Windows Virtual Desktop scenario. 修正后,初始作用域和前面的方法可以恢复。After they've been remediated, the initial scope and the preceding approaches can be resumed.

部署或迁移 Windows 虚拟桌面Deploy or migrate Windows Virtual Desktop

将所有注意事项分解为 Windows 虚拟桌面迁移或部署的生产范围后,该过程即可开始。After all considerations are factored into your production scope for the Windows Virtual Desktop migration or deployment, the process can begin. 在迭代节奏上,采用团队现在将部署主机池、应用程序和用户配置文件。On an iterative cadence, the adoption team will now deploy host pools, applications, and user profiles. 完成此阶段后, 测试和载入用户 的部署后工作就可以开始了。After this phase is completed, the post deployment effort of testing and onboarding users can begin.

后续步骤Next steps

将 Windows 虚拟桌面部署发布到生产环境Release your Windows Virtual Desktop deployment to production