規劃 VMM 安裝Plan VMM installation

重要

已不再支援此版本的 Virtual Machine Manager (VMM),建議升級至 VMM 2019This version of Virtual Machine Manager (VMM) has reached the end of support, we recommend you to upgrade to VMM 2019.

此文章將協助您規劃成功安裝 System Center - Virtual Machine Manager (VMM) 所需的所有元素並包含 VMM 2016 版與更新版本的資訊。This article helps you to plan all the elements required for a successful System Center - Virtual Machine Manager (VMM) installation and includes information for releases VMM 2016 and later. 視您計劃安裝的 VMM 版本,來使用適用的需求。Use these requirements as applicable for the VMM version you plan to install.

如需有關硬體和軟體支援版本的詳細資訊,請參閱您要安裝版本的系統需求文章。For additional information on the supported versions of hardware and software, see the system requirements article for the version you install.

部署需求Deployment requirements

確認下列系統需求Verify the following system requirements:

  • VMM 管理伺服器 :確認硬體和作業系統需求。VMM management server : Verify hardware and operating system requirements.
  • SQL Server :檢閱支援的 SQL Server 版本SQL Server : Review supported SQL Server versions
  • VMM 主控台 :檢閱作業系統需求,以及您是否想要在另一部電腦上執行 VMM 主控台。VMM console : Review operating system requirements and if you want to run the VMM console on a separate computer.
  • VMM 程式庫 :檢閱遠端 VMM 程式庫共用的硬體需求。VMM library : Review the hardware requirements for remote VMM library shares.
  • 虛擬化主機 :檢閱 VMM 網狀架構中 Hyper-V 和 SOFS 伺服器支援的作業系統。Virtualization hosts : Review the supported operating systems for Hyper-V and SOFS servers in the VMM fabric. 檢閱 VMware 伺服器的需求。Review requirements for VMware servers.
  • 其他網狀架構伺服器 :檢閱更新和 PXE (用於裸機部署) 伺服器支援的作業系統。Other fabric servers : Review the supported operating systems for update and PXE (used for bare metal deployment) servers.

其他部署需求Additional deployment requirements

元件Component 詳細資料Details
SQL Server 的命令列公用程式Command-line utilities for SQL Server 適用於 2019 之前版本的 SQL Server 2014 Feature Pack、適用於 2019 的 2016/2017 Feature PackSQL Server 2014 feature pack for release earlier to 2019, 2016/2017 feature pack for 2019

如果您想要部署使用 SQL Server 資料層應用程式的 VMM 服務,請在 VMM 管理伺服器上安裝相關的命令列公用程式。If you want to deploy VMM services using SQL Server data-tier apps, install the related command-line utilities on the VMM management server. 您所安裝的版本應該與 SQL Server 版本相符。The version you install should match the SQL Server version. 這些項目並非安裝 VMM 的必要需求。You don't have to install these to install VMM.
Windows 評定及部署套件 (ADK)Windows Assessment and Deployment Kit (ADK) 適用於 Windows 10 的 Windows ADK。Windows ADK for Windows 10.

您可以從安裝程式進行安裝,或加以下載You can install from setup, or download it. 您僅需 [部署工具] 和 [Windows 預先安裝環境] 選項。You only need the Deployment Tools and Windows Preinstallation Environment options.
客體作業系統Guest operating system Hyper-V 支援的 Windows 作業系統。Windows operating systems supported by Hyper-V.

Linux (CentOS、RHEL、Debian、Oracle Linux、SUSE、Ubuntu)Linux (CentOS, RHEL, Debian, Oracle Linux, SUSE, Ubuntu)
PowerShellPowerShell 支援的版本Supported versions
.NET.NET 支援的版本Supported versions
主機代理程式Host agent VMM 2016/1801/1807/2019VMM 2016/1801/1807/2019

VMM 中受管理主機的必要項目。Needed for hosts managed in VMM.
監視Monitoring System Center Operations Manager 2016/1801。System Center Operations Manager 2016/1801.

您也需要 SQL Server Analysis Services 2014 或更新版本。You also need SQL Server Analysis Services 2014 or a later version.
VMwareVMware vCenter 5.1、5.5、5.8、6.0、6.5vCenter 5.1, 5.5, 5.8, 6.0, 6.5

ESX 5.5、ESX 6.0、ESX 6.5ESX 5.5, ESX 6.0, ESX 6.5

