I have a SCCM server acting as child primary as well as parent for secondary site. HDDs have gone bad on drive where SCCM was installed. So we need to install SCCM again on that server after replacing hard disks. Note thjat OS is working fine and we do ot need to reinstall OS. Please let me know steps to follow to : 1. clean SCCM data so that all refernce to that server is removed. 2. Install SCCM again.Divya

Just reinstall SCCM in the same path, same site code then restore from SCCM backup. John Marcum | http://myitforum.com/cs2/blogs/jmarcum/|

you do not need to reinstall the OS. As John is saying reinstall ConfigMgr. in the same drive/folder and with the same SP level. When ou do the restore you should be able o use the parent site as a reference site.Kent Agerlund | My blogs: http://blog.coretech.dk/author/kea/ and http://scug.dk/ | Twitter @Agerlund | Linkedin: /kentagerlund

I do not have SCCM backup. Please let me know steps to 1. clean SCCM data so that all refernce to that server is removed. 2. Install SCCM again. Divya

Install all over againg with a new site code and site name. Join the site server to the existing hierarchy. Once the site is up and running, configure the site maintenance backup task. Delete all entries in the system management container that has a reference to the old site.Kent Agerlund | My blogs: http://blog.coretech.dk/author/kea/ and http://scug.dk/ | Twitter @Agerlund | Linkedin: /kentagerlund

Thanks Kent. But we need to do it with same server name , site code and site Name. DO i need to do any cleanup on Central and child site of this site before installing SCCM? Also, do i need to reinstall its secondary site? Divya

It is a best practice not to use the same site code. You will face multiple issues., and trust me you don't want to go there. Secondary Site have to be reinstalled as well.Follow me through my blog and Twitter!

I agree it's not best practice nor is it supported to re-use site codes. It's best if you make site codes totally random. Nobody will ever see the secondary site code except for the SCCM admin. Having said all of that. I was forced by management to reuse them where I work ONLY on secondary sites. I rebuilt over 100 seconadry site servers last year on new hardware using the document in my blog and didn't have a single issue. Site codes are a bigger deal on primary sites. In that case you CAN NOT reuse them because the site code is appended to all package, advertisement, etc. This would be a major problem because they could end up being duplicated from the old environment to the new one which would wreak havoc on your clients. In other words in your scenario where you want to replace a primary they only way to reuse that site code is to restore the primary site from the SCCM backup created on the server before it died. John Marcum | http://myitforum.com/cs2/blogs/jmarcum/|