Data disk drive configuration: All data drives must be of the same type (SAS or 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)

* 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.

Deploy Azure Stack POC

Before you deploy, prepare the Azure Stack POC machine and make sure it meets the minimum requirements.

Reboot the machine. It will automatically run Windows Setup as the VHD system is prepared.

Configure the BIOS to use Local Time instead of UTC.

Verify that four drives for Azure Stack POC data:

Are visible in disk management

Are not in use

Show as Online, RAW

Verify that the host is not joined to a domain.

Log in using a local account with administrator permissions.

Verify network connectivity to Azure.com.

Important: Only one NIC is allowed during the deployment process. If you want to use a specific NIC, you must disable all the others.

Run the PowerShell deployment script

Open PowerShell as an administrator.

In PowerShell, go to the Azure Stack folder location (\Microsoft Azure Stack POC\ if you used the default).

Run the deploy command:

I’m running the script with Proxy settings.

Deployment starts and the Azure Stack POC domain name is hardcoded as azurestack.local.

At the Enter the password for the built-in administrator prompt, enter a password and then confirm it. This is the password to all the virtual machines. Be sure to record this Service Admin password.

At the Please login to your Azure account in the pop-up Azure authentication page, hit any key to open the Microsoft Azure sign-in dialog box.

Enter the credentials for your Azure Active Directory Account. This user must be the Global Admin in the directory tenant

Back in PowerShell, at the account selection confirmation prompt, enter y. This creates two users and three applications for Azure stack in that directory tenant: an admin user for Azure Stack, a tenant user for the TiP tests, and one application each for the Portal, API, and Monitoring resource providers. In addition to this, the installer adds consents for the Azure PowerShell, XPlat CLI, and Visual Studio to that Directory Tenant.

The deployment process will take a few hours, during which several automated system reboots will occur. Signing in during deployment will automatically launch a PowerShell window that will display deployment progress. The PowerShell window closes after deployment completes.

On the Azure Stack POC machine, sign in as an AzureStack/administrator, open Server Manager, and turn off IE Enhanced Security Configuration for both admins and users.

Double-click the AzureStack.local.rdp desktop icon to open a Remote Desktop Connection to the client virtual machine. This automatically uses the AzureStack\AzureStackUser account that was created by the deployment script. Use the admin password you gave in step 5 of the script process at the Enter the password for the built-in administrator prompt.

Tenants provision, monitor, and manage services that they subscribe to, like Web Apps, storage, and virtual machines. A service administrator can log in as a tenant to test the plans, offers, and subscriptions that their tenants might use. If you don’t already have one, Create a tenant account before you log in.

Log in to the Azure Stack physical machine.

Double-click the AzureStack.local.rdp desktop icon to open a Remote Desktop Connection to the client virtual machine. This automatically uses the AzureStack\AzureStackUser account that was created by the deployment script. Use the admin password you gave in step 5 of the script process at the Enter the password for the built-in administrator prompt.