執行這些版本的 vCenter 與 ESX 伺服器可在 VMM 中接受管理。vCenter and ESX servers running these versions can be managed in VMM.
裸機佈建Bare metal provisioning 透過 WS-MAN 的伺服器硬體系統管理架構 (SMASH) (v1 或更新版本)。System Management Architecture for Server Hardware (SMASH) (v1 or higher) over WS-MAN.

智慧平台介面 1.5 或更新版本Intelligent Platform Interface 1.5 or higher

資料中心管理員介面 (DCMI) 1.0 或更高版本。Data Center Manager Interface (DCMI) 1.0 or higher.

這是探索與部署實體裸機伺服器的必要項目。Required to discover and deploy physical bare metal servers.

SPNSPN

如果安裝 VMM 或執行 VMM 安裝程式的 VMM 使用者沒有在 Active Directory 中寫入 VMM 伺服器服務主體名稱 (SPN) 的權限,安裝程式會完成但有警告。If the VMM user installing VMM, or running VMM setup, doesn't have permissions to write the service principal name (SPN) for the VMM server in Active Directory, setup will finish with a warning. 如果未登錄 SPN,其他執行 VMM 主控台的電腦將無法連線到管理伺服器,而您將無法在 VMM 網狀架構的裸機電腦上部署 Hyper-V 主機。If the SPN isn't registered, other computers running the VMM console won't be able to connect to the management server, and you won't be able to deploy a Hyper-V host on a bare metal computer in the VMM fabric. 為避免這個問題,您需要以網域系統管理員身分登錄 SPN,然後再安裝 VMM,如下所示︰To avoid this issue, you need to register the SPN as a domain administrator before you install VMM, as follows:

  1. 以網域系統管理員身分,從 <SystemDrive>\Windows\System32> 執行下列命令:Run these commands from <SystemDrive>\Windows\System32>, as a domain administrator:

    • setspn -u -s SCVMM/<MachineBIOSName> <VMMServiceAccount>
    • setspn -u -s SCVMM/<MachineFQDN> <VMMServiceAccount>

    針對叢集,<MachineBIOSName> 應為 <ClusterBIOSName>,<MachineFQDN> 應為 <ClusterFQDN>For a cluster, <MachineBIOSName> should be <ClusterBIOSName> and <MachineFQDN> should be <ClusterFQDN>

  2. 在 VMM 伺服器上 (或叢集的每個節點上),瀏覽至登錄中的 HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft System Center Virtual Machine Manager Server\SetupOn the VMM server (or on each node in a cluster), in the registry, navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft System Center Virtual Machine Manager Server\Setup.

  3. VmmServicePrincipalNames 設為 SCVMM/<MachineBIOSName>,SCVMM/<MachineFQDN>Set VmmServicePrincipalNames to SCVMM/<MachineBIOSName>,SCVMM/<MachineFQDN>. 對於叢集: SCVMM /<ClusterBIOSName>,SCVMM /<ClusterFQDN>For a cluster: SCVMM/<ClusterBIOSName>,SCVMM/<ClusterFQDN>.

如果您無法這麼做,也可以在 VMM 安裝期間登錄 SPN。If you can't do this, you can also register the SPN during VMM installation. 網域系統管理員可以提供 SPN 寫入權限給 VMM 服務使用者或安裝程式使用者。A domain administrator can provide the SPN write permissions to VMM service user or setup user. 請注意,此方法並非慣用方法。Note that this approach isn't the preferred one. 允許委派的使用者註冊任何 servicePrincipalName 而無任何限制的權限。The permission allows the delegated user to register any servicePrincipalName, with no restrictions. 因此,委派的使用者應受高度信任,而且必須妥善保存帳戶認證。Hence, the delegated user should be highly trusted, and the account credentials must be kept secure. 若要這樣做:To do this:

  1. 以系統管理員身分執行 adsiedit。Run adsiedit as a domain administrator.
  2. 瀏覽以尋找 VMM 服務使用者。Navigate to find the VMM service user. 以滑鼠右鍵按一下 [內容] > [安全性] > [進階] 。Right-click Properties > Security > Advanced. 按一下 [新增] ,然後在 [選取一個主體] 中,指定將被授與權限的使用者。Then click Add , and in Select a principal , specify user who will be granted the permissions.
  3. 選取 [寫入 servicePrincipalName] > [確定] 。Select Write servicePrincipalName > OK.

