We will making a change to our Reporting Services deployment next month. We will be moving from our SQL 2000 server to a new SQL 2005 server. In addition, we will moving from a Local Catalog Deployment to a Remote Catalog Deployment. My question is this: Is there a way I can prevent my team from having to manually redeploy our reports in the new system? They have not been diligent about saving the Visual Studio solution or project files, so they will have to pull the most up-to-date RDL's off the server and deploy them on the new server one by one. I suppose I can install SQL 2000 on the new server first, then move the Reporting Services databases to the new server, then upgrade the server to 2005, but installing 2000 and upgrading to 2005 does not sound like a best practice. I would prefer a clean install of 2005. Does anyone know if I can move the deployed reports from one server to another?