Configuration Manager requires a dedicated SQL Server instance

In my lab environment I’m doing quite a lot of ConfigMgr testing. Recently, I was doing some testing on System Center Configuration Manager and Endpoint Protection (current branch – version 1511) and I broke the ConfigMgr primary site server and decided to re install the primary site.

In my lab I am using a dedicated SQL 2014 server to host the database and a dedicated server for the ConfigMgr installation. So I uninstalled the site server VM using the uninstall wizard, I deleted the database file in SQL and started a new installation wizard.
During the installation, the prerequisite checker gave me the following error. The error message stated that the SQL instance chosen already has a site database.

Configuration Manager requires a dedicated SQL Server instance to host its site database. You selected a SQL Server instance that hosts the site database for another Configuration Manager site. Select a different SQL Server instance for this new site to use, or resolve the conflict by uninstalling the other site or moving its database to a different SQL Server instance.

To solve this problem, I logged on the SQL Server and started the registry editor, there I found the following registry key with information about the ConfigMgr site:


After removing the registry key and restarting the SQL server I was able to continue the new ConfigMgr installation.

Kind regards,


This Post Has 2 Comments

  1. paul

    I have the same issue, however when I delete SMS it repopulate, almost immediately in the registry….I see an old folder in the server that cannot be deleted as well as there is a process that is using it for some reason

  2. Ben

    This is the answer is the above registry hack does not work :

    Remove the stale entries in master.sys.service_broker_endpoints: DROP ENDPOINT [Endpoint-Name-Like-ConfigMgrEndpoint];

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.