Old site server remains in Site Status node after moving secondary site to new server
Morning All,We've recently moved a couple of secondary site serversonto new hardware. Each site was deinstalled from the SCCM console, preinst /deljobs and preint /delsite run to remove all references to the site, then reinstalled on the new server and site configuration reapplied. All worked OK and the sites are functioning normally.My question is regarding the Site Status in the SCCM console. Under both Component Status and Site System Status for the secondary sites, the old site server is still listed together with the new server, so for example under Component Status there are two entries for SMS_DESPOOLER, one for the old server and one for the new. It is the same for all other components for both secondary sites.Should these entries have been removed by preinst before the site was reinstalled? Will they disappear by themselves as aged status messages are scavenged? Is there something I need to do to clean them up?Any suggestions would be much appreciated.Thanks,Pierre
February 8th, 2009 6:16pm

Did you reuse the old site codes?John Marcum, Systems Management Architect - www.TrueSec.com
Free Windows Admin Tool Kit Click here and download it now
February 9th, 2009 9:37am

Hi John,Thanks for the response, sorry for the delay in replying.Yes, we reused the old site codes. I was under the impression at the time that this was the best way to move a secondary site to new hardware. I believed I'd read something to that effect but now I'm not so sure. Everything worked perfectly well, however I was surprised to see that the old servers were still in the console as I thought preinst would ensure that all traces of the old site (including the site server) were removed.The old servers still exist, so could in theory be re-added/re-removed to SCCM if this would help with the cleanup?Pierre
February 10th, 2009 5:19pm

reusing sitre codes is unsupported. I had a feeling from your problem description that this was what happened. I would call PSS and see if they can help. John Marcum, Systems Management Architect - www.TrueSec.com
Free Windows Admin Tool Kit Click here and download it now
February 10th, 2009 7:18pm

Using SCCM 2007 SP2 R3. Built primary site PRI and secondary site SEC. After testing was done, in the primary site's console I deinstalled secondary site SEC and allowed time for primary site to process change (about 2 hours). Also deleted Address for secondary site SEC from the primary site's Site Settings. Deployed new secondary site to a different server, but used the same site code, SEC. Everything seems to be working fine, except for the fact that the previous, decommissioned secondary site server shows up in the Component Status list for the secondary site. The status columns show many error, warning, and informational status message counts, but when I right-click->show messages->all, I get an empty status message viewer. Is there a way to clean this old server completely out of the site database automatically/manually?
March 30th, 2012 3:39am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics