Currently, we are looking to upgrade our SCCM server from a hardware standpoint. Everything is up to date but the server it is currently installed on is old and running slow. We are looking to build a new OS from scratch and then restore it from backup (the SCCMBACKUP folder on our current server) - is this the correct way to do it? We've never done this before. Thanks.

Hi, Yes a backup and Restore can be sued. Another way is to install ConfigMgr. on the new server and assign it as a child site - let it replicate all objects (packages, collections etc), then break the relationship and let the new server become the parent site. This will replicate all data. Once replication is done you can reassign all the clients to the new site (requires that bounaries are configured on the new site server).. Kent Agerlund | http://scug.dk/ | The Danish community for System Center products

To add a little to what Kent said... If you can keep the same computer name and installation paths the backup and restore method will give you the best results. If you want to change either the computer name or the install paths backup and restore is not an option so you must go the other route. John Marcum | http://myitforum.com/cs2/blogs/jmarcum |

Thanks for the info....we are looking to do this next week.....once we restore the backup, will it automatically restore all of the installs back to where they were (D:/PACKAGES) or do I do this manually? Thanks again.

D:\Pacakge is not an SCCM folder so I assume you mean you package source files? If so you need to restore that manually. If you mean SMSPKGD$ you will need to copy the packages to the DP for that to happen. Use the copy packages wizard for that. John Marcum | http://myitforum.com/cs2/blogs/jmarcum |

Here's a list what gets backed up and what not: http://technet.microsoft.com/en-us/library/bb633229.aspx