Search the Community
Showing results for tags 'ha'.
Found 2 results
I have inherited an SCCM 2211 environment that was supposed to have been setup in HA, but it was not fully configured (no passive site node). I'm a bit stumped with how the SQL AOG has been configured and the person that built it is no longer around. In the past when setting up HA, I would setup the SQL AOG and point SCCM to the listener node. In the console I would see a single site database sever and it would use the name of the listener as the server name. In the environment I inherited, they setup an AOG, but there are 2 site database server roles in the console and they are both pointing to the 2 AOG replicas rather than the listener. I can't find anything saying this is supported and I don't see how that gets you HA capability, but before I start reconfiguring things I wanted to make sure this is not a supported method for HA with SQL and SCCM? Thanks
SCCM and SQL AG
WAZZIE posted a topic in System Center Configuration Manager (Current Branch)Hi All, I hope you are well, Currently I have an issue I have unsuccessfully been battling with for a few days now. The original plan was to have the sccm db running on a sql high availability always on group setup. 1 x primary server 1 x sup server 1 x dp server 2 x sql servers when I tried to install SCCM initially, on the clustered sql, I was getting issues with listener admin rights / ports Excerpt from sccm install log --------------- CWmiRegistry::GetStr: Failed to get string value MSSQLSERVER Configuration Manager Setup 06/03/2018 16:05:16 92 (0x005C) Failed to retrieve SQL Server instance name[MSSQLSERVER]. Configuration Manager Setup 06/03/2018 16:05:16 92 (0x005C) WARNING: failed to retrieve port number for XXX-SCCM-LST.ncc.local. Configuration Manager Setup 06/03/2018 16:05:16 92 (0x005C) WARNING: failed to retrieve port number for XXX-SCCM-LST.ncc.local. Configuration Manager Setup 06/03/2018 16:05:16 92 (0x005C) ---------------- End of Excerpt XXX-SCCM-LST = sql listener this is a named instance on the sql (SCCM) and the sql port is 1433 /broker 4022 Why is it looking for MSSQLSERVER ? why failing to retrieve port ? So - I recently gave up and installed SCCM on a named server (not the listener) (SERVER-A - which is to be used in the HA cluster) sccm installs and works fine. I have installed the DB on a single box, and SCCM is looking good and functioning / patched up to 1710 + hotfix. OK - So I think I can do SCCM site maintenance, and change the DB location to the SQL Listener. But no same errors in logs again. Any one got any ideas or further experience with sql availability groups and are we missing something simple. Hope to hear back from anyone Regards, WAZZIE