I am having issues with the SQL DB and SCCM 2007 will not upgrade to sp2. I have been googleing and trying many different things but its just not connectiong to the SQL DB. I am almost at the point that I will just rebuild everything. We have about 300 clients. My question is would it be a good idea to name the new SCCM server as the same name as the old one with the same IP? Since all the clients already point to it. the DB is on SQL2005 server which is having its own issues so I am going to build the new DB using SQL 2008r2. I know I will have to redo a discovery and populate all collections, plus Ill lose my software packages. Any issues with what I am thinking, anything to be in particular to look out for, or just general suggestions. Thanks,

The same server name and IP isn't that big of a deal. Though I would change the nam. The main issue is the Site code. Since this is store in WMI, AD and other places, you really don't want to confuse the clients. So if you want, keep the same computer name and IP but please please change the site code so that the clients assign to the new site and function properly. It will also help you identify clients that didn't move for some reason.http://www.sccm-tools.com http://sms-hints-tricks.blogspot.com

If you've given up on repairing the server, I would create a new one and perform the steps required in a side-by-side migration. It's possible you can have issues with the trusted root key being stored in clients. http://technet.microsoft.com/en-us/library/bb632759.aspxNicholas Jones, MCITP | Core Infrastructure Consultant | Sparkhound | https://www.mcpvirtualbusinesscard.com/VBCServer/nicholas.jones/profile

For 300 clients (or for any number actually) I'd reccoemend you keep SQL on the SCCM server. If you want to backup and restore SCCM I am pretty sure you cannot change the servername. The IP does not matter. If you are doing a side-by-side then I would change the servername. Also if you are doing a backup and restore the install path of SCCM must stay the same. It is supported to change the SQL version during a site server hardware replacement such as this. I have a document on my skydrive that details how to do it. John Marcum | http://myitforum.com/cs2/blogs/jmarcum/|