We have just started getting the following error logged on one of our secondary site servers. All other sites are okay. Systems Management Server cannot update the already existing object SMS-Site-xxx in Active Directory The errors started after rebooting our secondary site server and has been logged every hour since then. No other changes have been made to the environment. AD schema has been extended and the system management container exists in Active Directory with Full Control permission set to this object and all child objects for all our SCCM servers - they have been added seperately rather than through a group membership. This error seems to have appeared from nowhere and we are looking to resolve it asap - would removing this particular secondary server from the ACL against the system management container and then re-adding it be worthwhile or would this create additional problems?

I would delete the existing object within AD and let it get recreated. If it does then it means all your premission are good, if not, then it show there is another issues.http://www.enhansoft.com/

Are you referring to deleting the SMS-Site-xxx object within the System Managemnt container? What would start the recreation of this object and how long would it generally take? Assuming it does not get recreated, what else can we do to resolve the issue?

Yes, I do mean the SMS-Site-XX objects.. and it should be recreated within an hour. However I normally fine it is re-created within a few minutes. If it doesnt get re-created it means that you have a permissions issue or AD issue. Either way, it is not directly a CM07 problem. Removing the data will have little effect on your site other than new PCs will not know where to get assigned to and all client at that site will be considered slow. http://www.enhansoft.com/

Thanks for the reply Garth, I will try your suggestions and let you know the outcome. Our concern was by deleting objects within the systems management container that they would not be recreated and leave the site in an unstable state. If they do not get recreated, are we able to create the SMS-Site-XX object manually?

If the site server cant update the object now, then it means that you cant truly trust the data that exist within it anyways. Aka it could have out of date boundary data, MP data, etc. So. You need to know why you cant update the object. This is the easy way. http://www.enhansoft.com/

Yes that makes sense. I will try deleting the object - can we recreate it manually if SCCM doesn't do it in a timely manner?

No you can't manually recreate it.http://www.enhansoft.com/

Ok, so it's a matter of waiting for SCCM to create it automatically again. I realise that permissions on the system management container and all objects should be granted as Full Control to all primary and secondary SCCM servers and this is indeed the case - we have checked this numerous times and all other site servers can update their SMS-Site-XX objects without any problems. It is just this one secondary server that is unable to (even though the permission are set correctly for the computer$ account). As you said previously, this should not be a problem within SCCM anymore. However, if it does not appear back in the AD container is there something obvious we should check for? As far as we can see, AD permissions and replication are all set and working correctly. Have you seen other situation where the object is not automatically created again? Sorry for all the questions and thanks again for your help so far.