The hardware required to perform a proper evaluation consists of six (6) physical servers and two (2) network switches. And while not every physical computer will host every component, the software that you will need for this evaluation is:
· Windows Server® 2012 R2 Preview
· SQL Server 2012
· Virtual Machine Manager
· Windows Azure Pack for Windows Server
· Service Management Automation*
· Service Provider Foundation*
|
|
*You will use the setup utility in Orchestrator to install Service Management Automation and Service Provider Foundation.
VHD Downloads for System Center 2012 R2
All of the System Center components are available on the Microsoft Connect website. System Center 2012 R2 Virtual Machine Manager and System Center 2012 R2 Orchestrator are available as VHDs and Windows Azure Pack will be installed using Web Platform Installer (WPI) as described in the following section. Download two self-extracting executable files which include deployment documentation from the following locations:
Virtual Machine Manager at http://go.microsoft.com/fwlink/p/?LinkId=311549
Orchestrator at http://go.microsoft.com/fwlink/p/?LinkId=311555
Deploying Windows Azure Pack in System Center 2012 R2
For this evaluation you can use the express installation option available in the Web Platform Installer to install all the pieces of Windows Azure Pack onto a single system. Express installation is used to create a proof of concept deployment and not to deploy Windows Azure Pack into production.
You will first need to prepare your computer for and install the Web Platform Installer. For more information see Windows Azure Pack installation requirements at http://go.microsoft.com/fwlink/p/?LinkId=309949.
After you have installed the Web Platform Installer, you can perform an express install of Windows Azure Pack. For more information see Install an express deployment of Windows Azure Pack at http://go.microsoft.com/fwlink/p/?LinkId=309947.
Hardware Configuration
You will need six (6) physical computers and two (2) network switches for your evaluation environment Two of the computers will serve as Management Scale Units (MSU), two Compute Scale Units (CSU), one gateway, and one file server. An example is shown in the following diagram.
Each physical server must meet the following hardware requirements:
|
CPU |
24-core |
|
RAM |
128 GB |
|
Local Disk Space |
40 GB |
MSU Environment
Each of the two MSU computers will serve specific functions.
The first computer, MSU1 must be configured as follows:
· Computer Name: WNVHOST1
· Configured as a Hyper-V host
· Domain Controller: cor.adatum.com
· DNS Server
· Two Virtual Machines, each on their own virtual network, each running Windows Server 2012 R2 Preview.
· One virtual machine named APP2 that is configured as a datacenter hosted application and web server for the Contoso tenant network.
· The other virtual machine named APP2 that is configured as a datacenter hosted application and web server for the Fabrikam tenant network.
The second computer, MSU2 must be configured as follows:
· Computer Name: WNVHOST2
· Configured as a Hyper-V host
· Install SQL Server
· Install IPAM Server
· Install System Center 2012 R2 Virtual Machine Manager
· Two Virtual Machines, each on their own virtual network, each running Windows Server 2012 R2 Preview.
· One virtual machine named APP1 that is configured as a datacenter hosted application and web server for the Contoso tenant network.
· The other virtual machine named APP1 that is configured as a datacenter hosted application and web server for the Fabrikam tenant network.
Gateway Environment
The gateway consists of one physical computer running Windows Server 2012 R2 Preview that is configured as a Windows Network Virtualization Gateway. This computer is configured as follows:
· Computer Name: WNVHOST3
· Host one virtual machine running winserver_blue_2 named GatewayVM1, and that is configured as a cross-premises gateway for the hosted tenant networks.
CSU Environment
The two CSU computers will be part of a Hyper-V cluster.
The first computer, CSU1 must be configured as follows:
· Computer Name: WNVHOST4
· Configured as a Hyper-V host
· Seven virtual machines running winserver_blue_1 to simulate the Internet and an on-premises network
· One virtual machine named INET1 that is configured as an Internet Domain Name System (DNS) server and web server.
· One virtual machine named DC1 that is configured as a Contoso customer private intranet domain controller and DNS server.
· One virtual machine named APP1 that is configured as a general application and web server for the Contoso domain.
· One virtual machine named EDGE1 that is configured as an Internet edge server for the Contoso domain.
· One virtual machine named DC1 that is configured as a Fabrikam customer private intranet domain controller and DNS server.
· One virtual machine named APP1 that is configured as a general application and web server for the Fabrikam domain.
· One virtual machine named EDGE1 that is configured as an Internet edge server for the Fabrikam domain.
The second computer, CSU2 is a Hyper-V cluster of CSU1: