tions your storage presents to you (for example, shared VHDX, CSV caching, storage tiering, and so on) Planning for the technology involved and where it will be deployed in your infrastructure will involve where VMM servers are to be located and the number and types of availability required: All of the information gained in the previous steps will be used to determine the requirements of the deployment The different deployment types are described in the following table: Deployment type Description Single server This has a single point of failure, all on one VM or physical server. This also has the test environment and demo lab. This is supported in production, but it is not scalable. Multiserver In this type of deployment, the components of VMM are installed on separate servers that could be highly available. Appendix B The minimum requirements for each component of VMM 2012 R2 are covered in the following table: Component Minimum requirements VirtualManagerDB Software: SQL Server 2008 R2 SP2 (Standard, Enterprise, or Datacenter) or later, with the Database Engine Services and Management Tools (complete features) Hardware: Dual-core, 64-bit, 2 GHz CPU processor 4 GB RAM 150 GB of HDD space on which the operating system is installed 50 GB of HDD space on which the database is stored Management Server Software: Windows Server 2012 or higher (Standard or Datacenter) .NET Framework 4.5 or 4.5.1 Windows Remote Management (WinRM) service Windows ADK (Deployment tools and Windows preinstallation environment) SQL Server 2008 R2 Command Line Utilities or SQL Server 2012 Command Line Utilities, depending on which version of SQL Server you install Hardware: Pentium 4, 64-bit, 2 GHz CPU processor 4 GB RAM 2 GB of HDD space (without a local SQL install) 80 GB of HDD space (with a local SQL install) Planning the Virtual Machine Manager Component Minimum requirements VMM Console Software: Any x86 or x64 version of Windows 7 SP1 (Professional, Enterprise, or Ultimate editions), or Windows 8/8.1 (Professional or Enterprise) Windo