yeah, some script help to migration password.
It does migrate the password under normal circumstances. I know having done MS Dynamics GP disaster recovery tests that it doesn't work. But on all the rest it was just fine.
the migration of MSDB already do this, why recreate it ?
The name change from Server1 to Server2 will force you to touch every single job to maybe get them to work again. And that isn't guaranteed.
so in your steps, still don;t worry about the resource DB and simply ignore it, right?
The resource DB is for use of the sqlservr.exe only. You never touch it directly. So it is not for anyone to touch at all.
Try to look here:
http://www.reddit.com/r/microsoft/comments/2bhntz/how_to_open_corrupted_mdf_file/
Submit an article or tip