Discovered objects in a child site vs. parent site
If I have a discovered resource in a child site that shows Client=No, and a resource in the parent site by the same name but shows Client=Yes, then is it safe to delete the resource from the Child site? Should I check each one to make sure the ResourceID
is different?
Background: The child site was discovering servers in AD, but the child site should only discover/push to workstations. I've reconfigured AD System Discovery in the child site so these servers are no longer discovered. I don't want
to wait 60 or 90 days whatever it is for the resource to be deleted so I want to delete all the servers, but I don't want the deletes to replicate up to the parent site (for servers).
May 4th, 2010 1:16am
Site replication should bring this child object up to the parent, so there should be two objects in the parent site by the same name, one showing client=yes, the other showing client=no. So you could look for that on the parent, if that is the case
then you can safely delete the client=no object. Otherwise, you should definitely verify the object ID's are different prior to deleting them (I would guess they probably are since they're in two different sites, but no harm in checking).Scott Gill
SCCM Consultant
Free Windows Admin Tool Kit Click here and download it now
May 4th, 2010 2:17am
The resource IDs will be different even if the object was replicated up from the child site. Check the SMSGUID instead.
May 4th, 2010 9:27am
Thanks Scott, and Torsten. The ResourceIDs were different for all of the objects I checked, and the SMS GUID is null in the child site so I went ahead and deleted all the servers from the child.
So does that mean Resource IDs are always different between sites?
And does that mean if the child site discovers a system/installs the client/records the SMS Unique Identifier, when it's replicated to the parent site the Resource ID will always change but the SMS Unique Identifier will never change?
Thanks!
Free Windows Admin Tool Kit Click here and download it now
May 6th, 2010 1:25am
Yes basically. Sorry I should've caught that sooner. The ResourceID is just a key that is generated automatically by the DB (Primary Key) but the SMS Unique Identifier is generated on the client and sent up to the server when the client connects.
The SMS UID is based upon HW specific info so it is genuinely unique (in theory) world wide, while the ResourceID is just a number that is added +1 each time a new resource is added to the SMS database. (AKA it's basically nothing more than a generic
Primary Key in database terms)Scott Gill
SCCM Consultant
May 6th, 2010 7:32am