Correct Answer:
Explanation/Reference:
Explanation/Reference:
http://technet.microsoft.com/en-us/library/gg697604.aspx
The following are some considerations about using distributed key management in VMM:
If you are installing a highly available VMM management server, you must use distributedkey management to store encryption keys in AD DS.
Distributed key management is required in this scenario because when the Virtual MachineManager service fails over to another node in the cluster, the Virtual Machine Managerservice still needs access to the encryption keys in order to access data in the VMMdatabase. This is only possible if the encryption keys are stored in a central location like ADDS.
For future upgrades that involve Virtual Machine Roles, it is recommended that you usedistributed key management during setup. This will ensure that Virtual Machine Roles areproperly upgraded, and that you can manage them after the upgrade.
You must create a container in AD DS before installing VMM. You can create the containerby using ADSI Edit.
You must create the container in the same domain as the user account with which you areinstalling VMM. Also, if you specify a domain account to be used by the System CenterVirtual Machine Manager service, that account must also be in the same domain.For example, if the installation account and the service account are both in thecorp.contoso.com domain, you must create the container in that domain. So, if you want tocreate a container named VMMDKM, you would specify the container location asCN=VMMDKM,DC=corp,DC=contoso,DC=com.
After the Active Directory administrator has created the container, the account with whichyou are installing VMM must be given Full Control permissions to the container in AD DS.
Also, the permissions must apply to This object and all descendant objects of thecontainer.
On the Configure service account and distributed key management page, you mustspecify the location of the container in AD DS by typing. For example, by typing CN=VMMDKM,DC=corp,DC=contoso,DC=com.