One suggestion - which might not completely help your current situation, but will make this drop-dead simple next time this happens (and it will happen again!) is to use CNAMEs:
Using CNAMEs for Flexibility.
To help your current situation, you could create a CNAME for your current architecture. Actually, I might create several CNAMEs. If you ever think you
might scale out - as in separate your SQL DB instance from your SSIS and SSRS onto different boxes, I would create several CNAMEs for those different "services". Map them all to SVR1. Now change all of your apps/connection strings/etc.. to hit those CNAMEs. Step 2 - install SQL 2008 using whatever machine name you wish, in whatever configuration you wish. Then - "service" by "service" you can migrate the work over to the new server just by changing the CNAME alias. Sound good? It worked for us...
