Hi, We have issues when deleting resources from the SCCM console. Our setup: Windows server 2008 R2, SQL 2008, SCCM SP2 R2 1 central site 3 primary sites 1 secondary connected to one of the primary 15 DPs spread across all primary servers. Boundaries are set so clients report to one the 3 primary servers. No client assigned to central site. In an effort to have better representation of what is live and in SCCM, we want to delete resource from SCCM when removed from the floor. We do so by deleting the resource from the console (right click delete). The actual problem comes from where we delete the resource. If the delete is done on the central site, it gets replicated on primary site in less than 2-3minutes. If the opposite is done, delete from the primary site, it doesn’t replicate to the central site (waiting for 2 days now). In addition, the delete from central will only replicate if the resource was Client=1. Not Client doesn’t replicate on the other server when deleted (for both server). Is this default behavior? We also have SCCM installed in a lab in a similar setup, and the exact same happen. No errors are recorded in the Replication manager on both servers. Thanks for any help.

If the opposite is done, delete from the primary site, it doesn’t replicate to the central site (waiting for 2 days now). That's default. The clients won't be deleted then, but the decomissioned flag will be set to 1. You could create a collection that contains just those clients.Torsten Meringer | http://www.mssccmfaq.de

You have an explanation of the different states here - http://technet.microsoft.com/en-us/library/bb633138.aspxKent Agerlund | My blogs: http://blog.coretech.dk/author/kea/ and http://scug.dk/ | Twitter @Agerlund | Linkedin: /kentagerlund

Thanks Torsten, It is actually the case. But how about not client? Will it do the same or does it as another flag? thanks