Azure Stack deployment prerequisites
Before you deploy Azure Stack POC (Proof of Concept), make sure your computer meets the following requirements. The Technical Preview 2 deployment requirements for the POC are the same as those required for Technical Preview 1. Therefore, you can use the same hardware that you used for the previous single-box preview.
|Disk drives: Operating System||1 OS disk with minimum of 200 GB available for system partition (SSD or HDD)||1 OS disk with minimum of 200 GB available for system partition (SSD or HDD)|
|Disk drives: General Azure Stack POC Data||4 disks. Each disk provides a minimum of 140 GB of capacity (SSD or HDD). All available disks will be used.||4 disks. Each disk provides a minimum of 250 GB of capacity (SSD or HDD). All available disks will be used.|
|Compute: CPU||Dual-Socket: 12 Physical Cores (total)||Dual-Socket: 16 Physical Cores (total)|
|Compute: Memory||96 GB RAM||128 GB RAM|
|Compute: BIOS||Hyper-V Enabled (with SLAT support)||Hyper-V Enabled (with SLAT support)|
|Network: NIC||Windows Server 2012 R2 Certification required for NIC; no specialized features required||Windows Server 2012 R2 Certification required for NIC; no specialized features required|
|HW logo certification||Certified for Windows Server 2012 R2||Certified for Windows Server 2012 R2|
Data disk drive configuration: All data drives must be of the same type (all SAS or all SATA) and capacity. If SAS disk drives are used, the disk drives must be attached via a single path (no MPIO, multi-path support is provided).
HBA configuration options
- (Preferred) Simple HBA
- RAID HBA – Adapter must be configured in “pass through” mode
- RAID HBA – Disks should be configured as Single-Disk, RAID-0
Supported bus and media type combinations
- SATA HDD
- SAS HDD
- RAID HDD
- RAID SSD (If the media type is unspecified/unknown*)
- SATA SSD + SATA HDD
- SAS SSD + SAS HDD
* RAID controllers without pass-through capability can’t recognize the media type. Such controllers will mark both HDD and SSD as Unspecified. In that case, the SSD will be used as persistent storage instead of caching devices. Therefore, you can deploy the Microsoft Azure Stack POC on those SSDs.
Example HBAs: LSI 9207-8i, LSI-9300-8i, or LSI-9265-8i in pass-through mode
Sample OEM configurations are available.
|OS Version||Windows Server 2012 R2 or later. The operating system version isn’t critical before the deployment starts, as you'll boot the host computer into the VHD that's included in the Azure Stack installation. The OS and all required patches are already integrated into the image. Don’t use any keys to activate any Windows Server instances used in the POC.|
Deployment requirements check tool
After installing the operating system, you can use the Deployment Checker for Azure Stack Technical Preview 2 to confirm that your hardware meets all the requirements.
Microsoft Azure Active Directory accounts
The Microsoft Azure Stack POC deployment must be connected to Azure. Therefore, you must prepare a Microsoft Azure Active Directory account before running the deployment PowerShell script. This account becomes the Global Admin for the Azure Active Directory tenant. It will be used to provision and delegate applications and service principals for all Azure Stack services that interact with Azure Active Directory and Graph API. It will also be used as the owner of the default provider subscription (which you can later change). You can log in to your Azure Stack system’s admin portal by using this account.
Create an Azure AD account that is the directory administrator for at least one Azure Active Directory. If you already have one, you can use that. Otherwise, you can create one for free at http://azure.microsoft.com/en-us/pricing/free-trial/ (in China, visit http://go.microsoft.com/fwlink/?LinkID=717821 instead.)
Save these credentials for use in step 6 of Run the PowerShell deployment script. This service administrator account can configure and manage resource clouds, user accounts, tenant plans, quotas, and pricing. In the portal, they can create website clouds, virtual machine private clouds, create plans, and manage user subscriptions.
Create at least one account so that you can sign in to the Azure Stack POC as a tenant.
Azure Active Directory account Supported? Work or school account with valid Public Azure Subscription Yes Microsoft Account with valid Public Azure Subscription No Work or school account with valid China Azure Subscription Yes Work or school account with valid US Government Azure Subscription Yes
One available port on a switch for the POC machine.
The Azure Stack POC machine supports connecting to a switch access port or trunk port. No specialized features are required on the switch. If you are using a trunk port or if you need to configure a VLAN ID, you have to provide the VLAN ID as a deployment parameter. You can see examples in the list of deployment parameters.
Do not connect the POC machine to the following subnets:
These subnets are reserved for the internal networks within the Microsoft Azure Stack POC environment.
Only IPv4 is supported. You cannot create IPv6 networks.
Make sure there is a DHCP server available on the network that the NIC connects to. If DHCP is not available, you must prepare an additional static IPv4 network besides the one used by host. You must provide that IP address and gateway as a deployment parameter. You can see examples in the list of deployment parameters.
Azure Stack requires access to the Internet, either directly or through a transparent proxy. Azure Stack does not support the configuration of a web proxy to enable Internet access. Both the host IP and the new IP assigned to the MAS-BGPNAT01 (by DHCP or static IP) must be able to access Internet. Ports 80 and 443 are used under the graph.windows.net and login.windows.net domains.
To support telemetry data flow, port 443 (HTTPS) must be open in your network. The client endpoint is https://vortex-win.data.microsoft.com.