當您使用此使用者帳戶安裝 VMM 時,將會登錄 SPN。When you install VMM with this user account SPN will be registered.

VMM 管理伺服器VMM management server

  • 您無法在 Nano 伺服器 (適用於 2019 之前的版本) 上執行 VMM 管理伺服器。You can't run the VMM management server on Nano server (applicable to releases prior to 2019).
  • 管理伺服器電腦名稱不能超過 15 個字元。The management server computer name cannot exceed 15 characters.
  • 請勿在執行 Hyper-V 的伺服器上安裝 VMM 管理伺服器,或代理程式以外的其他 System Center 元件。Don’t install the VMM management server, or other System Center components other than agents, on servers running Hyper-V.
  • 您可在 VM 上安裝 VMM 管理伺服器。You can install the VMM management server on a VM. 如果您這麼做,並使用 Hyper-V 的「動態記憶體」功能,就必須將虛擬機器的啟動 RAM 設定為至少 2048 MB。If you do, and you use the Dynamic Memory feature of Hyper-V, then you must set the startup RAM for the virtual machine to be at least 2,048 megabytes (MB).
  • 如果您要管理超過 150 部主機,建議您使用 VMM 管理伺服器專用的電腦,並且執行下面項目:If you want to manage more than 150 hosts, we recommend that you use a dedicated computer for the VMM management server and do the following:
    • 將一個或多個遠端電腦新增為程式庫伺服器,請勿使用 VMM 管理伺服器上的預設程式庫共用。Add one or more remote computers as library servers, and do not use the default library share on the VMM management server.
    • 請勿在 VMM 管理伺服器上執行 SQL Server 執行個體。Don't run the SQL Server instance on the VMM management server.
  • 如需高可用性,可以在容錯移轉叢集上安裝 VMM 管理伺服器。For high availability, the VMM management server can be installed on a failover cluster. 深入了解Learn more.

SQL Server 和資料庫SQL Server and database

  • 您要使用的 SQL Server 執行個體必須允許不區分大小寫的資料庫物件。The instance of SQL Server that you are using must allow for case-insensitive database objects.
  • SQL Server 的電腦名稱不能超過 15 個字元長度。The SQL Server’s computer name cannot exceed 15 characters in length.
  • 如果 VMM 管理伺服器和 SQL Server 電腦不是同一個 Active Directory 網域的成員,則這兩個網域之間必須有雙向信任關係。If the VMM management server and the SQL Server computer are not members of the same Active Directory domain, then a two-way trust must exist between the two domains.
  • 安裝 SQL Server 時,請選取 [資料庫引擎服務] 和 [管理工具 - 完整] 功能。When you install SQL Server, select the Database Engine Services and Management Tools - Complete features.
  • 您可以對支援的 SQL Server 版本執行就地升級 (不需移動 VMM 資料庫)。You can perform an in-place upgrade to a supported version of SQL Server (without moving the VMM database). 請確定執行升級時沒有任何工作正在執行,否則工作可能會失敗且需要手動重新啟動。Make sure no jobs are running when you perform the upgrade, or jobs may fail and may need to be restarted manually.
  • 對於 VMM 資料庫,為獲得較佳的效能,請不要在作業系統安裝所在磁碟上儲存資料庫檔案。For the VMM database, for better performance, do not store database files on the disk that is used for the operating system.
  • 如果您在 VMM 中使用軟體定義網路功能 (SDN),則所有的網路資訊都會儲存在 VMM 資料庫中。If you are using Software Defined Networking (SDN) in VMM, then all networking information is stored in the VMM database. 因此,您可能會想要考慮為 VMM 資料庫提供高可用性,請使用下列指導方針:Because of this, you might want to consider high availability for the VMM database, using the following guidelines:
    • 為了在單一地理區域或資料中心內的可用性,可支援並建議使用容錯移轉叢集組態。Failover clustering is supported and is the recommended configuration for availability within a single geographical area or datacenter. 閱讀其他資訊Read more.
    • 可支援在 Microsoft SQL Server 中使用 AlwaysOn 可用性群組,但請務必檢閱同步認可與非同步認可這兩種可用性模式之間的差異。Use of Always On Availability Groups in Microsoft SQL Server is supported, but it's important to review the differences between the two availability modes, synchronous-commit and asynchronous-commit. 深入了解Learn more.
      • 使用非同步認可模式時,資料庫的複本可以在每次認可之後過期一段時間。With asynchronous-commit mode, the replica of the database can be out of date for a period of time after each commit. 這樣會使資料庫看起來好像時間倒退,而導致客戶資料遺失、意外洩漏資訊,或可能提高權限。This can make it appear as if the database were back in time which might cause loss of customer data, inadvertent disclosure of information, or possibly elevation of privilege.
      • 您可以使用同步認可模式做為遠端網站可用性案例的組態。You can use synchronous-commit mode as a configuration for remote-site availability scenarios.
  • SQL Server 服務必須使用具有 Active Directory 網域服務 (AD DS) 存取權限的帳戶。The SQL Server service must use an account that has permission to access Active Directory Domain Services (AD DS). 例如,您可以指定本機系統帳戶,或網域使用者帳戶。For example, you can specify the Local System Account, or a domain user account. 請勿指定本機使用者帳戶。Do not specify a local user account.
  • 您不需要設定定序。You don't need to configure collation. 在部署期間,安裝程式會根據伺服器作業系統的語言自動設定 CI 定序。During deployment, Setup automatically configures CI collation according to the language of the server operating system.

