Move/ change the location of SMS Provider

The SMS Provider is a component of Configuration Manager 2007 primary sites and is used by Configuration Manager consoles to access site database information from the SQL Server hosting the site database.

The SMS Provider is a dynamic-link library file (smsprov.dll) and is installed or moved by running Configuration Manager 2007 Setup. You can install the SMS Provider on the primary site server computer, the computer hosting the site database server, or another computer not hosting the primary site or site database. A server class operating system is required to install the SMS Provider on a computer other than the site server or site database server computers.

Important
Installing the SMS Provider on a virtual SQL Server cluster instance is not supported. You can move the SMS Provider after setup has completed to a different server computer system by starting Configuration Manager Setup from the Start menu (if the SMS Provider is installed on the primary site server) or from the Configuration Manager installation media.

To move the SMS Provider using the Start menu

1. Close any open Configuration Manager console connections to the site server.
2. On the primary site server computer, click Start, click All Programs, click Microsoft System Center, click Configuration Manager 2007, and click ConfigMgr Setup, or navigate to the .\bin\i386 directory of the Configuration Manager 2007 installation media and double-click Setup.exe.
3. Click Next on the Configuration Manager Setup Wizard Welcome page.
4. Click Perform site maintenance or reset this site on the Configuration Manager Setup Wizard Setup Options page.
5. Select Modify SMS Provider configuration on the Configuration Manager Setup Wizard Site Maintenance page.
6. Enter the appropriate installation location for the SMS Provider on the Configuration Manager Setup Wizard SMS Provider Settings Modification page.
7. Configuration Manager Setup performs the SMS Provider reinstallation process.

Software Updates Detection State Unknown

If you are seeing a number of clients at a site that is not local to the SUP returning "Detection State Unknown" open up the scanagent.log on one of those clients and see if there's and error 0x80072efd. In the log you should also see which WSUS server the client is attempting to contact and on what port number. If you installed WSUS in the manner described in the docs this should be port 8530 and 8531. Try to telnet from the client to the WSUS server using the address and port number listed. If you do not get a reply have your network team check the firewall settings to make sure that the client is allowed to connect to the WSUS over the listed port.

HTTP 500 Error at Secondary Site Management Point

Most commonly when I have seen HTTP 500 errors on a management point it’s been a SQL permissions issue. Today I ran across another problem that resulted in HTTP 500 errors when testing a management point on a child secondary site. in an effort to resolve the issue I removed the MP using the console on the central site then I noticed that the change was never reflected at the child primary to which to secondary site reports. I opened the sitectrl.ct0 file at the secondary site and I saw there was a delta change reflecting the removal of the MP however that change was not being sent up to the parent site for some reason. To test I made a copy of the sitectrl.ct0, renamed it to sitectrl.ct2 and copied it to the parent sites hman box. The hman.log showed that the site control file serial number was wrong and the file was rejected.

Editing the site control file manually is very unsupported. This is where you should really call CSS.

Of course I figured it was broken already so I may as well take a chance on it before calling support. I took note of the expected serial number version in the HMAN.log at the primary site. I then stopped the sms executive and site component manager services at the secondary site. Open the site control file in notepad, changed the serial number to the number expected by the primary site and saved the file. Next copy the file and rename the extension to ct2. Copy the renamed file to the hman inbox at the primary site and watch the hman.log. You should see the file process successfully this time.

Wait a few minutes then reinstall the management point from the console at the central site. After you see it’s been installed successfully by viewing the mpsetup.log test again using MPList and MPCert.

Cheers!!!!!!!