SOLVED During MECM 2002 I have choose Standalone Primary Site but once installation finish it converted to Central Site

[Rajneeshkaura]

Dear All,

Yesterday I did the Installation for SCCM 2002 with a Primary standalone site in one of my customer environment with SQL cluster it went well, but once the Installation finish I have verified the Site settings & found that in place of the Primary site the site changes to the central site and then I have verified the screenshot & the video which I took during Installation I correctly choose primary site server only with MP & DP.

But there is one issue in the customer environment they already have one 1510 sccm server in the same domain environment as a stand-alone primary.

Now my concern is as per my knowledge I cannot degrade central to primary and can I do something with their current primary and to outcome this what is the best approach.

 

[Youssef Saad]

Hi @Rajneeshkaura,

I've never seen this behavior about switching from the standalone to CAS, but I have one question to be clarified.

Why your customer want to install another ConfigMgr? If it is just to get the latest version, you can upgrade directly using the 2002 baseline media.

 

[Rajneeshkaura]

Hi Youssef,
Actually, my customer wants to wipe out the old server because of the configuration for the Base OS also that server is into standalone same server DB not in the cluster.
Also, some more changes which they need to be expected in the latest see the attached screenshot for the installation which I have taken during setup.

Hope I am able to clarify your point.

 

[Youssef Saad]

The setting in the screenshot is correct.
If you have not yet done any configuration on the new ConfigMgr infra, uninstall the CAS and delete the CMDB, then install a new standalone PS, I think it's the only way to start clean.

Btw, you can follow my guide if needed:

• SCCM Installation Guide - Step by step

 

[Rajneeshkaura]

Sure Saad thanks, I am thinking this is my last option only let me follow your guide and will see if there is no issue by tomorrow accordingly will update you.

 

[Youssef Saad]

Perfect Rajneesh, let us know for the result.

 

[Rohit]

@Youssef Saad if we uninstall the failed sccm setup. How can we clean the registry keys on primary server as well as on SQL which is in cluster ? Before start to re-install.

 

[Rohit]

My setup got failed and I uninstalled the failed setup. Then I tried to reinstall but it showing an error that "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"

So I deleted some registry entries and tried to reinstall but still same error is coming.

 

[Prajwal Desai]

My setup got failed and I uninstalled the failed setup . Then I tried to reinstall but it showing error that "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"

So I delete some registry entries and tried to reinstall but still same error is coming.

Why are you not using a dedicated SQL Server instance for Configuration Manager ?.

 

[Rohit]

Why are you not using a dedicated SQL Server instance for Configuration Manager ?.

Hello Prajwal,

Actually, the client wants to use the existing instance.

 

[Youssef Saad]

Try to connect into your existing instance using SSMS and check if there is any CMDB, delete all and try again.
As said by @Prajwal Desai, I would suggest to you to create a dedicated instance for ConfigMgr to avoid any issue.

 

[Rohit]

Try to connect into your existing instance using SSMS and check if there is any CMDB, delete all and try again.
As said by @Prajwal Desai, I would suggest to you to create a dedicated instance for ConfigMgr to avoid any issue.

Hello,

My issue got resolved, I deleted all leftover registry on the MECM server. Now the error has gone.
Thanks, @Prajwal Desai @Youssef Saad

 

[Youssef Saad]

Glad to hear that the installation works fine. You're welcome.

 

[hafizgab]

Hello,

My issue got resolved, I deleted all leftover registry on the MECM server. Now the error has gone.
Thanks, @Prajwal Desai @Youssef Saad

Hi Rohit, Mind sharing which registry you have deleted ?
Im having similar issue now. We had MECM installed but apparently, we had to uninstall and reinstall and prereq come out with this error

 

[Geraldo Viana]

Hello Rohit, I'm having the same issue with SCCM. Could you share what register you need to delete to solve the problem?
Tks