So TP3 is here and i quickly downloaded the bits and installed some systems. Here a quick wrapup of my experience so far.
First, some parameters are changed as well the folder to start the install from. Find here an example to start the deployment once you have the VHDX installed on the server:
|
1 2 3 4 5 6 7 8 9 10 11 |
#Using Azure AAD cd C:\CloudDeployment\Setup $adminpass = ConvertTo-SecureString "<PASSWORD>" -AsPlainText -Force $aadpass = ConvertTo-SecureString "<PASSWORD>" -AsPlainText -Force $aadcred = New-Object System.Management.Automation.PSCredential ("serviceadmin@<AADTENANT>.onmicrosoft.com", $aadpass) .\InstallAzureStackPOC.ps1 -AdminPassword $adminpass -InfraAzureDirectoryTenantAdminCredential $aadcred -InfraAzureDirectoryTenantName <AADTENANT>.onmicrosoft.com #Using ADFS cd C:\CloudDeployment\Setup $adminpass = ConvertTo-SecureString "<PASSWORD>" -AsPlainText -Force .\InstallAzureStackPOC.ps1 -AdminPassword $adminpass -UseADFS |
Then after just 4 hours TP3 is installed. The password policy issue is still active, so update the password policy if you want to use your POC longer than 40 days! You might also be used to install AzureRm version 1.2.6, but in TP3 we can use 1.2.8. Be aware of that too.
I use this script to quickly connect to Azure Stack with PowerShell
|
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 |
Install-Module -Name AzureRM -RequiredVersion 1.2.8 Install-Module -Name AzureStack set-location C:\Users\AzureStackAdmin\Desktop Invoke-WebRequest -UseBasicParsing -Uri https://github.com/Azure/AzureStack-Tools/archive/master.zip -OutFile master.zip Expand-Archive -Path .\master.zip -DestinationPath . -Force $Folder = New-Item -ItemType Directory -Path ~\Documents\WindowsPowerShell\Modules -Force Get-ChildItem -Path .\AzureStack-Tools-master -Directory | ForEach-Object -Process { if (Get-ChildItem -Path $_.FullName -Filter *.psm1) { $PSM1 = Get-ChildItem -Path $_.FullName -Filter *.psm1 Copy-Item -Path $_.FullName -Destination "$($Folder.FullName)\$($PSM1.BaseName)" -Recurse New-ModuleManifest -Path "$($Folder.FullName)\$($PSM1.BaseName)\$($PSM1.BaseName).psd1" -RootModule $PSM1.BaseName } } #endregion $Password = ConvertTo-SecureString "<PASSWORD>" -AsPlainText -Force $AadTenant = Get-AzureStackAadTenant -HostComputer 192.168.200.65 -Password $Password # Use this command to access the administrative portal Add-AzureStackAzureRmEnvironment -AadTenant $AadTenant -Name AzureStack # Use this command to access the tenant portal Add-AzureStackAzureRmEnvironment -AadTenant $AadTenant -ArmEndpoint https://publicapi.local.azurestack.external -Name AzureStack Login-AzureRmAccount -EnvironmentName "AzureStack" -TenantId $AadTenant |
When you try to configure Marketplace syndication be aware that you installed Azure Stack in online mode (not ADFS) and have a subscription enabled on your Azure account. When you have installed Azure Stack in a AAD that doesn’t has a subscription, don’t worry. If you have another account that has an Azure subscription enabled and active use that one.
|
1 2 |
Set-Location C:\Users\AzureStackAdmin\Desktop\AzureStack-Tools-master\Registration .\RegisterWithAzure.ps1 -azureDirectory markscholman.com -azureSubscriptionId b0d81e1e-8d78-0000-0000-08de7933af4a -azureSubscriptionOwner <SUBADMIN>@markscholman.com |
UPDATE: I came around a message on twitter from Marius Sandbu that CSP subscriptions dont have the microsoft.azurestack resource provider registered yet. So if you have a CSP subscription it might not work yet to use marketplace syndication:
@Darmour_MSFT @OrchestratorGuy actually the AzureRMresourceprovider microsoft.azurestack isn’t available in CSP subscription?!
— Marius Sandbu (@msandbu) March 2, 2017
Now the nasty part… It looks like there is a bug, but again, we are running preview guys… Whenever you update a VM (add/remove extension, add disk, etc.) the VM reboots. and sometimes the operation fails. This has to be fixed in a new build, so that’s a good reason to get the Azure Stack downloader running once in a while and opt-in for the development branch 🙂
Also note, that the PaaS (SQL , MySQL & AppService) installation we have from TP2 do not work on TP3. We have to wait for an updated PaaS installer to get it running on TP3
That’s my 2 cents for today, more blogs will follow with the experience of TP3 deployments!