What to ask when taking over external servers?

At $WORK, I'm going to be taking over the administration of four servers that currently do stuff for a variety of researchers scattered around the province. There are a number of players here:

• My department, which contains:
  • Me, the guy whose services are being promised, and
  • The researcher who's arranging all this (my local contact)
• The agency that owns them, who I don't think has any techical staff
• The agency that currently hosts and administers the servers

The owning agency has also ponied up for an upgrade to the four servers; I'll be taking delivery some time next week.

I've got some preliminary information -- what the servers do, how the users use the thing, etc -- but I'm preparing a more detailed plan. In the meantime, I've compiled a list of questions for my local contact.

In the middle of that, it occurred to me that this would be a good discussion topic. Have I missed anything? Let me know!

• Will the old servers be moved over, or will the new ones replace them?
• What's the primary means of talking to users? (Mailing list, status page)
• Where's the list of those users? (one of the above, spreadsheet)

• What info do users/owners expect from us? How? (Mailing list, status page; 2 weeks notice of downtime, monthly stats by CPU) - Are any funding decisions influenced by this information?

• Where is the info for the software? - media - license #, what we have licenses for (unlimited use, # cores, etc) - support #, what it covers

• Can I see a demo of the software?

• Do any of the labs have shell access? What do they do with it?

• What exactly is involved in maintenance? Where is this documented?

• What DNS changes will be made? Who makes them?

• Who makes policy/purchase decisions about these servers? How do I contact them?