A common question in forums is how to replace the hardware for secondary site servers. I documented the procedure for our internal use and I decided that the documentation may be useful for others so I am posting it here with a couple words of caution. Some of the steps in my document directly edit the SCCM database. This is totally unsupported, do it at your own risk. If you do it incorrectly you could totally break your site so please make sure you understand what you are doing before you do it. if you don't feel comfortable you can just skip that step, it's very likely skipping that won't hurt anything else in this process because some of the steps in this document are overkill and can safely be skipped. My document assumes there's a central site and a child primary site with secondary sites assigned there. Also you will want to make sure you read my other blog post here http://myitforum.com/cs2/blogs/jmarcum/archive/2010/05/19/146968.aspx and use the files attached to that post to ensure you don't have problems with the preloadpkgonsite.exe tool. I use a bat file to remove certain pck files from SMSPKG before I run the preload tool. That's because OSD packages are not supported when using that tool. Attached to this post are a couple script and files I use in the server replacement process. Before we ship the server on-site I copy the following files to it. SCCM is installed once the server arrives onsite.
SCCM installation media
SCCM Prereqs
R2 install media
KB978021 install
SCCM Toolkit 2
No_sms_on_drive.sms
preloadpkgonsite.exe
xcopy_updated_files.bat
write_preload_bat.ps1
Pstools
Webdav
Clean_files.vbs