Comments (6)
Hello. Have you tried creating each cluster in a different resource group? Otherwise, all of the scripts used in the ARM template can be found under the deployment folder.
from azurestackhci-evalguide.
Even if we use different resource groups, the App Registrations in AAD will be named the same. Will look at the deployment scripts
from azurestackhci-evalguide.
Hey Byron - are you referring to when you get to the registration phase of the cluster, and because all clusters by default should be called AZSHCICLUS, that's causing the challenge, or is it related to the Windows Admin Center registration?
If it's the AZSHCICLUS naming that's causing the issue, you could choose a different name, you may just need to pre-create the AD objects to streamline things. The automation does take care of that, however there's a script here that would help you do that after the fact: https://github.com/Azure/AzureStackHCI-EvalGuide/blob/main/deployment/helpers/Update-AD.ps1 - just choose whatever cluster name you like in that script, run it on the AzSHCIHost001 and then you should be good to create your AzSHCI cluster, with whatever name you specified in that script, and register accordingly.
Does that help?
In future, I could possibly edit the ARM template to allow you to specify a cluster name, and that would pass through to the DSC and onto the Update-AD script, but that would take me a bit of time to test and validate - hopefully the workaround above is OK for now.
Thanks!
Matt
from azurestackhci-evalguide.
Hey Byron - are you referring to when you get to the registration phase of the cluster, and because all clusters by default should be called AZSHCICLUS, that's causing the challenge, or is it related to the Windows Admin Center registration?
If it's the AZSHCICLUS naming that's causing the issue, you could choose a different name, you may just need to pre-create the AD objects to streamline things. The automation does take care of that, however there's a script here that would help you do that after the fact: https://github.com/Azure/AzureStackHCI-EvalGuide/blob/main/deployment/helpers/Update-AD.ps1 - just choose whatever cluster name you like in that script, run it on the AzSHCIHost001 and then you should be good to create your AzSHCI cluster, with whatever name you specified in that script, and register accordingly.
Does that help?
In future, I could possibly edit the ARM template to allow you to specify a cluster name, and that would pass through to the DSC and onto the Update-AD script, but that would take me a bit of time to test and validate - hopefully the workaround above is OK for now.
Thanks! Matt
Thanks for the reply Matt...I will see if I can follow the steps you outlined.
from azurestackhci-evalguide.
@mattmcspirit I was able to deploy a new cluster by making edits to the script you mentioned and the Register-AzSHCI
script.
from azurestackhci-evalguide.
Hey Byron - are you referring to when you get to the registration phase of the cluster, and because all clusters by default should be called AZSHCICLUS, that's causing the challenge, or is it related to the Windows Admin Center registration?
If it's the AZSHCICLUS naming that's causing the issue, you could choose a different name, you may just need to pre-create the AD objects to streamline things. The automation does take care of that, however there's a script here that would help you do that after the fact: https://github.com/Azure/AzureStackHCI-EvalGuide/blob/main/deployment/helpers/Update-AD.ps1 - just choose whatever cluster name you like in that script, run it on the AzSHCIHost001 and then you should be good to create your AzSHCI cluster, with whatever name you specified in that script, and register accordingly.
Does that help?
In future, I could possibly edit the ARM template to allow you to specify a cluster name, and that would pass through to the DSC and onto the Update-AD script, but that would take me a bit of time to test and validate - hopefully the workaround above is OK for now.
Thanks! Matt
Matt, this morning I turned on my host and reviewed the various objects in Azure. I observed the following issues:
- My host came up fine and the cluster node VMs started fine. When I went into WAC and looked at the cluster, everything seemed fine but when I went into the Azure portal it shows the nodes as not connected.
- When I created the cluster, I modified the scripts to call the cluster a different name and to put the cluster into a different Resource Group. I noticed that another Resource Group got created that is named with the format <cluster_name>-GUID-Arc-Infra-RG. This Resource Group has the
Server -Azure Arc
resources for each cluster node (AZSHCINODE01, AZSHCINODE02). - When I click on either
Server -Azure Arc
object, they both sayThis server is not connected to Azure
- If I go into the Resource Group I specified in the script to create my cluster in, it only has the
Azure Stack HCI
resource. If I click on that resource, it shows both nodes as disconnected. - I tried restarting the host but it did not change anything.
from azurestackhci-evalguide.
Related Issues (20)
- unable to install/upgrade Chocolatey HOT 2
- 2 HCI Servers Never Deployed
- Question: Network ATC support HOT 2
- Unable to pass test on Define Network pages HOT 3
- It doesn't look like the latest screen. HOT 3
- Template Deployment Issue HOT 1
- Issue deploying template DSC Config: A drive with the name 'AD' does not exist HOT 2
- Script missing after phase 1 HOT 2
- DSC in a loop copying vhdx HOT 3
- image not working HOT 1
- WAC Install VM Request HOT 2
- Incorrect Network Controller URL HOT 1
- DSC fails to create AD Forest HOT 1
- Branch 21H2 refere to main scripts HOT 2
- Unable to register cluster to Azure HOT 1
- Error when trying to Enable AKS on AzSHCI (Azure based) Eval HOT 8
- Deployment step 'AzSHCIHost001/ConfigureAzSHCIHost' Failing HOT 1
- Network Controller Rest URI - Invalid URI
- HCI Sandbox script fails HOT 3
- 404 - page not found
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from azurestackhci-evalguide.