Select the product you need help with
- Internet Explorer
- Windows Phone
- More products
Reinstall of a System Center Configuration Manager 2007 secondary site fails when attempted via the primary site console
Article ID: 2469993 - View products that this article applies to.
You issue an instruction to uninstall a System Center Configuration Manager 2007 secondary site from the primary site console. After doing so you notice on the secondary site server that the uninstall process completed properly but when you then try to reinstall the secondary site on the same server using the primary site's console it gets stuck showing install pending on the primary site console. On the secondary site in the file SMS_BootStrap.ini, you will also notice that it mentions the purpose as DEINSTALL.
After the secondary site gets uninstalled, it should ideally send a notification back to its primary site informing it that the deinstallation was successful. If for any reason this notification does not reach the primary site, it will not know about the deinstallation being completed. When this happens, when we then try to install the secondary site on the same server again it will first try to uninstall it. This is why the instruction sent to the server in the SMS_BootStrap.ini file is DEINSTALL.
To resolve this situation, browse to the hman.box on the primary site server. You will find a file there by the name of delsite.lkp. This file contains entries for each of the secondary sites that are set for deinstallation. Open this file in notepad and depending on the scenario, you may want to remove just the entry or delete the file itself (as this contains the deinstall instructions for all secondary sites which were initiated from this primary site).
If the site we're trying to install has the site code N01, you would remove the entry for only N01 and the rest of the file remains the same. So for this example, after removing the N01 entry, the information contained in this file would be:
The hierarchy manager is the component which handles all hierarchy changes including install and uninstall of secondary sites assuming it is initiated from the primary site. In the case above, we will remain stuck in the deinstall loop because when the setup tries to uninstall the secondary site on the destination server it will fail as there are no secondary site components currently installed there. In cases of actual failures, this will work and is the actual purpose of this process.
(http://go.microsoft.com/fwlink/?LinkId=151500)for other considerations.