Azure Arc Servers is a feature of Azure Arc that enables organizations to manage servers across different environments, including on-premises, multi-cloud, and edge environments, through a single control plane. This allows organizations to have a consistent management experience across all their servers, regardless of where they are located.
At a high level, the various features of Azure Arc Servers, include:
Server management: With Azure Arc Servers, organizations can manage their servers using Azure Policy and Azure Security Center, which provide policy-based control, monitoring, and threat protection.
Network ATC deployment.
Recommendations:
Use the defaults where possible If unsure, refer to rule #1. This cluster is a 5x node each with 4x 25Gbps adapters. 2x for Compute & Management, and 2x for Storage.
I set jumbo across the board. Don’t argue, just do it.
I use default Vlan ID’s for storage (711 & 712) and use the IPs that get assigen via Network ATC. Yeh my OCD kinda wanted the last octet to align with the host number but at the end of the day, we just want it to work.
Azure Stack HCI is a hardware appliance that allows businesses to run their own private cloud infrastructure on their own servers. It is designed for companies that want to keep their data and applications on-premises (i.e., not in the public cloud). With Azure Stack HCI, companies can create their own cloud-like environment for their applications and data, but with the added benefits of Azure services, such as backup, monitoring, and security.
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
Quick tip:Â Another day in the life of a Cloud Operator
Got a call from a user who was in the Azure Stack tenant portal and could access some resource types but not others and when in those resources blades the info was all weird (technical term…) as shown below:
I thought it was a cache/auth issue, so I asked the user to open a new browser and try again.
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 /]
This is for SQL Resource Provider (RP) 1.1.24.0 which is now superseded by 1.1.30.0 literally the next day after I executed the install. The only reason for posting this blog is to give a baseline for my update SQL RP post. The exact same install process will work for any newer Azure Stack deployments just skip the section where I rollback the PowerShell module version
This post will cover the deployment of the SQL RP with other posts in the series covering the various other steps and considerations
You’re a cloud operator for an Azure Stack Integrated system and for whatever reason you have the task of deploying the App Services Resource provider…
In this blog series, I’m going to take you through the considerations and deployment processes I went through for the App Services resource provider on an Azure Stack Integrated System. This will work on an ASDK but it’d get fairly crowded on your single server instance if you follow the HA design all the way through.
You’re a cloud operator for an Azure Stack Integrated system and for whatever reason you have the task of deploying the App Services Resource provider…
In this blog series, I’m going to take you through the considerations and deployment process of the App Services resource provider on an Azure Stack Integrated System. This should work on an ASDK but you’re probably going to make life tough for your single server instance.
Quick tip for all potential Azure Stack Cloud Operators
As you’d be aware, essentially the majority of the Azure Stack extended setup requires PowerShell. Not only does managing Azure Stack require PowerShell, it requires specific modules, tools and PowerShell profiles…
Oh, did I mention Azure Stack management requires PowerShell?
This is typically fine, but if you’re anything like me and tend to use your computer (desktop/laptop etc) for many different functions, managing PowerShell profiles and having them all aligned can be a bit of a pain.
I recently had the task of enabling monitoring of an Azure Stack Integrated System using System Center Operations Manager.
Below I will go through the process of how this is done and what to consider a long the way.
Firstly, RTFM Secondly, you probably don’t need this blog post as the documentation for this process is spot on! https://docs.microsoft.com/en-us/azure/azure-stack/azure-stack-integrate-monitor
The SCOM bits (MP and Docco) can be found here: https://www.
So, if you’ve found your way here you have got yourself an Azure Stack Integrated System and need to register it as a Cloud Solution Provider (CSP).
Before we registered we needed to identify the type of subscription we want to use. The choice is a CSP or APSS subscription.
This deployment is being registered directly to my company as the CSP reseller so a CSP subscription was the preferred choice.
Another quick one! :D
For those playing with the Azure Stack TP3 POC deployment that want to make the portal available without having to logon to the console VM.
This extends on from the work Ruud Borst did for TP2.. I suggest you read the full article which can be found here: https://azurestack.blog/2016/12/expose-portal-azurestack-through-nat/
Same rules apply around the certificate etc.
Let me know if I have missed any ports.
Enjoy! Dan