Nice summary - perhaps I could suggest a follow on article for Embarrassing Hazards Involved in Staged Migration to 2005?

Eg)

Logshipping not working from 2000 to 2005 or vv.

Reporting Services...

ok, what you need to do if you want each one to be a file in its own right is to a) read books online where it talks about BACKUP...

<with>

For what its work my SQLCMD -L is picking up all sorts of things - a lot of which I think are Office Vista installs which seem to use 2k5...

I really have to take exception to that statement.

mind you, you could probably query the active directory to get that.

They can be slow, depends how you query them.

Well, I guess you'll be doing it by hand then...

'That's right - when I know my servers.'

If your servers are broadcasting their details - someone can tell us the technical term I hope!  you can call "sqlcmd.exe -L" ...

Processes do not really block themselves as such.  In Sp4 they made a change so things look like they do ...

usually when I get this kind of error its because I misspelled something...

Inventory of the DBs can be acheived using sp_helpdb.  Use sqlcmd.exe to connect to a list using trusted connections.  Also look at sp_MSForeachdb.  Pipe it out to a textfile.  This...

Do you need to write to these tables?

well, looking at the reference provided in the error:

http://msdn2.microsoft.com/en-us/library/ms151782.aspx

looks like it might help?

I have recently installed 2000 as a named instance on a box with 2005 as default.  Seems to be ok.