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 Files 來裝載使用者配置檔。You can use Azure NetApp Files to host user profiles. 這麼做將需要範圍中的幾個額外步驟,包括:Doing so will require a few extra steps in the scope, including:

  • 每一 NetApp 實例: 設定 NetApp files、磁片區和 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 Domain Services (AD DS) 、指派 Active Directory 使用者群組的 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