o the newly created Active Directory container using PowerShell There are two possible methods of creating a container in Active Directory: one is using ADSI Edit and the other is via PowerShell. The method discussed here will be PowerShell-based: On a Domain Controller, or a machine where the Active Directory PowerShell Module is installed, open an elevated PowerShell console. The following PowerShell line will create a container called DKMVMM in the root of Active Directory: New-ADObject -Name DKMVMM -Type container -Path "DC=ad, DC=demo, , DC=com" Chapter 1 3. Once the container has been created, the user who will be installing VMM needs to have full control of the container and that permission must apply to the container and all descendant objects. The following PowerShell will perform this function: Set-PSDrive AD: $VMMInstallAccount = Get-ADUser Identity Install_VMM $SID = New-Object System.Security.Principal.SecurityIdentifier $VMMInstallAccount.SID $DKMVMMacl = Get-Acl -Path "CN=DKMVMM, DC=ad, DC=demo, DC=com" $ObjectGuid = New-Object Guid 00000000-0000-0000-0000- 000000000000 $newACL = New-Object System.DirectoryServices.ActiveDirectoryAccessRule $SID, "GenericAll", "Allow", $objectguid, "All" DKMVMMacl.AddAccessRule ($newACL) Set-Acl -AclObject $DKMVMMacl -Path "CN=DKMVMM, DC=ad, DC=demo, DC=com" This recipe is complete and the Distributed Key Management container is now ready to be used by DEMO\Install_VMM during installation. How it works. When VMM is installed, it uses the Distributed Key Management container to store its encryption keys and using the privileges granted to it previously, it will lock down the container to ensure that only the account running the VMM Management Service, the VMM Installation Account, and Domain Administrators have access to the container. Installing Virtual Machine Manager Installing Virtual Machine Manager on a single server This recipe provides the steps required to install all the VMM roles on a single server, including SQL Server. This type of deployment is suitabl