Hi All,

I've a primary site server that connect to remote SQL server, then I install server for secondary site, after finish installing I check at Site System Status at my secondary server, it said for ConfigMgr SQL Server have a status unknownwwhen Show Messages > All, it give me an empty status, where I have to troubleshoot ?

Make sure that your secondary site to SQL server you need to open the  SQL (1433) port

also look the smsdbmon.log file...

I can telnet the SQL port from secondary server. The log you mention only exist at primary server and nothing suspicious. Do I have to add the computer account secondary server to the SQL DB with same permission for primary server ?

I have another environment that have SQL+SCCM primary in same box, I have secondary server too, but at the site system status there is no ConfigMgr SQL server. Is it correct ? So I mean the ConfigMgr SQL Server only exist at the secondary server if we use SQL remotely ?

I can telnet the SQL port from secondary server. The log you mention only exist at primary server and nothing suspicious. Do I have to add the computer account secondary server to the SQL DB with same permission for primary server ?

I have another environment that have SQL+SCCM primary in same box, I have secondary server too, but at the site system status there is no ConfigMgr SQL server. Is it correct ? So I mean the ConfigMgr SQL Server only exist at the secondary server if we use SQL remo

I can telnet the SQL port from secondary server. The log you mention only exist at primary server and nothing suspicious. Do I have to add the computer account secondary server to the SQL DB with same permission for primary server ?

I have another environment that have SQL+SCCM primary in same box, I have secondary server too, but at the site system status there is no ConfigMgr SQL server. Is it correct ? So I mean the ConfigMgr SQL Server only exist at the secondary server if we use SQL remo

Is your secondary in another (truste

Yes, I know this is an old post, but Im trying to clean them up.

Did you solve this problem, if so what was the solution?

Since no one has answer this post, I recommend opening  a support case with CSS as they can work with you to solve this problem.