注意

如果資料庫屬於 SQL Always On (AO) 群組,則目標資料庫定序與 VMM 伺服器定序必須相同。Target database collate and the VMM server collate must be the same if the database is part of SQL Always On (AO) group. 若要在 VMM 機器上查看目前的文化特性 (Culture),請使用 Get-Culture PowerShell 命令。To check the current culture on your VMM machine, use the Get-Culture PowerShell command. 深入了解 VMM 伺服器定序對應Learn more about VMM server collate mappings.

  • 支援動態連接埠。Dynamic port is supported.
  • 如果您想要在 VMM 安裝之前建立 VMM 資料庫:If you want to create the VMM database prior to VMM installation:
    • 請確定您有建立 SQL 資料庫的權限,或者要求 SQL Server 系統管理員來執行此動作。Make sure you have permissions or create a SQL database, or ask the SQL Server admin to do it.

    • 設定資料庫,如下所示:Configure the database as follows:

      1. 使用下列設定建立新的資料庫:名稱:VirtualManagerDB;定序:Latin1_General_100_CI_AS,但會配合特定的 SQL Server 執行個體定序。Create a new database with settings: Name: VirtualManagerDB; Collation: Latin1_General_100_CI_AS, but aligned with the specific SQL Server instance collation.
      2. 將資料庫的 db_owner 權限授與 VMM 服務帳戶。Grant db_owner permissions for the database to the VMM service account.
      3. 在 VMM 安裝程式中,您將選取選項來使用現有的資料庫,並將資料庫詳細資訊和 VMM 服務帳戶指定為資料庫使用者。In VMM setup you'll select the option to use an existing database and specify the database details and VMM service account as the database user.

程式庫伺服器Library server

  • 如果您在 VMM 管理伺服器上執行程式庫伺服器,就必須提供額外的硬碟空間以存放物件。If you run the library server on the VMM management server, then you must provide additional hard disk space to store objects. 所需的空間依據您所儲存的物件大小和數量而異。The space required varies, based on the number and size of the objects you store.
  • 程式庫伺服器是 VMM 儲存如虛擬機器範本、虛擬硬碟、虛擬磁碟片、ISO 映像、指令碼和預存虛擬機器等項目的地方。The library server is where VMM stores items such as virtual machine templates, virtual hard disks, virtual floppy disks, ISO images, scripts, and stored virtual machines. 依據數量和這些檔案的大小,針對 VMM 資源庫伺服器所指定的最佳硬體需求也隨之而異。The optimal hardware requirements that are specified for a VMM library server vary, depending on the quantity and size of these files. 您必須檢查 CPU 使用率和其他系統狀態變數,以決定哪一種最適合您的環境。You will need to check CPU usage, and other system state variables to determine what works best in your environment.
  • 如果您要以 .vhdx 檔案格式管理虛擬硬碟,VMM 程式庫伺服器必須執行 Windows Server 2012 或更新版本。If you want to manage Virtual hard disks in the .vhdx file format, the VMM library server must run Windows Server 2012 or later.
  • VMM 不會提供在 VMM 資源庫中複寫實體檔案的方法,也不會提供針對儲存於 VMM 資料庫中的物件傳送中繼資料的方法。VMM does not provide a method for replicating physical files in the VMM library or a method for transferring metadata for objects that are stored in the VMM database. 如有必要,您必須複寫 VMM 外部的實體檔案,並且需要使用指令碼或其他方式傳送中繼資料。Instead, if necessary, you need to replicate physical files outside of VMM, and you need to transfer metadata by using scripts or other means.
  • 因為已將網路檔案系統 (NFS) 案例控制項設為 [略過] ,所以 VMM 不支援 Windows Services for UNIX 中,以區分大小寫選項所設定的檔案伺服器。VMM does not support file servers that are configured with the case-sensitive option for Windows Services for UNIX, because the Network File System (NFS) case control is set to Ignore.

