AzureStack-QuickStart-Templ.../rds-deployment-existing-ad
Heath Lawson fa692f4c4e Updating to Development Kit references (#268)
* Updating to Development Kit reference

* Scrubbing TP references
2017-07-31 11:36:49 -07:00
..
Configuration.zip fixing DSC 2016-08-03 11:37:57 -07:00
README.md Updating to Development Kit references (#268) 2017-07-31 11:36:49 -07:00
azuredeploy.json Add public IP dependencies (#196) 2017-01-27 14:23:16 -08:00
azuredeploy.parameters.json Fixing RDS custom Image 2016-08-07 21:31:05 -07:00
metadata.json Push changes from develop to master (#155) 2016-09-21 13:33:28 -07:00

README.md

Create Remote Desktop Sesson Collection deployment using existing AD.

This template will create a Remote Desktop Sesson Collection farm using the PowerShell DSC Extension. Please note this expects that AD is already setup (The Vnet and Subnet names are currently in variables so, you need to update it to use yours). it creates the following resources:

  • One Storage Account
  • One external load balancer
  • One VM configured as RDS Connection Broker and Licensing Server role
  • One VM configured as RDS Gateway and Web access Server role
  • One (or more) VMs configured as RDSH host role. NOTE: Because HA is not supported on Azure Stack Development Kit, please use only one VM or it will fail.
  • The imageSKU is choice in parameter and rest of image configuration is defined in variables - but the scripts that configure this deployment have only been tested with windows server 2012 R2 data center image and may not work on other images.

Deploying from Portal

  • Login into Azurestack portal
  • Click "New" -> "Custom" -> "Template deployment"
  • Deploy ad-non-ha template. if you already have deployed ad-non-ha, then you can use that AD deployment by its resource group for this deployment.
  • Copy conent in azuredeploy.json, Click "Edit Tempalte" and paste content, then Click "Save"
  • Fill the parameters. Again, this uses existing AD. Please see note above.
  • Click "Create new" to create new Resource Group
  • Click "Create"

Deploying from PowerShell

Download azuredeploy.json and azuredeploy.azurestack.parameters.json to local machine

Modify parameter value in azuredeploy.azurestack.parameters.json as needed

Allow cookies in IE: Open IE at c:\Program Files\Internet Explorer\iexplore.exe -> Internet Options -> Privacy -> Advanced -> Click OK -> Click OK again

Launch a PowerShell console

Change working folder to the folder containing this template


# Add specific Azure Stack Environment 

$AadTenantId = <Tenant Id> #GUID Specific to the AAD Tenant 

Add-AzureRmEnvironment -Name 'Azure Stack' `
<EFBFBD><EFBFBD><EFBFBD> -ActiveDirectoryEndpoint ("https://login.windows.net/$AadTenantId/") `
<EFBFBD><EFBFBD><EFBFBD> -ActiveDirectoryServiceEndpointResourceId "https://azurestack.local-api/" `
<EFBFBD><EFBFBD><EFBFBD> -ResourceManagerEndpoint ("https://api.azurestack.local/") `
<EFBFBD><EFBFBD><EFBFBD> -GalleryEndpoint ("https://gallery.azurestack.local/") `
<EFBFBD><EFBFBD><EFBFBD> -GraphEndpoint "https://graph.windows.net/"

# Get Azure Stack Environment Information 
$env = Get-AzureRmEnvironment 'Azure Stack' 

# Authenticate to AAD with Azure Stack Environment 
Add-AzureRmAccount -Environment $env -Verbose 

# Get Azure Stack Environment Subscription 
$SubName = <Subscription Name> # The sbuscription name is the offer name by default 
Get-AzureRmSubscription -SubscriptionName $SubName | Select-AzureRmSubscription

#Resource group name. Please make sure the resource group does not exist 
$resourceGroupName = "rdsResourceGroup"
$deploymentName = "RDSDeployment"
$location = "Local" 
New-AzurermResourceGroup -Name $resourceGroupName -Location $location 

#Start new Deployment
New-AzurermResourceGroupDeployment -Name $deploymentName -ResourceGroupName $resourceGroupName `
<EFBFBD><EFBFBD><EFBFBD> -TemplateParameterFile .\azuredeploy.parameters.json -TemplateFile .\azuredeploy.json