This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(160, 4%, 25%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EPG%3C/text%3E%3C/svg%3E)
Please guide on step-by-step SCCM/MECM current branch setup approaches with SQL AOAG, because we are trying to publish new SCCM/MECM primary sites into current hierarchy.
We are referring sites but won't helpful for new installations.
https://learn.microsoft.com/en-us/mem/configmgr/core/servers/deploy/configure/configure-aoag
Thank you for posting in Microsoft Q&A forum.
This is mentioned in the article:
When installing a new site, after you have created and configured the availability group, direct setup to use the FQDN of the availability group listener. If you used a custom port and named instance, leave the instance name empty in the setup wizard and use the format FQDN of listener, port number. For example, use listener.contoso.com, 1445 for a named instance that doesn't use the default port of 1433.
If the answer is the right solution, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Add comment".
It means, during primary site installation we can use SQL AOAG listener name instead of individual node... In our case using listener name but setup is failing continually. Few sources have suggested to go ahead with one node then later on add into availability group.
You mean that, we can use SQL Linster name during installation window only wherein database information need to pass on.
Actually, we are following the same steps however getting multiple failure during primary site installation (database failover sync is problem at end).
So few sources are stating that, use stand alone SQL node at the time of installtion and once installtion sucseeded then add that database into avaiability groups.
Below URL not helping for new installation setup. It seems to be pointed toward exiting sccm setup.
https://learn.microsoft.com/en-us/mem/configmgr/core/servers/deploy/configure/configure-aoag
So few sources are stating that, use stand alone SQL node at the time of installtion and once installtion sucseeded then add that database into avaiability groups.
This should be the right process.