帳戶和網域需求Account and domain requirements

當您安裝 VMM 時,您必須設定 VMM 服務以使用本機系統帳戶或網域帳戶或群組受管理的服務帳戶 (gMSA)。When you install VMM you need to configure the VMM service to use either the Local System account or a domain account or a Group Managed Service Account (gMSA).

準備帳戶前,請確保下列事項:Ensure the following before you prepare an account:

  • VMM 服務帳戶應該要有 VMM 伺服器上的 [允許本機登入] 與 [允許透過遠端桌面服務登入] 權限。VMM service account should have Allow log on locally and Allow log on through Remote Desktop Services permissions on the VMM server.

  • 在安裝之後,就無法變更 Virtual Machine Manager 服務帳戶的身分識別。You cannot change the identity of the Virtual Machine Manager service account after installation. 這包括將本機系統帳戶變更為網域帳戶,將網域帳戶變更為本機系統帳戶,或是將網域帳戶變更為另一個網域帳戶。This includes changing from the local system account to a domain account, from a domain account to the local system account, or changing the domain account to another domain account. 若要在安裝後變更 Virtual Machine Manager 服務帳戶,您必須解除安裝 VMM (如果您想要保留 SQL Server 資料庫,請選取 [保留資料] 選項),然後使用新的服務帳戶重新安裝 VMM。To change the Virtual Machine Manager service account after installation, you must uninstall VMM (selecting the Retain data option if you want to keep the SQL Server database), and then reinstall VMM by using the new service account.

  • 如果您指定網域帳戶,該帳戶必須是電腦上本機系統管理員群組的成員。If you specify a domain account, the account must be a member of the local Administrators group on the computer.

  • 如果指定網域帳戶,強烈建議您建立專為此用途而設的帳戶。If you specify a domain account, it is strongly recommended that you create an account that is specifically designated to be used for this purpose. 從 VMM 管理伺服器移除主機時,便會從該主機的本機系統管理員群組中,移除正在執行 System Center Virtual Machine Manager 服務。When a host is removed from the VMM management server, the account that the System Center Virtual Machine Manager service is running under is removed from the local Administrators group of the host. 如果同一個帳戶用於主機上的其他用途,可能會造成無法預期的結果。If the same account is used for other purposes on the host, this can cause unexpected results.

  • 如果您計畫搭配使用共用 ISO 映像檔與 Hyper-V 虛擬機器,則必須使用網域帳戶。If you plan to use shared ISO images with Hyper-V virtual machines, you must use a domain account.

  • 如果您使用脫離的命名空間,則必須使用網域帳戶。If you are using a disjointed namespace, you must use a domain account. 如需脫離的命名空間的詳細資訊,請參閱<Active Directory 中的電腦、網域、網站和 OU 的命名慣例>。For more information about disjointed namespaces, see Naming conventions in Active Directory for computers, domains, sites, and OUs.

  • 如果您安裝高可用性 VMM 管理伺服器,則必須使用網域帳戶。If you are installing a highly available VMM management server, you must use a domain account.

  • 您安裝 VMM 管理伺服器的電腦必須是 Active Directory 網域的成員。The computer on which you install the VMM management server must be a member of an Active Directory domain. 在您的環境中,您的使用者帳戶可能在一個樹系中,而您的 VMM 伺服器和主機可能在另一個樹系中。In your environment you might have user accounts in one forest and your VMM servers and host in another. 在這個環境中,您必須建立兩個跨樹系網域之間的雙向信任。In this environment, you must establish a two-way trust between the two cross-forest domains. VMM 中不支援跨樹系網域之間的單向信任。One-way trusts between cross-forest domains are not supported in VMM.

  • 若要建立及使用 gMSA,請檢閱 gMSA 上的文章並根據適用的指導方針來建立 gMSA。To create and use gMSA, review the article on gMSA and create the gMSA as per the guidance available. 請確定 VMM 管理服務安裝所在的伺服器有權可擷取 gMSA 帳戶的密碼。Make sure that the servers on which the VMM Management service would be installed have permissions to retrieve the password of gMSA account.

    注意

    建立 gMSA 時,您不需要指定「服務主體名稱 (SPN)」。You do not need to specify the ‘Service Principle Name (SPN)’ when creating gMSA. VMM 服務會為 gMSA 設定適當的 SPN。VMM service sets the appropriate SPN for gMSA.

