Configuration Manager – The server cannot be deleted because it contains the following site system roles – Unable to remove Site Systems from SCCM

Unable to remove Site Systems from SCCM when Multicast Service Point has been enabled

All roles have been removed but Component server still shows


First step is to check what roles may be remaining but not showing in the console by running the powershell command


Get-CMSiteRole -SiteCode “ABC” -SiteSystemServerName “” | Select RoleName


As you can see above the SMS Multicast Service Point is showing but its not possible to remove this role via the console as the Distribution Point role has already been removed.

And of course I cannot remove the site system as not all roles are removed





Run the command in powershell

Remove-CMSiteRole -SiteCode ABC -SiteSystemServerName -RoleName “SMS Multicast Service Point”


Then restart the SMS_SITE_COMPONENET_MANAGER Service


You should now be able to remove the site system after some time once the component server is no longer showing under Servers and Site System Roles

If you still find the component server is still showing after a long wait you can remove the entry in the registry and restart the same service:

HKLM\Software\Microsoft\SMS\Components\SMS_SITE_COMPONENT_MANAGER\Component Servers\SERVERNAME


Configuration Manager Health Check Script

With the recent events (wannacry) in the last few months making sure your environment has a collection of healthy clients including the latest Windows Update Agent is crucial to surviving the threats being unleashed in the modern world. Although you may be able to produce compliance reports showing good figures >96% ( lets get real that almost impossible ) what about the clients that are not showing in your compliance report that should be present. Are you reporting against the unknown? How are you tackling those clients falling into the category?

Here is some help:

Thanks to Anders Roland there is a health script available to help take care of those pesky clients you don’t have the time to take care of yourself, or maybe have been queuing that task up for later, now you can once and for all (99.9%) of the time – nothing is ever perfect right……


Please follow Anders instructions on the implementation guide – 


I strongly recommend following the Group Policy guide found here also


Powershell Script with Arguments as a Scheduled Task










Windows 10 1511 & SCCM CB WSUS Error – 0x80240fff

### Please review the fix – ####


I recently encountered an error on all Windows 10 version 1511 scanning against the SCCM CB lab environment for updates.


The error messages in WUAhandler.log on a Windows 10 version 1511

“OnSearchComplete – Failed to end search job. Error = 0x80240fff”

“Scan failed with error = 0x80240fff”

The Windowsupdate.log provides more information,  for 1511 you’ll need to run the PowerShell command Get-WindowsUpdatelog to generate a readable log file to get more valuable information



Opening the log it shows some error messages:

Two Swap OSUpgrades are found, Update1 = {7F016D4C-C9A6-4699-A7DA-3D86EF81843F}.201, Update2 = {83695761-2AAC-4890-B68E-94B01BAC720C}
FilterInappropriateOSUpgrade failed, hr=80240FFF
Exit code = 0x80240FFF

Now I need to identify the update ID’s shown in the error log and translate into English

Fire up SQL Management Studio on you top level site and run the following SQL query populating the update ID’s


Make sure you change the DB name to your environment

FROM [CM_LAB].[dbo].[v_UpdateInfo]

and replace the CI_UniqueID = ‘7F016D4C-C9A6-4699-A7DA-3D86EF81843F‘  value


The results are shown below, look for the title…

Now I know two updates could be the problem, considering 1607 has been available for a while and the problem only started with 1703 lets focus on that particular update

Feature update to Windows 10 Enterprise, version 1703, en-us

The following are changes made in a Lab environment, for Production Systems it is best to log a MS Support ticket.


Fire up the WSUS console and select the filter shown below


Search for the update title returned in the SQL query and choose decline

Once declined the problem machine should complete a WSUS scan

If you’re worried about declining updates from the WSUS console, you can always set them back to not approved. Once a full sync occurs with SCCM SUP (Top Level) the updates will show green again for deployment.


For returning the updates declined back to normal, locate the declined updates in the WSUS console


Right click the update and select approve

Then select not approved

And OK


This will reverse the changes made, next thing is to have the update show green in SCCM. This is the tricky part, because a full sync of WSUS is required from the top level site. Just setting a custom schedule wont achieve a full sync, you will need to change a setting for this to work.

Navigate to Administration > Site Configuration > Sites and select your top level site (the site that syncs with Microsoft) in my case its the Primary

Choose Configure Site Components > Software Update Point

I changed the setting Do not expire updates and bumped up the time limit to 4 months, I need to do this for a full sync to occur ( You can change this back once the full sync completes).


Now select the sync schedule tab and choose Custom schedule

Set this 5 minutes into the future

Click ok and open the wsyncmgr.log on the top level site server, you should start to see the updates resync back into the DB. This may take a few hours.

SCCM Console – Before




Best advice:

Log a support case with MS.