SMS Admin console unable to connect to local sms site

[wolfej]

Hi, I have what seems to be a couple of major problems with my sms site. SMS was previously installed on a Windows 2000 server that also functioned as a domain controller. We needed to uninstall active directory on that server in order to bring it up as a new child domain within another tree. Because of that SMS lost all its necessary user accounts. I uninstalled SMS and reinstalled it with a different three letter site code, hoping that it would recreate everything new and fix any problems in the process.

Well now I really seem to be having two major problems. The first is that SMS Administrator Console only tries to connect to the old incorrect site and gives me a "connection failed" error. I have tried to run the SMS site database connection wizard to connect to the new correct site, but it doesn't allow me to connect to any other site on the local computer. What really irks me is that the SMS site seems to be up and running in spite of it, I just can't connect to it! I can tell that it is running because on login I get messages from the sms service saying that I may be experiencing problems with one or more of the sms elements.

So my first question is how do I get the Administrator Console to connect to the correct SMS site (the one that appears to be running)?

After the reinstallation of SMS, it did not appear to recreate the SMSLogonSvc user account (upon which the NT_Logon_Something_or_other service depends.) So I went ahead and created it myself, but what rights does it require and to what groups must it belong?

I'm really stuck on this one. Any help will be appreciated.

 

[snyderj]

If you uninstalled SMS successfully then reinstalled it with new a new code then the admin console automatically established on the SMS server itself should connect.

What do you mean by "[the connection wizard] doesn't allow me to connect to any other site on the local computer"? You may need to open the sms msc in author mode in order to delete the old entry and save the new one.

Another thing to consider is whether your admin console matches the SP level of the server. SP2, SP3, SP4, SP4HRP and some hotfixes applied to the site server require that the admin console also be updated.

 

[RodTrent]

I had this problem once upon a time and the old SMS server's WMI namespace was still listed in WBEM. Here's what I did to fix it:

http://www.myitforum.com/articles/1/view.asp?id=172

Rod Trent
Microsoft.MVP.SMS
=======================================
Main site:

http://www.myITforum.com

=======================================

 

[wolfej]

Thanks Guys. Rod, I found this article yesterday and it did indeed fix it immediately!

My problem at the moment is that my second domain controller that I want to serve as a distribution and client access point has something wrong with its client installation. In the SMS icon in control panel on the components tab, there is a repair pending for both software distribution and for the software inventory agent. How can I clean this up so it will once again work?

I have tried browsing directly to the smslogon share at:
\\servername\SMSLOGON\x86.bin\00000409\smsman.exe so that I can try uninstalling the client, but it doesn't do anything when I try running it.

Appreciate any help! Thanks. Joel