分散式金鑰管理Distributed key management

根據預設,VMM 會使用資料保護應用程式發展介面 (DPAPI),在 VMM 資料庫中,將某些資料加密。By default, VMM encrypts some data in the VMM database by using the Data Protection Application Programming Interface (DPAPI). 例如,執行身分帳戶認證、客體作業系統設定檔中的密碼,和虛擬硬碟內容中的產品金鑰資訊。For example, Run As account credentials, passwords in guest operating system profiles, and product key information in virtual hard disks properties. 資料的加密與安裝 VMM 的特定電腦,以及 VMM 所使用的服務帳戶相關聯。Data encryption is tied to the specific computer on which VMM is installed, and the service account that VMM uses. 如果您將 VMM 安裝移動至其他電腦,VMM 將不會保留加密的資料,而您將必須手動輸入加密的資料。If you move your VMM installation to another computer, VMM won't retain the encrypted data, and you'll need to enter it manually.

若要確保 VMM 在移動過程中會保留加密的資料,您可以使用分散式金鑰管理在 Active Directory 中儲存加密金鑰。To ensure that VMM retains encrypted data across moves, you can use distributed key management to store encryption keys in Active Directory. 如果您移動 VMM 安裝,VMM 會保留加密的資料,因為新的 VMM 電腦可以存取 Active Directory 中的加密金鑰。If you move your VMM installation, VMM retains the encrypted data because the new VMM computer has access to the encryption keys in Active Directory. 若要設定分散式金鑰管理,您應該與您的 Active Directory 系統管理員協調。To set up distributed key management you should coordinate with your Active Directory administrator. 請注意:Note that:

  • 安裝 VMM 之前,您必須在 AD DS 中建立容器。You must create a container in AD DS before you install VMM. 您可以使用 ADSI 編輯器 (從 [伺服器管理員] > [遠端伺服器管理工具] 安裝) 建立容器。You can create the container by using ADSI Edit (installed from Server Manager > Remote Server Administration Tools.
  • 您要在與您安裝 VMM 時所用之使用者帳戶相同的網域中建立容器。You create the container in the same domain as the user account with which you are installing VMM. 如果您指定 VMM 服務使用網域帳戶,該帳戶必須位於相同的網域中。If you specify that the VMM service uses a domain account, that account must be in the same domain. 例如,若安裝帳戶與服務帳戶同時位於 corp.contoso.com 網域中,則您必須在該網域中建立容器。For example, if the installation account and the service account are both in the corp.contoso.com domain, you must create the container in that domain. 因此,如果您想要建立名為 VMMDKM 的容器,請將容器位置指定為 CN=VMMDKM,DC=corp,DC=contoso,DC=com。So, if you want to create a container that is named VMMDKM, you specify the container location as CN=VMMDKM,DC=corp,DC=contoso,DC=com. 您用來安裝 VMM 的帳戶,必須有 AD DS 中容器的「完全控制」權限。The account with which you're installing VMM needs Full Control permissions to the container in AD DS. 這些權限必須套用至此物件及所有的子系物件。The permissions must apply to this object, and to all descendant objects.
  • 如果您正在安裝高可用性的 VMM 管理伺服器,則必須使用分散式金鑰管理,才能將加密金鑰存放在 Active Directory 中。If you are installing a highly available VMM management server, you must use distributed key management to store encryption keys in Active Directory. 您需要分散式金鑰管理是因為假如 VMM 容錯移轉至節點,該節點將需要存取加密金鑰。You need distributed key management because if VMM fails over to a node, that node will need access to the encryption keys.
  • 當您在設定中設定服務帳戶和分散式金鑰時,您必須鍵入 AD DS 中容器的位置,例如:CN=VMMDKM,DC=corp,DC=contoso,DC=comWhen you configure the service account and distributed key in setup, you must type the location of the container in AD DS, for example: CN=VMMDKM,DC=corp,DC=contoso,DC=com

後續步驟Next steps

安裝 VMMInstall VMM