Deleting Orphaned Distribution Points From SCCM Packages

1. Backup the database.

2. Find the entries for the DP package share:

Select * from pkgservers where NALpath like ‘%\<server>%’
Select * from pkgstatus where pkgserver like ‘%\<server>%’
Select * from contentdpmap where serverpath like ‘%\<server>%’
Select * from DPinfo where servername like ‘%<server>%’

3. Delete any entries from any of the above tables that point to the nonexistent share:
Delete from pkgservers where NALpath like ‘%\<server>%’
Delete from pkgstatus where pkgserver like ‘%\<server>%’
Delete from contentdpmap where serverpath like ‘%\<server>%’
Delete from DPinfo where servername like ‘%<server>%’

Keep in mind – This metod is NOT supported by Microsoft

cannot remove or reinstall site server system

error:

SMS Site Component Manager failed to deinstall all SMS server components from site system “\servername“.

SMS Site Component Manager failed to reinstall this component on this site system.

If logging is enabled for the SMS_SITE_COMPONENT_MANAGER service, entries similar to the following are found in the SmsLogsSitecomp.Log file:

Starting service SMS_SERVER_BOOTSTRAP_RIVIERA with command-line arguments “RE0 E:SMS /deinstall \LUXORE$SMSbini386smsexecd.exe”…
Execution of “\LUXORE$SMSbini386smsexecd.exe /deinstall /siteserver:RIVIERA” on server LUXOR failed: The file “\LUXORE$SMSbini386smsexecd.exe” does not exist.
Bootstrap operation failed.
Deinstalled service SMS_SERVER_BOOTSTRAP_RIVIERA.
Bootstrap operations aborted.
Deinstallation failed and will be retried in the next polling cycle.Could not start service SMS_SERVER_BOOTSTRAP_LUXOR. The operating system reported error 997: Overlapped I/O operation is in progress.
Bootstrap operation failed.

To work around this issue, follow these steps.
  1. If a recent backup of the SMS directory exists, restore the SMS folder to the CAP. Stop and restart the SMS_SITE_COMPONENT_MANAGER service on the Site Server to force a Site Component Manager update cycle.In some cases the Site Component Manager will still be unable to remove (deinstall) or reinstall the CAP. In this situation, remove the CAP role from the server (if reinstallation is being attempted). The Site Component Manager will attempt to remove the CAP role from the CAP server for 1440 minutes (24 hours), and then it will time out. After the Site Component Manager has timed out, the errors will cease and you can attempt reinstallation can be attempted if you want to. If a 24-hour wait is not feasible, proceed to step 2.
  2. If a 24-hour wait is not feasible, the removal timeout process can be accelerated by modifying an SMS registry key.To accelerate the CAP removal timeout, modify the following registry value:
    HKLMSoftwareMicrosoftSMSComponentsSMS_SITE_COMPONENT_MANAGERComponent ServersSERVERNAMEDeinstallation Start Time

    Change the value of Deinstallation Start Time to 1. Stop and restart the SMS_SITE_COMPONENT_MANAGER service on the Site Server to force a Site Component Manager update cycle. The Site Component Manager log should indicate the deinstallation process has timed out as follows:

Bootstrap operation failed.
Deinstalled service SMS_SERVER_BOOTSTRAP_NETLKWI02.
Bootstrap operations aborted.
Deinstallation failed. Deinstall retry interval of 1440 minutes exceeded.
Component assumed to be deinstalled; deinstallation will not be retried.