Greetings, The initial scenario is the following: SCCM 2007 SP2 R3.1 Primary Site. 1 server (Win2008 R2 SP1)1 Secondary Site. 1 sever (Win2003 R2 SP2) Five days ago I have removed the secondary site using Add/Remove Programs in the Secondary Site server. I have removed using this article: http://technet.microsoft.com/en-us/library/bb632423.aspx The objects in AD (System Management) was removed successfully. The secondary site was removed from the SCCM console. The problem is in sender.log I have the following: Cannot connect to server Secondary_Server at remote site Secondary_Site_Code, won't try send requests going to site Secondary_Site_Code for an hour or until there are no active send requests. SMS_LAN_SENDER 24/08/2012 10:08:08 5036 (0x13AC) Could not establish connection. SMS_LAN_SENDER 24/08/2012 10:08:08 5036 (0x13AC) Attempt to connect failed. SMS_LAN_SENDER 24/08/2012 10:08:08 5036 (0x13AC) Restart time = 24/08/2012 10:13:08 SA Pacific Standard Time SMS_LAN_SENDER 24/08/2012 10:08:08 5036 (0x13AC) There is no existing connection, Win32 error = 67 SMS_LAN_SENDER 24/08/2012 10:08:08 1168 (0x0490) Error during connection to \\Secondary_Server\SMS_SITE (67). SMS_LAN_SENDER 24/08/2012 10:08:08 1168 (0x0490) Error is considered fatal. SMS_LAN_SENDER 24/08/2012 10:08:08 1168 (0x0490) I need the procedure to completely and successfully remove the secondary site remainders. Thanks in advance!

Sounds like you've got a few pending jobs over that were queued up prior to turning your old secondary site into a smoking hole. Try this. Although it doesn't ALWAYS work, there aren't (AFAIK) any negative effects. Open an elevated command prompt. Head to your ConfigMgr install folder. Go to bin\i386\00000409Run "preinst /deljob <oldsitecode>".If any pending jobs were deleted, it'll tell you how many. Or tell you "zero pending jobs deleted". If you continue to see activity in the sender.log, here's a method for doing some additional cleaning up. http://nickedtoday.wordpress.com/2011/01/22/deleted-sccm-secondary-site-with-preinst-exe-but-i-still-see-the-site-in-the-primary%C2%B4s-sender-log/ Although its not a supported method since it involved directly editing the database (without having PSS helping out).

Hi, When Configuration Manager 2007 sites are deleted, the deleted site information is only deleted from the deleted site's direct parent site. Site deletion information is not propagated up the hierarchy to grandparent sites. In order to delete the site from the site database at sites above the deleted site's direct parent site, the hierarchy maintenance tool (Preinst.exe) must be run on every primary site above the deleted site's parent primary site using the command Preinst /delsite. For more information about the hierarchy maintenance tool, see Hierarchy Maintenance Tool (Preinst.exe). Refer to: How to Remove a Secondary Site Using the Configuration Manager Console You may follow steps in the KB article: How to remove and rebuild a SMS 2003 secondary site to clean up the remaining SCCM objects. Note: Although the steps listed in KB 828370 are for SMS 2003, they are also applicable for SCCM. Some registry keys mentioned in KB 828370 might not exist on SCCM. Just ignore them during the clean up. Regards, Sabrina

Thank you ChrisMullins. Thank you Sabrina Shen.

You are welcome.