If you find yourself in a scenario where you need to change the registration subscription of an Azure Stack Hub deployment, the below is what you need to do to complete the task..
High level:
Gather info or source and destination Remove existing registration Register to new subscription Gather info or source and destination First thing is to get your new subscription ID
$NewSubscriptionId = "325*****-****-****-****-********432" Connect to Azure Stack ARM endpoint
Excited to be speaking at Microsoft Ignite The Tour in Sydney. For those coming along, below are my sessions and demo times slots⌠If you see me make sure you come up and say hi!
[table id=5 /]
In a recent project, the management were keen to see some dashboards and insights into their organizations shiny new infrastructure.
Whilst SCOM gives some great data and statistics, itâs not overly helpful in demonstrating the high level view to management out of the box.
This is where Microsoft Operations Management Suite (OMS)Â steps in..
Background: This engagement included a new Hyper-converged platform (Hyper-V and Storage Spaces Direct) managed and monitoring with System Center (SCVMM and SCOM), so we had a great foundation to light up OMS and some chosen solutions.
This is one I use regularly, so thought it might come in handy for you..
Assumption here is you are connected via PowerShell to your intended subscription..
A few key points:
The VM will need to be stopped to execute Check the Azure VM sizing to see how many NICs you can attach I have a pre-created Network Interface with my desired settings #Using OGV to target your objects $RG = Get-AzureRmResourceGroup | ogv -PassThru $NIC = Get-AzureRmNetworkInterface | ogv -PassThru $VM = Get-AzureRmVm | ogv -PassThru #The actual adding of the NIC to the VM $VM = Add-AzureRmVMNetworkInterface -VM $VM -Id $NIC.
Another quick one (becoming a habit..)
In deploying and testing Azure Connector for Windows Azure Pack found here, deploying a virtual machine can sometimes fail with an obscure status message of:
âError in CheckCheckVmCreation()â
This is because the parameters of the resource creation are rejected. In the below example, I faced this because my lab password did not meet the required complexities.
Running the the process using the same account in Azure, I am faced with a minimum password complexity error