Before I begin, let me say that I'm trying to fix what has already been done by a colleague. I know that things were not done that should have been done, but we're passed that already. I just need to fix what I have.
Scenario: We had an SCCM server connected to an SQL availability group. SQL group had sql1 and sql2 and listener of sql. That worked fine. SQL servers were decommissioned. All databases were backed up and then restored to a new single SQL server. No availability group was created. New SQL server has fqdn of sql listener. Connections for other services work fine. SCCM is not working. Restoring the old SQL servers group is possible but would be extremely difficult and time consuming. I think I'd rather rebuild SCCM than go down that path because of the potential interruption it would cause.
When I rerun the setup and select modify SQL settings it runs through, connects just fine, starts doing operations and then fails at "Failed to create group for distributed view access." From what I can find, I think this is related to it trying to recreate the setup for an availability group (again, this is just my best guess).
Is there any way to force SCCM to know that it's no longer in an availability group? I really don't want to have to rebuild this from the ground up, but I will if that's where this leads to.
Any guidance is greatly appreciated.
Scenario: We had an SCCM server connected to an SQL availability group. SQL group had sql1 and sql2 and listener of sql. That worked fine. SQL servers were decommissioned. All databases were backed up and then restored to a new single SQL server. No availability group was created. New SQL server has fqdn of sql listener. Connections for other services work fine. SCCM is not working. Restoring the old SQL servers group is possible but would be extremely difficult and time consuming. I think I'd rather rebuild SCCM than go down that path because of the potential interruption it would cause.
When I rerun the setup and select modify SQL settings it runs through, connects just fine, starts doing operations and then fails at "Failed to create group for distributed view access." From what I can find, I think this is related to it trying to recreate the setup for an availability group (again, this is just my best guess).
Is there any way to force SCCM to know that it's no longer in an availability group? I really don't want to have to rebuild this from the ground up, but I will if that's where this leads to.
Any guidance is greatly appreciated.
