Some items to add to the list that I have come accross:
a) SQL Authentication for report server db - on install, it will attempt to connect to the database via the windows account you have logged onto the server with, it uses this to verify if the DB exists and the user account is setup (and do the build if not there). This is typically via builtin\administrators group. Be aware of this if you get the classic windows login error re trusted connections.
b) Anonymous ReportServer report access - as a simple approach, I replicated the /reportserver virtual directory (must copy the properties identically) and enabled anonymous logins - both virtual dirs point to the same binaries of course. I created a /private and /public root folders within reportserver and the anonymous account having /public access only. Be carefully playing with your primary /reportserver virtual dir in relation to /reports (reportmanger), especially IIS security settings and domain/realm properties.
c) Web farms - I had a senario where I wanted two webservers sharing the same reporting services repository but they are NOT in a webfarm. On install to the second server, it "assumes" you do want a webfarm, and are asked for the details. To get around this, I let it create a new reportserver repository, then used rsconfig to point back to the shared repository thereafter.
d) SQL client net utility alias - when asked for the sql server to connect to, I recommend you use sql client net utility and create an alias instread to quickly point RS to another repository (as need be of course)
Author of "SQL Server Backup, Recovery & Troubleshooting"
Author of "SQL Server 2k for the Oracle DBA"